Design token init

Design Token Init

You are helping the user scaffold a new design token system using @quieto/tokens.

Prerequisites

Before running anything, verify the CLI is available:

npx quieto-tokens --version

If this fails, tell the user to install the package first (npm install @quieto/tokens).

Workflow

1. Gather intent

Ask the user what they need. The key inputs are:

• Brand color: a hex color (e.g. #4F46E5). This seeds the primary color ramp.
• Spacing base: 4 or 8 (pixel unit). Determines the spacing scale.
• Type scale: compact, balanced, or spacious. Controls font-size progression.
• Dark mode: whether to generate both light and dark themes.
• Advanced mode: whether to customize individual tokens per category (additional hues, custom spacing steps, typography overrides).
• Output platforms: CSS is always included. Optionally: Figma JSON, iOS Swift, Android (XML or Compose).

If the user already stated preferences (e.g. "set up tokens with brand color #E11D48"), extract what you can and confirm the rest with sensible defaults.

Bootstrapping from an existing codebase: If the user already has stylesheets and wants to seed the system from them rather than answering prompts, use --from-codebase. It analyzes existing CSS/SCSS/Sass/Less/Styl, proposes a token system, and shows a preview before anything is written. Scans the current directory by default, or pass --from-codebase=<path> to scan elsewhere.

This works on already-tokenized codebases too: var(--x) references are resolved through custom-property definitions and counted as usage, so a token referenced many times outweighs single-use literals in the inference, and a dark :root/html/body background turns on light + dark theme generation even without prefers-color-scheme styles. If the CLI warns Existing token system detected, explain that init rebuilds a system from scratch — if the user actually wants to modify an existing Quieto system, point them to /design-token-update or /design-token-category-add instead.

2. Run the CLI

Execute the init command:

npx quieto-tokens init

Or with advanced mode:

npx quieto-tokens init --advanced

Or bootstrap from existing stylesheets instead of prompting:

npx quieto-tokens init --from-codebase

npx quieto-tokens init --from-codebase=src/styles

Use --dry-run first if the user wants to preview without writing files:

npx quieto-tokens init --dry-run

The CLI is interactive (uses @clack/prompts), so it will prompt for each input. Since the CLI requires interactive terminal input, tell the user to run this command themselves using ! prefix:

! npx quieto-tokens init

3. Verify output

After init completes, check what was generated:

ls tokens/
ls build/
cat quieto.config.json

Summarize the generated token system for the user:

• Number of tokens per tier (primitive, semantic, component)
• Categories included (color, spacing, typography)
• Output platforms configured
• Whether dark mode was generated

4. Next steps

Suggest logical follow-ups:

• Run /design-token-audit to verify the system health
• Use /design-token-category-add to add shadow, border, or animation tokens
• Use /design-token-component to generate component-level tokens
• Run /design-token-migrate to scan existing CSS for hardcoded values to replace