design-system
Skill3 starsChanged 5 months agoMITView on GitHub
Generate a unique, production-grade brand design system from a short brief. Use when starting a new site or product, defining or extending design tokens (color, type, spacing, radii, shadows, motion), producing a token file plus Tailwind config plus a brand rules doc plus a storybook, or giving a project a distinct visual identity. Encodes a house DNA and forces per-brand variation so no two systems look alike.
193 other projects use a version of this.
Adopted by
Most recently taken up by
- Rugved1652/skillstheir own version, first seen Nov 16, 2026
- mannobeats/hyper-tastetheir own version, first seen Nov 16, 2026
- irank786/Claude-skillstheir own version, first seen Nov 16, 2026
- david33137/claude-skillstheir own version, first seen Nov 16, 2026
- AndresArreguy/ecc-pi-porttheir own version, first seen Nov 16, 2026
- Vujavujavuja/Stillmotion-onbrandtheir own version, first seen Nov 16, 2026
Used with
Projects with it also use setup-engine, team-level and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
CoralGameSkillsetup-engine
Configure the project's game engine and version. Pins the engine in CLAUDE.md, detects knowledge gaps, and populates engine reference docs via WebSearch when the version is beyond the LLM's training data.
Also in 13 projects that use this
CoralGameSkillteam-level
Orchestrate level design team: level-designer + narrative-director + world-builder + art-director + systems-designer + qa-tester for complete area/level creation.
Also in 12 projects that use this
lilangMaxSkillcreate-stories
Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.
Also in 11 projects that use this
lilangMaxSkillstory-done
End-of-story completion review. Reads the story file, verifies each acceptance criterion against the implementation, checks for GDD/ADR deviations, prompts code review, updates story status to Complete, and surfaces the next ready story from the sprint.
Also in 11 projects that use this
- +2 more from CoralGame
- +6 more from lilangMax
Other versions193 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 193
- nextlevelbuilder/ui-ux-pro-max-skill★ 150ksame name
- getsentry/sentry★ 46ksame name
- Donchitos/Claude-Code-Game-Studios★ 39ksame name
- anthropics/knowledge-work-plugins★ 36ksame name
- ethereum/ethereum-org-website★ 6ksame name
- langwatch/langwatch★ 5ksame name
- joye61/pic-smaller★ 2.9ksame name
- daveebbelaar/bama★ 1.7ksame name
- reatom/reatom★ 1.4ksame name
- microsoft/power-platform-skills★ 1.2ksame name
183 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 176 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 54
Put them in a <project>/design-system/ folder (the LeCoffre pattern).
- Distinctive: line 67
Commit to ONE dominant color and ONE sharp accent.
- Very specific: line 68
Never the purple-on-white gradient.
- Distinctive: line 69
Every color, space, radius, shadow goes through a token.
“Common” is measured: kept by at least 6 in 10 of the 176 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Design System
A factory for brand identities. Given a short brief, it produces a complete, unique design system in the house DNA: a token file, a Tailwind config, a brand rules doc the agent obeys, a storybook, and a human spec. The opposite of a template: the DNA (method and quality bar) stays constant, the output (palette, type, shape, mood) is different every time.
It is the piece that kills the generic look at the source. The fluid skill handles motion, the detector catches slop after the fact, this gives each project an identity from line one.
Built from four hand-made systems: MVP "Liquid Glass" (the structural template), LeCoffre (the delivery format), PLR @plr/ui, and Vigie.
When to use
- Starting a new client site or product and you need its visual identity defined.
- Producing or extending design tokens (color, type, spacing, radii, shadows, motion).
- You want a
tokens.css+ Tailwind config + brandCLAUDE.md+ storybook for a project. - An existing UI feels generic and needs a committed identity.
The two halves
A system here is DNA (constant) plus brand (variable). Get both right.
- The DNA is the house method and quality bar. It never changes. See
reference/dna.md. - The brand is what makes this system unlike any other: palette, type, shape, surface, mood. Derived per project from the brief. This is where you must NOT converge.
init: the workflow
- Gather the brief (ask only what is missing):
- Brand name and sector/positioning.
- Personality, pick an extreme: institutional/refined, editorial, luxury, playful/energetic, techy/precise, brutalist/raw, organic/warm. Half-measures read as generic.
- Light, dark, or both (auto).
- Surface treatment: flat, soft (subtle shadow/relief), or glass (liquid, translucent).
- One anchor or constraint: an existing logo color, a reference you admire, a competitor you must NOT resemble.
- Derive the brand variables (commit, do not hedge):
- Start from the database: pick a palette from
data/palettes.md(100+ committed palettes), a type pairing fromdata/type-pairings.md(50+ distinctive pairings), a style direction fromdata/styles.md, and a layout archetype fromdata/layouts.mdthat fit the brief. Adapt the exact values; never improvise a generic default, and never default to the split-hero-plus-three-cards skeleton. Two clients in the same sector get different picks, including a different page shape. For motion reach intodata/motion-presets.md, for any data display intodata/chart-types.md, and for the build pick a stack fromdata/tech-stacks.md. - Color: one dominant brand hue + one sharp accent + semantic (success/warn/danger) + tuned neutrals. Never pure black. See
reference/color.md. - Type: a distinctive display font paired with a refined body font, self-hosted. Never Inter/Roboto/Arial as the primary. See
reference/typography.md. - Shape: a radii scale (sharp 4 to 8, rounded 12 to 22, or pill) chosen to match the personality.
- Surface/relief: flat, soft-shadow, or glass tokens.
- Motion: the house easings, already in the template (
--ease-out,--spring,--ease-in-out), shared withfluid.
- Start from the database: pick a palette from
- Map to light/dark tokens: decide which tokens invert (bg, surface, text, glass, tints, on-tint) and which hold (brand hues, accent). See
reference/color.md. - Emit the files from
templates/(fill the{{placeholders}}):tokens.css: the source of truth (CSS variables + base classes).tailwind.config.js: same tokens for Tailwind/TanStack sites (omit for CSS-pur projects).CLAUDE.md: the brand rules the agent obeys on every UI task.storybook.html: a live showcase of every token and base component.DESIGN_SYSTEM.md: the human-readable spec. Put them in a<project>/design-system/folder (the LeCoffre pattern).
- Wire it: load the fonts, import
tokens.css(or extend Tailwind), and from then on every color/space/radius isvar(--token), never a raw value.
Stack note (light/dark strategy)
- App with auto theme (like MVP): light by default, dark via
@media (prefers-color-scheme: dark). CSS pur, no Tailwind needed. - Vitrine site with a theme toggle (like LeCoffre, TanStack/Tailwind): dark via
:root[data-theme="dark"]/.dark, plus thetailwind.config.js.
The template carries both, keep the one you use.
Anti-generic rules (non negotiable)
- Commit to ONE dominant color and ONE sharp accent. Timid, evenly spread palettes read as generic. Ration the brand: a thin accent beats a full wash.
- Never the purple-on-white gradient. Never Inter/Roboto/Arial as the primary font. Never pure black, use a tuned near-black.
- Every color, space, radius, shadow goes through a token. No raw hex on text or surface.
- Bespoke SVG over stock icons, zero decorative emoji. (MVP runs a 3-tier icon system: glossy 3D for large elements, duotone gradient-sheen inline, bespoke SVG art for brand marks.)
- Keyboard accessibility is part of premium: a global
:focus-visiblering, defined with:where()so components can override. - Vary every system. Two projects must never share a palette or a type pairing. Do not default to the same fonts each time.
- Distinctive does not mean loud. Refined minimal and bold maximal both work; intentionality is the bar.
Output checklist
- One dominant + one accent, committed, not a timid spread.
- Distinctive type pairing, self-hosted, no generic primary.
- Full token set: color (light + dark), type scale, base-8 spacing, radii, shadows, motion.
- Light and dark both resolve through tokens, both tested.
- No raw hex on text/surface, no #000, no emoji.
- Global
:focus-visible, and a reduced-motion path (CSS and JS). tokens.css+ (tailwind.config.js) +CLAUDE.md+storybook.html+DESIGN_SYSTEM.mdemitted.- Distinct from the last system produced (different palette and type).
- Run the
fluiddetector on the result.
Database (pick from these first)
data/palettes.md: 100+ committed palettes by sector and mood (dominant + accent + neutrals).data/type-pairings.md: 50+ distinctive display + body + mono pairings, never Inter primary.data/styles.md: 53 aesthetic directions with their token tendencies.data/layouts.md: 14 page-shape archetypes (bento, centered editorial, index, full-bleed, single column, broken grid, maximalist type, lineup, sidebar, poster, and more). Pick one per page, vary across pages so two never share a silhouette.data/motion-presets.md: ready-to-use motion recipes in the house easings (reveals, hovers, press, overlays, ambient).data/chart-types.md: 32 chart and data-viz types, which one answers which question, with house data-viz defaults.data/tech-stacks.md: 10 curated build stacks by project type, each wired back to the house tokens and motion.
Reference
reference/rules.md: the hard rules (locks, hero discipline, layout honesty, bans). Read before shipping.reference/dna.md: the constant house DNA.reference/typography.md: choosing a distinctive type pairing.reference/color.md: building a committed palette and the light/dark token map.reference/glass.md: liquid-glass and surface recipes (the actual CSS, plus the shimmer button and card).reference/icons.md: the 3-tier bespoke icon system, with code.templates/:tokens.css,tailwind.config.js,CLAUDE.md,storybook.html.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

