@mstar-harness/opencode 0.6.12 → 0.6.14

package/harness-skills/mstar-design-md/references/design-md-spec.md

@@ -0,0 +1,378 @@
+# DESIGN.md Normative Spec
+
+This document defines the normative structure, token naming conventions, and rules for a properly formed `DESIGN.md` file. It is the single source of truth for what each section means and how tokens should be defined.
+
+## 1. File format
+
+- Plain Markdown (`.md`) in project root
+- UTF-8 encoding
+- Multi-theme: `DESIGN.md` (light/default) + `DESIGN.dark.md` (dark variant, same token names)
+
+## 2. Section definitions
+
+Each section below maps to one heading in `DESIGN.md`. Sections are ordered as shown in Vercel Geist (recommended), but projects may omit sections not yet relevant.
+
+### 2.1 Overview
+
+**Purpose:** Declare the design system's identity — a short statement that grounds all downstream decisions.
+
+**What to include:**
+- Name of the design system
+- Core aesthetic principles (e.g., minimal, high-contrast, playful)
+- Primary audience (developer tools, consumer app, dashboard, etc.)
+- Note whether this is a light theme, dark theme, or references another file for the opposite theme
+
+**Example (minimal):**
+
+```
+# Acme Design
+
+Acme Design is a minimal, high-contrast design system for our developer dashboard.
+Prioritize readability and signal state through color and iconography, not decoration.
+
+This is the Light theme. The Dark theme lives at `/DESIGN.dark.md`.
+```
+
+**Level relevance:** Level 1+
+
+### 2.2 Colors
+
+**Purpose:** Define every color used in the UI, organized into scales.
+
+**Conventions:**
+- Each color scale has 10 steps (`100`–`1000`), encoding intent:
+  - `100`: default background
+  - `200`: hover background
+  - `300`: active background
+  - `400`: default border
+  - `500`: hover border
+  - `600`: active border
+  - `700`: solid fill
+  - `800`: solid fill hover
+  - `900`: secondary text/icons
+  - `1000`: primary text/icons
+- **Background scales** (`background-100`, `background-200`): page/card surfaces
+- **Alpha scales** (`gray-alpha-*`): translucent overlays, borders, dividers — layer over any background
+- **Solid scales** (`gray-*`): text, opaque fills — hold contrast on any surface
+- **Accent scales** (`blue`, `red`, `amber`, `green`, `teal`, `purple`, `pink`): carry meaning — success, error, warning, links, focus
+- Accent scales may use fewer steps if not all needed
+
+**Values:** sRGB hex (`#ffffff`), optionally with wide-gamut equivalents in `oklch()`.
+
+**Example:**
+
+```
+## Colors
+
+### Background
+| Token | Value |
+|-------|-------|
+| background-100 | #ffffff |
+| background-200 | #f5f5f5 |
+
+### Gray (solid)
+| Token | Value |
+|-------|-------|
+| gray-100 | #f5f5f5 |
+| gray-700 | #333333 |
+| gray-1000 | #111111 |
+
+### Accent
+| Token | Value |
+|-------|-------|
+| blue-700 | #0066ff |
+| red-700 | #e60000 |
+```
+
+**Level relevance:** Level 1+ requires at least background, gray, and one accent. Level 2+ requires full 10-step scales, alpha scale, and all accent colors.
+
+### 2.3 Typography
+
+**Purpose:** Define font families, sizes, weights, line heights, and letter spacing for every text role.
+
+**Conventions:**
+- **Heading tokens** (`heading-72` through `heading-14`): title pages and section headings
+- **Label tokens** (`label-20` through `label-12`): single-line scannable text — navigation, form labels, table headers
+- **Copy tokens** (`copy-24` through `copy-13`): multi-line body text with taller line height
+- **Button tokens** (`button-16` through `button-12`): medium-weight labels for buttons
+- **Mono tokens**: same metrics with monospace font for code/data
+- Each token carries: `fontFamily`, `fontSize`, `fontWeight`, `lineHeight`, `letterSpacing`
+- Token name encodes intended font size (e.g., `copy-14` ≈ 14px body copy)
+- Use tabular figures for numbers that need alignment
+
+**Example (minimal):**
+
+```
+## Typography
+
+### Headings
+| Token | Font | Size | Weight | Line | Spacing |
+|-------|------|------|--------|------|---------|
+| heading-32 | Inter | 32px | 600 | 1.2 | -0.02em |
+| heading-20 | Inter | 20px | 600 | 1.3 | -0.01em |
+
+### Body
+| Token | Font | Size | Weight | Line | Spacing |
+|-------|------|------|--------|------|---------|
+| copy-16 | Inter | 16px | 400 | 1.6 | 0 |
+| copy-14 | Inter | 14px | 400 | 1.5 | 0 |
+```
+
+**Level relevance:** Level 1+ requires at least body text (one copy token) and one heading token. Level 2+ requires full heading/label/copy/button typography scale.
+
+### 2.4 Spacing & Layout
+
+**Purpose:** Define the spatial grid and responsive breakpoints.
+
+**Conventions:**
+- Base unit: 4px or 8px (consistent across the system)
+- Scale: `4, 8, 12, 16, 24, 32, 40, 64, 96` (on 4px) or equivalent on 8px
+- Three-step rhythm: small inside group → medium between groups → large between sections
+- Card padding: 24px default, 16px compact, 32px hero
+- Content max-width with responsive side padding
+- Breakpoints: provide explicit pixel values and names
+
+**Example:**
+
+```
+## Layout
+
+### Spacing scale
+4px, 8px, 12px, 16px, 24px, 32px, 40px, 64px, 96px
+
+### Rhythm
+- 8px: inside a group (label + input, icon + text)
+- 16px: between related groups
+- 32-40px: between sections
+
+### Breakpoints
+| Name | Width |
+|------|-------|
+| sm | 401px |
+| md | 601px |
+| lg | 961px |
+| xl | 1200px |
+```
+
+**Level relevance:** Level 1+ requires spacing scale and at least 2 breakpoints.
+
+### 2.5 Elevation & Depth
+
+**Purpose:** Define shadow values for layered UI elements.
+
+**Conventions:**
+- Use tonal surfaces first, shadows second — keep shadows subtle
+- Define shadow values per elevation level: cards, popovers, modals
+- Pair each elevation with a matching border radius
+
+**Example:**
+
+```
+## Elevation
+
+### Shadows
+| Level | Value |
+|-------|-------|
+| Card | 0 2px 2px rgba(0,0,0,0.04) |
+| Popover | 0 1px 1px rgba(0,0,0,0.02), 0 4px 8px -4px rgba(0,0,0,0.04), 0 16px 24px -8px rgba(0,0,0,0.06) |
+| Modal | 0 1px 1px rgba(0,0,0,0.02), 0 8px 16px -4px rgba(0,0,0,0.04), 0 24px 32px -8px rgba(0,0,0,0.06) |
+```
+
+**Level relevance:** Level 3 only.
+
+### 2.6 Motion
+
+**Purpose:** Define animation durations and easing curves.
+
+**Conventions:**
+- Motion clarifies change, never decorates
+- Default: 0ms (instant) is often the best choice
+- When needed: short, physical easing — roughly 150ms state, 200ms popover, 300ms modal
+- Honor `prefers-reduced-motion`
+- No looping or attention-grabbing animations
+
+**Example:**
+
+```
+## Motion
+
+### Easing
+Default: cubic-bezier(0.175, 0.885, 0.32, 1.1)
+
+### Durations
+| Context | Duration |
+|---------|----------|
+| State change | 150ms |
+| Popover/Tooltip | 200ms |
+| Modal/Overlay | 300ms |
+```
+
+**Level relevance:** Level 3 only.
+
+### 2.7 Shapes
+
+**Purpose:** Define border radius values.
+
+**Conventions:**
+- Keep radii tight and consistent
+- One radius family per view, never mix rounded and sharp corners
+- Common values: 6px (surfaces), 12px (menus/modals), 16px (fullscreen), 9999px (pills)
+
+**Example:**
+
+```
+## Shapes
+
+### Border Radius
+| Context | Value |
+|---------|-------|
+| Surface, Input, Button | 6px |
+| Menu, Modal, Popover | 12px |
+| Fullscreen | 16px |
+| Pill, Avatar | 9999px |
+```
+
+**Level relevance:** Level 3 only.
+
+### 2.8 Components
+
+**Purpose:** Define ready-to-use token values for common components.
+
+**Conventions:**
+- Each component gets: `backgroundColor`, `textColor`, `rounded`, `height` (and `borderColor` where applicable)
+- Size variants: default (40px), small (32px), large (48px)
+- State mappings: hover steps foreground up one, active steps up two; border from 400→500→600
+- Focus ring: two-layer box-shadow (surface gap + accent ring)
+- Disabled: 100 fill + 700 text + not-allowed cursor
+
+**Example:**
+
+```
+## Components
+
+### Button
+| Variant | Background | Text | Border | Radius | Height |
+|---------|-----------|------|--------|--------|--------|
+| primary | gray-1000 | background-100 | — | 6px | 40px |
+| secondary | background-100 | gray-1000 | gray-alpha-400 | 6px | 40px |
+| tertiary | transparent | gray-1000 | — | 6px | 40px |
+| error | red-800 | #fff | — | 6px | 40px |
+
+### Input
+| Variant | Background | Text | Border | Radius | Height |
+|---------|-----------|------|--------|--------|--------|
+| default | background-100 | gray-1000 | gray-alpha-400 | 6px | 40px |
+```
+
+**Level relevance:** Level 2+ requires at least Button and Input tokens. Level 3 requires full component library.
+
+### 2.9 Voice & Content
+
+**Purpose:** Define content writing rules for the UI.
+
+**Conventions:**
+- Title Case for labels, buttons, titles, tabs
+- Sentence case for body, helper text, toasts
+- Verb + Noun for actions (`Deploy Project`, never `Confirm`)
+- Errors: what happened + what to do
+- Toasts: specific thing + no trailing period + no `successfully`
+- Empty states: describe the first action
+- In-progress: present participle + ellipsis (`Deploying…`)
+- Use numerals, curly quotes, the ellipsis character
+
+**Example:**
+
+```
+## Voice & Content
+
+- Use Title Case for labels, buttons, titles, and tabs
+- Sentence case for body, helper text, and toasts
+- Name actions with a verb and a noun: `Deploy Project`, `Delete Member`
+- Write errors as what happened plus what to do next
+- Toasts name the specific thing that changed, drop the trailing period
+- Empty states point to the first action: `No deployments yet. Push to your Git repository to create one.`
+```
+
+**Level relevance:** Level 3 only.
+
+## 3. Token naming conventions
+
+### Color tokens
+
+```
+{namespace}-{step}
+```
+
+- `namespace`: `background`, `gray`, `gray-alpha`, `blue`, `red`, `amber`, `green`, `teal`, `purple`, `pink`
+- `step`: `100`–`1000` (10-step scale encoding intent as defined in §2.2)
+
+### Typography tokens
+
+```
+{role}-{size}
+```
+
+- `role`: `heading`, `label`, `copy`, `button`
+- `size`: approximate font size in pixels
+- Mono variant: `{role}-{size}-mono`
+
+### Breakpoint tokens
+
+Lowercase short names: `sm`, `md`, `lg`, `xl`, `2xl`
+
+## 4. Light/Dark dual-theme rules
+
+### Contract
+
+Dual theme uses **same token names with different values** in two separate files:
+
+- `DESIGN.md` — light (or default) theme
+- `DESIGN.dark.md` — dark theme
+
+### Rules
+
+1. **Token names are identical** across both files
+2. **Only the values differ** — a light `background-100: #ffffff` becomes dark `background-100: #111111`
+3. **Both files define the same token set** — no token can exist in only one file
+4. **DESIGN.md is always the SSOT for token names** — DESIGN.dark.md copies the structure
+5. If a token isn't relevant to dark mode (e.g., a light-only accent), include it in DESIGN.dark.md anyway with a sensible dark-equivalent value
+6. Add `DESIGN.dark.md` path reference in DESIGN.md Overview
+
+### Naming
+
+Dark theme file must be named `DESIGN.dark.md` (not `design-dark.md` or `DESIGN_DARK.md`).
+
+## 5. Upgrade placeholders
+
+Sections not yet filled should use HTML comment markers:
+
+```
+<!-- LEVEL2_PLACEHOLDER: Complete the 10-step color scales and add alpha scale when the design matures. See `references/completeness-checklist.md` § Level 2. -->
+```
+
+```
+<!-- LEVEL3_PLACEHOLDER: Add Elevation, Motion, Shapes, Voice & Content, and full Component library when ready for production design system. See `references/completeness-checklist.md` § Level 3. -->
+```
+
+Agents encountering these placeholders understand that:
+- The section is intentionally deferred, not accidentally empty
+- The placeholder describes what's missing and when to revisit
+- An upgrade workflow can detect these markers and recommend progression
+
+## 6. Mapping to implementation
+
+DESIGN.md tokens should map to implementation as follows:
+
+| DESIGN.md | Implementation |
+|-----------|---------------|
+| Color tokens | CSS custom properties (`--color-gray-100`) or theme object |
+| Typography tokens | CSS classes or Tailwind prose config |
+| Spacing scale | CSS custom properties or Tailwind spacing config |
+| Breakpoints | CSS media queries or Tailwind screens |
+| Elevation | `box-shadow` or Tailwind shadow config |
+| Motion | `transition` or animation library config |
+| Shapes | `border-radius` or Tailwind radius config |
+| Component tokens | Component prop defaults or CSS classes |
+| Voice rules | Linter rules or prompt context for copy generation |
+
+The agent consuming DESIGN.md is responsible for this mapping, not DESIGN.md itself. DESIGN.md stays implementation-agnostic.

package/harness-skills/mstar-design-md/references/vercel-example.md

@@ -0,0 +1,138 @@
+# Vercel Geist DESIGN.md — Annotated Reference
+
+This is Vercel's Geist design system as published at `vercel.com/design.md`, presented as a reference for creating new DESIGN.md files. Annotations are inline as `> **Design note:**` blockquotes explaining the rationale behind key decisions.
+
+**Source:** <https://vercel.com/design.md>
+
+**Why this as reference:**
+- Vercel's DESIGN.md is the canonical example of the `DESIGN.md` format in the `awesome-design-md` ecosystem
+- It defines a complete Level 3 design system covering all sections
+- The token naming conventions (100-1000 step scale with intent encoding) are widely adopted
+- Light/Dark dual-theme pattern shows how to split same-name tokens across two files
+
+---
+
+# Geist
+
+## Overview
+
+Geist is Vercel's design system for building consistent, developer-focused interfaces. The aesthetic is minimal and high-contrast: plenty of whitespace, restrained color, and content set on near-neutral surfaces. Prioritize readability and accessibility, and use color to signal state or hierarchy rather than decoration.
+
+This is the Light theme. The Dark theme uses the same token names with different values and lives at `/design.dark.md`. Colors are sRGB hex with Display P3 equivalents.
+
+> **Design note:** The Overview does two things well: (1) it states the aesthetic in terms an agent can operationalize ("minimal and high-contrast", "color to signal state or hierarchy rather than decoration"), and (2) it declares the multi-theme structure upfront.
+
+## Colors
+
+Each non-background scale runs 10 steps (`100`–`1000`), and the step encodes intent, not just lightness:
+
+- `100` default background
+- `200` hover background
+- `300` active background
+- `400` default border
+- `500` hover border
+- `600` active border
+- `700` solid fill, high contrast
+- `800` solid fill, hover
+- `900` secondary text and icons
+- `1000` primary text and icons
+
+`background-100` is the primary page and card surface; `background-200` is a secondary surface for subtle separation. The `gray-alpha-*` tokens are translucent, so they layer over any background; use them for borders, dividers, overlays, and hover states. Solid `gray-*` holds its contrast on any surface, so use it for text and opaque fills. Accent scales carry meaning: `blue` for success, links, and focus; `red` for errors; `amber` for warnings; plus `green`, `teal`, `purple`, and `pink`. Use the hex tokens everywhere; each accent scale also ships a `*-p3` wide-gamut value in `oklch()` for Display P3 screens. The Dark theme redefines the same names at `/design.dark.md`.
+
+> **Design note:** This is the key innovation of Vercel's approach: the 10-step scale encodes **intent**, not just a lightness gradient. An agent reading this knows that `700` means "solid fill" and `400` means "border", regardless of the actual hex value. This makes the scale **self-documenting** — an agent can apply tokens correctly without memorizing specific colors. The separation of `gray-alpha` (translucent, layers over any background) from `gray` (solid, holds contrast) is another critical design decision that prevents common UI mistakes.
+
+## Typography
+
+Geist Sans sets UI and prose; Geist Mono sets code, data, and tabular figures. Both are open-source. The `typography` tokens above carry concrete `fontFamily`, `fontSize`, `fontWeight`, `lineHeight`, and `letterSpacing`:
+
+- Headings, `heading-72` through `heading-14`, title pages and sections; `letterSpacing` tightens as the size grows.
+- Labels, `label-20` through `label-12`, carry single-line, scannable text: navigation, form labels, table headers, metadata.
+- Copy, `copy-24` through `copy-13`, set multi-line body text with a taller `lineHeight`.
+- Buttons, `button-16` through `button-12`, are medium-weight labels for buttons and compact controls.
+
+`copy-14` and `label-14` cover most text. The `-mono` tokens pair Geist Mono with the same metrics; prefer tabular figures when numbers need to align.
+
+> **Design note:** The typography system encodes **role** plus **size** in the token name (`copy-14`, `label-14`, `button-16`). An agent knows `copy-14` is body text (multi-line, taller line-height) and `label-14` is single-line scannable text — even though they share the same font size. This is the same "intent encoding" pattern as the color scales.
+
+## Layout
+
+Spacing follows a 4px scale: 4, 8, 12, 16, 24, 32, 40, 64, 96px. Keep a three-step rhythm: 8px inside a group, 16px between groups, 32–40px between sections. Cards use 24px padding, 16px when compact and 32px for hero areas. Center content in a 1200px column with side padding that grows at wider breakpoints, and make every layout work on mobile and desktop. Breakpoints are `sm` 401px, `md` 601px, `lg` 961px, `xl` 1200px, and `2xl` 1400px.
+
+> **Design note:** The "three-step rhythm" rule (8px/16px/32px) gives an agent a clear, mechanical way to decide how much space to put between elements. Without this, agents tend to use arbitrary spacing. The card padding variants (24px/16px/32px) similarly prevent inconsistent padding choices.
+
+## Elevation & Depth
+
+Hierarchy comes from tonal surfaces and borders first, so shadows stay subtle. Apply these `box-shadow` values for the light theme:
+
+- Raised cards: `0 2px 2px rgba(0, 0, 0, 0.04)`
+- Popovers and menus: `0 1px 1px rgba(0, 0, 0, 0.02), 0 4px 8px -4px rgba(0, 0, 0, 0.04), 0 16px 24px -8px rgba(0, 0, 0, 0.06)`
+- Modals and dialogs: `0 1px 1px rgba(0, 0, 0, 0.02), 0 8px 16px -4px rgba(0, 0, 0, 0.04), 0 24px 32px -8px rgba(0, 0, 0, 0.06)`
+
+Tooltips take the lightest of these. Pair each elevation with the matching radius below.
+
+> **Design note:** The hierarchy principle is stated first ("tonal surfaces and borders first, so shadows stay subtle"). This prevents agents from over-using shadows. Each elevation is tied to a specific UI element (card, popover, modal) — not an abstract level number — making it trivial for an agent to pick the right shadow.
+
+## Motion
+
+Use motion only when it clarifies a change, never for decoration. Most interactions should feel instant: a duration of `0ms` is often the snappiest and best choice, and the call is context-dependent. When motion genuinely helps, such as revealing or moving an element, keep it short and physical with the easing `cubic-bezier(0.175, 0.885, 0.32, 1.1)`: roughly 150ms for state changes, 200ms for popovers and tooltips, and 300ms for overlays and modals. Avoid long, looping, or attention-grabbing animation, and honor `prefers-reduced-motion` by dropping nonessential motion.
+
+> **Design note:** The explicit "0ms is often the best choice" is crucial — it prevents agents from defaulting to the common 300ms ease-out. The duration table maps cleanly to element types (state change → popover → modal), making it self-documenting.
+
+## Shapes
+
+Radii stay tight: 6px for everyday surfaces and controls, 12px for menus and modals, 16px for fullscreen surfaces. Reserve 9999px for pills, avatars, and circular controls. Keep one radius family per view rather than mixing rounded and sharp corners.
+
+> **Design note:** "One radius family per view" is a strong constraint that prevents inconsistent corner radius mixing — a common agent mistake.
+
+## Components
+
+The `components` tokens above give ready-to-use values per element (`backgroundColor`, `textColor`, `rounded`, `height`) drawn from this theme:
+
+- Primary button: solid `gray-1000` fill with a `background-100` label, for the single most important action on a view.
+- Secondary button: `background-100` fill with a translucent `gray-alpha-400` border.
+- Tertiary button: transparent fill with `gray-1000` text for low-emphasis actions; it tints with `gray-alpha` on hover.
+- Error button: solid `red-800` fill with white text, for destructive actions.
+- Input: `background-100` fill, translucent border, 6px radius.
+
+The variant tokens are the default medium (40px) size. Use the `button-small`/`input-small` (32px) and `button-large`/`input-large` (48px) tokens for the other sizes; large buttons step up to `button-16`. Hover and active states step up the scale: a `100` fill becomes `200` on hover and `300` on active, and borders move from `400` to `500` to `600`. Disabled uses a `gray-100` fill, `gray-700` text, and a not-allowed cursor. Focus shows a two-layer ring (`box-shadow: 0 0 0 2px #ffffff, 0 0 0 4px #006bff`): a 2px gap in the surface color, then a 2px `blue-700` ring.
+
+> **Design note:** The component tokens reference the color/typography/shape tokens defined above — there is no duplication. The state progression rule ("100 → 200 → 300 fill on hover → active") is a **systematic rule**, not a per-component value table. An agent can derive any component's hover state from this rule alone. The focus ring pattern (surface gap + accent ring) is explicitly described with box-shadow values, preventing agents from guessing focus styles.
+
+## Voice & Content
+
+Copy is part of the design; keep it precise and free of filler.
+
+- Use Title Case for labels, buttons, titles, and tabs; sentence case for body, helper text, and toasts.
+- Name actions with a verb and a noun (`Deploy Project`, `Delete Member`), never `Confirm`, `OK`, or a bare verb.
+- Write errors as what happened plus what to do next: `Build failed. Bundle exceeds 50 MB. Reduce it or raise the limit.`
+- Toasts name the specific thing that changed, drop the trailing period, and never say `successfully`: `Project deleted`, not `Successfully deleted the project.`
+- Empty states point to the first action: `No deployments yet. Push to your Git repository to create one.`
+- Use the present participle with an ellipsis for in-progress states: `Deploying…`, `Saving…`.
+- Use numerals (`3 projects`), curly quotes, and the ellipsis character; skip `please` and marketing superlatives.
+
+> **Design note:** Voice rules are highly actionable for agents because they give negative examples ("never `Confirm`, `OK`") and positive patterns ("what happened + what to do next"). This turns copy generation from guesswork into a mechanical fill-in-the-blank exercise.
+
+## Do's and Don'ts
+
+- Use the gray scale to rank information: `1000` for primary text, `900` for secondary, `700` for disabled.
+- Keep solid accent color for state and the single most important action on a view.
+- Hold WCAG AA contrast (4.5:1 for body text).
+- Show the focus ring on every interactive element at `:focus-visible`, and never remove an outline without a visible replacement.
+- Apply the typography tokens instead of setting font size, line height, or weight by hand.
+- Don't signal state with color alone; pair it with an icon or text label.
+- Don't use `background-200` as a general fill; it is for subtle separation only.
+- Don't mix rounded and sharp corners, or more than two font weights, in one view.
+- Don't swap `gray-*` for `background-*`; they are separate scales.
+
+> **Design note:** The Do's and Don'ts section serves as a **correctness checklist** for agents. Each item is a specific, verifiable rule. Agents can self-check their UI output against this list. The "Don't" items prevent common mistakes ("don't mix rounded and sharp corners", "don't use `background-200` as a general fill").
+
+---
+
+## Key takeaways for creating your own DESIGN.md
+
+1. **Encode intent in token names**, not just values — `gray-400 = border`, `copy-14 = body text`
+2. **State rules, not just values** — "three-step spacing rhythm" is more useful than a raw scale
+3. **Give negative examples** — agents need to know what NOT to do as much as what to do
+4. **Make state derivable** — "100 → 200 → 300 on hover" means the agent can compute any component's state
+5. **Tie tokens to concrete UI elements** — "card shadow", not "level-1 shadow"
+6. **Voice rules should be mechanical** — fill-in-the-blank templates, not vague principles

package/harness-skills/mstar-design-md/templates/DESIGN.dark.md.template

@@ -0,0 +1,133 @@
+<!-- COMPLETENESS_LEVEL: 3 — dark theme companion to DESIGN.md -->
+
+# [Design System Name] — Dark
+
+## Overview
+
+[Design System Name] Dark is the dark theme companion to [Design System Name]. Use the same token names as DESIGN.md; only the values change. Every token defined in DESIGN.md must have a corresponding entry in this file.
+
+This file uses the same structure as DESIGN.md. When DESIGN.md is updated, update this file with the dark-equivalent values.
+
+<!-- 
+  IMPORTANT: Switch to dark mode by loading this file's values in place of DESIGN.md values.
+  Consumers reference tokens by name, not by value — the switch is transparent.
+-->
+
+## Colors
+
+### Background
+
+<!-- Dark backgrounds are dark grays instead of whites. background-100 is the primary dark surface. -->
+
+| Token | Value |
+|-------|-------|
+| background-100 | #[dark page/card surface, e.g., #111111] |
+
+<!-- LEVEL2_PLACEHOLDER: Match DESIGN.md Level 2 background tokens -->
+<!--
+| background-200 | #[slightly lighter dark surface] |
+| background-300 | #[active dark surface] |
+-->
+
+### Gray (text and fills)
+
+<!-- Dark text colors are light grays. Invert the scale: gray-1000 is light (primary text on dark), gray-100 is dark. -->
+
+| Token | Value |
+|-------|-------|
+| gray-1000 | #[primary text on dark, e.g., #eeeeee] |
+| gray-900 | #[secondary text on dark, e.g., #999999] |
+
+<!-- LEVEL2_PLACEHOLDER: Match DESIGN.md Level 2 gray scale with dark-appropriate values -->
+<!--
+| gray-100 | #[darkest fill, e.g., #1a1a1a] |
+| gray-200 | #[hover fill, e.g., #222222] |
+| gray-300 | #[active fill, e.g., #333333] |
+| gray-400 | #[border, e.g., #444444] |
+| gray-500 | #[hover border, e.g., #555555] |
+| gray-600 | #[active border, e.g., #666666] |
+| gray-700 | #[disabled text, e.g., #777777] |
+| gray-800 | #[solid hover, e.g., #888888] |
+-->
+
+<!-- LEVEL2_PLACEHOLDER: Add gray-alpha scale with white-based transparency for dark backgrounds -->
+<!--
+### Gray Alpha (translucent overlays)
+
+| Token | Value |
+|-------|-------|
+| gray-alpha-100 | rgba(255, 255, 255, 0.04) |
+| gray-alpha-200 | rgba(255, 255, 255, 0.06) |
+| gray-alpha-300 | rgba(255, 255, 255, 0.08) |
+| gray-alpha-400 | rgba(255, 255, 255, 0.12) |
+| gray-alpha-500 | rgba(255, 255, 255, 0.16) |
+| gray-alpha-600 | rgba(255, 255, 255, 0.24) |
+-->
+
+### Accent
+
+<!-- Accent colors may shift to maintain contrast on dark backgrounds. Same token names, adjusted values. -->
+
+| Token | Value | Usage |
+|-------|-------|-------|
+| blue-700 | #[adjusted for dark, typically lighter to maintain contrast] | Interactive elements |
+| red-700 | #[adjusted for dark, typically lighter] | Errors |
+| amber-700 | #[adjusted for dark, typically lighter] | Warnings |
+
+<!-- LEVEL2_PLACEHOLDER: Match all accent scales from DESIGN.md with dark-appropriate values -->
+
+## Typography
+
+<!-- Typography tokens typically remain the same in dark mode. Copy verbatim from DESIGN.md. -->
+
+| Token | Font Family | Size | Weight | Line Height | Letter Spacing |
+|-------|------------|------|--------|-------------|----------------|
+| copy-16 | [same as DESIGN.md] | 16px | 400 | 1.6 | 0 |
+| heading-32 | [same as DESIGN.md] | 32px | 600 | 1.2 | -0.02em |
+
+## Spacing & Layout
+
+<!-- Spacing and breakpoints are identical to DESIGN.md. Copy verbatim. -->
+
+Base unit: [same as DESIGN.md]
+
+| Step | Value |
+|------|-------|
+| 1x | [base × 1] |
+| 2x | [base × 2] |
+| 3x | [base × 3] |
+| 4x | [base × 4] |
+| 6x | [base × 6] |
+
+| Name | Min Width | Target |
+|------|-----------|--------|
+| sm | 401px | Mobile landscape |
+| lg | 961px | Desktop |
+
+<!-- LEVEL3_PLACEHOLDER: Add dark-mode Elevation, Components tokens, and full dark theme parity with DESIGN.md -->
+<!--
+## Elevation & Depth
+
+Shadows on dark backgrounds use lighter, more subtle values. Hierarchy still comes from tonal surfaces first.
+
+### Shadows (dark theme)
+
+| Element | Value |
+|---------|-------|
+| Card | 0 2px 2px rgba(0, 0, 0, 0.12) |
+| Popover | 0 1px 1px rgba(0, 0, 0, 0.08), 0 4px 8px -4px rgba(0, 0, 0, 0.12), 0 16px 24px -8px rgba(0, 0, 0, 0.16) |
+| Modal | 0 1px 1px rgba(0, 0, 0, 0.08), 0 8px 16px -4px rgba(0, 0, 0, 0.12), 0 24px 32px -8px rgba(0, 0, 0, 0.16) |
+
+## Components
+
+Button tokens reference dark color values. Same structure as DESIGN.md, different color references.
+
+### Button
+
+| Variant | Background | Text | Border | Radius | Height |
+|---------|-----------|------|--------|--------|--------|
+| primary | gray-100 (dark value) | background-100 (dark value) | — | 6px | 40px |
+| secondary | background-100 | gray-1000 | gray-alpha-400 | 6px | 40px |
+
+States, sizes, and focus follow the same rules as DESIGN.md.
+-->