Cherry Electron Dev Agent Skill
Develop, fix, and profile Cherry Studio in a tracked Electron instance. Use for everyday implementation, UI and interaction work, bug fixing, runtime debugging, DevTools inspection, lag or jank investigation, CPU and memory monitoring, leak checks, and startup-performance analysis; reuse a verified workspace instance across instructions and launch or replace one only when required.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/CherryHQ/cherry-studio --skill cherry-electron-devThe instruction itself
5 sections, as written by the authorCherry Studio Development
Use this skill for ongoing work in the current checkout. Do not use it to check
out or report on PRs; use cherry-pr-test for that workflow.
Required runtime workflow
Before reading or controlling Electron UI, read
Electron Instance Management and use its
persistent policy.
That reference is the only authority for instance discovery, instance.json,
CDP target selection, launching, replacement, shutdown, and troubleshooting.
Do not reproduce those procedures here or substitute generic Electron app
control.
Development loop
- State the requested behavior and the evidence that will prove it.
- Read the relevant code and nearby README files.
- Verify and reuse the tracked instance through the runtime reference.
- Reproduce or inspect the current behavior before editing when practical.
- Capture the smallest useful evidence: UI state, DOM, console/network output,
main-process logs, persisted state, or performance metrics.
- Trace the responsible code path and make only the requested change.
- Keep Electron running. Use HMR for renderer changes and verify in the same
window.
- Repeat the same scenario and compare before/after evidence.
Inspect the real window at the relevant size and theme for UI work. Check both
renderer and main-process evidence for renderer failures.
Restart only for a non-reloadable layer, crash, unreliable runtime state, or
startup profiling. Use the reference's exact-instance replacement procedure,
refresh instance.json, and keep the replacement running.
Run the narrowest relevant validation and follow current user and repository
instructions for lint, formatting, and tests.
Performance and DevTools
For lag, jank, high CPU, memory growth, leaks, slow startup, or explicit
DevTools use, read
Performance Debugging.
Store temporary logs, screenshots, and profiles under
.context/cherry-electron-dev/. Compare a quiet baseline with the same bounded
scenario before and after a fix. Detach profiling sessions afterward; do not
close the CDP browser, page, or Electron process.
Handoff
Leave reused user-owned and healthy agent-launched instances running after the
instruction. Stop one only when the user asks, a required restart is part of
the task, or the instance is unhealthy and blocks progress.
Report the verified PID, whether it remains running, CDP port, tracking file,
evidence paths, reproduction, and verification.
Other skills for the same job
different authors, same section of the catalogue
Comprehensive healthcare AI toolkit for developing, testing, and deploying machine learning models with clinical data. This skill should be used when working with electronic health records (EHR), clinical prediction tasks (mortality, readmission, drug recommendation), medical coding systems (ICD, NDC, ATC), physiological signals (EEG, ECG), healthcare datasets (MIMIC-III/IV, eICU, OMOP), or implementing deep learning models for healthcare applications (RETAIN, SafeDrug, Transformer, GNN).
Comprehensive healthcare AI toolkit for developing, testing, and deploying machine learning models with clinical data. This skill should be used when working with electronic health records (EHR), clinical prediction tasks (mortality, readmission, drug recommendation), medical coding systems (ICD, NDC, ATC), physiological signals (EEG, ECG), healthcare datasets (MIMIC-III/IV, eICU, OMOP), or implementing deep learning models for healthcare applications (RETAIN, SafeDrug, Transformer, GNN).
Expert performance engineer specializing in modern observability, application optimization, and scalable system performance. Masters OpenTelemetry, distributed tracing, load testing, multi-tier caching, Core Web Vitals, and performance monitoring. Handles end-to-end optimization, real user monitoring, and scalability patterns. Use PROACTIVELY for performance optimization, observability, or scalability challenges.
Master AI-powered test automation with modern frameworks, self-healing tests, and comprehensive quality engineering. Build scalable testing strategies with advanced CI/CD integration. Use PROACTIVELY for testing automation or quality assurance.
Internet Court adapter for GenLayer Intelligent Contract supervision. Use to specify agent-performance rubrics, evidence schemas, decision outputs, and ERC-7710 connector expectations, while delegating actual GenLayer contract writing, linting, testing, deployment, and CLI interaction to the official GenLayer skills at https://skills.genlayer.com/.
> Suggests using Microsoft Testing Platform (MTP) hot reload to iterate fixes on failing tests without rebuilding. Use when user says "hot reload tests", "iterate on test fix", "run tests without rebuilding", "speed up test loop", "fix test faster", or needs to set up MTP hot reload to rapidly iterate on test failures. Covers setup (NuGet package, environment variable, launchSettings.json) and the iterative workflow for fixing tests. normally with dotnet test (use run-tests), applying test filters, producing TRX reports, CI/CD pipeline configuration, or Visual Studio Test Explorer hot reload (which is a different feature).
Build production Apache Airflow DAGs with best practices for operators, sensors, testing, and deployment. Use when creating data pipelines, orchestrating workflows, or scheduling batch jobs.
Build production-grade Azure Cosmos DB NoSQL services following clean code, security best practices, and TDD principles.
How to use it
Take cherryhq/cherry-electron-dev from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.