Files
2025-11-29 18:20:07 +08:00

685 B

[Refactoring Name]

Why this refactoring is needed - code quality issues, maintainability concerns, or technical debt.

<current_state> Brief description of what exists now that needs refactoring. </current_state>

<target_state> What the code should look like after refactoring:

  • Structural improvements
  • Pattern or architecture changes
  • Quality improvements (readability, maintainability, performance)

Focus on design and structure, not specific code. </target_state>

How to ensure refactoring doesn't break functionality: - Existing tests that should pass - New tests if behavior changes - Performance benchmarks if applicable