@motion-proto/live-tokens 0.47.0 → 0.48.0

package/src/editor/docs/content/themes-workflow.md

@@ -1,60 +1,100 @@
 # Themes
 
-Save your work, switch between themes, and ship one to production.
+Save your work, switch between looks, and ship one to production.
+
+## The Theme panel
+
+The **Theme** panel at the foot of the editor sidebar holds the whole look:
+colors, type, and a setting for every component you changed, in one file. It
+carries the name the look ships under, whether production is running it, and
+**Adopt**. Two parts sit under it, each a read-out rather than a file to manage.
+
+- **Colors & Type** holds the design tokens. Components read those tokens to
+  define their appearance. It names the two faces the page is showing.
+- **Components** counts how many components run something the theme does not
+  carry, and opens the component editors.
+
+A theme holds its own copy of every part, so one theme can never break another.
 
 ## How themes work
 
-- **Your live edits** are what the page shows right now. They save to your
-  browser automatically and survive a reload, but they are not yet a file.
-- **A saved theme** is a named JSON file in `src/live-tokens/data/themes/`. You
-  create one with **Save as**.
-- **The active theme** is the saved theme the page loads at startup. Exactly one
-  at a time.
-- **The production theme** is the one that ships. Promoting sets it.
+A theme is a document, and the editor works the way any editor does.
+
+- **A theme** is a named JSON file in `src/live-tokens/data/themes/`. It carries
+  the whole look: the colors and type plus a setting for every component you
+  changed.
+- **The open theme** is the one the editor is working on, named in
+  `themes/_active.json`. One at a time.
+- **Your unsaved edits** are what the page shows right now. The editor keeps
+  them in your browser as you work and writes them to a buffer, `_working.json`,
+  one slot per part of the look. **Save** captures that buffer into the open
+  theme.
+- **The production theme** is the one your site ships, named in
+  `themes/_production.json`. Only **Adopt** changes it.
+
+Absence is the answer for anything untouched: a buffer exists only where the
+look sits off the shipped default, so a new project has none at all.
 
 ## Saving
 
-In the editor header:
+In the Theme panel:
 
-- **Save** updates the current theme.
-- **Save as** names a new theme. Use it for your first save and for forking.
+- **Save** captures the look on screen into the open theme. Your colors and type
+  go in as part of it, so there is nothing to save first.
+- **Save As** names a new theme. Use it for your first save and for forking.
 
-Names are tidied to lowercase with underscores, so "My Brand!" becomes
-`my_brand`. There is a built-in `default` theme you can always return to; the
-editor never overwrites it.
+Component edits are the exception. Each component editor holds its own unsaved
+state, which this panel cannot write, so save a component in its editor before
+capturing it. The panel says how many are waiting.
+
+Names are tidied to lowercase with hyphens, so "My Brand!" becomes `my-brand`,
+and a leading underscore is dropped: those names are reserved for the buffer.
+**Motion Proto** is the built-in theme and is read-only. You can always return
+to it, and the editor never overwrites it, so start your own with **Save As**.
 
 ## Switching
 
-The file menu lists every saved theme. Pick one to make it active; the page
-reloads with it applied. Your current edits are saved to the previous theme
-first, so you don't lose work.
+**Load** lists your saved themes and the seven example looks. Picking one shows
+it on the page as a preview with nothing written to disk, so you can try each
+look and compare. **Save** in that window opens the previewed theme: its copies
+fill the buffers, components it does not carry go back to their defaults, and
+the editor works on it from then on. **Cancel** returns you to where you were.
+Trying a look never changes what your site ships.
+
+**Colors and type only. Keep my shapes.** narrows the load to the palette and
+the fonts: your component settings stay as they are and the theme you have open
+stays open. Saved colors and type files are listed there too, marked *colors &
+type*, and picking one is always that narrower load.
 
 ## Shipping
 
-**Promote to production** is the "ship it" step. It bakes the theme's variables
-into `src/live-tokens/data/tokens.generated.css`, which your build bundles
-alongside `tokens.css`. Fonts regenerate to match.
+**Adopt**, in the Theme panel, is the "ship it" step, and it ships the whole
+look. It saves the open theme, then bakes that theme into
+`src/live-tokens/data/tokens.generated.css`, which your build bundles alongside
+`tokens.css`: the colors and type plus every component the theme carries. Fonts
+regenerate to match. The line under the theme name says whether production is
+running this theme.
 
-Production builds (`npm run build`) ship only that plain CSS and your
-components. No editor, no JSON loading, no runtime indirection. If you save
-while the production theme is active, the generated CSS updates immediately,
-with no separate promote step.
+Production is one saved theme, so nothing else publishes. Trying a look, moving
+a token, saving a theme: all of it leaves the generated CSS alone until you
+Adopt. A component editor's Adopt runs the same whole-look step, because a
+component never ships alone. Adopting while Motion Proto is open saves your look
+as a theme of your own first, since the built-in one is read-only.
 
-## Manifests
-
-A **manifest** bundles one theme plus a config for each component into a single
-named set. Useful when you run several brands and want each to apply its theme
-and component tweaks in one move. There is a protected default and an active
-manifest; applying one swaps everything at once.
+Production builds (`npm run build`) ship only that plain CSS and your
+components. No editor, no JSON loading, no runtime indirection.
 
 ## Keeping your work safe
 
-Everything under `src/live-tokens/data/` is plain JSON, so commit it. Themes
-show up as readable diffs you can review per branch. There are no automatic
-backups: git is your safety net. To experiment freely, **Save as** a new name
-first, then edit.
+Everything under `src/live-tokens/data/` is plain JSON, so commit it. Themes show
+up as readable diffs you can review per branch, and the buffer shows up as the
+work you have not saved into a theme yet. Nothing is backed up anywhere else:
+git is your safety net. To experiment freely, **Save As** a new name first, then
+edit.
 
 ## Where to go next
 
+- **[Where themes live](where-themes-live.md)**: the files behind all of this,
+  and what writes each one.
 - **[Creating components](creating-components.md)**: make your own components
   editable in the same editor.

package/src/editor/docs/content/where-themes-live.md

@@ -0,0 +1,61 @@
+# Where themes live
+
+Everything the editor writes is plain JSON and CSS inside your project. There
+is no database and no hidden state: the files are the storage, and git is the
+history.
+
+## The data tree
+
+```
+src/live-tokens/data/
+  themes/
+    _active.json         names the theme the editor has open
+    _production.json     names the theme your site ships
+    default.json         Motion Proto, the built-in look, rewritten at boot
+    my-brand.json        a saved theme: the whole look in one file
+  colors-and-type/
+    _working.json        unsaved colors and type edits
+  component-configs/
+    button/
+      default.json       Button's shipped settings, derived at boot
+      _working.json      unsaved Button edits
+      my-button.json     a preset you saved from the Button editor
+  tokens.generated.css   the baked CSS your production build ships
+src/system/styles/
+  tokens.css             your token vocabulary, hand-authored, never written
+  fonts.css              font imports, rewritten when you Adopt
+```
+
+A saved theme carries the whole look by value: the colors and type plus a
+setting for every component you changed. It depends on no other file, so
+deleting anything else never breaks it.
+
+## What writes when
+
+- **Editing** changes the page through CSS variables. The editor keeps your
+  edits in the browser as you work and writes them to the `_working.json`
+  buffers when you save a component or capture the look. A buffer exists only
+  where your look sits off the shipped default, so a fresh project has none.
+- **Save** captures the buffers into the open theme's file. That file is the
+  durable copy of your look.
+- **Load** fills the buffers from the theme you picked and points
+  `themes/_active.json` at it. Nothing else changes, so trying looks is free.
+- **Adopt** points `themes/_production.json` at the open theme, bakes it into
+  `tokens.generated.css`, and rewrites `fonts.css` to match. It is the only
+  action that changes what your site ships.
+
+The `default.json` files are the shipped baseline. The editor derives them at
+boot and refreshes them when the package updates; it never saves your work
+over them.
+
+## What to commit
+
+All of it. The data tree is designed to live in git: themes diff readably, the
+two pointers say what is open and what ships, and a `_working.json` in a diff
+is exactly the work you have not yet saved into a theme. Nothing is backed up
+anywhere else.
+
+## Where to go next
+
+- **[Themes](themes-workflow.md)**: the workflow built on these files: saving,
+  loading, and shipping.

package/src/editor/docs/content.generated.ts

@@ -2,9 +2,10 @@
 // Source of truth: src/editor/docs/content/*.md  ·  regenerate: npm run sync:docs
 
 export const docContent: Record<string, string> = {
-  "01-overview": "# Overview\n\nLive Tokens is a design system for building Svelte microsites quickly. You\nstyle your site by editing tokens and components in a live editor. When it looks right, you save the manifest and ship it.\n\n## How it works\n\n- The editor runs in your dev server, on top of your real pages. You style in\n  context, not in a separate sandbox.\n- Every change updates a CSS variable, so the page repaints instantly. No\n  reload, no build step.\n- Saving writes a small JSON file into your project. Shipping bakes your chosen\n  theme into a plain CSS file that the build bundles.\n- The editor is dev-only. Production ships plain CSS variables and the\n  components you used, nothing else.\n\n## What you can edit\n\n- **Tokens**: the design-system primitives, colour palettes, type, spacing,\n  radius, shadow, and gradients, that apply across your whole site.\n- **Components**: the package ships about 25 editable components (Button,\n  IconButton, Card, Dialog, Table, and more). You style components by changing\n  the tokens assigned to each property.\n\n## Where to go next\n\n- **[Getting started](getting-started.md)**: scaffold a project and make your\n  first edit.\n- **[Editing tokens](editing-tokens.md)**: a tour of the editor.\n- **[Themes](themes-workflow.md)**: save, switch, and ship.\n- **[Creating components](creating-components.md)**: make your own components\n  editable.\n",
+  "01-overview": "# Overview\n\nLive Tokens is a design system for building Svelte microsites quickly. You\nstyle your site by editing tokens and components in a live editor. When it looks right, you save the theme and ship it.\n\n## How it works\n\n- The editor runs in your dev server, on top of your real pages. You style in\n  context, not in a separate sandbox.\n- Every change updates a CSS variable, so the page repaints instantly. No\n  reload, no build step.\n- Saving writes a small JSON file into your project. Shipping bakes your chosen\n  theme into a plain CSS file that the build bundles.\n- The editor is dev-only. Production ships plain CSS variables and the\n  components you used, nothing else.\n\n## What you can edit\n\n- **Tokens**: the design-system primitives, colour palettes, type, spacing,\n  radius, shadow, and gradients, that apply across your whole site.\n- **Components**: the package ships about 25 editable components (Button,\n  IconButton, Card, Dialog, Table, and more). You style components by changing\n  the tokens assigned to each property.\n\n## Where to go next\n\n- **[Getting started](getting-started.md)**: scaffold a project and make your\n  first edit.\n- **[Editing tokens](editing-tokens.md)**: a tour of the editor.\n- **[Themes](themes-workflow.md)**: save, switch, and ship.\n- **[Creating components](creating-components.md)**: make your own components\n  editable.\n",
   "creating-components": "# Creating components\n\nThe package ships about 25 editable components. When you need one it doesn't\nhave, you can make your own Svelte component editable, so anyone using the\neditor can re-point its colours, type, and spacing without touching code.\n\nThe simplest way is to ask Claude. The package bundles a Claude Code skill that\nknows the conventions, writes the files, and checks the result for you.\n\n## Install the skills\n\n```bash\nnpx @motion-proto/live-tokens setup-claude\n```\n\nThis copies the bundled skills into your project's `.claude/skills/`. Once\nthey're there, Claude Code picks them up automatically.\n\n## Ask for a component\n\nDescribe what you want in plain English. Phrases like these trigger the skill:\n\n- \"Add a Toggle component to live-tokens\"\n- \"Make this Svelte component editable in the live-tokens editor\"\n- \"Create a Stat component with a value and a label\"\n\nClaude asks any clarifying questions it needs (which variants, which states,\nwhich parts), then writes the component, registers it with the editor, and runs\nits verification checklist. When it finishes, open `/live-tokens/components` to see your new\ncomponent in the editor and confirm everything works.\n\n## What you get\n\n- A runtime component whose editable properties default to your theme tokens.\n- An editor entry that appears under **Custom** in the `/live-tokens/components` view.\n- The naming and wiring handled for you, so the component fits the system.\n\nAdvanced authors who want to write a component by hand can read the naming and\nstate-model conventions shipped in the package\n(`src/system/styles/CONVENTIONS.md` and the skill's own `SKILL.md`).\n",
-  "editing-tokens": "# Editing tokens\n\nA tour of the editor. The page behind it repaints on every change; saving\nwrites a theme file you can reload later.\n\nThe editor has two views:\n\n- **Tokens**: the design-system primitives (colour, type, spacing, and so on).\n  They apply everywhere your site uses them.\n- **Components**: per-component editors. Re-Assign what tokens a component uses\n  without changing the underlying system.\n\nThis page covers **Tokens**. For components, see\n[Creating components](creating-components.md).\n\n## Palettes\n\nMost colour work happens here. Each palette (Brand, Accent, Neutral, Canvas,\nSuccess, Warning, Info, Danger, and a few more) has:\n\n- **Base colour.** Pick a hex; the palette derives an 11-step ramp (100 to 950)\n  from it.\n- **Curves.** Two curves shape how lightness and saturation fall off across the\n  ramp. Drag the handles to bias it darker, lighter, or more saturated.\n- **Overrides.** Lock a single step to a hand-picked hex when the curve doesn't\n  land where you want.\n\nEditing a palette base ripples through every colour that depends on it, in real\ntime. Colours use OKLCH, so the ramp stays perceptually even across hues\nwithout muddy mid-tones.\n\n## Type\n\n- **Fonts.** Add sources from Google Fonts, Adobe (Typekit), a CSS URL, or an\n  inline `@font-face`. The font loads in the page as soon as you add it.\n- **Stacks.** Named font cascades you reference by token, such as a display\n  stack and a body stack.\n- **Sizes and weights.** A t-shirt scale (xs, sm, md, lg, xl, 2xl…) for size and\n  a numeric scale (100 to 900) for weight.\n\n## Spacing, radius, shadow\n\nNumeric scales with a slider per step.\n\n- **Spacing**: the padding, gap, and margin scale.\n- **Radius**: none through full.\n- **Shadow**: colour, offset, blur, spread, and opacity per step, with stacked\n  shadows supported.\n\nChange a step and every element using it repaints.\n\n## Overlays and gradients\n\n- **Overlays** are translucent tints layered over surfaces, like the subtle\n  tint a card gets on hover. Set a colour and opacity per state.\n- **Gradients** are reusable gradient tokens with a stop list and direction, for\n  hero panels and accent backgrounds.\n\n## Columns\n\nThe page-grid overlay. Set column count, gutter, and outer margin, and toggle\nthe visual guide with `Cmd/Ctrl+G`. Pages built on the column system reflow\nlive.\n\n## Saving\n\nThe editor saves to your browser continuously, so work survives a reload\nmid-edit. **Save** is a separate step: it writes a named theme file under\n`src/live-tokens/data/themes/`.\n\nThe header gives you undo/redo (`Cmd/Ctrl+Z`, `Cmd/Ctrl+Shift+Z`) and a file\nmenu for New, Save, Save as, Switch, and Delete. You can keep many themes side\nby side; one is active at a time. See [Themes](themes-workflow.md) for the full\nlifecycle.\n",
-  "getting-started": "# Getting started\n\nScaffold a live token site in a moments. You need Node 20 or later, a\npackage manager (npm, pnpm, or yarn), and a browser. Open claude code in your repo and start building.\n\n## Scaffold a new app\n\n```bash\nnpm create @motion-proto/live-tokens@latest my-app\ncd my-app\nnpm install\nnpm run dev\n```\n\nOpen the URL Vite prints (usually `http://localhost:5173`). You get a\none-page Svelte + Vite app that depends on the published package, with the\neditor wired up and the full component set ready to import.\n\n`npx @motion-proto/live-tokens create my-app` runs the same scaffold without\nthe initialiser package.\n\n### What the scaffold gives you\n\nEvery editable file lives under `src/` and is committed, so `npm install` and\nversion upgrades never touch your styles. The package code stays in\n`node_modules`.\n\n| Path | What it is |\n|------|------------|\n| `src/pages/Home.svelte` | The starter page. Replace it with your own content. |\n| `src/App.svelte` | Your routes. `<LiveTokensRouter>` adds dev-only routes under a reserved `/live-tokens/*` namespace: `/live-tokens/editor`, `/live-tokens/components`, and `/live-tokens/docs`. |\n| `src/system/styles/tokens.css` | Your base token vocabulary, hand-authored. |\n| `src/styles/site.css` | Themed page typography, yours to edit. |\n\n## Your first edit\n\n1. Run `npm run dev` and open the home page.\n2. Click **Open Token Editor**, or visit `/live-tokens/editor`. The editor opens beside\n   the page.\n3. Open **Palettes**, pick **Brand**, and change the base hex. The page\n   repaints as you type.\n4. Open the file menu and choose **Save as**. A theme appears as JSON under\n   `src/live-tokens/data/themes/`.\n5. Reload. Your saved theme is the active theme, so the page returns as you\n   left it.\n\n## What you just changed\n\nEvery edit sets a CSS custom property on `:root`. Your components read those\nproperties through `var(--...)`. There is no token build step and no\npreprocessor rewriting your code: the page renders against plain CSS variables\nthe editor swaps live.\n\nTo ship, promote a theme to production in the editor. That bakes the theme's\nvariables into `src/live-tokens/data/tokens.generated.css`, which your build\nbundles alongside `tokens.css`. The editor itself never reaches production.\n\nAlready have a Svelte 5 + Vite app? The\n[README](https://github.com/motionproto/live-tokens#readme) covers installing\ninto an existing project.\n\n## Where to go next\n\n- **[Editing tokens](editing-tokens.md)**: a tour of the editor.\n- **[Themes](themes-workflow.md)**: save, switch, and ship.\n- **[Creating components](creating-components.md)**: make your own component\n  editable.\n",
-  "themes-workflow": "# Themes\n\nSave your work, switch between themes, and ship one to production.\n\n## How themes work\n\n- **Your live edits** are what the page shows right now. They save to your\n  browser automatically and survive a reload, but they are not yet a file.\n- **A saved theme** is a named JSON file in `src/live-tokens/data/themes/`. You\n  create one with **Save as**.\n- **The active theme** is the saved theme the page loads at startup. Exactly one\n  at a time.\n- **The production theme** is the one that ships. Promoting sets it.\n\n## Saving\n\nIn the editor header:\n\n- **Save** updates the current theme.\n- **Save as** names a new theme. Use it for your first save and for forking.\n\nNames are tidied to lowercase with underscores, so \"My Brand!\" becomes\n`my_brand`. There is a built-in `default` theme you can always return to; the\neditor never overwrites it.\n\n## Switching\n\nThe file menu lists every saved theme. Pick one to make it active; the page\nreloads with it applied. Your current edits are saved to the previous theme\nfirst, so you don't lose work.\n\n## Shipping\n\n**Promote to production** is the \"ship it\" step. It bakes the theme's variables\ninto `src/live-tokens/data/tokens.generated.css`, which your build bundles\nalongside `tokens.css`. Fonts regenerate to match.\n\nProduction builds (`npm run build`) ship only that plain CSS and your\ncomponents. No editor, no JSON loading, no runtime indirection. If you save\nwhile the production theme is active, the generated CSS updates immediately,\nwith no separate promote step.\n\n## Manifests\n\nA **manifest** bundles one theme plus a config for each component into a single\nnamed set. Useful when you run several brands and want each to apply its theme\nand component tweaks in one move. There is a protected default and an active\nmanifest; applying one swaps everything at once.\n\n## Keeping your work safe\n\nEverything under `src/live-tokens/data/` is plain JSON, so commit it. Themes\nshow up as readable diffs you can review per branch. There are no automatic\nbackups: git is your safety net. To experiment freely, **Save as** a new name\nfirst, then edit.\n\n## Where to go next\n\n- **[Creating components](creating-components.md)**: make your own components\n  editable in the same editor.\n",
+  "editing-tokens": "# Editing tokens\n\nA tour of the editor. The page behind it repaints on every change; saving\nwrites a theme file you can reload later.\n\nThe editor has two views:\n\n- **Tokens**: the design-system primitives (colour, type, spacing, and so on).\n  They apply everywhere your site uses them.\n- **Components**: per-component editors. Re-Assign what tokens a component uses\n  without changing the underlying system.\n\nThis page covers **Tokens**. For components, see\n[Creating components](creating-components.md).\n\n## Palettes\n\nMost colour work happens here. Each palette (Brand, Accent, Neutral, Canvas,\nSuccess, Warning, Info, Danger, and a few more) has:\n\n- **Base colour.** Pick a hex; the palette derives an 11-step ramp (100 to 950)\n  from it.\n- **Curves.** Two curves shape how lightness and saturation fall off across the\n  ramp. Drag the handles to bias it darker, lighter, or more saturated.\n- **Overrides.** Lock a single step to a hand-picked hex when the curve doesn't\n  land where you want.\n\nEditing a palette base ripples through every colour that depends on it, in real\ntime. Colours use OKLCH, so the ramp stays perceptually even across hues\nwithout muddy mid-tones.\n\n## Type\n\n- **Fonts.** Add sources from Google Fonts, Adobe (Typekit), a CSS URL, or an\n  inline `@font-face`. The font loads in the page as soon as you add it.\n- **Stacks.** Named font cascades you reference by token, such as a display\n  stack and a body stack.\n- **Sizes and weights.** A t-shirt scale (xs, sm, md, lg, xl, 2xl…) for size and\n  a numeric scale (100 to 900) for weight.\n\n## Spacing, radius, shadow\n\nNumeric scales with a slider per step.\n\n- **Spacing**: the padding, gap, and margin scale.\n- **Radius**: none through full.\n- **Shadow**: colour, offset, blur, spread, and opacity per step, with stacked\n  shadows supported.\n\nChange a step and every element using it repaints.\n\n## Overlays and gradients\n\n- **Overlays** are translucent tints layered over surfaces, like the subtle\n  tint a card gets on hover. Set a colour and opacity per state.\n- **Gradients** are reusable gradient tokens with a stop list and direction, for\n  hero panels and accent backgrounds.\n\n## Columns\n\nThe page-grid overlay. Set column count, gutter, and outer margin, and toggle\nthe visual guide with `Cmd/Ctrl+G`. Pages built on the column system reflow\nlive.\n\n## Saving\n\nThe editor saves to your browser continuously, so work survives a reload\nmid-edit. Writing a file is a separate step: the **Theme** panel at the foot of\nthe sidebar has **Save**, **Save As**, and **Load**, and each theme is one JSON\nfile under `src/live-tokens/data/themes/`.\n\nThe header gives you undo/redo (`Cmd/Ctrl+Z`, `Cmd/Ctrl+Shift+Z`). You can keep\nmany themes side by side; one is open at a time, and only **Adopt** publishes\none. See [Themes](themes-workflow.md) for the full lifecycle.\n",
+  "getting-started": "# Getting started\n\nScaffold a live token site in a moments. You need Node 20 or later, a\npackage manager (npm, pnpm, or yarn), and a browser. Open claude code in your repo and start building.\n\n## Scaffold a new app\n\n```bash\nnpm create @motion-proto/live-tokens@latest my-app\ncd my-app\nnpm install\nnpm run dev\n```\n\nOpen the URL Vite prints (usually `http://localhost:5173`). You get a\none-page Svelte + Vite app that depends on the published package, with the\neditor wired up and the full component set ready to import.\n\n`npx @motion-proto/live-tokens create my-app` runs the same scaffold without\nthe initialiser package.\n\n### What the scaffold gives you\n\nEvery editable file lives under `src/` and is committed, so `npm install` and\nversion upgrades never touch your styles. The package code stays in\n`node_modules`.\n\n| Path | What it is |\n|------|------------|\n| `src/pages/Home.svelte` | The starter page. Replace it with your own content. |\n| `src/App.svelte` | Your routes. `<LiveTokensRouter>` adds dev-only routes under a reserved `/live-tokens/*` namespace: `/live-tokens/editor`, `/live-tokens/components`, and `/live-tokens/docs`. |\n| `src/system/styles/tokens.css` | Your base token vocabulary, hand-authored. |\n| `src/styles/site.css` | Themed page typography, yours to edit. |\n\n## Your first edit\n\n1. Run `npm run dev` and open the home page.\n2. Click **Open Token Editor**, or visit `/live-tokens/editor`. The editor opens beside\n   the page.\n3. Open **Palettes**, pick **Brand**, and change the base hex. The page\n   repaints as you type.\n4. In the **Theme** panel at the foot of the sidebar, choose **Save As**. Your\n   theme appears as JSON under `src/live-tokens/data/themes/`.\n5. Reload. The editor reopens on your theme, so the page returns as you left\n   it.\n\n## What you just changed\n\nEvery edit sets a CSS custom property on `:root`. Your components read those\nproperties through `var(--...)`. There is no token build step and no\npreprocessor rewriting your code: the page renders against plain CSS variables\nthe editor swaps live.\n\nTo ship, click **Adopt** in the Theme panel. That saves the open theme and bakes\nit into `src/live-tokens/data/tokens.generated.css`, which your build bundles\nalongside `tokens.css`. Adopt is the only action that changes what your site\nships, so try any look you like first. The editor itself never reaches\nproduction.\n\nAlready have a Svelte 5 + Vite app? The\n[README](https://github.com/motionproto/live-tokens#readme) covers installing\ninto an existing project.\n\n## Where to go next\n\n- **[Editing tokens](editing-tokens.md)**: a tour of the editor.\n- **[Themes](themes-workflow.md)**: save, switch, and ship.\n- **[Creating components](creating-components.md)**: make your own component\n  editable.\n",
+  "themes-workflow": "# Themes\n\nSave your work, switch between looks, and ship one to production.\n\n## The Theme panel\n\nThe **Theme** panel at the foot of the editor sidebar holds the whole look:\ncolors, type, and a setting for every component you changed, in one file. It\ncarries the name the look ships under, whether production is running it, and\n**Adopt**. Two parts sit under it, each a read-out rather than a file to manage.\n\n- **Colors & Type** holds the design tokens. Components read those tokens to\n  define their appearance. It names the two faces the page is showing.\n- **Components** counts how many components run something the theme does not\n  carry, and opens the component editors.\n\nA theme holds its own copy of every part, so one theme can never break another.\n\n## How themes work\n\nA theme is a document, and the editor works the way any editor does.\n\n- **A theme** is a named JSON file in `src/live-tokens/data/themes/`. It carries\n  the whole look: the colors and type plus a setting for every component you\n  changed.\n- **The open theme** is the one the editor is working on, named in\n  `themes/_active.json`. One at a time.\n- **Your unsaved edits** are what the page shows right now. The editor keeps\n  them in your browser as you work and writes them to a buffer, `_working.json`,\n  one slot per part of the look. **Save** captures that buffer into the open\n  theme.\n- **The production theme** is the one your site ships, named in\n  `themes/_production.json`. Only **Adopt** changes it.\n\nAbsence is the answer for anything untouched: a buffer exists only where the\nlook sits off the shipped default, so a new project has none at all.\n\n## Saving\n\nIn the Theme panel:\n\n- **Save** captures the look on screen into the open theme. Your colors and type\n  go in as part of it, so there is nothing to save first.\n- **Save As** names a new theme. Use it for your first save and for forking.\n\nComponent edits are the exception. Each component editor holds its own unsaved\nstate, which this panel cannot write, so save a component in its editor before\ncapturing it. The panel says how many are waiting.\n\nNames are tidied to lowercase with hyphens, so \"My Brand!\" becomes `my-brand`,\nand a leading underscore is dropped: those names are reserved for the buffer.\n**Motion Proto** is the built-in theme and is read-only. You can always return\nto it, and the editor never overwrites it, so start your own with **Save As**.\n\n## Switching\n\n**Load** lists your saved themes and the seven example looks. Picking one shows\nit on the page as a preview with nothing written to disk, so you can try each\nlook and compare. **Save** in that window opens the previewed theme: its copies\nfill the buffers, components it does not carry go back to their defaults, and\nthe editor works on it from then on. **Cancel** returns you to where you were.\nTrying a look never changes what your site ships.\n\n**Colors and type only. Keep my shapes.** narrows the load to the palette and\nthe fonts: your component settings stay as they are and the theme you have open\nstays open. Saved colors and type files are listed there too, marked *colors &\ntype*, and picking one is always that narrower load.\n\n## Shipping\n\n**Adopt**, in the Theme panel, is the \"ship it\" step, and it ships the whole\nlook. It saves the open theme, then bakes that theme into\n`src/live-tokens/data/tokens.generated.css`, which your build bundles alongside\n`tokens.css`: the colors and type plus every component the theme carries. Fonts\nregenerate to match. The line under the theme name says whether production is\nrunning this theme.\n\nProduction is one saved theme, so nothing else publishes. Trying a look, moving\na token, saving a theme: all of it leaves the generated CSS alone until you\nAdopt. A component editor's Adopt runs the same whole-look step, because a\ncomponent never ships alone. Adopting while Motion Proto is open saves your look\nas a theme of your own first, since the built-in one is read-only.\n\nProduction builds (`npm run build`) ship only that plain CSS and your\ncomponents. No editor, no JSON loading, no runtime indirection.\n\n## Keeping your work safe\n\nEverything under `src/live-tokens/data/` is plain JSON, so commit it. Themes show\nup as readable diffs you can review per branch, and the buffer shows up as the\nwork you have not saved into a theme yet. Nothing is backed up anywhere else:\ngit is your safety net. To experiment freely, **Save As** a new name first, then\nedit.\n\n## Where to go next\n\n- **[Where themes live](where-themes-live.md)**: the files behind all of this,\n  and what writes each one.\n- **[Creating components](creating-components.md)**: make your own components\n  editable in the same editor.\n",
+  "where-themes-live": "# Where themes live\n\nEverything the editor writes is plain JSON and CSS inside your project. There\nis no database and no hidden state: the files are the storage, and git is the\nhistory.\n\n## The data tree\n\n```\nsrc/live-tokens/data/\n  themes/\n    _active.json         names the theme the editor has open\n    _production.json     names the theme your site ships\n    default.json         Motion Proto, the built-in look, rewritten at boot\n    my-brand.json        a saved theme: the whole look in one file\n  colors-and-type/\n    _working.json        unsaved colors and type edits\n  component-configs/\n    button/\n      default.json       Button's shipped settings, derived at boot\n      _working.json      unsaved Button edits\n      my-button.json     a preset you saved from the Button editor\n  tokens.generated.css   the baked CSS your production build ships\nsrc/system/styles/\n  tokens.css             your token vocabulary, hand-authored, never written\n  fonts.css              font imports, rewritten when you Adopt\n```\n\nA saved theme carries the whole look by value: the colors and type plus a\nsetting for every component you changed. It depends on no other file, so\ndeleting anything else never breaks it.\n\n## What writes when\n\n- **Editing** changes the page through CSS variables. The editor keeps your\n  edits in the browser as you work and writes them to the `_working.json`\n  buffers when you save a component or capture the look. A buffer exists only\n  where your look sits off the shipped default, so a fresh project has none.\n- **Save** captures the buffers into the open theme's file. That file is the\n  durable copy of your look.\n- **Load** fills the buffers from the theme you picked and points\n  `themes/_active.json` at it. Nothing else changes, so trying looks is free.\n- **Adopt** points `themes/_production.json` at the open theme, bakes it into\n  `tokens.generated.css`, and rewrites `fonts.css` to match. It is the only\n  action that changes what your site ships.\n\nThe `default.json` files are the shipped baseline. The editor derives them at\nboot and refreshes them when the package updates; it never saves your work\nover them.\n\n## What to commit\n\nAll of it. The data tree is designed to live in git: themes diff readably, the\ntwo pointers say what is open and what ships, and a `_working.json` in a diff\nis exactly the work you have not yet saved into a theme. Nothing is backed up\nanywhere else.\n\n## Where to go next\n\n- **[Themes](themes-workflow.md)**: the workflow built on these files: saving,\n  loading, and shipping.\n",
 };

package/src/editor/index.ts

@@ -8,7 +8,7 @@ export type { BootLiveTokensOptions } from './bootstrap';
 
 export { columnsVisible, toggleColumns, init as initColumnsOverlay } from './overlay/columnsOverlay';
 export { configureEditor, storageKey } from './core/store/editorConfig';
-export { activeFileName } from './core/store/editorConfigStore';
+export { openThemeSlug } from './core/store/editorConfigStore';
 export { init as initRouter, route, navigate, setScrollReset } from './core/routing/router';
 export { init as initCssVarSync } from './core/cssVarSync';
 export {
@@ -22,22 +22,20 @@ export {
 export { setCssVar, removeCssVar } from './core/cssVarSync';
 
 export {
-  listThemes,
-  loadTheme,
-  saveTheme,
-  deleteTheme,
-  getActiveTheme,
-  setActiveFile,
-  getProductionInfo,
-  setProductionFile,
+  listColorsAndType,
+  loadColorsAndType,
+  saveColorsAndType,
+  deleteColorsAndType,
+  getActiveColorsAndType,
+  writeWorkingColorsAndType,
   sanitizeFileName,
-} from './core/themes/themeService';
-export type { ProductionInfo } from './core/themes/themeService';
+} from './core/themes/colorsAndTypeService';
 
 export type {
   PaletteConfig,
-  Theme,
-  ThemeMeta,
+  ColorsAndType,
+  ColorsAndTypeMeta,
+  LiveSource,
   GradientStyle,
   GradientStop,
   FontSource,
@@ -48,22 +46,24 @@ export type {
   FontStackVariable,
   SystemCascadePreset,
   GenericFamily,
-  Manifest,
-  ManifestMeta,
+  Theme,
+  ThemeMeta,
 } from './core/themes/themeTypes';
 
 export {
-  listManifests,
-  loadManifest,
-  saveManifest,
-  deleteManifest,
-  getActiveManifest,
-  setActiveManifest,
-  applyManifest,
-  saveAsManifest,
-  saveActiveManifest,
-} from './core/manifests/manifestService';
-export type { ApplyManifestResult } from './core/manifests/manifestService';
+  listThemes,
+  loadTheme,
+  saveTheme,
+  deleteTheme,
+  getActiveTheme,
+  setActiveTheme,
+  getProductionTheme,
+  applyTheme,
+  adoptLook,
+  saveAsTheme,
+  saveActiveTheme,
+} from './core/themes/themeService';
+export type { AdoptLookResult, ApplyThemeResult } from './core/themes/themeService';
 
 export {
   applyFontSources,
@@ -71,7 +71,7 @@ export {
   resolveFontStackValues,
   SYSTEM_CASCADES,
 } from './core/fonts/fontLoader';
-export { migrateThemeFonts, defaultFontSources, defaultFontStacks } from './core/fonts/fontMigration';
+export { migrateColorsAndTypeFonts, defaultFontSources, defaultFontStacks } from './core/fonts/fontMigration';
 
 export { hexToOklch, oklchToHex, gamutClamp } from './core/palettes/oklch';
 export type { Oklch } from './core/palettes/oklch';

package/src/editor/pages/ComponentEditorPage.svelte

@@ -3,7 +3,7 @@
 
   import { onMount, onDestroy } from 'svelte';
   import ComponentsTab from '../component-editor/scaffolding/ComponentsTab.svelte';
-  import ManifestFileManager from '../ui/ManifestFileManager.svelte';
+  import ThemePanel from '../ui/ThemePanel.svelte';
   import { navigate } from '../core/routing/router';
   import { getComponentRegistryEntries, validateRegistryAgainstServerScan } from '../component-editor/registry';
   import { listComponents } from '../core/components/componentConfigService';
@@ -177,7 +177,7 @@
     </div>
     {#if drawerOpen}
       <div class="sidebar-footer">
-        <ManifestFileManager />
+        <ThemePanel showComponentsLink={false} />
       </div>
     {/if}
   </nav>

package/src/editor/pages/EditorShell.svelte

@@ -2,16 +2,12 @@
   import { run } from 'svelte/legacy';
 
   import { onMount } from 'svelte';
-  import { get } from 'svelte/store';
   import VariablesTab from '../ui/VariablesTab.svelte';
   import ColorsTab from '../ui/colors/ColorsTab.svelte';
-  import ThemeFileManager from '../ui/ThemeFileManager.svelte';
   import EditorViewSwitcher from '../ui/EditorViewSwitcher.svelte';
   import ComponentsTab from '../component-editor/scaffolding/ComponentsTab.svelte';
-  import ManifestFileManager from '../ui/ManifestFileManager.svelte';
-  import { persistTheme, hydrateTheme } from '../core/themes/themeService';
+  import ThemePanel from '../ui/ThemePanel.svelte';
   import { scrollSectionIntoView } from '../ui/scrollSection';
-  import { editorState } from '../core/store/editorStore';
   import { editorView, sidebarCondensed, selectedComponent } from '../core/store/editorViewStore';
   import { componentDirty } from '../core/store/editorStore';
   import { getComponentRegistryEntries, validateRegistryAgainstServerScan } from '../component-editor/registry';
@@ -40,7 +36,6 @@
   const customNavItems = allComponentNavItems.filter((i) => i.origin === 'custom');
 
   let selectedTokenSection: string | null = $state(null);
-  let saveStatus: 'idle' | 'saving' | 'saved' | 'error' = $state('idle');
 
   // 'auto' = open by default. Auto-condensing on shellWidth caused a bounce
   // as the overlay panel grew past the threshold mid-animation.
@@ -88,27 +83,6 @@
     sidebarCondensed.update((v) => !(v === true));
   }
 
-  async function handleSave(detail: { fileName: string; displayName: string }) {
-    const { fileName, displayName } = detail;
-    saveStatus = 'saving';
-    try {
-      await persistTheme(get(editorState), fileName, displayName);
-      saveStatus = 'saved';
-      setTimeout(() => { saveStatus = 'idle'; }, 2000);
-    } catch {
-      saveStatus = 'error';
-      setTimeout(() => { saveStatus = 'idle'; }, 3000);
-    }
-  }
-
-  async function handleLoad(detail: { fileName: string }) {
-    try {
-      await hydrateTheme(detail.fileName);
-    } catch {
-      // silent
-    }
-  }
-
   onMount(async () => {
     try {
       const summaries = await listComponents();
@@ -152,7 +126,7 @@
       </div>
       {#if !condensed}
         <div class="sidebar-footer">
-          <ThemeFileManager {saveStatus} onsave={handleSave} onload={handleLoad} />
+          <ThemePanel />
         </div>
       {/if}
     {:else if $editorView === 'colors'}
@@ -172,7 +146,7 @@
       </div>
       {#if !condensed}
         <div class="sidebar-footer">
-          <ThemeFileManager {saveStatus} onsave={handleSave} onload={handleLoad} />
+          <ThemePanel />
         </div>
       {/if}
     {:else}
@@ -217,7 +191,7 @@
       </div>
       {#if !condensed}
         <div class="sidebar-footer">
-          <ManifestFileManager />
+          <ThemePanel />
         </div>
       {/if}
     {/if}

package/src/editor/ui/BezierCurveEditor.svelte

@@ -4,7 +4,7 @@
   import {
     type CurveAnchor, type CurveConfig,
     CURVE_H, CURVE_PAD_Y, CURVE_Y_PAD,
-    isCornerAnchor, curveXToSvg, curveYToSvg, svgToX, svgToY,
+    isCornerAnchor, tangentAnchor, curveXToSvg, curveYToSvg, svgToX, svgToY,
     evalBezier, buildCurvePath, curveTemplates,
     serializeCurve, deserializeCurve,
   } from './curveEngine';
@@ -191,7 +191,7 @@
     const a = anchors[index];
     const updated = [...anchors];
     if (isCornerAnchor(a)) {
-      updated[index] = { ...a, inDx: -15, inDy: 0, outDx: 15, outDy: 0 };
+      updated[index] = tangentAnchor(a.x, a.y, anchors[index - 1] ?? null, anchors[index + 1] ?? null);
     } else {
       updated[index] = { ...a, inDx: 0, inDy: 0, outDx: 0, outDy: 0 };
     }

package/src/editor/ui/ColorEditPanel.svelte

@@ -340,7 +340,7 @@
      regardless of row content; the row wrappers dissolve into the grid. */
   .hsl-sliders {
     display: grid;
-    grid-template-columns: 2.5rem minmax(6rem, 1fr) 3.5rem 0.75rem;
+    grid-template-columns: 1.25rem minmax(6rem, 1fr) 3.5rem 0.75rem;
     gap: var(--ui-space-6) var(--ui-space-8);
     align-items: center;
   }