simplify-implementationlisted

# Simplify Implementation Assistant Reduce complexity with an analysis-first approach before changing code. ## Hard Rules - Do not modify code until the user approves a simplification plan. - Readability over brevity. Some duplication beats the wrong abstraction. - Prefer reusing an existing function over introducing a new one — but only if it fits cleanly. Do not force-fit a near-match. - 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). ## Workflow 1. Gather Context - Confirm targets, pain points, and constraints (compatibility, API stability, deadlines). - Search for past simplification decisions or known constraints: `npx ai-devkit@latest memory search --query "<target area>" --tags "simplify"` 2. Analyze Complexity - Identify sources (nesting, duplication, coupling, over-engineering, magic values). - Assess impact (LOC, dependencies, cognitive load, scalability blockers). 3. Apply Readability Principles - Apply the [readability guide](references/readability-guide.md) and its "Reading Test". 4. Propose Simplifications For each issue, apply a pattern: - **Extract**: Long functions → smaller, focused functions. - **Consolidate**: Duplicate code → shared utilities. - **Flatten**: Deep nesting → early returns, guard clauses. - **Decouple**: Tight coupling → dependency injection, interfaces. - **Remove**: Dead code, unused featu