Design System Generate Skill
There is a skill for auditing a design system that exists and a skill for
extracting one from a brand that exists. This one is for the case in between:
there is no system, and something ships on Thursday.
The output is not a mood board. It is a set of files an engineer can commit,
with a contrast audit attached to them.
Required Inputs
Ask for these if not provided:
- A name or seed — anything; the product name works. The same seed always
produces the same system, so this is how a design becomes reproducible.
- A brand colour, if one is non-negotiable (
#E4002B and so on). If there
isn't one yet, say so and let it choose.
- Light, dark, or both — default to both.
- A feeling, loosely: editorial, brutalist, glassy, terminal, or playful.
If the user describes it in their own words, map it to the nearest.
- Where it has to land — CSS variables, Tailwind, design tokens, Figma, a
VS Code theme, a deck theme, Storybook. Default to CSS + tokens.
Programmatic Helper
This skill is a thin wrapper around a deterministic generator. Do not invent hex
values — run it.
# Look at one first
npx --yes notugly <seed> --vibe editorial
# Lock a brand colour that is not up for discussion
npx --yes notugly <seed> --brand "#e4002b"
# Write the files
npx --yes notugly export <seed> --brand "#e4002b" --out ./design
npx --yes notugly slides <seed> --out ./deck # .thmx for PowerPoint/Keynote
npx --yes notugly storybook <seed> --out ./stories
# Prove the claim rather than making it
npx --yes notugly audit <seed> --brand "#e4002b"
npx --yes notugly vision <seed> # colour-blind collisions
npx --yes notugly print <seed> # what survives CMYK
export writes ten files: CSS custom properties, a Tailwind config, W3C design
tokens, React and Svelte snippets, a demo page, a loadable Figma plugin, and a
VS Code theme. Runtime cost is zero — it is all static text, so there is no
package to install and nothing to break at 3am.
Zero dependencies and no model call, so it is free to run and gives the same
answer every time.
The Method
Start from the constraint, not the palette. If there is a mandated brand
colour, pass it to --brand and build everything else around it. Generating
a lovely system and then discovering it cannot accommodate the company red is
the most common way this work gets thrown away.
Let the text colour be derived, never chosen. The generator picks each
text colour from its background so that no combination can fail. If you
find yourself hand-picking a hex for body copy, you have left the system.
Check it against the three things nobody checks. Colour-blind collisions
(vision), the CMYK gamut if anything will be printed (print), and the
chart accents if it will ever be a deck (slides warns when two chart series
are indistinguishable).
Ship the audit with the tokens. A design system without a contrast report
is a claim. Paste the audit output into the handoff.
Say what was decided and why. Record the seed and the flags. npx notugly <seed> --vibe <vibe> reproduces the whole thing exactly, which means the
design is a one-line command rather than a folder somebody has to keep.
Output Structure
Design System: [Product Name]
Seed: [seed] · Vibe: [vibe] · Brand locked: [hex or "no"]
Reproduce: npx notugly [seed] --vibe [vibe] [--brand #hex]
Palette
| Role |
Colour |
Hex |
Name |
On background |
Verdict |
| Background |
▪ |
#ffffff |
Paper |
— |
— |
| Body text |
▪ |
#020404 |
Soot |
20.55:1 |
AAA |
| Brand |
▪ |
#004054 |
Navy |
11.28:1 |
AAA |
Every ratio above is computed, not estimated.
Type
Headings: [family] · Body: [family] · Scale: [ratio] ([name])
[The size ladder, in px.]
Spacing, radius, elevation
[The 4px grid, the radius set, and the five elevation levels.]
What was checked
Files produced
[The list from export, with byte counts, and the runtime cost line.]
Open decisions for a human
[Anything the generator cannot decide: illustration style, photography
direction, motion beyond the presets, iconography.]
Quality Checks
- Did you run it, or describe it? Every hex in the output must come from the
tool. A plausible palette written by hand is exactly what this skill exists to
replace.
- Is the seed recorded? Without it the design is not reproducible and the
next person starts over.
- Did the brand colour survive? If the user gave one,
--brand must be in
the reproduce command.
- Is the audit attached? Not "it meets AA" — the actual ratios.
- Are the open decisions listed? A generator cannot choose an illustration
style. Pretending otherwise is how these documents lose credibility.
Anti-Patterns
- Inventing hex values. The whole point is that these are computed.
- Claiming AA without a number. "Accessible" is a marketing word; "4.52:1"
is a fact.
- Generating a system when one already exists. If the product has a design
system, use [[design-system-audit]]. If it has a brand but no system, use
[[brand-guidelines]] to extract first, then pass the result in via
--brand.
- Shipping the light theme only. Dark mode is where elevation and contrast
break, and it is cheaper to check now than to retrofit.
- Treating the vibe as the deliverable. The vibe is a starting point. The
deliverable is the token file and the audit.
Example Trigger Phrases
- "We need a design system by Thursday"
- "Pick a colour palette for [product]"
- "Build a starter theme around our brand red"
- "Generate design tokens for the new app"
- "Give me a Tailwind config that passes accessibility"
- "Make a deck theme that matches our product"
1---2name: design-system-generate3description: "Generate a complete, accessibility-checked design system from scratch — colour ramps, type scale, spacing, elevation, and exports for CSS, Tailwind, design tokens, Figma, VS Code and PowerPoint. Use when asked to create a design system, pick a colour palette, build a starter theme, produce design tokens for a new product, or apply an existing brand colour to a full system. For auditing a system that already exists use design-system-audit; for extracting one from a live site use brand-guidelines."4disable-model-invocation: true # skill-optimizer5metadata:6 source: https://skillmd.com/skills/slipcast-dev/design-system-generate7---89# Design System Generate Skill1011There is a skill for auditing a design system that exists and a skill for12extracting one from a brand that exists. This one is for the case in between:13**there is no system, and something ships on Thursday.**1415The output is not a mood board. It is a set of files an engineer can commit,16with a contrast audit attached to them.1718## Required Inputs1920Ask for these if not provided:2122- **A name or seed** — anything; the product name works. The same seed always23 produces the same system, so this is how a design becomes reproducible.24- **A brand colour**, if one is non-negotiable (`#E4002B` and so on). If there25 isn't one yet, say so and let it choose.26- **Light, dark, or both** — default to both.27- **A feeling**, loosely: editorial, brutalist, glassy, terminal, or playful.28 If the user describes it in their own words, map it to the nearest.29- **Where it has to land** — CSS variables, Tailwind, design tokens, Figma, a30 VS Code theme, a deck theme, Storybook. Default to CSS + tokens.3132## Programmatic Helper3334This skill is a thin wrapper around a deterministic generator. Do not invent hex35values — run it.3637```bash38# Look at one first39npx --yes notugly <seed> --vibe editorial4041# Lock a brand colour that is not up for discussion42npx --yes notugly <seed> --brand "#e4002b"4344# Write the files45npx --yes notugly export <seed> --brand "#e4002b" --out ./design46npx --yes notugly slides <seed> --out ./deck # .thmx for PowerPoint/Keynote47npx --yes notugly storybook <seed> --out ./stories4849# Prove the claim rather than making it50npx --yes notugly audit <seed> --brand "#e4002b"51npx --yes notugly vision <seed> # colour-blind collisions52npx --yes notugly print <seed> # what survives CMYK53```5455`export` writes ten files: CSS custom properties, a Tailwind config, W3C design56tokens, React and Svelte snippets, a demo page, a loadable Figma plugin, and a57VS Code theme. **Runtime cost is zero** — it is all static text, so there is no58package to install and nothing to break at 3am.5960Zero dependencies and **no model call**, so it is free to run and gives the same61answer every time.6263## The Method64651. **Start from the constraint, not the palette.** If there is a mandated brand66 colour, pass it to `--brand` and build everything else around it. Generating67 a lovely system and then discovering it cannot accommodate the company red is68 the most common way this work gets thrown away.69702. **Let the text colour be derived, never chosen.** The generator picks each71 text colour *from* its background so that no combination can fail. If you72 find yourself hand-picking a hex for body copy, you have left the system.73743. **Check it against the three things nobody checks.** Colour-blind collisions75 (`vision`), the CMYK gamut if anything will be printed (`print`), and the76 chart accents if it will ever be a deck (`slides` warns when two chart series77 are indistinguishable).78794. **Ship the audit with the tokens.** A design system without a contrast report80 is a claim. Paste the `audit` output into the handoff.81825. **Say what was decided and why.** Record the seed and the flags. `npx notugly83 <seed> --vibe <vibe>` reproduces the whole thing exactly, which means the84 design is a one-line command rather than a folder somebody has to keep.8586## Output Structure8788---8990# Design System: [Product Name]9192**Seed:** `[seed]` · **Vibe:** [vibe] · **Brand locked:** [hex or "no"]93**Reproduce:** `npx notugly [seed] --vibe [vibe] [--brand #hex]`9495## Palette9697| Role | Colour | Hex | Name | On background | Verdict |98|---|---|---|---|---|---|99| Background | ▪ | `#ffffff` | Paper | — | — |100| Body text | ▪ | `#020404` | Soot | 20.55:1 | AAA |101| Brand | ▪ | `#004054` | Navy | 11.28:1 | AAA |102103*Every ratio above is computed, not estimated.*104105## Type106107**Headings:** [family] · **Body:** [family] · **Scale:** [ratio] ([name])108[The size ladder, in px.]109110## Spacing, radius, elevation111112[The 4px grid, the radius set, and the five elevation levels.]113114## What was checked115116- [ ] Every text pairing clears WCAG AA — *weakest: X:1*117- [ ] No two colours merge under any simulated colour vision deficiency118- [ ] Every colour is inside the CMYK gamut *(if printing)*119- [ ] All six chart accents are distinguishable *(if there will be decks)*120121## Files produced122123[The list from `export`, with byte counts, and the runtime cost line.]124125## Open decisions for a human126127[Anything the generator cannot decide: illustration style, photography128direction, motion beyond the presets, iconography.]129130---131132## Quality Checks133134- **Did you run it, or describe it?** Every hex in the output must come from the135 tool. A plausible palette written by hand is exactly what this skill exists to136 replace.137- **Is the seed recorded?** Without it the design is not reproducible and the138 next person starts over.139- **Did the brand colour survive?** If the user gave one, `--brand` must be in140 the reproduce command.141- **Is the audit attached?** Not "it meets AA" — the actual ratios.142- **Are the open decisions listed?** A generator cannot choose an illustration143 style. Pretending otherwise is how these documents lose credibility.144145## Anti-Patterns146147- **Inventing hex values.** The whole point is that these are computed.148- **Claiming AA without a number.** "Accessible" is a marketing word; "4.52:1"149 is a fact.150- **Generating a system when one already exists.** If the product has a design151 system, use [[design-system-audit]]. If it has a brand but no system, use152 [[brand-guidelines]] to extract first, then pass the result in via `--brand`.153- **Shipping the light theme only.** Dark mode is where elevation and contrast154 break, and it is cheaper to check now than to retrofit.155- **Treating the vibe as the deliverable.** The vibe is a starting point. The156 deliverable is the token file and the audit.157158## Example Trigger Phrases159160- "We need a design system by Thursday"161- "Pick a colour palette for [product]"162- "Build a starter theme around our brand red"163- "Generate design tokens for the new app"164- "Give me a Tailwind config that passes accessibility"165- "Make a deck theme that matches our product"