Quickly navigate through the dashboard with your keyboard using the command menu.
Plain instructions, so it works in every AI that reads skills, even pasted into a ChatGPT project. Pick your AI below; we remember it on every skill.
Your AI reads this line to decide when the skill applies. You never have to call it by name.
“Apply production-grade design standards when building or reviewing pages, components, or UI. Use this skill whenever the user asks to build a page, design a component, lay out a section, review the UI, fix the layout, or check design quality. Triggers on build a page, create a component, design a section, hero, card, CTA, layout, review the UI, fix the design, design system, design tokens, spacing, typography scale, button standards, mobile design. Also triggers for any production design decision where contrast, accessibility, spacing, or visual hierarchy matters.”
6 files of instructions.
Production design standards for any web project. Stack-agnostic. Tool-agnostic. Covers tokens, contrast, hierarchy, spacing, mobile rules, and the pre-ship checklist.
This skill complements brand-identity (which defines the visual system) and brand-style-guide (which documents it). This skill is for the day-to-day work of applying those standards in real components and pages.
brand-identity)brand-style-guide)design-system)frontend-component-build)accessibility-audit)If brand tokens are undefined, define a working set first using the template in references/design-tokens-template.md.
Six standards apply to every piece of UI. Hold the line on these and most design problems disappear.
Every project needs tokens defined before any UI gets built. Tokens are the source of truth.
Color tokens (minimum):
Spacing tokens:
Type tokens:
Radius tokens:
Document the tokens once. Reference them everywhere. Hardcoded values are technical debt.
Contrast is not a preference. It is a baseline. A design that fails AA is broken, regardless of how it looks to designers with full vision.
| Element | Required ratio |
|---|---|
| Normal body text | 4.5:1 |
| Large text (18pt regular or 14pt bold) | 3:1 |
| UI components and graphical elements | 3:1 |
Common failures to avoid:
For the math, the contrast checker, and brand-color strategies, see brand-identity/references/contrast-and-accessibility.md.
A well-designed page has a clear scan order. Hierarchy comes from:
Apply hierarchy intentionally. Every visual element should be reachable through the hierarchy. If three things compete for primary attention, none of them wins.
Common failures:
Spacing is what separates a polished layout from a cluttered one.
Rules:
Common failures:
Most users are on mobile. Designing for desktop first guarantees mobile failures.
Standards:
Common failures:
The same thing should look the same everywhere. Variations should be intentional.
Common consistency principles:
Common failures:
references/preship-checklist.md.This skill produces design decisions and review notes more than artifacts. Outputs include:
design-tokens.md or equivalentWhen generating component code (HTML, CSS, framework-specific markup), the SKILL.md remains stack-agnostic. Stack-specific patterns live in reference files.
references/design-tokens-template.md - Template for setting up tokens for any project.references/preship-checklist.md - Final design review checklist before shipping.references/tailwind-patterns.md - Optional. Tailwind-specific component patterns (hero, cards, buttons, data rows) for projects on that stack.Stops the generic AI look. Pushes your AI to pick a bold visual direction and build production-grade pages with real typographic and colour choices.
A design partner for designing, critiquing, auditing and polishing a frontend, including writing a DESIGN.md for your project.
Anti-slop rules for company websites: one idea per screen, restrained type and spacing, the polish of top product sites.
Production-grade standards for building and reviewing pages and sections: hierarchy, spacing, type, CTAs and the details that separate pro work from templates.