design-bundle-audit

What problem does it solve?

Prevents internal inconsistencies inside a design-bundle handoff so the build lane doesn’t transcribe wrong structure, voice, recommendations, tokens, or asset paths.

Core Features & Use Cases

• Structural truthfulness checks: Verifies every README-enumerated file/directory path actually exists on disk.
• Voice and copy consistency: Detects mismatches between stated voice rules and the rendered component/preview copy.
• RECOMMENDATION-to-implementation validation: Ensures UI kit behavior matches the prescriptions in RECOMMENDATION.md.
• Token coverage auditing: Finds dead tokens (defined but unused) and broken references (used but undefined).
• Asset reference verification: Checks local asset existence and flags unresolved external references as unverified.
• Cross-file fact consistency: Confirms key facts (colors, opacity values, banned rules) agree across bundle files.

This is used when you receive a Claude Design bundle (or similar handoff) and need to verify it is internally truthful before it becomes build inputs.

Quick Start

Run design-bundle-audit on the frozen bundle directory path you received (for example, the Designs root containing the bundle README).