flpbalada Refactoring
Improve structure. Keep behavior same. Avoid breaking changes.
Goal
Improve code structure without changing behavior. Reduce complexity only where it pays off.
Inputs
- Target files, components, modules, or changed code.
- Desired outcome or pain point.
- Constraints and behavior that must not change.
Rules
- Preserve behavior.
- Make incremental changes.
- Follow project conventions.
- Keep changes minimal.
- Avoid over-refactoring.
- Do not change public contracts without request.
- Verify when checks exist.
Flow
- Analyze target code.
- Identify goal, constraints, patterns, and anti-patterns.
- Load relevant skills only when they materially improve the refactor.
- Define smallest safe steps.
- Apply changes incrementally.
- Verify behavior is unchanged.
Skill Hints
- Naming issues:
naming-cheatsheet. - Abstraction issues:
code-architecture-wrong-abstraction. - React:
react-use-state,react-useeffect-avoid,react-use-client-boundary. - TypeScript:
typescript-best-practices,typescript-interface-vs-type,typescript-satisfies-operator. - Project layout:
project-structure.
Output
## Refactor
- [changed area]
## Behavior
- [behavior preserved]
## Verification
- [check run or reason not run]