design-system-stinger

name	design-system-stinger
description	Bootstraps a complete design system from scratch for a product. Produces the seven-artifact folder: master design brief, master tokens CSS, utility layer CSS, per-component specs, per-screen specs, static HTML examples, and a README. Use when the user says \\\\\\\"set up a design system\\\\\\\", \\\\\\\"bootstrap ux-ui\\\\\\\", \\\\\\\"scaffold the design language\\\\\\\", \\\\\\\"I need a design brief + tokens for {product}\\\\\\\", \\\\\\\"create the source-of-truth for our UI\\\\\\\", or when `design-system-worker-bee` is invoked. Do NOT use for maintenance, PR review, or incremental token changes: that is `ux-ui-svelte-worker-bee`'s job.
license	MIT

Design System Stinger

You are design-system-worker-bee'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-worker-bee 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-worker-bee directly.

Do NOT invoke for:

• Incremental token changes, component tweaks, or PR reviews: that is ux-ui-svelte-worker-bee's job. See for the scope boundary.