Anti-Vibecoded Design

What it does

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

When to use it

Use during art direction, design review, or final QA to check a site doesn't read as a reusable template.

Problems it prevents

Catches the specific, nameable patterns that make a site read as Claude/Lovable/v0/Bolt-generated instead of bespoke.

Typical workflow

1. Run all 30 checks against the build
2. Score and evidence each one
3. Apply the blocking gate where needed
4. Report specific fixes, not vague notes

Example output

A scored report naming the exact components or copy lines that still read as generic, with a specific fix for each.

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

• SystemPremium Content Hierarchy

  Writes message architecture and copy hierarchy from a real offer, audience, evidence and objections, not filler.

• SystemEditorial Layout Composition

  Composes distinctive, premium page layouts using editorial grids, negative space, layering and deliberate asymmetry.

• SystemWebsite Final Audit

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