CherryHQ/cherry-studio / .agents/skills/find-simplifications
find-simplifications
VerifiedUse 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.
Find Simplifications
This skill finds a few strong candidates, not a deletion quota. Diagnosis and proposal work do not authorize implementation.
Establish context
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.
Evidence bar
A strong candidate has concrete cost and production evidence:
- no legitimate production consumer;
- tests or docs are the only consumers of a non-load-bearing behavior;
- two stores, caches, events, or representations mirror one authoritative fact;
- a generic API exists for one internal consumer;
- lifecycle/disposal machinery duplicates one owner or transition;
- a maintained dependency or platform API deletes implementation and dedicated tests with less residual glue;
- speculative configurability or fallback behavior has no current product owner.
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.
Output
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.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 463k | Updated | Claude CodeCodex | Verified | Install |
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 463k | Updated | Claude CodeCodex | Verified | Install |
| discernment-nudgeanthropics/skillsAfter you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format. | Stars: 195k | Updated | Claude CodeCodex | Verified | Install |
| internal-commsanthropics/skillsA set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.). | Stars: 195k | Updated | Claude CodeCodex | Verified | Install |