vibe-code-hardening

Use this skill to convert a promising prototype into a codebase that can survive repeated agent edits. Treat "vibe-coded" work as a hypothesis: preserve what works, write down the intended behavior, then add mechanical pressure so future changes must prove they are safe.

Operating stance

• Start by discovering the actual stack, entrypoints, deploy path, and current behavior. Do not impose a framework rewrite just because the project is messy.
• Prefer small gates that run on every change over a big architecture document nobody enforces.
• Capture behavior before refactoring. For fragile code, characterization tests are the harness that lets you improve design without losing the product.
• Use CI as the source of truth. Local hooks are fast feedback; CI is the merge/deploy contract.
• When the existing project has too much debt to make strict gates pass immediately, create a ratchet: baseline current failures, block new failures, then burn the baseline down in follow-up work.

First pass audit

Before editing, gather: