design-systemlisted

# 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 + brand `CLAUDE.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 1. Gather the brief (ask only what is missing): - Brand name and sector/positioning.