@radicool/throughline 0.21.4 → 0.23.0

package/README.md

@@ -73,7 +73,7 @@ Everything above was created during a single working session and synced directly
 
 | | |
 |---|---|
-| **A supported agent** | Required — [Claude Code](https://docs.claude.com/en/docs/claude-code) (native plugin), or **Cursor**, **Codex**, or any **AGENTS.md**-aware agent via `npx @radicool/throughline@0.21.4 init`. |
+| **A supported agent** | Required — [Claude Code](https://docs.claude.com/en/docs/claude-code) (native plugin), or **Cursor**, **Codex**, or any **AGENTS.md**-aware agent via `npx @radicool/throughline@0.23.0 init`. |
 | **Figma** | Required, **desktop app** (the browser version causes connection errors). **Professional plan or higher recommended** — multi-mode variables (Light/Dark, brand themes) need it. |
 | **Figma access token** | Optional — only for the few Figma calls the Desktop Bridge can't make, like reading a published library. Without it, you work through the bridge alone. The setup skill walks you through it; your token stays yours and is never shared in chat. |
 | **GitHub** (or similar) | Optional — only when you're ready to graduate to a real remote repo with PRs and CI. |
@@ -114,9 +114,9 @@ Update anytime with `/plugin marketplace update throughline-marketplace`.
 Run the installer in your project — it stamps in the skills, the reference docs, the scripts, and the Figma MCP config for your tool:
 
 ```
-npx @radicool/throughline@0.21.4 init --target=cursor    # → .cursor/rules + .cursor/mcp.json
-npx @radicool/throughline@0.21.4 init --target=codex      # → prompts/ + AGENTS.md index + codex-mcp.toml
-npx @radicool/throughline@0.21.4 init --target=generic    # → skills/ + AGENTS.md index
+npx @radicool/throughline@0.23.0 init --target=cursor    # → .cursor/rules + .cursor/mcp.json
+npx @radicool/throughline@0.23.0 init --target=codex      # → prompts/ + AGENTS.md index + codex-mcp.toml
+npx @radicool/throughline@0.23.0 init --target=generic    # → skills/ + AGENTS.md index
 ```
 
 It's safe to re-run (it merges `AGENTS.md` and `.cursor/mcp.json` non-destructively) and stages everything the skills read into `.throughline/`. Then open the `figma-environment-setup` skill/rule/prompt for your tool to begin. For Codex, add the printed `codex-mcp.toml` block to your Codex config to enable Figma access.
@@ -162,7 +162,7 @@ For the technically curious — how the machine actually runs.
 
 **Modes, within Figma's limits.** Light/Dark lives on the semantic collections; brand variants live on the primitive palette. Splitting the two axes across two collections keeps each one under Figma's 4-modes-per-collection cap on the Professional plan while still resolving correctly (`bg/default` → `{gray/50}` → the active brand's gray).
 
-**Model routing.** ThroughLine routes work by *cognition, not guesswork* — the expensive thinking on the best model, the mechanical doing on a cheap one. Setup pins **Haiku** to keep first-run costs low. Inside a skill, the deciding — a token architecture, a variant matrix, a slot contract — is planned once on the strongest tier, while the long mechanical part — placing Figma nodes, transcribing component code, running SVGR — runs on a cheap tier and self-verifies. You get the best model where it matters and a cheap one where it doesn't, without micromanaging it. The recommended mapping is **Haiku → Sonnet → Opus** for the `fast < balanced < deep` tiers, but apart from setup's Haiku pin, nothing is hardcoded — the ladder resolves against whatever models your install actually has, and on hosts without subagents skills degrade cleanly to a single model. You can still steer the session yourself (`/model opus` for the heaviest authoring, back to `/model sonnet` after); nothing forces an expensive model on you.
+**Model routing.** ThroughLine routes work by *cognition, not guesswork* — the expensive thinking on the best model, the mechanical doing on a cheap one. Inside a skill, the deciding — a token architecture, a variant matrix, a slot contract — is planned once on the strongest tier, while the long mechanical part — placing Figma nodes, transcribing component code, running SVGR — runs on a cheap tier and self-verifies. You get the best model where it matters and a cheap one where it doesn't, without micromanaging it. The recommended mapping is **Haiku → Sonnet → Opus** for the `fast < balanced < deep` tiers, but nothing is hardcoded — the ladder resolves against whatever models your install actually has, and on hosts without subagents skills degrade cleanly to a single model. You can still steer the session yourself (`/model opus` for the heaviest authoring, back to `/model sonnet` after); nothing forces an expensive model on you.
 
 ## Who it's for
 

package/adapters/codex/prompts/component-builder.md

@@ -67,8 +67,9 @@ inconsistent output:
 - **Sizes** (sm, md, lg). Each size is its **own variant row**, not a state — see
   the layout law below.
 - **States** — **include the full relevant set, don't trim it.** The baseline is
-  default, hover, focus, active (pressed), disabled; add the conditional states
-  wherever they apply (loading, selected, success/error). Decide which conditional
+  the set `.throughline/references/state-baseline.md` owes that component
+  (default included); add the conditional states wherever they apply (loading,
+  success/error). Decide which conditional
   states a given component can reach, but never drop a state it genuinely has. See
   "State handling" in `.throughline/references/figma-component-standards.md`
   for the per-component checklist.
@@ -172,8 +173,12 @@ deterministic naming):
   re-screenshot) **and its "Post-build audit (REQUIRED before handoff)"
   read-back checklist** (container type, auto layout, bound variables,
   deterministic names) before the checkpoint. When you build inline, with no
-  `figma-executor`, that includes item 9's `focus-indicator` check: a miss stops
-  the build, as it would for the executor.
+  `figma-executor`, run `.throughline/references/figma-checks.md` the
+  way the executor does: `'spec'` mode before the first write and `'built'` mode
+  in the self-verify loop, with `EXPECT` built from your own matrix. You are the
+  architect here, so you name `controlLayer` yourself for a wrapped control (an
+  Input with a label or helper text). A `fail` on the `focus-indicator` check
+  stops the build, as it would for the executor.
 
 Checkpoint after each component: show all variants, confirm before the next.
 
@@ -400,9 +405,9 @@ Offer next steps: build the code counterparts and stories
   auto-layout grid where **variants are rows and states are columns**: one row per
   variant (each `type`, and each `size`, since size is a variant) stepping through
   states across the columns, size groups stacked vertically (see the standards doc).
-- Never ship a component with only its `default` state — include the full relevant
-  state set (default/hover/focus/active/disabled plus applicable
-  loading/selected/success/error).
+- Never ship a component with only its `default` state — include every state
+  `.throughline/references/state-baseline.md` owes that component, plus
+  `default`, plus any applicable loading/success/error.
 - Never run the component header and the component area together with no division —
   every doc card segments the header from the component area with a divider line or
   a distinct header surface.

package/adapters/codex/prompts/token-sync-layer.md

@@ -140,7 +140,10 @@ fit in the adapter output.
 
 ## Step 3 — Set up Style Dictionary + adapters
 
-Install and configure Style Dictionary v4 in `packages/tokens/`. For each chosen
+Install Style Dictionary pinned to an exact version with
+`pnpm add -D style-dictionary@4.4.0` (or the project's package manager) in
+`packages/tokens/`; the generated config is verified against 4.4.0, and a newer
+release can rename or add stock transforms. Then configure it. For each chosen
 platform, apply its adapter preset (per `.throughline/references/sync-adapters.md`):
 register the platform, transform group, format, and `outputReferences`
 (true for web → preserves the semantic→primitive cascade; false for native →

package/adapters/cursor/.cursor/rules/component-builder.mdc

@@ -71,8 +71,9 @@ inconsistent output:
 - **Sizes** (sm, md, lg). Each size is its **own variant row**, not a state — see
   the layout law below.
 - **States** — **include the full relevant set, don't trim it.** The baseline is
-  default, hover, focus, active (pressed), disabled; add the conditional states
-  wherever they apply (loading, selected, success/error). Decide which conditional
+  the set `.throughline/references/state-baseline.md` owes that component
+  (default included); add the conditional states wherever they apply (loading,
+  success/error). Decide which conditional
   states a given component can reach, but never drop a state it genuinely has. See
   "State handling" in `.throughline/references/figma-component-standards.md`
   for the per-component checklist.
@@ -176,8 +177,12 @@ deterministic naming):
   re-screenshot) **and its "Post-build audit (REQUIRED before handoff)"
   read-back checklist** (container type, auto layout, bound variables,
   deterministic names) before the checkpoint. When you build inline, with no
-  `figma-executor`, that includes item 9's `focus-indicator` check: a miss stops
-  the build, as it would for the executor.
+  `figma-executor`, run `.throughline/references/figma-checks.md` the
+  way the executor does: `'spec'` mode before the first write and `'built'` mode
+  in the self-verify loop, with `EXPECT` built from your own matrix. You are the
+  architect here, so you name `controlLayer` yourself for a wrapped control (an
+  Input with a label or helper text). A `fail` on the `focus-indicator` check
+  stops the build, as it would for the executor.
 
 Checkpoint after each component: show all variants, confirm before the next.
 
@@ -404,9 +409,9 @@ Offer next steps: build the code counterparts and stories
   auto-layout grid where **variants are rows and states are columns**: one row per
   variant (each `type`, and each `size`, since size is a variant) stepping through
   states across the columns, size groups stacked vertically (see the standards doc).
-- Never ship a component with only its `default` state — include the full relevant
-  state set (default/hover/focus/active/disabled plus applicable
-  loading/selected/success/error).
+- Never ship a component with only its `default` state — include every state
+  `.throughline/references/state-baseline.md` owes that component, plus
+  `default`, plus any applicable loading/success/error.
 - Never run the component header and the component area together with no division —
   every doc card segments the header from the component area with a divider line or
   a distinct header surface.

package/adapters/cursor/.cursor/rules/token-sync-layer.mdc

@@ -144,7 +144,10 @@ fit in the adapter output.
 
 ## Step 3 — Set up Style Dictionary + adapters
 
-Install and configure Style Dictionary v4 in `packages/tokens/`. For each chosen
+Install Style Dictionary pinned to an exact version with
+`pnpm add -D style-dictionary@4.4.0` (or the project's package manager) in
+`packages/tokens/`; the generated config is verified against 4.4.0, and a newer
+release can rename or add stock transforms. Then configure it. For each chosen
 platform, apply its adapter preset (per `.throughline/references/sync-adapters.md`):
 register the platform, transform group, format, and `outputReferences`
 (true for web → preserves the semantic→primitive cascade; false for native →

package/adapters/generic/skills/component-builder/SKILL.md

@@ -67,8 +67,9 @@ inconsistent output:
 - **Sizes** (sm, md, lg). Each size is its **own variant row**, not a state — see
   the layout law below.
 - **States** — **include the full relevant set, don't trim it.** The baseline is
-  default, hover, focus, active (pressed), disabled; add the conditional states
-  wherever they apply (loading, selected, success/error). Decide which conditional
+  the set `.throughline/references/state-baseline.md` owes that component
+  (default included); add the conditional states wherever they apply (loading,
+  success/error). Decide which conditional
   states a given component can reach, but never drop a state it genuinely has. See
   "State handling" in `.throughline/references/figma-component-standards.md`
   for the per-component checklist.
@@ -172,8 +173,12 @@ deterministic naming):
   re-screenshot) **and its "Post-build audit (REQUIRED before handoff)"
   read-back checklist** (container type, auto layout, bound variables,
   deterministic names) before the checkpoint. When you build inline, with no
-  `figma-executor`, that includes item 9's `focus-indicator` check: a miss stops
-  the build, as it would for the executor.
+  `figma-executor`, run `.throughline/references/figma-checks.md` the
+  way the executor does: `'spec'` mode before the first write and `'built'` mode
+  in the self-verify loop, with `EXPECT` built from your own matrix. You are the
+  architect here, so you name `controlLayer` yourself for a wrapped control (an
+  Input with a label or helper text). A `fail` on the `focus-indicator` check
+  stops the build, as it would for the executor.
 
 Checkpoint after each component: show all variants, confirm before the next.
 
@@ -400,9 +405,9 @@ Offer next steps: build the code counterparts and stories
   auto-layout grid where **variants are rows and states are columns**: one row per
   variant (each `type`, and each `size`, since size is a variant) stepping through
   states across the columns, size groups stacked vertically (see the standards doc).
-- Never ship a component with only its `default` state — include the full relevant
-  state set (default/hover/focus/active/disabled plus applicable
-  loading/selected/success/error).
+- Never ship a component with only its `default` state — include every state
+  `.throughline/references/state-baseline.md` owes that component, plus
+  `default`, plus any applicable loading/success/error.
 - Never run the component header and the component area together with no division —
   every doc card segments the header from the component area with a divider line or
   a distinct header surface.

package/adapters/generic/skills/token-sync-layer/SKILL.md

@@ -140,7 +140,10 @@ fit in the adapter output.
 
 ## Step 3 — Set up Style Dictionary + adapters
 
-Install and configure Style Dictionary v4 in `packages/tokens/`. For each chosen
+Install Style Dictionary pinned to an exact version with
+`pnpm add -D style-dictionary@4.4.0` (or the project's package manager) in
+`packages/tokens/`; the generated config is verified against 4.4.0, and a newer
+release can rename or add stock transforms. Then configure it. For each chosen
 platform, apply its adapter preset (per `.throughline/references/sync-adapters.md`):
 register the platform, transform group, format, and `outputReferences`
 (true for web → preserves the semantic→primitive cascade; false for native →

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@radicool/throughline",
-  "version": "0.21.4",
+  "version": "0.23.0",
   "description": "Build a complete design system end to end — author in Figma, sync tokens to code, generate Storybook. Usable from Claude Code, Cursor, Codex, or any AGENTS.md agent.",
   "type": "module",
   "bin": {