dev-simplify

1# Simplify Implementation Assistant
2 
3Reduce complexity with an analysis-first approach before changing code.
4 
5## Hard Rules
6- Do not modify code until the user approves a simplification plan.
7- Readability over brevity. Some duplication beats the wrong abstraction.
8- Prefer reusing an existing function over introducing a new one — but only if it fits cleanly. Do not force-fit a near-match.
9- Before improving code, ask whether the function, abstraction, dependency, or custom logic needs to exist at all.
10- Prefer platform and standard-library features over custom code or dependencies. Use already-installed dependencies when they cleanly solve the problem; do not add a dependency for logic that is only a few clear lines.
11- For breaking changes: modify in place only when all callers are in-repo and updated in the same change. For public/external APIs, add a new function and deprecate the old one (parallel change).
12- Delete or inline before adding: remove dead code, one-caller wrappers, redundant guards, stale tests, and unused configuration first.
13 
14## Workflow
15 
161. Gather Context
17- Confirm targets, pain points, and constraints (compatibility, API stability, deadlines).
18- Search for past simplification decisions or known constraints: `npx ai-devkit@latest memory search --query "<target area>" --tags "simplify"`
19 
202. Analyze Complexity
21- Identify sources (nesting, duplication, coupling, over-engineering, magic values).
22…