Are you building cathedrals or digging graves?

Use this interactive audit tool to measure the synthetic technical debt accumulated in your AI-assisted project.

Vibe-Code Smell Audit

Select all patterns currently present in your repository.

Estimated Total Debt
0 Units
Status: Healthy

This estimate is based on the Clean Vibe Code methodology. Learn how to pay down this debt in Part IV of the book.

Get the Remediation Guide

How the Assessment Works

This tool uses the Severity Scale defined in Clean Vibe Code to quantify risks that are often invisible to traditional linters or static analysis tools.

10 Units
Critical Risk

Production-breaking vulnerabilities or complete loss of IP control.

5 Units
High Risk

Opaque logic in critical paths that no human can explain.

2 Units
Medium Risk

Minor inconsistencies, prompt drift, or inefficient token usage.

Research shows that once a codebase exceeds 100 Debt Units, the cost of maintaining legacy AI code exceeds the value of shipping new features. This is known as Technical Bankruptcy.

The Road to Recovery

  • 1

    Deep Audit

    Read about the [7 categories of debt](/debt) to understand your specific risks.

  • 2

    Refactor Plan

    Identify the [Vibe-Code Smells](/smells) you checked and apply recovery patterns.

  • 3

    Scale Securely

    Establish [Team Standards](/faq/ai-coding-team-standards) to prevent future debt accumulation.