tt-audit

Context Check

1. Read .tt-impeccable.md from the project root → check ### Fidelity Intent. If found, use it.
2. If absent, infer from the codebase:
   • Canvas ≤ 390px, mobile-first flex, safe area insets → Strict TUX-native
   • Desktop-first, 1440px max-width, dark #000000 canvas → TT Style
   • If still unclear, ask: "Is this Strict TUX-native (mobile product screen) or TT Style (web / marketing)?"

Load token values as needed from tt-impeccable/reference/tokens.md and tt-impeccable/reference/typography.md.

Rules below marked (TUX-native only) are skipped for TT Style — they are not violations. Rules marked (TT Style only) are skipped for TUX-native. Universal rules apply to both tiers.

Run systematic technical quality checks against TUX v2 standards and generate a comprehensive report. Do not fix issues — document them for /tt-impeccable extract or /tt-impeccable craft to address.

This is a code-level audit, not a design critique. Check what is measurable and verifiable in the implementation.