Skip to content

xinetzone/SpecWeave / .agents/skills/design-library-creator

design-library-creator

Flagged

Create, expand, and refine professional Design Libraries / Design Systems with structured token architecture. ONLY invoke when user EXPLICITLY mentions design-system terminology: 'Design Library', 'Design System', '设计系统', '设计库', 'token system', 'design tokens', '组件库规范', or provides a parsed design-spec bundle (ZIP/Figma export). Also covers creating a new theme / color theme as a design-system deliverable (创建主题/新建暖色主题/深色主题等 — tokens + palette + component styling). Do NOT route here for: '素材库', '全套素材', '素材合集', '物料库', '生成素材', '做一套设计', '做几张图', '设计一套页面', '帮我出图', page/poster/landing-page creation, or any visual-asset generation intent where the user does not demonstrate knowledge of design-system concepts. Those belong to solo-design.

FileKindSize
SKILL.mdskill md19.3 KB
aesthetics/dark-mode.mdmarkdown1.8 KB
aesthetics/index.mdmarkdown33.8 KB
aesthetics/navigation-footer.mdmarkdown2.2 KB
aesthetics/screen-craft.mdmarkdown9.2 KB
aesthetics/self-check.mdmarkdown24.9 KB
examples/templates/component-dispatch-rules.mdmarkdown9.1 KB
examples/templates/figma-token-gen.mdmarkdown50.3 KB
examples/templates/incremental.mdmarkdown5.7 KB
examples/templates/phase-2-analysts.mdmarkdown6.8 KB
examples/templates/phase-2-structured-spec.mdmarkdown8.8 KB
examples/templates/phase-2.5-intent-synthesis.mdmarkdown31.0 KB
examples/templates/phase-3-4-component.mdmarkdown9.0 KB
examples/templates/phase-4-ui-kit.mdmarkdown39.3 KB
examples/templates/phase-5-docs.mdmarkdown12.5 KB
examples/templates/scratch-token-gen.mdmarkdown14.4 KB
examples/templates/specimen-reference.htmlother6.0 KB
file-specs/css-json.mdmarkdown9.5 KB
file-specs/css-tokens.mdmarkdown33.6 KB
file-specs/design-library-output.mdmarkdown10.3 KB
file-specs/design-spec-bundle.mdmarkdown5.9 KB
file-specs/documentation.mdmarkdown12.3 KB
file-specs/preview-pages.mdmarkdown28.0 KB
file-specs/ui-kit.mdmarkdown28.5 KB
operation-policies/agent-orchestration.mdmarkdown20.2 KB
operation-policies/bundle-exploration.mdmarkdown9.0 KB
operation-policies/decision-rules.mdmarkdown10.7 KB
operation-policies/quality-gates.mdmarkdown10.5 KB
operation-policies/user-output-policy.mdmarkdown7.8 KB
scripts/check-design-library-phase.mjsscript85.1 KB
scripts/copy-bundle-assets.mjsscript12.3 KB
scripts/css-to-json.mjsscript53.1 KB
scripts/css-utils.mjsscript748 B
scripts/extract-components-css.mjsscript10.3 KB
scripts/generate-uikit-plan.mjsscript27.5 KB
scripts/jsonl-utils.mjsscript7.3 KB
scripts/validate-design-library-output.mjsscript3.1 KB
scripts/validate-intent.mjsscript7.3 KB
scripts/validate-token-input.mjsscript4.0 KB
scripts/validate-uikit-plan.mjsscript13.6 KB
skill-release-manifest.jsonconfig202 B
workflows/create-from-scratch.mdmarkdown22.5 KB
workflows/create-from-structured-spec.mdmarkdown17.5 KB
workflows/create-library.mdmarkdown53.0 KB
workflows/expand-components.mdmarkdown9.0 KB
workflows/generate-additional-kit.mdmarkdown4.9 KB
workflows/refine-library.mdmarkdown9.7 KB

aesthetics/self-check.md

View on GitHub
# Aesthetic Self-Check Checklist

This checklist runs after every page is generated. It is the post-generation gate that makes the §0 North Star and §8 Anti-AI-Slop blacklist in `aesthetics/index.md` enforceable.

Run three passes top-to-bottom. Any failure must be fixed before declaring completion. "Fix later" is not allowed.

- **Pass 1 — Design Review** confirms the page is directionally right.
- **Pass 2 — Aesthetic Lifting** confirms the page hits the visual lift bar.
- **Pass 3 — Infrastructure** confirms the page survives real production conditions.

---

## Pass 1 — Design Review

Before detailed checks, confirm the page passes this review. If two or more checks fail, stop and revise.

1. **Starts from the right context** — the page reflects the actual product, brand, design system, and business scenario. If it feels generic or interchangeable with another product, it is not ready.
2. **Has clear hierarchy** — there is a single instant focal point, readable structure, intentional rhythm. If it feels flat, noisy, or confused, it is not ready.
3. **Uses purposeful structure** — structure comes from composition, spacing, typography, and imagery. If it depends on filler, repeated containers, or decorative noise, it is not ready.
4. **Fits the scenario** — the layout and density fit the real business + user scenario. If it feels artificial, generic, or disconnected from real use, it is not ready.
5. **Holds up in real use** — coherent across states, edge cases, responsiveness, accessibility. If it only works as a polished screenshot, it is not ready.

---

## Pass 2 — Aesthetic Lifting Checklist

These checks correspond directly to `aesthetics/index.md`. Each line is a binary pass / fail.

### A. North Star (`index.md` §0)

- [ ] Information focus is identifiable within 1 second.
- [ ] Rhythm separates primary, secondary, tertiary content via whitespace, scale, composition.
- [ ] Detail is restrained: radius, shadow, border, decoration each follow a single system.
- [ ] Believability is real: copy, data, imagery match the business; no Lorem; no fabricated metrics.
- [ ] No AI smell: no rainbow gradients, no colored-icon-tile feature walls, no neon, no particles.

### B. System Discipline (`index.md` §1)

- [ ] All values come from tokens / brand-prefixed CSS variables; no inline raw HEX / RGB.
- [ ] Spacing follows 8pt grid; section vertical padding meets desktop ≥ 80px / mobile ≥ 48px.
- [ ] ≤ 4 type sizes per screen with clear jumps. 14 / 15 / 16 in the same view does not appear.
- [ ] Color count ≤ 6 per page; accent area ≤ 5%; no 3+ stop gradients; no rainbow strokes.
- [ ] ≤ 2 radius tiers per screen; only the three approved shadow tiers; border + shadow not stacked on the same element.
- [ ] Motion uses only transform / opacity / clip-path / filter; no `transition: all`; `prefers-reduced-motion` downgraded to 0.01ms; touch devices have hover transitions disabled.

### C. Composition (`index.md` §2)

- [ ] Page picks one explicit rhythm pattern from §2.1 (editorial / stacked / sticky+flow / asymmetric / scenes); default Hero + 3-column Feature + CTA is forbidden.
- [ ] Whitespace discipline holds (heading → body ≥ 24px; safe inset met).
- [ ] Grid is explicit: desktop 12 col / tablet 8 col / mobile single column.
- [ ] No card disease: cards carry information value, equal-height in the same block, nesting ≤ 2 levels.

### D. Detail Treatment (`index.md` §3, §4, §5, §6)

- [ ] Default left-align; centered only in legitimate ceremonial use (hero / pull quote / numeric hero / poster).
- [ ] Title vs subtitle differs on at least 2 of size / weight / color.
- [ ] Tabular Nums applied to all numeric content.
- [ ] ≤ 2 type families per screen.
- [ ] One icon library, single stroke width, fixed size set.
- [ ] No "colored rounded square + white Lucide icon" feature grid.
- [ ] Floating widgets (when used) follow §6.13 (≥ 2 around hero, ±2°–4° rotation, real data, no glass).
- [ ] Device mocks (when used) follow §6.16 (single radius tier inside, real business surface, no system UI mimicry).
- [ ] In-app surface (when used) follows §6.17 (homologous radius; single accent halo; real proportions).
- [ ] Store badges (when used) follow §6.18 (height 36–44px, two-line type, single icon color).

### E. Believability

- [ ] All copy is business-specific; no "Insert title here", no "Lorem", no "示例标题".
- [ ] All metrics either come from user input or are absent. Fabricated quantified claims ("10x faster", "99.9% uptime") are not present.
- [ ] All avatars are real photos (or abstract monogram for B2B / government). No initials-on-color circles.
- [ ] All product / object proportions follow real-world ratios (credit cards 1.586:1, products 1:1 / 4:5, content covers 16:10 / 16:9).

### F. Anti-AI-Slop (`index.md` §8)

This list mirrors §8. Any single hit fails the gate.

- [ ] No rainbow / multi-stop gradient backgrounds.
- [ ] No colored rounded tile + white Lucide icon Feature Grid.
- [ ] No "left 4px colored bar + rounded card" alert ornament used as decoration.
- [ ] No glow / neon / holographic halos.
- [ ] No particle noise / star sparkles / floating geometric particles in the background.
- [ ] No purple-blue-pink trio without business meaning.
- [ ] No centered hero stack: gradient title + dual CTA + 3-column Feature.
- [ ] No three equal feature cards as the dominant first content block after the hero unless the business explicitly requires equal comparison.
- [ ] No hero / first-screen pill or tag overload (> 5 pills/tags without real information value).
- [ ] No cards-inside-cards-inside-cards: consecutive visible card layers where each layer has background, border, or radius.
- [ ] No glass morphism + inner shadow + heavy blur stacked together.
- [ ] No "data-feel" charts (bars without scale or label).
- [ ] No ≥ 3 radius tiers or ≥ 3 shadow specs in the same screen.
- [ ] No mobile hero with single centered phone surrounded by emoji / dots / floating geometry.
- [ ] No in-screen UI mimicking system surfaces (Settings / Calculator / clock wallpaper).
- [ ] No emoji as functional icon (sparkles/rocket/target/lightning); use Lucide instead.
- [ ] No Tailwind default accent colors (`#6366f1`, `#8b5cf6`, `#3b82f6`) used as primary brand accent.
- [ ] No fabricated quantified claims not provided by the user.

**Design soul test**: A stranger seeing one screenshot can identify which product the page is for. If they cannot, the page is a template — fix it.

### G. Chinese Environment (`index.md` §9)

- [ ] Primary heading ≤ 20 Chinese characters; button copy ≤ 6 chars; tab copy ≤ 4 chars.
- [ ] No CJK letter-spacing > 0.05em.
- [ ] No text overlap, no clipping, no character-by-character vertical wrap.
- [ ] CJK + Latin uses separate font families.
- [ ] No narrow containers, dense side-by-side, or pill-heavy patterns that cramp Chinese.
- [ ] CJK heading in split-column (< 60% width) uses H1 scale, never Display.
- [ ] CJK headings use both `text-wrap: balance` and `word-break: keep-all`.

### H. Scenario Specifics (`index.md` §7, §11)

When the page is a Hero / Showcase / Landing surface:

- [ ] Exactly one Pattern from §11 (P-1 / P-2 / P-3 / P-4 / P-5) is used as the Hero.
- [ ] Pattern constraints fully met (e.g. P-1 KPI strip is 1px line dividers; P-5 dual phones each show different stories; P-5 ≤ 980px viewport downgrades to single phone, rotation removed).
- [ ] If business is unsuited to any P-x (serious government, medical, annual report), page falls back to §2.1 rhythm with restrained UI Kit; North Star and the blacklist still pass.

When the page is a mobile App Showcase:

- [ ] Stage uses §6.16 + §11.5 P-5; outer device halo restricted to §6.16 shadow.
- [ ] In-screen content is real business (balance / order / cover / task / notice).
- [ ] ≥ 2 store badges per §6.18.
- [ ] Floats: 1–3, real business info, never littered.

When the page is a portfolio / personal site:

- [ ] Hero is Display + a single positioning sentence; no triple-tag list.
- [ ] Project list uses uniform thumbnail aspect; project detail covers background / role / process / outcome.

When the page is a graphic / print surface:

- [ ] Explicit grid (≥ 6 columns) and baseline grid (multiples of 4 / 8).
- [ ] Primary information ≥ 60% of visual area; whitespace ≥ 8% of short edge.

### I. Dark Mode (when `<html class="dark">`)

- [ ] Background is NOT pure #000000; uses `--bg` in #0B0B0F–#14141A range.
- [ ] Text is NOT pure #FFFFFF; uses `--ink` ≤ #E8E8EC.
- [ ] Cards use border (`rgba(255,255,255,.06)`) or elevated surface, not light-mode shadow values.
- [ ] Images have `brightness(.92) saturate(.92)` or equivalent darkening.
- [ ] Contrast ratio ≥ 4.5:1 tested against `--surface` (not `--bg`).

Deep read trigger: If 2+ items above fail or are uncertain, read `aesthetics/dark-mode.md`.

### J. Footer

- [ ] Multi-page project has consistent footer on every page.
- [ ] Footer uses `<footer>` semantic element.
- [ ] Footer links are real (not "Link 1"); ≤ 5 social icons if present.
- [ ] Mobile: footer columns stack single-file, not cramped side-by-side.

Deep read trigger: If footer is missing or malformed, read `aesthetics/navigation-footer.md`.

---

## Pass 3 — Infrastructure Checks

These items ensure the page's visual + style infrastructure is complete. Missing any single item causes partial or total style loss in production.

### Token Compliance

This check takes precedence over all others. A page that fails token compliance is unqualified regardless of visual quality.

- All colors, fonts, radii, and shadows must come from brand-prefixed CSS variables.
- Same semantic role must use the same token across the page.
- No hardcoded values outside the brand system.

[FORBIDDEN] Tailwind named color classes (`bg-blue-500`, `text-gray-200`), hard-coded HEX/RGB (`bg-[#5B4FE8]`), radius classes outside brand tiers (`rounded-2xl`, `rounded-3xl`).

**Quick text-search self-check** — any hit on the generated HTML is a violation:

| Search Pattern | What It Catches |
|--------------|----------------|
| `bg-red-`, `bg-blue-`, `bg-green-`, `bg-gray-`, `bg-slate-`, `bg-zinc-`, `bg-neutral-`, `bg-stone-`, etc. | Tailwind named colors in backgrounds |
| `text-red-`, `text-blue-`, `text-green-`, etc. | Tailwind named colors in text |
| `border-red-`, `border-blue-`, etc. | Tailwind named colors in borders |
| `bg-[#`, `text-[#`, `border-[#` | Hard-coded color values |
| `rounded-[` | Hard-coded radius values |
| `rounded-2xl`, `rounded-3xl` | Radius classes outside brand tiers |
| `#6366f1`, `#8b5cf6`, `#3b82f6` | Tailwind default accents masquerading as brand color |

### Library Conformance (Required when Design Library exists)

> This check verifies that the page implementation properly consumed and followed the Design Library's component documentation and UI Kit layout patterns. **Skip this section only when no Design Library exists.**

#### Component Doc Compliance

| Detection Signal | Design Goal |
|---------|---------|
| A UI element (button, card, table, form, nav) exists on the page, its component doc was assigned, but the implementation does not follow the doc's variant/size/state definitions | When a component doc is assigned, the implementation must match its spec — same variant structure, size options, state handling |
| Component HTML structure significantly differs from the doc's "HTML Reference" section | Implementation must adapt the HTML Reference as its starting point; reimplementing from scratch when a reference exists is [FORBIDDEN] |
| The component uses CSS classes, structures, or patterns not mentioned in the doc when the doc provides explicit guidance | Follow the doc's explicit guidance; only extend beyond it when the doc does not cover a specific need |

#### UI Kit Layout Compliance

| Detection Signal | Design Goal |
|---------|---------|
| Page layout architecture (section order, component composition, spacing rhythm) has no resemblance to the assigned UI Kit | The Kit's layout patterns serve as the baseline; deviations should be intentional improvements, not divergent reimaginations |
| Kit demonstrates a specific navigation pattern (sidebar, top-nav, bottom-tab) but the page uses a completely different one without justification | Navigation patterns should follow Kit precedent unless page requirements specifically demand otherwise |
| Kit uses a consistent component composition pattern (e.g., card structure) but the page invents a different pattern | Prefer Kit-demonstrated patterns for consistency with the Library's visual language |

#### Quick Self-check Method

Before declaring the page complete, verify:
1. For each assigned component doc: did I read it? Does my implementation match its variants/sizes/states?
2. For the assigned UI Kit: did I read it? Does my page layout echo its demonstrated patterns?
3. Can I point to specific elements in my HTML that were adapted from component HTML References?

**If the answer to any question is "no" and the corresponding Library resource was assigned — the page is non-conformant and must be revised.**

### Components, Charts, and Graphics

- Prefer mature systems (§6 UI Kit, shadcn, Lucide, stable open source) before inventing new ones.
- Single chart series uses `--brand`; multi-series steps brand lightness; grid `--line`; one Tooltip on hover (no crosshair + tooltip + marker triple stack).
- One icon library per page; single stroke width; fixed size set.

### Typography

- Hierarchy is clear (size + spacing + alignment + contrast before weight).
- Headings, body, supporting text do not collapse into one visual level.
- Chinese text remains restrained, readable, structurally stable.
- Numbers use Tabular Nums.

[FORBIDDEN] Inter / Roboto / Arial / Poppins / DM Sans / Nunito / Quicksand applied as the sole system on every page when a business-tone choice exists per `index.md` §3.1 Font Selection.

### Color and Surface

- Color usage is restrained and consistent.
- Accent appears only where focus or action requires it.
- Backgrounds and surfaces feel continuous, not fragmented; surface depth used for partition before borders.
- No neon, no rainbow, no decorative saturation.

[FORBIDDEN] Blue-purple / neon / high-saturation pink gradients, rainbow gradients, neon-colored blurred light spots.

### Layout and Shape

- Layout has rhythm, hierarchy, and breathing room.
- No repetitive card walls, equal-emphasis layouts, or over-containerization.
- Containers are justified by information value.
- Shape language is consistent and structurally meaningful (≤ 2 radius tiers per screen).
- Navigation is taken out of document flow and spans full viewport width.
- On mobile, every section carries an irreplaceable narrative role; adjacent sections use different layout arrangements.

### Imagery

- Icons and images match the business scenario and page meaning.
- No decorative icon wrappers, no semantically empty imagery, no generic visual filler.
- Image and icon style is consistent within the page.
- Image generation prompts begin with business keywords (not "modern office" / "happy people"), with quality and exclusion keywords appended.

[FORBIDDEN] DOM placeholders instead of real images; colored background wrappers around icons used purely for decoration.

### Motion

- Motion supports hierarchy, feedback, or interaction.
- Subtle and purposeful.
- No decorative motion that distracts from content.

### State and Real Use

- Data surfaces account for loading, empty, error, populated, edge states.
- Forms include validation, submission, recovery.
- Not just the happy path.

### Accessibility Baseline

- Every `<img>` has `alt`.
- Every form input has an associated `<label>`.
- No heading level skips (h1 to h3 is forbidden).
- Buttons and links have accessible names or `aria-label`.
- No `outline: none` without a `:focus-visible` replacement.
- Touch targets ≥ 24×24px.
- Color is not the sole information carrier (status dots have text labels).
- Interactive elements are native (`<button>`, `<a href>`), not `<div onclick>`.

### Style Integrity

> **Applicability**: This section applies ONLY to Tailwind-based page artifacts. UIKit (`ui_kits/*/index.html`, React 18 + external `colors_and_type.css`, zero Tailwind) and `preview/*.html` artifacts MUST skip this section entirely — their head/script contracts are defined by their own templates.

**Required `<head>` elements** — verify each exists exactly once:

| Element | Why It Matters |
|---------|---------------|
| `<script src="...@tailwindcss/browser@4">` | Tailwind CSS runtime — without it, all utility classes are ineffective |
| `<script src="...lucide@1.8.0">` | Lucide Icons CDN — without it, all icons fail to render |
| `<style id="theme-vars">` with `:root { ... }` block | Light mode CSS variable definitions |
| `<style id="theme-vars">` with `.dark { ... }` block | Dark mode CSS variable definitions |
| `@theme inline { ... }` block | Tailwind v4 bridge configuration |
| `@layer base { ... }` block | Base styles (body bg, font, table word-breaking) |
| `lucide.createIcons()` script at `<body>` bottom | Lucide icon initialization |

**Required element attributes:**

| Element | Required Attribute |
|---------|-------------------|
| `<html>` | `class="light"` or `class="dark"` |
| `<html>` | `lang="..."` |
| `<body>` | `min-h-screen font-sans antialiased` |

[FORBIDDEN] Manually rewriting `<head>` content, deleting `<style id="theme-vars">`, modifying the `@theme inline` bridge.

### Metadata Leak

- No node IDs, indices, file paths, or technical identifiers shown as visible text.
- Visible text is business semantics only; canvas / system internals never leak.
- Technical fields belong to DOM attributes or JSON config, never visible text.

### Responsive & Overflow Defense

**Responsive layout:**

- Multi-column layouts must downgrade responsively.
- Image-text side-by-side stacks vertically on mobile, upgrades to side-by-side on desktop.
- No fixed-pixel widths; fluid layout only.
- Images adapt to container width.

**Overflow protection:**

- Tag / badge text stays single line.
- On mobile, auxiliary rounded blocks inside cards take their own line, never sit beside main content.
- KPI numbers and numeric content [FORBIDDEN] from wrapping.
- Table headers stay single line.
- Narrow-column CJK that breaks character-by-character into vertical layout is forbidden.
- Narrow-screen tables provide horizontal scrolling.
- Long text columns limit displayed line count; full content via tooltip.

---

## What to Do When Something Fails

1. **One or two failures**: fix in place; re-run the affected pass section before declaring completion.
2. **Three or more failures in Pass 1 or Pass 2.A / 2.F**: the visual direction is wrong. Stop, re-pick the §2.1 rhythm or §11 Pattern, and regenerate the page. Patching cosmetic details is not enough.
3. **Any Pass 3 Token Compliance failure**: page is unqualified regardless of how it looks. Replace inline values with brand-prefixed variables before any visual review.

---

## Automatable Checks (Future Lint Candidates)

The following checks are amenable to scripting; mark them here for future `lint-artifact` implementation.

| Check | Automation Method | Priority |
|-------|-------------------|----------|
| Tailwind default HEX as accent | grep for `#6366f1` / `#8b5cf6` / `#3b82f6` in HTML | High |
| Emoji as icon | regex for emoji in visible text contexts | High |
| Raw HEX count outside `:root` | count unique color literals | High |
| Hard-coded radius values | grep `rounded-[`, `rounded-2xl`, `rounded-3xl` | High |
| AI-default font as sole family | grep `font-family` for Inter / Roboto / Poppins without companion brand stack | High |
| Type-scale ambiguity | scan for 14 / 15 / 16 px coexisting in the same component | Medium |
| External placeholder image URLs | grep for known placeholder domains | Medium |
| Missing `<head>` elements | verify required scripts / tags exist exactly once | Medium |
| Metadata leak in visible text | grep node IDs, file paths, technical identifiers | Medium |
| Fabricated quantified claims | regex for digit + x or % cross-checked against user-provided data | Medium |

---

## Anti-AI-Slop Severity Grading

> **Scope boundary**: This check applies ONLY to HTML/CSS code quality. Generated image files (`assets/*.jpg`) are **explicitly excluded** from AI-slop inspection — the Agent cannot read binary image content and must not make quality judgments about images based on assumptions. If `GenerateImage` returned success, the image passes this check unconditionally.

> Supplements Pass 2.F with severity levels. Pass 2.F checkboxes catch the pattern; this section grades the severity.

### P0 — Must Fix (any single hit disqualifies the page)

| # | AI-Slop Signal | Detection Method | Fix Direction |
|---|---------------|-----------------|---------------|
| 1 | **Tailwind default color as accent** | Search for `#6366f1`, `#8b5cf6`, `#3b82f6`, `#06b6d4`, `#10b981`, `#f59e0b` or their CSS variable equivalents used as the primary brand accent (not as status colors) | All accent colors must come from brand CSS variables. The fact that indigo-500 "looks nice" is exactly why every AI picks it |
| 2 | **"Trust gradient" in Hero section** | Visual: hero background uses a blue→purple, purple→pink, or blue→cyan gradient that isn't defined in the brand CSS system | Gradients only within same-hue lightness channel; cross-hue gradients must come from brand CSS or be eliminated |
| 3 | **Emoji as functional icons** | Search HTML for emoji characters (✨🚀🎯⚡🔥💡📊💪🎉✅❌⭐) used as feature/section icons | Use Lucide icons or brand icon system. Emoji convey "demo mockup," not "shipping product" |
| 4 | **Font mismatch with brand CSS** | Brand CSS specifies a Serif display font but headings render in Sans-serif (or vice versa) | `font-family` must always resolve to `var(--{prefix}-font-*)`. Never override with a "safer" font |
| 5 | **Rounded card + left color bar** pattern | Cards that have `border-left: 3-4px solid [accent]` + large border-radius — the classic "AI Dashboard tile" | If the brand doesn't explicitly call for this pattern, it is a template artifact. Use surface differentiation (background shade, elevation) instead |
| 6 | **Fabricated metrics** | Page displays quantified claims like "10× faster", "99.9% uptime", "500+ integrations", "Trusted by 10,000+ teams" that weren't provided by the user | All numeric claims must come from user-provided content. When no real data exists, use qualitative copy. (Design Library outputs must NOT contain placeholder markers — SKILL.md invariant #6; only user-facing page drafts outside this skill may leave markers for the user to fill) |
| 7 | **Filler copy** | Search for: "Lorem ipsum", "Feature One/Two/Three", "Your tagline here", "Description goes here", "Coming soon" | All copy must be contextually meaningful. If you don't know the real copy, write realistic placeholder copy derived from the business scenario |

### P1 — Should Fix (accumulated hits indicate template-level output)

| # | AI-Slop Signal | Detection Method |
|---|---------------|-----------------|
| 8 | **Standard section railroad** | Page follows the exact sequence: Hero → Features grid → Social proof → Pricing → FAQ → CTA — with no variation, unique section, or content-specific structure |
| 9 | **External placeholder images** | `src` attributes point to `unsplash.com`, `placehold.co`, `placeholder.com`, `via.placeholder.com`, `picsum.photos` |
| 10 | **Excessive raw HEX values** | More than 12 distinct HEX/RGB/HSL values appear outside `:root` / `<style id="theme-vars">` blocks |
| 11 | **`var(--{prefix}-primary)` overuse** | The primary/accent variable is referenced more than 6 times on a single screen viewport (count all `bg-*`, `text-*`, `border-*` that resolve to the accent) |
| 12 | **Homogeneous 3-column grid** | All feature/benefit sections use identical 3-column card grids with [icon → title → description] structure, no layout variation |
| 13 | **Generic CTA text** | Buttons say "Get Started", "Learn More", "Sign Up Now", "Try Free" without any product-specific language |
| 14 | **system-ui for display text** | Headings ≥ 24px using `font-family: system-ui` or `ui-sans-serif` without a brand-specific font declaration |

### Soul Injection Formula (80/20 Rule)

A well-designed page is **80% proven patterns + 20% unique decisions**. The 20% should live in:

1. **One bold visual decision** — an unusual font pairing, a single strong accent color, an unconventional aspect ratio, an asymmetric layout
2. **Copy micro-interactions** — "Start tracking" beats "Get started"; "See what changed" beats "Learn more"; verbs that reference the actual product action
3. **One memorable micro-interaction** — a button that shifts 2px on press, a card that subtly rotates on hover, a number that counts up on scroll-into-view
4. **One insider detail** — something only a person who has used the product would think to put on the page (specific feature name, workflow shortcut, domain-specific metric)

**Quick self-check**: After page generation, ask: "Which specific element on this page would I remember tomorrow?" If the answer is "nothing" — the 20% is missing.
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 322kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 198kUpdated Claude CodeCodexVerifiedInstall