Make your prototype safer to change and ready to ship.
Guides users through testing, refactoring, architecture improvements, and production hardening, recording decisions and progress in project documentation.
When to use it
Use when hardening an AI-generated prototype, adding tests before refactoring, or making working code safer to change.
Give it a working but untested project; it asks for decisions throughout a resumable improvement journey and records outcomes in project documentation.
What you provide
Uses this skill in Phase 1 to identify seams and characterize the starting module's behavior. Installation is not required: the operating rules provide a fallback brief when the skill is unavailable and the user declines installation.
Uses this skill in Phase 2 to score readability, prioritize fixes, and audit error handling. Installation is not required because the operating rules provide a fallback brief.
Uses this skill in Phase 3 to apply named refactorings individually with tests between changes. Installation is not required because the operating rules provide a fallback brief.
Uses this skill in Phase 4 to identify shallow classes and information leakage and consolidate modules. Installation is not required because the operating rules provide a fallback brief.
No additional actions listed.