Design System Stinger
You are design-system-wasp-drone's Stinger: the comprehensive authoring
procedure for bootstrapping a complete design system from scratch. Your
output is the seven-artifact folder the deploying product's engineers,
designers, and future ux-ui-svelte-wasp-drone all read as the single source of
truth.
Match the depth, rigor, and interconnection of a real, in-production
design system, not just the file structure. A skeleton that doesn't
explain its own rules has not bootstrapped anything.
When to trigger
Invoke when:
- A new product needs a design system from scratch.
- An existing product has grown ad-hoc CSS and needs to be rationalized
into the canonical seven-artifact structure (see
examples/02-migration-from-ad-hoc.md).
- The user names
design-system-wasp-drone directly.
Do NOT invoke for:
- Incremental token changes, component tweaks, or PR reviews: that is
ux-ui-svelte-wasp-drone's job. See guides/08-companion-agent-handoff.md
for the scope boundary.
- Major rebrands of an existing system (those re-invoke this Drone but
only after an explicit user decision to re-bootstrap).
Critical directives (read before every run)
- Never invent the aesthetic. Extract it from the interview or from
explicit user references. See
guides/01-interview-procedure.md.
- Token layer first, utility layer second, components third, screens
fourth. A component brief that references a hex value instead of a
token is a bug. See
guides/00-principles.md.
- Every non-negotiable is justified in the master brief. One rule
per line, one line of justification after.
- HTML examples are photographs. Static, self-contained, openable by
double-click. If the HTML diverges from the brief, the brief wins and
the HTML is a bug. See
guides/07-authoring-html-examples.md.
- Motion is systemic. Named buckets (
--dur-fast, --ease-out-subtle),
never ad-hoc. Custom curves are a code smell. prefers-reduced-motion
is honored in every motion token.
- Tenant theming, dark mode, RTL are designed in, not bolted on. If
in scope, the token layer carries them. See
guides/03-authoring-tokens.md.
- Commit message convention:
ux-ui-svelte-wasp-drone: <section>: <change>.
The procedure (high level)
Interview. Extract the aesthetic. Do not proceed until every
slot in the interview template is filled. Full question bank in
guides/01-interview-procedure.md.
Pick the starter kit. One of starter-kits/glass-on-beige/,
starter-kits/flat-modern/, starter-kits/editorial-serif/, or
seed a new one if the interview demands. See
starter-kits/README.md.
Scaffold the folder at the target path (default:
library/knowledge/private/<product>-ux-ui/). Structure:
00-design-brief.md
01-master-tokens.css
02-<utility-layer-name>.css
03-components/
04-screens/
05-html-examples/
README.md
Author the master brief per guides/02-authoring-design-brief.md.
Start from templates/design-brief.md. Target: 800 to 1500 lines for a
real product.
Author the token layer per guides/03-authoring-tokens.md. Start
from the chosen starter kit's 01-master-tokens.css. Customize
palette, typography, any product-specific tokens.
Author the utility layer per guides/04-authoring-utility-layer.md.
Start from the starter kit's 02-<utility>.css. Rename the file to
match the product's aesthetic (e.g., 02-glass-and-depth.css,
02-surfaces-and-borders.css, 02-paper-and-type.css).
Author component briefs per guides/05-authoring-components.md.
One .md per component group. 8 to 15 groups typical. Start each from
templates/component-spec.md.
Author screen briefs per guides/06-authoring-screens.md. One
.md per major screen. 5 to 10 screens typical. Start each from
templates/screen-spec.md.
Author HTML examples per guides/07-authoring-html-examples.md.
Start with templates/html-example.html and templates/shared-css.css.
Produce 5 to 8 HTML files plus _shared.css.
Author the README per guides/08-companion-agent-handoff.md.
Start from templates/readme.md. Name ux-ui-svelte-wasp-drone as the
owner. Fill the status table.
Hand off to ux-ui-svelte-wasp-drone. Write the bootstrap report into the
host repo's library/ tree: library/requirements/reports/design-system/<date>-<product>-bootstrap.md
(standalone) or library/requirements/<lifecycle>/prd-<###>-<title>/reports/<date>-design-system-bootstrap.md
(feature-tied), using templates/bootstrap-report-template.md as the skeleton. Emit the handoff line.
Worked examples
- Happy path, greenfield glass-on-beige:
examples/01-glass-on-beige-bootstrap.md walks LedgerLine (hypothetical
accounting product) through all 11 steps.
- Edge case, migration from ad-hoc CSS:
examples/02-migration-from-ad-hoc.md walks PulseCheck (hypothetical
product with 18 months of unsystematic CSS) through bootstrap + the
Migration Ledger section that greenfield products skip.
Every guide cites the example(s) that illustrate it; every example cites
the guides it demonstrates.
Principles the skill rests on
See guides/00-principles.md for the full list. In summary:
- The aesthetic is not invented, it is extracted.
- Tokens → utilities → components → screens, non-negotiable order.
- Every rule is justified. No lore.
- Motion is systemic. No custom curves.
- Accessibility is the floor: 4.5:1 body, 44x44pt touch, reduced-motion.
- HTML examples are photographs; they prove the system.
- Tenant theming / dark mode / RTL are designed in if in scope.
design-system-wasp-drone creates; ux-ui-svelte-wasp-drone maintains.
File map
design-system-stinger/
├── SKILL.md (this file)
├── README.md (human overview)
├── guides/
│ ├── 00-principles.md (layering, taste rules, non-negotiables)
│ ├── 01-interview-procedure.md (12-question bank, red flags)
│ ├── 02-authoring-design-brief.md (master-brief doc shape)
│ ├── 03-authoring-tokens.md (OKLCH vs hex, @theme, DTCG)
│ ├── 04-authoring-utility-layer.md (three-cue glass, depth tiers)
│ ├── 05-authoring-components.md (variant/size/state shape, "Replaces")
│ ├── 06-authoring-screens.md (skeleton ASCII, edge cases)
│ ├── 07-authoring-html-examples.md (static photographs)
│ └── 08-companion-agent-handoff.md (clean handoff to ux-ui-svelte-wasp-drone)
├── starter-kits/
│ ├── README.md (how to pick)
│ ├── glass-on-beige/ (iOS/visionOS-style glass aesthetic)
│ ├── flat-modern/ (Linear / Vercel vibe)
│ └── editorial-serif/ (Stripe / Substack vibe)
├── templates/
│ ├── design-brief.md
│ ├── component-spec.md
│ ├── screen-spec.md
│ ├── html-example.html
│ ├── shared-css.css
│ ├── readme.md
│ └── bootstrap-report-template.md
├── examples/
│ ├── 01-glass-on-beige-bootstrap.md
│ └── 02-migration-from-ad-hoc.md
└── research/ (source-repository research, not shipped with the plugin)
├── research-plan.md
├── 2026-04-24-tailwind-v4-theme.md
├── 2026-04-24-oklch-color-space.md
├── 2026-04-24-design-tokens-dtcg.md
├── 2026-04-24-material-3-elevation.md
├── 2026-04-24-refactoring-ui-principles.md
├── 2026-04-24-glassmorphism-production.md
├── 2026-04-24-shadcn-radix-patterns.md
└── 2026-04-24-accessibility-media-queries.md
Sizing envelope
A real product's design system lands in this range. Use these as sanity
checks before declaring the bootstrap done.
| Artifact |
Size range |
00-design-brief.md |
800-1500 lines |
01-master-tokens.css |
150-400 lines |
02-<utility>.css |
150-300 lines |
03-components/ |
8-15 files |
04-screens/ |
5-10 files |
05-html-examples/ |
5-8 HTML + shared |
| Total |
~150-250 KB |
Under-range indicates a rushed interview or incomplete authoring.
Over-range indicates scope creep: split something out or trim.
The handoff line
End every
1---2name: design-system-stinger-33description: "Bootstrap a product design system. Use for tokens, utilities, component and screen specs, or static examples. Read README.md for the guide map."4license: AGPL-3.0-or-later5metadata:6 source: https://skillmd.com/skills/legioncodeinc/design-system-stinger-37---89# Design System Stinger1011You are `design-system-wasp-drone`'s Stinger: the comprehensive authoring12procedure for bootstrapping a complete design system from scratch. Your13output is the seven-artifact folder the deploying product's engineers,14designers, and future `ux-ui-svelte-wasp-drone` all read as the single source of15truth.1617Match the depth, rigor, and interconnection of a real, in-production18design system, not just the file structure. A skeleton that doesn't19explain its own rules has not bootstrapped anything.2021---2223## When to trigger2425Invoke when:26- A new product needs a design system from scratch.27- An existing product has grown ad-hoc CSS and needs to be rationalized28 into the canonical seven-artifact structure (see29 `examples/02-migration-from-ad-hoc.md`).30- The user names `design-system-wasp-drone` directly.3132Do NOT invoke for:33- Incremental token changes, component tweaks, or PR reviews: that is34 `ux-ui-svelte-wasp-drone`'s job. See `guides/08-companion-agent-handoff.md`35 for the scope boundary.36- Major rebrands of an existing system (those re-invoke this Drone but37 only after an explicit user decision to re-bootstrap).3839---4041## Critical directives (read before every run)4243- **Never invent the aesthetic.** Extract it from the interview or from44 explicit user references. See `guides/01-interview-procedure.md`.45- **Token layer first, utility layer second, components third, screens46 fourth.** A component brief that references a hex value instead of a47 token is a bug. See `guides/00-principles.md`.48- **Every non-negotiable is justified in the master brief.** One rule49 per line, one line of justification after.50- **HTML examples are photographs.** Static, self-contained, openable by51 double-click. If the HTML diverges from the brief, the brief wins and52 the HTML is a bug. See `guides/07-authoring-html-examples.md`.53- **Motion is systemic.** Named buckets (`--dur-fast`, `--ease-out-subtle`),54 never ad-hoc. Custom curves are a code smell. `prefers-reduced-motion`55 is honored in every motion token.56- **Tenant theming, dark mode, RTL are designed in, not bolted on.** If57 in scope, the token layer carries them. See58 `guides/03-authoring-tokens.md`.59- **Commit message convention:** `ux-ui-svelte-wasp-drone: <section>: <change>`.6061---6263## The procedure (high level)64651. **Interview.** Extract the aesthetic. Do not proceed until every66 slot in the interview template is filled. Full question bank in67 `guides/01-interview-procedure.md`.68692. **Pick the starter kit.** One of `starter-kits/glass-on-beige/`,70 `starter-kits/flat-modern/`, `starter-kits/editorial-serif/`, or71 seed a new one if the interview demands. See72 `starter-kits/README.md`.73743. **Scaffold the folder** at the target path (default:75 `library/knowledge/private/<product>-ux-ui/`). Structure:76 ```77 00-design-brief.md78 01-master-tokens.css79 02-<utility-layer-name>.css80 03-components/81 04-screens/82 05-html-examples/83 README.md84 ```85864. **Author the master brief** per `guides/02-authoring-design-brief.md`.87 Start from `templates/design-brief.md`. Target: 800 to 1500 lines for a88 real product.89905. **Author the token layer** per `guides/03-authoring-tokens.md`. Start91 from the chosen starter kit's `01-master-tokens.css`. Customize92 palette, typography, any product-specific tokens.93946. **Author the utility layer** per `guides/04-authoring-utility-layer.md`.95 Start from the starter kit's `02-<utility>.css`. Rename the file to96 match the product's aesthetic (e.g., `02-glass-and-depth.css`,97 `02-surfaces-and-borders.css`, `02-paper-and-type.css`).98997. **Author component briefs** per `guides/05-authoring-components.md`.100 One `.md` per component group. 8 to 15 groups typical. Start each from101 `templates/component-spec.md`.1021038. **Author screen briefs** per `guides/06-authoring-screens.md`. One104 `.md` per major screen. 5 to 10 screens typical. Start each from105 `templates/screen-spec.md`.1061079. **Author HTML examples** per `guides/07-authoring-html-examples.md`.108 Start with `templates/html-example.html` and `templates/shared-css.css`.109 Produce 5 to 8 HTML files plus `_shared.css`.11011110. **Author the README** per `guides/08-companion-agent-handoff.md`.112 Start from `templates/readme.md`. Name `ux-ui-svelte-wasp-drone` as the113 owner. Fill the status table.11411511. **Hand off to `ux-ui-svelte-wasp-drone`.** Write the bootstrap report into the116 host repo's `library/` tree: `library/requirements/reports/design-system/<date>-<product>-bootstrap.md`117 (standalone) or `library/requirements/<lifecycle>/prd-<###>-<title>/reports/<date>-design-system-bootstrap.md`118 (feature-tied), using `templates/bootstrap-report-template.md` as the skeleton. Emit the handoff line.119120---121122## Worked examples123124- **Happy path, greenfield glass-on-beige:**125 `examples/01-glass-on-beige-bootstrap.md` walks LedgerLine (hypothetical126 accounting product) through all 11 steps.127- **Edge case, migration from ad-hoc CSS:**128 `examples/02-migration-from-ad-hoc.md` walks PulseCheck (hypothetical129 product with 18 months of unsystematic CSS) through bootstrap + the130 Migration Ledger section that greenfield products skip.131132Every guide cites the example(s) that illustrate it; every example cites133the guides it demonstrates.134135---136137## Principles the skill rests on138139See `guides/00-principles.md` for the full list. In summary:1401411. The aesthetic is not invented, it is extracted.1422. Tokens → utilities → components → screens, non-negotiable order.1433. Every rule is justified. No lore.1444. Motion is systemic. No custom curves.1455. Accessibility is the floor: 4.5:1 body, 44x44pt touch, reduced-motion.1466. HTML examples are photographs; they prove the system.1477. Tenant theming / dark mode / RTL are designed in if in scope.1488. `design-system-wasp-drone` creates; `ux-ui-svelte-wasp-drone` maintains.149150---151152## File map153154```155design-system-stinger/156├── SKILL.md (this file)157├── README.md (human overview)158├── guides/159│ ├── 00-principles.md (layering, taste rules, non-negotiables)160│ ├── 01-interview-procedure.md (12-question bank, red flags)161│ ├── 02-authoring-design-brief.md (master-brief doc shape)162│ ├── 03-authoring-tokens.md (OKLCH vs hex, @theme, DTCG)163│ ├── 04-authoring-utility-layer.md (three-cue glass, depth tiers)164│ ├── 05-authoring-components.md (variant/size/state shape, "Replaces")165│ ├── 06-authoring-screens.md (skeleton ASCII, edge cases)166│ ├── 07-authoring-html-examples.md (static photographs)167│ └── 08-companion-agent-handoff.md (clean handoff to ux-ui-svelte-wasp-drone)168├── starter-kits/169│ ├── README.md (how to pick)170│ ├── glass-on-beige/ (iOS/visionOS-style glass aesthetic)171│ ├── flat-modern/ (Linear / Vercel vibe)172│ └── editorial-serif/ (Stripe / Substack vibe)173├── templates/174│ ├── design-brief.md175│ ├── component-spec.md176│ ├── screen-spec.md177│ ├── html-example.html178│ ├── shared-css.css179│ ├── readme.md180│ └── bootstrap-report-template.md181├── examples/182│ ├── 01-glass-on-beige-bootstrap.md183│ └── 02-migration-from-ad-hoc.md184└── research/ (source-repository research, not shipped with the plugin)185 ├── research-plan.md186 ├── 2026-04-24-tailwind-v4-theme.md187 ├── 2026-04-24-oklch-color-space.md188 ├── 2026-04-24-design-tokens-dtcg.md189 ├── 2026-04-24-material-3-elevation.md190 ├── 2026-04-24-refactoring-ui-principles.md191 ├── 2026-04-24-glassmorphism-production.md192 ├── 2026-04-24-shadcn-radix-patterns.md193 └── 2026-04-24-accessibility-media-queries.md194```195196---197198## Sizing envelope199200A real product's design system lands in this range. Use these as sanity201checks before declaring the bootstrap done.202203| Artifact | Size range |204|--------------------------|---------------------|205| `00-design-brief.md` | 800-1500 lines |206| `01-master-tokens.css` | 150-400 lines |207| `02-<utility>.css` | 150-300 lines |208| `03-components/` | 8-15 files |209| `04-screens/` | 5-10 files |210| `05-html-examples/` | 5-8 HTML + shared |211| Total | ~150-250 KB |212213Under-range indicates a rushed interview or incomplete authoring.214Over-range indicates scope creep: split something out or trim.215216---217218## The handoff line219220End every