Cr8v Stacks
Strategy, Design & Liquid Performance
← All Playbooks PB-02 · CLAUDE CODE & SYSTEMS
Free PDF Playbook · 6 Chapters · 12 pages

Teaching Claude Code & Artifacts Your Exact Brand Tokens

Stop Claude from defaulting to generic rounded purple SaaS cards. Pack typography, Swiss grid borders, contrast ratios, and PHP/CSS template contracts into CLAUDE.md and MCP-ready rules.

Instant full-chapter reader + downloadable PDF emailed directly · Zero spam · Privacy Policy

✓ Playbook Unlocked

The PB-02 playbook is yours.

Full chapters and checklists are open below, and your styled PDF copy is ready for instant download.

Inside · PB-02
6 Engineering Chapters
  1. Why Claude Defaults to Generic SaaS UI (And How Constraints Fix It)
  2. Structuring a Machine-Readable Token Manifest in Your Theme Repo
  3. Writing Component Contracts for Mega Menus, Grids & Drawers
  4. Preventing WordPress CSS Collisions Across Plugins & Builders
CR8V STACKS PB-02
CLAUDE CODE & SYSTEMS
Claude Design Systems

CLAUDE.md token manifests, WordPress template contracts, and zero-drift component generation.

6 CH · 12 pages
Included Benchmarks
Specs & Decision Tables
  • 1 CLAUDE.md Spec: Single repository brief defining typography, radius=0px, paper/obsidian surfaces & CSS prefix laws
  • 100% Token Parity: Figma variables mapped 1:1 to --c8-* CSS custom properties with zero magic hexes
  • 0 Prefix Bleed: Scoped root containers preventing theme CSS from colliding with plugin shortcodes
Sound Familiar?

Where most builds lose speed, search visibility, or margin.

Written directly from technical audits we run before scoping client projects.

01 / GAP

Generic "AI-slop" card defaults

Without explicit constraints, Claude invents soft shadows, pill borders, neon gradients, and unapproved fonts on every new component.

02 / GAP

Inconsistent CSS custom properties

Every prompt introduces fresh hardcoded hex codes (#3b82f6 vs #0047E1) and arbitrary padding steps across theme files.

03 / GAP

Broken WordPress enqueue order

AI-generated stylesheets ignore prefix isolation (.c8hdr-root), breaking header mega menus or WooCommerce buttons on live pages.

04 / GAP

Multi-file edits losing header/mobile parity

Updating desktop navigation in one prompt leaves the mobile drawer or blog header out of sync silently.

What’s Inside

6 Chapters · Field Playbook

Enter your email above to unlock the full two-column editorial playbook, interactive checklists, code blocks, and PDF download.

Unlock Full Playbook ↑
  1. 01

    Why Claude Defaults to Generic SaaS UI (And How Constraints Fix It)

    Eliminate ambiguity by declaring forbidden styles (no neon gradients, no rounded boxes) right at the top of CLAUDE.md.

    Locked
  2. 02

    Structuring a Machine-Readable Token Manifest in Your Theme Repo

    Expose one canonical variable table covering color roles, type scale clamps, spacing, and z-index layers.

    Locked
  3. 03

    Writing Component Contracts for Mega Menus, Grids & Drawers

    Define DOM hierarchy, image aspect ratios (`aspect-ratio: 16/10`), and mobile drawer parity rules.

    Locked
  4. 04

    Preventing WordPress CSS Collisions Across Plugins & Builders

    How root namespace wrapping keeps theme styles clean alongside third-party widgets and stacks plugins.

    Locked
  5. 05

    Reviewing & Editing Live WordPress Pages Safely With Claude Code

    Small scoped diffs, `php -l` syntax checks, and keeping inline critical CSS synced with release packages.

    Locked
  6. 06

    Automated Browser Audit Loop After Every Component Change

    Pair Claude edits with real Chromium viewport captures at 1440px, 1280px, and 390px before pushing.

    Locked
PB-02 · CLAUDE CODE & SYSTEMS

A Design System Claude Can Build With (Zero Hallucinated CSS)

By Cr8v Stacks Engineering Team · Updated Nov 2026 · 6 Chapters · 12 pages
Download Styled PDF (12 pages) ↓
Chapter 01

Why Claude Defaults to Generic SaaS UI (And How Constraints Fix It)

Key Focus Eliminate ambiguity by declaring forbidden styles (no neon gradients, no rounded boxes) right at the top of CLAUDE.md.

LLMs regress toward statistical web averages when visual rules are implicit. Explicitly write negative constraints alongside positive tokens: specify exact Google Fonts (`Michroma`, `Space Mono`, `DM Sans`), `#FAFAF7` studio paper canvas, `#080808` obsidian panels, `#0047E1` Cobalt accent, `border-radius: 0px`, and `1px solid rgba(8,8,8,0.14)` architectural grid dividers.

STEP 01
Lock Negative Rules

Explicitly ban rounded pills, neon gradients & unapproved fallback fonts.

STEP 02
Bind CSS Variables

Define paper, obsidian, cobalt ink & grid-line variables at :root.

STEP 03
Enforce Prefix Scope

Wrap headers, grids & drawers in isolated namespace classes (.c8gd-*).

STEP 04
Verify Rendered DOM

Inspect live Chromium captures at 1440px & 390px before shipping.

Unconstrained AI Prompting

Produces generic Tailwind purple gradients, inconsistent border-radius, and CSS bleed.

CLAUDE.md Token Contract

Enforces Michroma/Space Mono/DM Sans, 0px geometry, and exact WordPress template parity.

Chapter 02

Structuring a Machine-Readable Token Manifest in Your Theme Repo

Key Focus Expose one canonical variable table covering color roles, type scale clamps, spacing, and z-index layers.

Keep a compact tokens reference listing global CSS custom properties and component class prefixes (`parts/header.php` `.c8hdr-root`, `home.php` `.blog-grid-frame`, `.c8gd-*`) so Claude extends existing selectors rather than inventing duplicate stylesheets.

CLAUDE.md — Visual & Theme Contract
# Cr8v Stacks Visual Tokens
- Heading font: 'Michroma', sans-serif (uppercase display)
- Mono font: 'Space Mono', monospace (eyebrows/codes)
- Body font: 'DM Sans', sans-serif (15px-17px readable prose)
- Surfaces: #FFFFFF | #FAFAF7 | #080808 | Accent: #0047E1
- Geometry: strict border-radius: 0px across cards, mega menus & inputs
- Escaping: wrap every PHP output in esc_html(), esc_attr(), esc_url()
✓ Always place negative visual constraints in the first 30 lines of CLAUDE.md so every prompt inherits them.
Chapter 03

Writing Component Contracts for Mega Menus, Grids & Drawers

Key Focus Define DOM hierarchy, image aspect ratios (`aspect-ratio: 16/10`), and mobile drawer parity rules.

Specify that any new header item added to `parts/header.php` must include a matching Customizer control in `inc/customizer/panel-header.php`, matching mobile card markup inside `#c8-md-drawer`, and fallback parity inside `parts/header-blog.php`.

1
Buyer Question in H1 Direct search or prompt intent matched clearly in the top heading.
2
20–40 Word Entity Lead Self-contained definition sentence models can lift verbatim.
3
Follow-Up Questions as H2s Structured sub-headings matching buyer scope, cost & comparison queries.
4
Semantic Tables & Specs HTML <table>, <dl> & <ol> data blocks instead of vague marketing prose.
5
Named Author, Date & @graph Verified provenance + connected Organization & Service JSON-LD.
Chapter 04

Preventing WordPress CSS Collisions Across Plugins & Builders

Key Focus How root namespace wrapping keeps theme styles clean alongside third-party widgets and stacks plugins.

Namespace interactive widgets under dedicated parent roots (e.g. `.c8gd-page`, `.c8hdr-root`, `.blog-grid-section`) and isolate third-party shortcodes so global typography and button resets never break embedded calculators or audit reports.

Chapter 05

Reviewing & Editing Live WordPress Pages Safely With Claude Code

Key Focus Small scoped diffs, `php -l` syntax checks, and keeping inline critical CSS synced with release packages.

Instruct Claude to target single functions or template parts per diff, escape every output with `esc_html()`, `esc_attr()`, and `esc_url()`, and always run local PHP syntax linting before assembling theme release ZIPs.

Chapter 06

Automated Browser Audit Loop After Every Component Change

Key Focus Pair Claude edits with real Chromium viewport captures at 1440px, 1280px, and 390px before pushing.

Require visual inspection of rendered screenshots on local staging/HTML previews—checking image cropping, zero horizontal overflow, legible contrast, and keyboard escape/focus behavior—before marking any UI change complete.

STEP 01

Prompt Audit

Run your top 20 buyer prompts across ChatGPT, Perplexity, Claude & Google AI.

STEP 02

Log Citations

Record whether your domain is named, which URLs are cited, and who ranks instead.

STEP 03

Compare Delta

Track month-over-month citation share and newly indexed comparison or service pages.

STEP 04

Verify UTM Traffic

Check analytics for referrals tagged utm_source=chatgpt.com and perplexity.ai.

STEP 05

30-Point AEO Scan

Run modified templates through the Cr8v Stacks Free AEO Checker after deploys.

STEP 06

Ship Next Fix

Prioritize 0-point blockers first: crawler blocks, SSR gaps, and missing schema edges.

Verified Citation & Performance Readiness (Cr8v Stacks Benchmarks)
Measured across 30 deterministic checks on cr8vstacks.com & shipped client builds (Nov 2026).
ChatGPT Search & OAI-SearchBot
94 / 100Default: 42 avg
Perplexity Live Answer Citations
92 / 100Default: 38 avg
Claude & /llms.txt Entity Parsing
96 / 100Default: 35 avg
Google AI Overviews & Core Web Vitals
95 / 100Default: 51 avg
Interactive Self-Audit

Playbook Execution Checklist

0 / 4 Complete
By The Numbers

Benchmarks from real shipped systems.

1 CLAUDE.md Spec
Single repository brief defining typography, radius=0px, paper/obsidian surfaces & CSS prefix laws
100% Token Parity
Figma variables mapped 1:1 to --c8-* CSS custom properties with zero magic hexes
0 Prefix Bleed
Scoped root containers preventing theme CSS from colliding with plugin shortcodes
WCAG 2.2 AA
Enforced 4.5:1 text contrast & visible keyboard focus rings built into base patterns
Architecture Layer Typical Default Approach Cr8v Stacks Playbook Standard
Unconstrained Prompts Generic Tailwind gradients & mismatched radii High manual cleanup after every AI component
Contract-Driven CLAUDE.md Locked Michroma/Space Mono/DM Sans + Swiss hairlines Production-ready PHP & CSS matching existing screens
Related Engineering Articles
Next Step

Want our team to audit your stack directly?

Bring your URL or project scope to a focused 30-minute discovery call — leave knowing exact bottlenecks, architecture options, timeline, and budget.

Book a 30-min Scope Call → All Playbooks
CR8V
ASK AI ABOUT US

Do your homework your own way

Pick a question, pick an assistant. It opens ready to go.

Ready to build what your business actually runs on?

Start Your Discovery Call
01 Pick a question
02 Open it in
© 2026 CR8V STACKS. All rights reserved.
Back to Top