Website Final Audit

What it does

Orchestrates the final evidence-based quality gate: anti-vibecode, production security and launch-readiness checks combined.

When to use it

Use only once implementation is complete enough to verify real outputs and flows, not mid-build.

Problems it prevents

Prevents sign-off happening on a gut feeling instead of a documented, evidenced review.

Typical workflow

1. Run the anti-vibecode gate
2. Run the production security gate
3. Run the launch-readiness gate
4. Combine evidence into one verdict

Example output

A single go/no-go report backed by three separate evidenced gates, not one person's impression of 'looks ready'.

What's included

1. 01
   The complete prompt

   The full manual as a ready-to-save SKILL.md file, matched exactly to what ships in the T7 library.

2. 02
   Install walkthrough

   Personal (~/.claude/skills/) and project (.claude/skills/) folder instructions, whichever fits how you work.

3. 03
   Use notes

   How Claude invokes it, what a good result looks like, and what to check before you trust the output.

Works well with

• SystemAnti-Vibecoded Design

  Runs the full 30-check gate against generic AI-generated design, copy, components, imagery and motion.

• SystemSecurity

  Applies the evidence-based production security gate across secrets, auth, data access, uploads, dependencies and APIs.

• SystemLaunch Readiness

  Classifies and verifies what customers, search engines and operators actually need before a production launch.