cherry-electron-dev
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.
npx skills add CherryHQ/cherry-studio --skill cherry-electron-dev --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Cherry 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](references/electron-instance.md) 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 1. State the requested behavior and the evidence that will prove it. 2. Read the relevant code and nearby README files. 3. Verify and reuse the tracked instance through the runtime reference. 4. Reproduce or inspect the current behavior before editing when practical. 5. Capture the smallest useful evidence: UI state, DOM, console/network output, main-process logs, persisted state, or performance metrics. 6. Trace the responsible code path and make only the requested change. 7. Keep Electron running. Use HMR for renderer changes and verify in the same window. 8. Repeat the same scenario and c
- Required runtime workflow
- Development loop
- Performance and DevTools
- Handoff
What does the cherry-electron-dev skill do?
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.
How do I install it?
Run `npx skills add CherryHQ/cherry-studio --skill cherry-electron-dev --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From CherryHQ/cherry-studio, a repository with 49,400 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.