flpbalada Decompose Component
Split a component into focused units. Keep behavior unchanged.
Goal
Improve readability and ownership. Do not create needless abstractions.
Rules
- Preserve behavior unless user approves behavior change.
- Prefer smallest correct split.
- Extract only when readability, reuse, or locality improves.
- Keep state near the code that owns it.
- Keep side effects explicit.
- Avoid moving code only to reduce file length.
- Do not create generic helpers for one unclear use.
Flow
- Read component and identify responsibilities.
- Mark state, effects, data transforms, handlers, and UI sections.
- Choose extraction candidates.
- Extract pure helpers first when obvious.
- Extract hooks only for cohesive state/effects.
- Extract sub-components for stable UI sections.
- Verify behavior and imports.
Output
## Decomposition
- Extracted: [helper/hook/component]
- Reason: [responsibility isolated]
- Preserved: [behavior]
- Verification: [check run or reason not run]