TypeScript Refactoring

Quick Start

1. Identify the dominant smell before changing structure.
2. Define scope, boundaries, and non-goals.
3. Choose one refactoring strategy that fits the smell.
4. State the safety net: tests, characterization tests, or explicit verification steps.
5. Make one conceptual transformation at a time.
6. Verify after each meaningful step.

For a small local change, a short scope and verification note is enough. Use a written plan only for multi-step, cross-module, or risky work; do not impose a six-part response on every cleanup.

Read references selectively from the symptom table below. They are a technique catalog, not a checklist of changes to apply.

Core Workflow

1. Diagnose Before You Rearrange