Agent skill · wondelai
improve-code-quality
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.
What it needs
About 12k tokens when loaded.
What this skill does
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. Journey Map Phase Skill Question it answers Artifact --- --- --- --- 1 working-with-legacy-code Can I change this code without breaking it unknowingly? Creates docs/TESTING.md + docs/TECH-DEBT.md — GATE 2 clean-code Is this readable to the next person (and agent)? Extends docs/TECH-DEBT.md 3 refactoring-patterns Can I reshape structure without changing behavior? Extends docs/TECH-DEBT.md 4 software-design-philosophy Is complexity hidden behind deep modules? Extends docs/TECH-DEBT.md 5 clean-architecture Do business rules depend on the framework, or vice versa? Extends docs/ARCHITECTURE.md 6 pragmatic-programmer What habits keep it clean after we stop? Extends docs/TECH-DEBT.md 7 release-it Will it survive a hostile production? Creates docs/RELIABILITY.md 8 system-design Is it sized for the load we actually have? Extends docs/ARCHITECTURE.md + docs/RELIABILITY.md 9 ddia-systems Is the data layer correct and durable under concurrency? Extends docs/ARCHITECTURE.md Operating Rules 1. Resume first. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills wondelai/improve-code-quality--c6abb2