Improve Code Quality
Guided journey from a working-but-untested vibe-coded prototype to a production-ready...
Install
npx skills add wondelai/skills --skill improve-code-quality -g -a claude-code -y- Repository
- wondelai/skills2.6k
- Category
- Design
- Updated
- 2mo ago
- License
- MIT
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Guided journey from a working-but-untested vibe-coded prototype to a production-ready product with tests, clean structure, a business-rules boundary, and resilience at scale. Orchestrates nine skills phase by phase - working-with-legacy-code, clean-code, refactoring-patterns, software-design-philosophy, clean-architecture, pragmatic-programmer, release-it, system-design, ddia-systems - asking the user questions at every decision point and recording results in the project docs/ folder (TESTING.md, TECH-DEBT.md, IMPROVE-CODE-QUALITY-PLAN.md) so the journey resumes across sessions. Use when the user wants to harden an AI-generated prototype, add tests before refactoring, make code safe to change, or says ''this works on my machine but I am scared to touch it''. For an aged codebase, remove-technical-debt; for greenfield structure, design-code-architecture; for a product and UX pass, improve-app; to optimize speed and structure, architecture-optimization. For one framework in isolation, invoke that skill directly.
Improve Code Quality
Turn a working-but-untested vibe-coded prototype into a product you can ship and operate. This is an
interactive, resumable journey of nine phases: the agent asks before every decision and records the
outcome in your project's docs/ folder, so you can stop after any phase and pick up later. A
week-old prototype is already legacy code, so the first move is a safety net, and every phase after
it is verifiable because of that net.
Core Principle
A week-old untested prototype is already legacy code: flip tactical to strategic, safety net
first, then readability, structure, and production hardening in order. This skill sequences the
phases, asks the decision questions, and records every choice in docs/. The constituent skills
carry the method, invoke them rather than improvising their frameworks. Skipping ahead (refactoring
before tests, scaling before sizing) is the exact failure mode this ordering exists to prevent.
