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.