design-bundle-audit

Auditing a design bundle for spec drift requires running six structured checks covering structural paths, voice consistency, recommendation parity, token coverage, asset references, and cross-file facts. This produces evidence-based RED, YELLOW, or GREEN output to verify internal truthfulness before build-lane transcription.

Token coverage auditing finds dead tokens that are defined but unused and broken references that are used but undefined within a UI kit. You need it when verifying a design handoff bundle to prevent developers from transcribing incorrect styling variables into code.

UI kit consistency is verified by checking that component behavior matches the prescriptions in RECOMMENDATION.md and that rendered copy aligns with stated voice rules. This cross-file fact consistency check confirms colors, opacity values, and banned rules agree across all bundle files.

Yes, you can check structural truthfulness by verifying every README-enumerated file and directory path exists on disk. The asset reference verification also checks local asset existence and flags any unresolved external references as unverified.

The best way to prevent internal inconsistencies is applying automated handoff audits that compare cross-file facts, token coverage, and voice rules across the bundle. This catches design bundle drift early with evidence-based output before it becomes broken build inputs.

RED or YELLOW flags indicate cross-file fact inconsistencies where key values like colors, opacity, or banned rules disagree across bundle files. These warnings mean the design bundle is not internally truthful and requires fixing before build-lane transcription into code.