Anti-AI-slop design skill for Claude Code, Cursor, and Codex.
CSS
SaaS sections become a deck that must deviate, not a sequence to stamp
Youssef1428d2bde013
diff --git a/skills/hallmark/references/macrostructures.md b/skills/hallmark/references/macrostructures.mdindex 8e800ce..0c6b612 100644--- a/skills/hallmark/references/macrostructures.md+++ b/skills/hallmark/references/macrostructures.md@@ -49,31 +49,30 @@ Each macrostructure also implies a **nav archetype** (N1a–N13) and a **footer----## SaaS page sequence+## SaaS section deck - deal it, don't sequence it-When the macrostructure is **Bento Grid · Stat-Led · Workbench · Marquee Hero** and the brief is a B2B SaaS marketing page, ship these sections in roughly this order. None are mandatory — but skipping more than two reads as "the page is incomplete":+When the macrostructure is **Bento Grid · Stat-Led · Workbench · Marquee Hero** and the brief is a B2B SaaS page, build from this **deck of eight core cards**. Cards have roles, not positions:-1. **Hero** — macrostructure-specific (Bento, Stat, Workbench, Marquee). Two CTAs (primary action + secondary "Talk to sales").-2. **Social proof / logo wall** — 6–8 customer logos in monochrome. (See [`assets.md` § Logo walls](assets.md).)-3. **Features** — 3–6 feature cards, varies by macrostructure (Bento has them inline; Stat-Led usually puts them after the supporting-stats grid).-4. **Testimonials** — 2–4 quote cards. Pull-quote + name + role + company. Photo optional. Avoid "We use [product] every day" language; the quote should be specific to a use case ("Foundry got us SOC2 in five weeks. We wrote zero policies ourselves.").-5. **Pricing** — 2–3 tiers in a comparison table. Feature checklist per tier. Recommended-tier badge on the middle tier. Show the actual price; "Contact sales for pricing" on every tier is a tell that the brand doesn't trust the buyer.-6. **FAQ** — 5–10 questions. Conversational FAQ archetype works here (see Macrostructure 06).-7. **Final CTA strip** — single button + one-sentence prompt.-8. **Footer** — index-style or tabular, theme-appropriate.+| Card | Role |+| --- | --- |+| Hero | the claim - macrostructure-specific, two CTAs max |+| Logo wall | borrowed trust - 6-8 monochrome marks (see [`assets.md` § Logo walls](assets.md)) |+| Features | the capabilities - 3-6, shaped by the macrostructure |+| Testimonials | outside voices - 2-4 quotes, use-case-specific, role + company |+| Pricing | the commitment - real prices, 2-3 tiers |+| FAQ | objections, answered like a person |+| CTA strip | the ask, once - one button |+| Footer | the colophon - theme-appropriate |-Each section transition uses theme-appropriate vertical spacing — `--space-3xl` minimum between major sections. Don't subdivide sections into "rows" with sub-rules — the section break is the visual rhythm.+**Every deal deviates twice.** (a) **Drop at least one** core card and name it (logo wall and CTA strip are the usual cuts; hero and footer never drop). (b) **Either promote one wildcard** - **spec-sheet (F3) · changelog · manifesto-inset · worked-example · comparison-anatomy · index (macro 13)** - into the run, **or reorder one adjacent pair meaningfully** (pricing before features says "the price is the pitch"; testimonials before features says "trust before claims"). State both moves in the Picks block: `deck: -logos +worked-example` or `deck: -faq · pricing<features`. A deal that keeps **at least five** core cards still reads complete; below five it is a landing strip, not a landing page - re-add cards or switch macrostructure.-**Voice rules for SaaS sections:**+**Voice, wherever a card lands:** pricing shows the actual price ("Contact sales" on every tier signals the brand doesn't trust the buyer); testimonials name the person's role *and* company, use-case-specific ("Foundry got us SOC2 in five weeks. We wrote zero policies ourselves." beats "we use it every day"), plausible names never "Jane Doe" (gate 19); FAQ answers like a person ("Yes - Stripe and Adyen are both supported out of the box" beats "our platform integrates with leading payment providers"); the CTA strip has one button - the repetition is the call to action.-- **Pricing:** show the actual price. Sales-led pricing on every tier ("Contact us") signals the brand doesn't trust the buyer.-- **Testimonials:** include the quoted person's role *and* company. Abstract "Engineering Manager" testimonials are slop. If the brief is a real product, use real names. If the brief is a placeholder, use plausible names — never "Jane Doe" / "John Smith" (gate 19).-- **FAQ:** answer like a person, not a sales doc. "Yes — Stripe and Adyen are both supported out of the box" beats "Our platform integrates with leading payment providers."-- **CTA strip:** one button. Not two. The repetition is the call to action.+Each card transition uses theme-appropriate vertical spacing - `--space-3xl` minimum between cards; the section break is the visual rhythm, no sub-rules.-This sequence is **not** a template you stamp out — it's a recipe of *what should be present*. The macrostructure determines *how* each section looks. A Bento Grid page interleaves features and proof inside the grid; a Stat-Led page sequences them top-to-bottom; a Marquee Hero page lets the marquee do the social-proof work.+The deck is **not** a template you stamp out - the macrostructure determines *how* each card looks. A Bento Grid page interleaves features and proof inside the grid; a Stat-Led page sequences them top-to-bottom; a Marquee Hero page lets the marquee do the social-proof work.-For non-SaaS work (Editorial, Manifesto, Letter, Long Document, Quote-Led), this sequence does **not** apply. A bakery does not need a pricing tier comparison.+For non-SaaS work (Editorial, Manifesto, Letter, Long Document, Quote-Led), this deck does **not** apply. A bakery does not need a pricing tier comparison.---diff --git a/skills/hallmark/references/themes/cobalt.md b/skills/hallmark/references/themes/cobalt.mdindex 0600bae..e3e2e98 100644--- a/skills/hallmark/references/themes/cobalt.md+++ b/skills/hallmark/references/themes/cobalt.md@@ -65,7 +65,7 @@ Composed and sparse. The one hero type-in (plays once). Section reveals fade + r**Cobalt loves these.**-- **SaaS / API Product** - hero + quick-start code + feature rows + pricing/CTA *(canonical - cobalt-01)*+- **SaaS / API Product** - deck ingredients: a quick-start code card, benchmark figures, real pricing - dealt per macrostructures.md § deck, never a fixed run *(canonical - cobalt-01)*- **Dev-tool / CLI** - terminal hero + install + benchmark figures + docs CTA- **Docs home** - a calm index with a search-first nav- **Workbench** - the technical, tool-first shapediff --git a/skills/hallmark/references/themes/coral.md b/skills/hallmark/references/themes/coral.mdindex b0c2e0a..673b0ae 100644--- a/skills/hallmark/references/themes/coral.md+++ b/skills/hallmark/references/themes/coral.md@@ -60,7 +60,7 @@ Composed and sparse. Optional section reveals fade and rise ~8px, once. Hover: c**Coral loves:**- **Stat-Led** - a warm metrics page (teams onboarded, uptime, volume processed)-- **Feature-stack / SaaS** - hero + feature rows + pricing + CTA+- **Feature-stack / SaaS** - deck ingredients: calm feature rows, real pricing, one warm CTA - dealt per macrostructures.md § deck- **Bento Grid** - warm, restrained product-surface tiles- **Marquee Hero** - when the hero is one confident typographic statement- **Conversational FAQ** - a calm, human support voicediff --git a/skills/hallmark/references/themes/field.md b/skills/hallmark/references/themes/field.mdindex e2773ed..e26c818 100644--- a/skills/hallmark/references/themes/field.md+++ b/skills/hallmark/references/themes/field.md@@ -62,7 +62,7 @@ Composed and warm. Primary button lifts `translateY(-2px)` on hover; nav/link un## Macrostructure affinity + rejection-**Field loves.** Marquee Hero *(canonical - field-01)* · SaaS / Product (hero + how-it-works beats + feature rows + warm CTA band) · Letter (the small-team, still-early warm note - Field can be intimate where the cool themes cannot) · Feature Tour (alternating document rows).+**Field loves.** Marquee Hero *(canonical - field-01)* · SaaS / Product (deck ingredients: how-it-works beats, feature rows, a warm CTA band - dealt, not sequenced) · Letter (the small-team, still-early warm note - Field can be intimate where the cool themes cannot) · Feature Tour (alternating document rows).**Field refuses.** Manifesto (too loud - Field is plain, not a shout) · Terminal / code-hero (that is the cool dev themes; Field shows a content artifact, not code) · Photographic / image-led (Field draws by hand) · Long Document / archive (prose-led editorial routes to the warm-editorial themes).diff --git a/skills/hallmark/references/themes/ledger.md b/skills/hallmark/references/themes/ledger.mdindex 7592d7e..5045c7b 100644--- a/skills/hallmark/references/themes/ledger.md+++ b/skills/hallmark/references/themes/ledger.md@@ -68,7 +68,7 @@ Composed and near-still. The `LIVE` dot pulses (opacity 1 → 0.4, `2.4s`). Ledg**Ledger loves these.**-- **Stat-Led** - hero balance panel + how-it-works + datasheet + trust + CTA *(canonical - ledger-01)*+- **Stat-Led** - deck ingredients: the hero balance panel, a numbered how-it-works trio, the datasheet, one trust row - dealt per macrostructures.md § deck *(canonical - ledger-01)*- **SaaS / Product** - fintech landing where the console is the proof- **Workbench** - the dashboard-first, tool-shaped page- **Comparison / datasheet** - dense spec tables, controller-facing