Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →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.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-07 | ✗→✓ | ▲ Improved | -53% | 0% |
| case-11 | ✗→✓ | ▲ Improved | -8% | 0% |
| case-12 | ✗→✓ | ▲ Improved | -36% | 0% |
| case-13 | ✗→✓ | ▲ Improved | -64% | 0% |
| case-15 | ✗→✓ | ▲ Improved | 30% | 0% |
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.
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.
main-process logs, persisted state, or performance metrics.
window.
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.
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.
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 measured skills in the registry, with their headline benchmark lift.