cm-reactorlisted

# Reactor — Strategic Codebase Re-direction > **When the code works but the direction is wrong, you don't debug — you REACT.** > TRIZ-powered protocol for pivoting large codebases without losing stability. ## When to Use **ALWAYS when:** - Requirements changed significantly after code was built - Architecture no longer fits the problem (wrong patterns, wrong abstractions) - 3+ patches on the same area — symptom of structural mismatch - Tech debt blocks new feature development - "We need to rewrite X" — STOP. Use this skill first. - Migrating from one framework/library/pattern to another - Post-mortem reveals systemic issues needing strategic change **Skip when:** - Simple bug fix → use `cm-debugging` - Routine refactoring (extract method, rename) → use `cm-clean-code` - New project from scratch → use `cm-project-bootstrap` - Small scope change (< 5 files affected) → just refactor directly ## The Iron Law ``` NO REWRITE WITHOUT REACTOR ANALYSIS FIRST ``` Rewrites fail 70% of the time. Incremental strategic migration succeeds 90% of the time. ## TRIZ Principles Applied | # | Principle | How Applied | |---|-----------|-------------| | **#35** | Parameter Change | Change the fundamental parameter (language, pattern, architecture) — not the symptom | | **#28** | Mechanics Substitution | Replace one mechanism with a more effective one (OOP → FP, REST → GraphQL, etc.) | | **#13** | The Other Way Around | Instead of adapting new code to old architecture, adapt old architectu