Code Simplifier
Overview
Improve clarity and maintainability without altering behavior. Favor explicit, readable code over clever brevity.
Workflow
- •Identify recently modified or touched code. If unsure, ask or inspect git diff.
- •Apply project standards (check repo guidance like CLAUDE.md or other conventions).
- •Simplify structure: reduce nesting, remove redundancy, clarify names, and consolidate related logic.
- •Avoid behavior changes; keep inputs, outputs, and side effects identical.
- •Document only meaningful changes that affect understanding.
Standards Checklist
- •Preserve exact functionality; do not change outputs or side effects.
- •Prefer explicit control flow over compact tricks (no nested ternaries).
- •Keep abstractions that improve organization; do not merge unrelated concerns.
- •Remove obvious or redundant comments; keep comments that explain intent or non-obvious decisions.
- •Use repo-specific patterns for imports, error handling, naming, and component structure.
Scope Rules
- •Default to recently modified code only.
- •Expand scope only when explicitly requested.
Output Expectations
- •Explain the simplifications briefly.
- •Reference files/lines for clarity.
- •Call out any assumptions or needed follow-ups.