loom-code-simplificationlisted

# loom-code-simplification Code simplification is a refactoring playbook for clearer code with preserved behavior. It grounds the current behavior, scopes the simplification, changes incrementally, and records evidence that behavior did not change. ## Loom Routing Common routes use these Loom skills for durable records or follow-up workflow: `loom-tickets`, `loom-evidence`, `loom-audit`, `loom-research`, `loom-specs`, `loom-retrospective`, and `loom-knowledge`. Follow any named Loom skill fully. This playbook adds workflow pressure; it does not shorten target-skill requirements. ## Use This Playbook When Use this playbook when: - implementation is correct but unnecessarily complex - review flags readability, duplication, dead code, or abstraction debt - a refactor should preserve behavior exactly - code has deep nesting, long functions, misleading names, unnecessary wrappers, or one-use abstractions - simplification needs evidence before closure Skip it when behavior is still wrong; debug or implement first. ## Route Use this route: ```text understand -> bound -> simplify -> verify -> record -> review ``` ## Understand Before changing code, identify: - responsibility of the code - callers and callees - behavior, edge cases, side effects, ordering, and error semantics - tests or evidence that define current behavior - performance or platform constraints - project conventions and nearby patterns Use `loom-research` when historical, source, or framework context