Investigate Cherry Studio code to identify unused behavior, duplicated state, and unnecessary abstractions. Turn a few well-supported findings into cleanup proposals that document current consumers, removal scope, risks, and observable acceptance criteria.
Use when asked to find or plan Cherry Studio cleanup, simplification, refactoring, dead-code removal, duplicated state removal, unnecessary APIs, speculative generality, or library replacements, especially when the result should become evidence-backed proposed Agent Notes.
Review the instructions the agent will receive before you install.
This skill finds a few strong candidates, not a deletion quota. Diagnosis and proposal work do not authorize implementation.
Read root instructions, relevant architecture/reference docs, and active Agent Notes. Run pnpm change:scope --base <verified-ref> when auditing a branch. When the user requests broad coverage, divide renderer, data systems, IPC, lifecycle services, Agent/runtime, packages/scripts, and test infrastructure into disjoint surveys.
A strong candidate has concrete cost and production evidence:
Search exact symbols, wire names, config keys, paths, dynamic registration, tests, docs, and Agent Notes. A call site proves pressure, not that the API belongs at that boundary. Reject a candidate when it removes supported behavior, violates documented ownership, or merely relocates the same complexity.
Small local improvements may be reported inline. A durable removal or redesign becomes one proposed simplification note through the agent-notes workflow, including current consumers, exact removal, strongest counterargument, observable ACs, risks, and verification owners. Do not create a duplicate note for an existing owner.
Report surveyed areas, evidence-backed candidates, rejected candidates worth preserving, deliberate exclusions, and checks actually run.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Record durable Cherry Studio engineering decisions in Agent Notes. Determine which changes need a note, prepare specifications with verifiable acceptance criteria, and manage approval, implementation, rejection, and replacement while preserving the reasoning behind decisions.
Get answers about Cherry Studio from the installed version’s product information. The skill explains features, settings locations, and shortcuts, provides clickable navigation entries, and helps diagnose connection failures, configuration problems, and runtime errors.
Operate the visible browser pane in a Cherry Studio conversation to navigate pages, click controls, fill forms, capture screenshots, and investigate browser issues. It can work with authenticated websites while checking page state and action outcomes.
Operates native desktop apps through Cherry Studio Computer Use. It reads interface information, types, clicks, and captures windows, using fresh observations to choose actions and verify results within the permissions and capabilities available.
Develop and verify changes in a tracked Cherry Studio Electron instance, a running desktop app. Use real UI behavior, logs, and performance measurements to investigate problems, compare fixes, or test a pull request and report the results.
Run repeatable tests of Cherry Studio’s key workflows with Playwright, which checks application behavior through automated interactions. Collect results on macOS and Windows and produce English reports for release acceptance or development validation.