Menu
Generate a composed UI pattern (card layout, list, form section, grid, etc.) using design system primitives
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | ss-pattern |
| description | Generate a composed UI pattern (card layout, list, form section, grid, etc.) using design system primitives |
| argument-hint | [pattern-type] [description] |
| allowed-tools | Read, Write, Edit, Grep, Glob, Bash |
/ss-component/ss-page/ss-flow/ss-tokensPattern type: $0 Description: $ARGUMENTS
mx-6)grid grid-cols-2 gap-4 px-6)flex gap-3 overflow-x-auto scrollbar-hide)Read the design system reference:
CLAUDE.md for conventionscomponents/ui/ for available primitivescomponents/patterns/ for existing patternsCompose the pattern from existing components — DO NOT recreate primitives.
Follow the design system layout rules:
bg-card rounded-2xl p-6 shadow-[var(--shadow-card)]mx-6 for horizontal margintext-foreground font-bold text-[18px] mb-4space-y-3gap-4Use semantic tokens for all visual properties.
Make the pattern a reusable component with props for dynamic content.
The VISUAL gate — render the UI, screenshot it, and score what you actually SEE, not what the code says. Catches the tells that only show up in pixels (dead whitespace, cramping, a hero that doesn't dominate, fonts that didn't load, real rendered color, the squint "does this look AI-made" test) — the things /ss-score can't read from source. Renders empty/loading/error states too, then fixes and re-renders until it passes. Use as the final gate on any screen you can render.
Turn ONE design axis up or down as a coordinated, deterministic transform — "denser", "sharper corners", "more muted", "bolder", "flatter", "livelier". Not a vibe the model reinterprets each time; a defined ramp that moves many tokens together, respects the guardrails (8px grid, a11y floors, single accent, nested-radius), updates the lock, and re-runs the gate. Use this when a human saying "more X" would otherwise get an inconsistent one-off.
Apply a named StyleSeed motion to a component — either one of the 5 personality seeds (Spring/Silk/Snap/Float/Pulse × entrance/exit/hover/press/layout) or a distinctive keyword move from the motion library (toggle-flip, toggle-curtain, reveal-blur, pop-in, shimmer, …). Translates vibe words into framer-motion code from one source of truth.
Score a UI file's design quality 0-100 against StyleSeed's design language — per-category breakdown, the worst offenders, and a prioritized fix list. A quantified version of /ss-review.
Re-style a project to a named aesthetic — swiss, editorial, technical, warm-dtc, minimal-mono, brutalist-lite. A preset is a *coordinate* across the dial axes (radius + density + color + weight + motion) plus a font, accent family, and one signature move — applied coherently as a single identity, written to the lock, and re-gated. This is for mood words ("more editorial") that aren't one axis; for a single axis use /ss-dial.
Build a screen the way the StyleSeed reference demo was built — one command that ENFORCES the full loop (lock the look → build → score → fix to ≥80 → only then show). Use this instead of building UI free-hand; it closes the gap between "knows the rules" and "actually followed them."