← Commit history

Migrate from adom-theme-system: rename + version lock at 2.0.0

John Lauer ·49488ea3c0 · ·parent 689c832
8 files changed +878−2
README.md+212−2
@@ -1,3 +1,213 @@-# Adom Theme+# Adom Theme System -The canonical Adom application theme: five schemes, exact tokens, font pairings, the version-locked VS Code pack, and the implementation contract.+The color schemes, tokens, and typefaces that make every Adom surface look like one company built it. This page is the extensive tour: what the five schemes look like, the exact background and foreground values, the fonts we install for the user, and how the system is wired into Hydrogen Desktop (including VS Code), Adom Desktop, and the wiki. The machine-readable contract an implementing agent should follow is [SKILL.md](https://wiki.adom.inc/api/pages/adom/adom-theme-system/files/SKILL.md) on this same page (install: `adom-wiki pkg install adom-theme-system`).++Why this gets its own page: themes are a big part of whether Adom reads as a professional product or an amateur one. A user touches three of our surfaces in their first ten minutes (Hydrogen Desktop, Adom Desktop, the wiki), and any mismatch between them is instantly visible. So the palette, the names, the fonts, and the rules live in one place, with screenshots proving what each surface actually renders today.++---++## 0. Identity and versioning (one number, everywhere)++This page is the whole Adom theme: docs, tokens, fonts, generators, and the VS Code theme pack. Two artifacts share ONE version, locked in the same commit, always:++| Artifact | Name | Version source |+|---|---|---|+| The wiki package (this page) | `adom-theme` | `package.json` at the page root |+| The VS Code extension it installs | `adom.adom-theme` | `vscode/package.json`, kept identical |++If the installed `adom.adom-theme` version differs from this package's version, the install is stale; run `adom-wiki pkg update`. That is the ONLY update channel: the extension is never published to the VS Code Marketplace or any gallery, so gallery update checks (`latestVersion`, `updateAvailable`) return null for it by design, and that null is not a defect.++History: before 2026-08-02 this page was `adom-theme-system` and the extension was `adom.adom-themes` with an independent 7.x version line. Both were renamed and version-locked at 2.0.0 while HD was still pre-release; install.sh purges the legacy extension id so theme pickers never show doubled entries.++One trap for auditors: extension files on disk carry the mtimes stored in the package tarball (publish time), not install time. Read timestamps with the date attached before concluding anything.++---++## 1. The five schemes and their standard names++Every scheme has a product label (what users see) and a slug (the frozen storage key). Labels and slugs were unified on 2026-07-25 so the HD settings picker, the VS Code theme pack, and stored preferences all agree. The naming rule: the flagship is plain **Adom Studio**, and variants earn a suffix.++| Product label | Slug | Character |+|---|---|---|+| **Adom Studio** (default) | `studio` | The editor sits on the lighter ground and the panels drop back, so the code you work in is the brightest thing on screen. Bright text ramp. |+| Adom Studio Bright | `studio-bright` | Everything on the deep ground with the brighter interface text. Adom Studio is exactly this scheme with the two grounds traded. |+| Adom Studio Dark | `studio-dark` | The original screen-tuned set with the quieter text ramp. This is the token base the other schemes override. |+| Adom Kickstand | `kickstand` | The identity palette as the design firm delivered it: near-black `#191919` ground, muted navy chrome, and the headline face used in prose. |+| Adom Slate | `slate` | A calm, cool blue-grey. Uses the code font Windows already ships, so it feels native on a stock machine. |++Each screenshot below is the real Hydrogen Desktop window (VS Code plus the AI chat on the left, the wiki on the right) captured with that scheme applied end to end, then pixel-verified against the scheme's expected editor background before it was allowed on this page.++### Adom Studio (the default)++![Adom Studio](https://wiki.adom.inc/api/pages/adom/adom-theme-system/files/docs/scheme-studio.png)++The flagship. The editor sheet is `#161b22` and the surrounding chrome drops back to `#0d1117`. Attention lands on the content, not the frame. The chat renders in Satoshi (an AI conversation is prose), the code blocks in JetBrains Mono.++### Adom Studio Bright++![Adom Studio Bright](https://wiki.adom.inc/api/pages/adom/adom-theme-system/files/docs/scheme-studio-bright.png)++Same ramp as Adom Studio with the grounds swapped: deep `#0d1117` everywhere, panels raised on `#161b22`. A build-time guard ([check-scheme-parity.sh](https://github.com/adom-inc/hydrogen-desktop/blob/main/scripts/check-scheme-parity.sh)) fails the build if these two schemes ever differ by anything other than that swap. The relationship is a contract, not a hope: tune one and the guard makes you tune both.++### Adom Studio Dark++![Adom Studio Dark](https://wiki.adom.inc/api/pages/adom/adom-theme-system/files/docs/scheme-studio-dark.png)++The original palette, tuned for long sessions: same grounds as Bright but with the quieter secondary text (`--text-2` drops from `#c9d1d9` to `#8b949e`). In CSS this is the base `:root` block; it deliberately has no override block of its own.++### Adom Kickstand++![Adom Kickstand](https://wiki.adom.inc/api/pages/adom/adom-theme-system/files/docs/scheme-kickstand.png)++The brand identity palette. Menus, dropdowns, and other overlay chrome use a muted navy `#0e1c31`, which is a derivation (a 45/55 mix of the brand navy `#00204f` into the `#191919` ground), not a new color. Full-strength navy chrome read as "that weird blue" and was demoted. Prose leads with Familjen Grotesk, the headline face. One documented correction (2026-07-26): the firm's neutral Black ground stays byte-exact, but the chrome grays we derived from it carry a few points of blue, because a pure neutral gray sitting beside the blue-tinted sibling schemes is perceived as warm brown even when the pixels measure exactly neutral.++### Adom Slate++![Adom Slate](https://wiki.adom.inc/api/pages/adom/adom-theme-system/files/docs/scheme-slate.png)++Cool blue-grey (`#17212e` ground) for people who find the black-on-black families too severe. Its code stack leads with Cascadia Code, which ships with Windows, so it never depends on our font install step.++---++## 2. Backgrounds and foregrounds: the token sheet++Backgrounds and foreground text colors are the two things that matter most, so here is the whole generated table, rendered from the live [styles.css](https://github.com/adom-inc/hydrogen-desktop/blob/main/src/routes/styles.css) rather than typed by hand:++![Token sheet for all five schemes](https://wiki.adom.inc/api/pages/adom/adom-theme-system/files/docs/tokens.png)++How to read it:++- **Grounds.** `--bg` is the deepest sheet, `--surface` carries panels and toolbars, `--elevated` is hover states, raised cards, and always the active tab, `--overlay` is menus and popovers. The law that keeps Adom Studio usable: the active tab maps to `--elevated` (`#1c2128`), never to `--surface`, because in Adom Studio `--surface` is darker than the editor and a surface-mapped tab renders as a black hole.+- **Foregrounds.** Three working tiers: `--text` (`#e6edf3` family) for emphasis only, `--text-body` (`#c9d1d9`) for running text, `--text-2` for secondary. `--text-3` exists but fails AA contrast as text; it is for disabled glyphs and borders only.+- **The constants.** Adom teal `#00b8b1` is the accent in all five schemes, with `--accent-hover #00d4cb` and a scheme-tinted `--accent-bright`. Status colors (green `#3fb950`, red `#f85149`, yellow `#d29922`, blue `#64abff`, purple `#8c6bf7`) never change between schemes, so "red means error" stays true everywhere.+- **Text on teal** uses `--on-accent` (a near-black teal like `#05221f`), never white.++The token-by-token table with every hex value, plus the measured constraints behind them (contrast bands, the halation ceiling, why there is no teal ground), is in [SKILL.md](https://wiki.adom.inc/api/pages/adom/adom-theme-system/files/SKILL.md).++---++## 3. The fonts we install for the user++Three faces, all licensed for redistribution, all shipped by us so no scheme silently falls back to Segoe UI:++| Face | Role | License |+|---|---|---|+| **Satoshi** | Prose: UI copy, chat, markdown preview | Fontshare ITF FFL |+| **Familjen Grotesk** | Headlines, and Kickstand's leading prose face | OFL |+| **JetBrains Mono** | Code: editor, terminal, code blocks | OFL |++The stacks are defined once in [settings.ts](https://github.com/adom-inc/hydrogen-desktop/blob/main/src/lib/stores/settings.ts) and follow the scheme:++| Scheme | Code stack | Prose stack |+|---|---|---|+| studio, studio-bright, studio-dark | `'JetBrains Mono', 'Cascadia Code', Consolas, ui-monospace, monospace` | `Satoshi, -apple-system, 'Segoe UI', sans-serif` |+| kickstand | same code stack | `'Familjen Grotesk', Satoshi, -apple-system, 'Segoe UI', sans-serif` |+| slate | `'Cascadia Code', Consolas, 'JetBrains Mono', ui-monospace, monospace` | Satoshi stack |++Who installs what, and where:++- **Inside the workspace** (the WSL2 distro that runs the editor): [install-brand-fonts.sh](https://github.com/adom-inc/hydrogen-desktop/blob/main/scripts/install-brand-fonts.sh) fetches the woff2 faces and registers them for the editor, verifying each face over HTTP and checking the wOF2 magic bytes before trusting it. The webfont URL must be absolute (`/_static/lib/vscode/...`); a relative URL resolves against the `/?folder=` route and 404s silently.+- **On Windows itself**: the AI chat panel is an isolated webview that does not load the workbench's webfonts, so Satoshi must also be installed as a real Windows font for chat prose to render there. Standing deployment requirement, documented in [DEPLOYMENT-CHECKLIST.md](https://github.com/adom-inc/hydrogen-desktop/blob/main/docs/DEPLOYMENT-CHECKLIST.md).+- **Fresh installs**: [hd-bootstrap.sh](https://github.com/adom-inc/hydrogen-desktop/blob/main/scripts/hd-bootstrap.sh) seeds new machines with the Adom Studio theme and the full font pairing, including the chat font keys.++Licensing decides what this page can carry. JetBrains Mono and Familjen Grotesk are OFL 1.1, so their woff2 files live right here in [fonts/](https://wiki.adom.inc/adom/adom-theme-system) with their license texts beside them. Satoshi's Fontshare EULA explicitly forbids "uploading them in a public server", so its binaries are deliberately absent: [fonts/satoshi/README.md](https://wiki.adom.inc/api/pages/adom/adom-theme-system/files/fonts/satoshi/README.md) documents the official Fontshare endpoints, and this page's install.sh fetches the faces from those servers automatically (the EULA-sanctioned channel). Read [fonts/LICENSES.md](https://wiki.adom.inc/api/pages/adom/adom-theme-system/files/fonts/LICENSES.md) for the full rules before copying font files anywhere.++Users can override both slots in Settings. Each picker shows a readout of the family the workbench actually resolved (measured inside the editor document, not assumed), and "Match theme" states which font that means right now. Picks narrate their progress ("Reloading VS Code to set font...", then "Done. JetBrains Mono loaded.") because an editor reload is slow enough to need a spinner:++![Hydrogen Desktop settings, Appearance section at defaults](https://wiki.adom.inc/api/pages/adom/adom-theme-system/files/docs/settings.png)++---++## 4. How Hydrogen Desktop implements it++### The app shell++- All tokens live in [src/routes/styles.css](https://github.com/adom-inc/hydrogen-desktop/blob/main/src/routes/styles.css): a base `:root` block (which IS Adom Studio Dark) plus one `[data-scheme='...']` override block per scheme. Components consume tokens only; a hardcoded hex in a component is a bug.+- The scheme applies as `<html data-scheme="...">`. Boot paint reads a versioned localStorage cache (`hd-color-scheme2`) written by [+layout.svelte](https://github.com/adom-inc/hydrogen-desktop/blob/main/src/routes/+layout.svelte), so there is no flash of the wrong scheme while stores load.+- Because the 2026-07-25 rename reused the slug `studio` with a different meaning, migrations are versioned: a one-shot boot migration stamps `desktop.scheme_slug_version = 2`, translates every legacy value (old `studio` becomes `studio-dark`; old `studio-bright-inverse` and `inverse` become `studio`; retired `blueprint` and `graphite` map to `slate`; `contrast` to `studio-bright`), then always reconciles the editor to match. The lesson: slugs are storage keys, and reusing one without a version bump corrupts every machine that saved the old meaning.+- Settings is a real OS window (so you can drag it aside and watch the scheme change underneath), talking to the main window over a small invoke bridge. Scheme picks preview instantly and persist only on Apply.++### VS Code specifically++The editor is the surface users stare at all day, so it gets the strictest contract:++- **Generated, not hand-maintained.** [tools/gen-vscode-themes.mjs](https://github.com/adom-inc/hydrogen-desktop/blob/main/tools/gen-vscode-themes.mjs) renders all five VS Code themes from the same tokens through [vscode-theme-template.json](https://github.com/adom-inc/hydrogen-desktop/blob/main/tools/vscode-theme-template.json) and packages them as the `adom.adom-themes` extension (currently v7.1.0). Change a token in styles.css, regenerate, and the editor follows. It is also why app-side laws (like the active tab being the elevated sheet) hold inside VS Code automatically.+- **Labels are the contract.** HD pushes `workbench.colorTheme` by label ("Adom Studio", "Adom Studio Bright", "Adom Studio Dark", "Adom Kickstand", "Adom Slate"). VS Code does not warn on an unknown theme name; it silently falls back to its default light theme. That failure turned the editor white three separate times during development, which is why two guards exist: [check-installed-themes.sh](https://github.com/adom-inc/hydrogen-desktop/blob/main/scripts/check-installed-themes.sh) verifies the pack on the machine and that the live setting resolves, and [check-vscode-theme-names.sh](https://github.com/adom-inc/hydrogen-desktop/blob/main/scripts/check-vscode-theme-names.sh) gates the bootstrap's theme name against the pack at build time.+- **Live switching.** A scheme pick writes the theme label, that scheme's font pairing, and the sizes through HD's control API in one combined write, then reloads the editor once, with the UI narrating the reload.+- **Editor fonts** follow section 3: `editor.fontFamily`, `terminal.integrated.fontFamily`, and chat code blocks get the code stack; `chat.fontFamily` and `markdown.preview.fontFamily` get the prose stack.++---++## 5. One system, three user-facing surfaces++The three surfaces a user actually looks at are Hydrogen Desktop, Adom Desktop, and the wiki. The theme system's job is to make them read as one product.++**Hydrogen Desktop** is the reference implementation: tokens, five schemes, generated VS Code pack, font installation, migrations. Everything above.++**Adom Desktop** already sits on the brand ground with teal accents and reads clearly as Adom:++![Adom Desktop v1.9.198](https://wiki.adom.inc/api/pages/adom/adom-theme-system/files/docs/ad.png)++What AD does not yet have is the token layer: its colors are its own CSS rather than the generated `--bg / --surface / --text` ramp, and it offers no scheme choice. The step-by-step checklist for bringing AD onto the system (adopt the token table, honor the five slugs, reuse the parity and naming laws, style approvals from the same tokens) is in [SKILL.md](https://wiki.adom.inc/api/pages/adom/adom-theme-system/files/SKILL.md), and the concrete artifacts to start from are on this page: [tokens.css](https://wiki.adom.inc/api/pages/adom/adom-theme-system/files/tokens.css) (drop-in CSS custom properties for all five schemes) and the generated [vscode/ pack](https://wiki.adom.inc/adom/adom-theme-system) as a worked example of projecting the tokens onto another surface. Since HD and AD share one machine and one user, the near-term win is AD honoring the same slugs so a scheme choice in HD can carry across.++**The wiki** ships the dark ground, teal identity, and Satoshi-style type today:++![wiki.adom.inc home](https://wiki.adom.inc/api/pages/adom/adom-theme-system/files/docs/wiki-home.png)++Its values are close cousins of Studio Dark rather than literal token consumers (it is a separate codebase serving the public internet). The alignment worth holding: teal `#00b8b1` as the only accent, near-black grounds, no second accent hue creeping in.++---++## 6. Where the identity card plays in++Every Adom user has an identity card (avatar, handle, accent treatment) that follows them across surfaces: profile chips in HD, author cards on the wiki, caller identity in AD's approval prompts. The theme system and the identity card divide the work cleanly:++- The **theme** owns the stage: grounds, chrome, text ramps, status colors.+- The **identity card** owns the person: their image, their name, their card styling, designed to sit on any of the five schemes without clashing.++That separation is why the same card reads correctly in a `#0d1117` Studio Bright panel and on Kickstand's navy overlay. The card assets and rules live in the [adom/adom brand hub](https://wiki.adom.inc/adom/adom) under `skills/identity-card/`; any surface rendering user identity should pull from there rather than restyling it per app.++---++## 7. Audit: the outer surfaces++The places a person meets Adom before installing anything should look like the same company as the product. Current state, screenshots taken 2026-07-26:++**adom.inc homepage: consistent.** Dark circuit-board ground, teal headline type, product shot of Hydrogen Desktop. On-system.++![adom.inc homepage](https://wiki.adom.inc/api/pages/adom/adom-theme-system/files/docs/adom-inc-home.png)++**The auth page: consistent.** [hydrogen.adom.inc/auth/login](https://hydrogen.adom.inc/auth/login) is where the wiki's Login button lands. Adom logo, near-black ground, teal primary button. Minor nit: the button teal runs slightly lighter than `#00b8b1`, worth a token pass someday, but nobody would read it as a different company.++![Adom auth page](https://wiki.adom.inc/api/pages/adom/adom-theme-system/files/docs/adom-auth.png)++**One real finding: adom.inc/login is an unbranded 404.** A person who guesses the login URL (a normal guess) gets the framework's default purple rocket instead of anything Adom:++![adom.inc/login renders a default 404](https://wiki.adom.inc/api/pages/adom/adom-theme-system/files/docs/audit-404-login.png)++Two cheap fixes, either works: redirect `/login` to [hydrogen.adom.inc/auth/login](https://hydrogen.adom.inc/auth/login), or give adom.inc a branded 404 (ground `#0d1117`, teal accent, Satoshi). Ideally both, since a branded 404 covers every future bad URL, not just this one.++---++## 8. Files++Everything an implementer needs is ON this page, because the living repo below is private and other agents cannot read it. The page copies are pinned at commit `a4c764be` (theme pack v7.2.0); browse the full tree on the [page's Files tab](https://wiki.adom.inc/adom/adom-theme-system).++- [SKILL.md](https://wiki.adom.inc/api/pages/adom/adom-theme-system/files/SKILL.md): the implementation contract (full token tables, laws, fonts, VS Code, the AD checklist)+- [tokens.css](https://wiki.adom.inc/api/pages/adom/adom-theme-system/files/tokens.css): all five schemes as CSS custom properties, extracted verbatim from the reference. The starting artifact for AD's re-brand and any web surface.+- `vscode/`: the complete generated theme pack ([package.json](https://wiki.adom.inc/api/pages/adom/adom-theme-system/files/vscode/package.json) plus five theme JSONs). Cloud containers and any code-server install can copy this directly into `~/.local/share/code-server/extensions/adom.adom-themes-7.2.0/`.+- `fonts/`: the redistributable brand fonts with their licenses. JetBrains Mono (4 faces) and Familjen Grotesk (variable), each with `OFL.txt` beside them. Satoshi has a folder too, holding only [fonts/satoshi/README.md](https://wiki.adom.inc/api/pages/adom/adom-theme-system/files/fonts/satoshi/README.md) (where to get it and why no binaries live here); [fonts/LICENSES.md](https://wiki.adom.inc/api/pages/adom/adom-theme-system/files/fonts/LICENSES.md) explains the exact license situation for all three faces and what you may copy where.+- `reference/`: byte-exact copies of the machinery, since the repo is private: the theme generator, its template, the font installer, and all three guard scripts, with a [provenance README](https://wiki.adom.inc/api/pages/adom/adom-theme-system/files/reference/README.md).+- [install.sh](https://wiki.adom.inc/api/pages/adom/adom-theme-system/files/install.sh): `adom-wiki pkg install adom-theme-system` installs the skill, and where code-server is present also installs the theme pack (making the five Adom themes selectable, without changing the active theme), the OFL fonts, and Satoshi fetched live from Fontshare's official servers with wOF2 verification. Verified end to end in a standard Adom cloud container.+- [docs/tokens.png](https://wiki.adom.inc/api/pages/adom/adom-theme-system/files/docs/tokens.png) and `docs/scheme-*.png`: the rendered token sheet and the five verified captures.++Source of truth in the Hydrogen Desktop repo (private; the copies above exist because of that):++- [src/routes/styles.css](https://github.com/adom-inc/hydrogen-desktop/blob/main/src/routes/styles.css): every token, every scheme block+- [src/lib/stores/settings.ts](https://github.com/adom-inc/hydrogen-desktop/blob/main/src/lib/stores/settings.ts): scheme-to-font mapping, VS Code sync, migrations+- [src/routes/+layout.svelte](https://github.com/adom-inc/hydrogen-desktop/blob/main/src/routes/+layout.svelte): boot paint and the versioned scheme cache+- [tools/gen-vscode-themes.mjs](https://github.com/adom-inc/hydrogen-desktop/blob/main/tools/gen-vscode-themes.mjs): the VS Code theme generator+- [scripts/install-brand-fonts.sh](https://github.com/adom-inc/hydrogen-desktop/blob/main/scripts/install-brand-fonts.sh): workspace font installation+- [scripts/check-scheme-parity.sh](https://github.com/adom-inc/hydrogen-desktop/blob/main/scripts/check-scheme-parity.sh), [scripts/check-installed-themes.sh](https://github.com/adom-inc/hydrogen-desktop/blob/main/scripts/check-installed-themes.sh), [scripts/check-vscode-theme-names.sh](https://github.com/adom-inc/hydrogen-desktop/blob/main/scripts/check-vscode-theme-names.sh): the guards++Related pages: [adom/adom brand hub](https://wiki.adom.inc/adom/adom) (brand + identity card), [Adom Desktop](https://wiki.adom.inc/adom/adom-desktop), [Adom Wiki Skill Pack](https://wiki.adom.inc/adom/adom-wiki-skillpack) (publishing conventions, including the wiki-bloat rule this page was weighed against before it earned its own slug).
SKILL.mdadded+223
@@ -0,0 +1,223 @@+---+name: adom-theme-system+description: THE Adom application theme system, the canonical spec every Adom desktop app implements (Hydrogen Desktop is the reference; Adom Desktop is the next implementer). Five colour schemes with exact tokens, slugs vs product labels, per-scheme font pairings, the VS Code theme contract, storage migration rules, and the guard scripts that keep implementations honest. Trigger words - adom theme, adom themes, color scheme, colour scheme, theme tokens, adom design tokens, implement adom themes, adom studio theme, kickstand, adom slate, bright inverse, scheme slugs, adom fonts, satoshi, jetbrains mono, familjen grotesk, vs code adom theme.+---++# The Adom Theme System++One theme system for every Adom desktop surface. Hydrogen Desktop (HD) is the REFERENCE+IMPLEMENTATION; this skill is the contract for implementing the same system elsewhere,+starting with Adom Desktop (AD). The design was measured into place on 2026-07-25 (contrast+maths, live pixel sampling, in-workbench font probes), so treat the numbers here as decisions,+not suggestions.++Source of truth files (HD repo, hydrogen-desktop - PRIVATE):+- `src/routes/styles.css` - the token set and all five scheme blocks+- `tools/gen-vscode-themes.mjs` - generates the VS Code theme pack FROM the tokens (pack v7.2.0)+- `scripts/check-scheme-parity.sh` + `scripts/check-installed-themes.sh` - the guards+- `scripts/install-brand-fonts.sh` - webfont delivery into code-server+- `src/lib/stores/settings.ts` - FONTS_FOR_SCHEME, slugs, labels, migrations++Because that repo is private, the wiki page carries usable copies (pinned @ a4c764be, pack+v7.2.0) at https://wiki.adom.inc/adom/adom-theme-system :+- `tokens.css` - all five scheme blocks as drop-in CSS custom properties+- `vscode/` - the complete generated theme pack; copy into+  `~/.local/share/code-server/extensions/adom.adom-themes-<version>/` (the page's install.sh+  does this automatically when code-server is present)+- `fonts/` - the REDISTRIBUTABLE faces only: JetBrains Mono + Familjen Grotesk (both OFL 1.1,+  license texts beside the files). Satoshi binaries are NOT there and must never be uploaded+  to any public server (Fontshare EULA); `fonts/satoshi/README.md` documents the official+  Fontshare endpoints and the page's install.sh fetches the faces from them automatically.+  Full rules: `fonts/LICENSES.md` on the page.+- `reference/` - byte-exact copies of the generator, template, font installer, and guards++## 1. The five schemes++| slug (storage key) | product label | character |+|---|---|---|+| `studio` | **Adom Studio** | THE DEFAULT (John 2026-07-27; this design briefly staged as 'Adom Studio v2', then took over the name — zero-migration rename). VS Code's Dark 2026 architecture re-grounded on the brand: body #161b22, base text #c9d1d9, every gray on the brand slate hue at 2026's exact contrast steps, product blue re-issued as Adom teal, syntax untouched. Generated by `reference/gen-adom-studio-v2.mjs` from `reference/reference-2026-dark.json`. The old template-projected Studio is abandoned. |+| `studio-bright` | Adom Studio Bright | Everything on the deep ground, brighter interface text. |+| `studio-dark` | Adom Studio Dark | The original screen-tuned dark set, quieter text. This is the TOKEN BASE. |+| `kickstand` | Adom Kickstand | The design firm's identity palette: #191919 ground, muted navy chrome, headline face in prose. |+| `slate` | Adom Slate | Calm cool blue-grey; uses the code font Windows already ships. |++**Invariant history:** the old "Adom Studio == Adom Studio Bright with `--bg`/`--surface`+traded" parity guard applied to the ABANDONED template-projected Studio and is retired with+it. The new invariant for Adom Studio (since 2026-07-27) is: it is a pure function of+`reference/reference-2026-dark.json` + the two brand anchors, regenerated by+`reference/gen-adom-studio-v2.mjs` — never hand-edited. `check-scheme-parity.sh` still+guards the APP schemes (studio vs studio-bright tokens in styles.css); it no longer+constrains the VS Code Studio theme.++## 2. The tokens, per scheme (generated from styles.css, do not hand-edit)++| token | Adom Studio | Adom Studio Bright | Adom Studio Dark | Adom Kickstand | Adom Slate |+|---|---|---|---|---|---|+| `--bg` | `#161b22` | `#0d1117` | `#0d1117` | `#191919` | `#17212e` |+| `--surface` | `#0d1117` | `#161b22` | `#161b22` | `#202127` | `#202a37` |+| `--elevated` | `#1c2128` | `#1c2128` | `#1c2128` | `#282a30` | `#28323f` |+| `--overlay` | `#21262d` | `#21262d` | `#21262d` | `#0e1c31` | `#313b48` |+| `--border` | `#30363d` | `#30363d` | `#30363d` | `#3d3f46` | `#3d4754` |+| `--text` | `#e6edf3` | `#e6edf3` | `#e6edf3` | `#f5f7f9` | `#f0f6fc` |+| `--text-body` | `#c9d1d9` | `#c9d1d9` | `#c9d1d9` | `#d7dde3` | `#d3e0ef` |+| `--text-2` | `#c9d1d9` | `#c9d1d9` | `#8b949e` | `#97a0aa` | `#93a6bd` |+| `--text-3` | `#6e7681` | `#6e7681` | `#484f58` | `#5a626b` | `#4a5a70` |+| `--accent` | `#00b8b1` | `#00b8b1` | `#00b8b1` | `#00b8b1` | `#00b8b1` |+| `--accent-hover` | `#00d4cb` | `#00d4cb` | `#00d4cb` | `#00d4cb` | `#00d4cb` |+| `--accent-bright` | `#00e6dc` | `#00e6dc` | `#00e6dc` | `#8fd3d4` | `#5fe6de` |+| `--on-accent` | `#05221f` | `#05221f` | `#05221f` | `#003c3f` | `#04211f` |+| `--blue` | `#64abff` | `#64abff` | `#64abff` | `#64abff` | `#64abff` |+| `--blue-fill` | `#0061ef` | `#0061ef` | `#0061ef` | `#0061ef` | `#0061ef` |+| `--purple` | `#8c6bf7` | `#8c6bf7` | `#8c6bf7` | `#8c6bf7` | `#8c6bf7` |+| `--green` | `#3fb950` | `#3fb950` | `#3fb950` | `#3fb950` | `#3fb950` |+| `--red` | `#f85149` | `#f85149` | `#f85149` | `#f85149` | `#f85149` |+| `--yellow` | `#d29922` | `#d29922` | `#d29922` | `#d29922` | `#d29922` |++Rationale you must not undo:+- Body text lives in the 9-13:1 contrast band. Below strains; above ~14:1 dark-mode text+  haloes (that is why Adom Studio's primary text is 13.0:1, not 15.8:1).+- The teal accent must stay >= 6:1 on every ground. That constraint is why there is no teal+  or purple GROUND: they were built and measured into failure.+- Five distinct dark grounds are impossible inside those constraints (closest achievable pair+  measured 24 apart, i.e. invisible). The family therefore differentiates on AXES: hue+  (Slate), elevation (Adom Studio), legibility (Bright), accents (Kickstand).+- `--blue-fill` (#0061ef) is 3.6:1 on dark grounds: FILLS AND ACCENTS ONLY, never text.+  Links and informational text use `--blue` (#64abff).+- `--green/--red/--yellow` are semantic (success/destructive/warning) and nothing else.+  A settings confirmation is not "success"; use the accent.+- Kickstand's chrome navy is a DERIVATION, not a new colour: mix(#00204f 45%, #191919 55%)+  = #0e1c31. Full-strength navy as a dropdown fill read as "that weird blue" and was demoted+  to accents only.+- Kickstand's derived chrome greys are COOL-SHIFTED (correction, 2026-07-26): the firm's PDF+  specifies only the #191919 Black ground, which stays byte-exact. The greys we derived from+  it (`--surface` #202127, `--elevated` #282a30, `--border` #3d3f46) carry a few points of+  blue because pure neutral grey beside the blue-tinted sibling schemes and the wiki is+  perceived as warm brown (simultaneous contrast; the shipped pixels measured exactly+  neutral, and still read "brownish"). Implementers copying Kickstand must copy these+  corrected values, not re-derive neutral ones from the ground.++## 3. Token roles (what drives what)++| token | role |+|---|---|+| `--bg` | the app's deepest ground / the editor sheet |+| `--surface` | panels, toolbars, dialogs |+| `--elevated` | hover surfaces, raised cards, and THE ACTIVE TAB (always the raised sheet; mapping tabs to --surface inverts into a black tab in Adom Studio) |+| `--overlay` | menus, dropdowns, tooltips, popovers |+| `--text` | emphasis only (headings, active items) |+| `--text-body` | running text |+| `--text-2` / `--text-3` | secondary / disabled-borders-only (text-3 fails AA as text) |++## 4. Slugs vs labels, and the migration law++Slugs are storage keys (persisted preferences, data attributes, CSS selectors). Labels are+product names, and they are EXACTLY the VS Code theme names, so one look has one name on+every surface.++History that bites: on 2026-07-25 the slug `studio` CHANGED MEANING (it was the dark base,+it is now the flagship). Any store that ever held old values must translate them ONCE under+old semantics, guarded by a version marker, because the string alone cannot say which era+wrote it. HD's pattern: a NEW localStorage key (`hd-color-scheme2`) whose legacy-key read+translates {studio->studio-dark, studio-bright-inverse->studio, inverse->studio,+blueprint->slate, contrast->studio-bright, graphite->slate} then deletes the legacy key;+plus `desktop.scheme_slug_version = 2` on the saved-preference layer. If AD stores scheme+state, implement the same translation once, and NEVER reuse a slug again without bumping the+version and extending the map.++Unknown/retired slug at load time: fall back to `studio` explicitly. Note the base tokens+ARE studio-dark's look, so "no attribute set" silently paints Dark, not the default: always+set the scheme attribute explicitly.++## 5. Fonts (part of the theme, three faces only)++Brand faces: **Familjen Grotesk** (headline), **Satoshi** (body/prose), **JetBrains Mono**+(code, SIL OFL 1.1 - ship the licence with the files). Do not add faces; variety for its own+sake is how a design system becomes a font menu.++Per-scheme pairing (FONTS_FOR_SCHEME):++| scheme | code stack | prose stack |+|---|---|---|+| studio, studio-bright, studio-dark | `'JetBrains Mono', 'Cascadia Code', Consolas, ui-monospace, monospace` | `Satoshi, -apple-system, 'Segoe UI', sans-serif` |+| kickstand | same code stack | `'Familjen Grotesk', Satoshi, -apple-system, 'Segoe UI', sans-serif` |+| slate | `'Cascadia Code', Consolas, 'JetBrains Mono', ui-monospace, monospace` | Satoshi stack |++Delivery, learned the hard way:+- Webfonts must be served from YOUR OWN origin with ABSOLUTE paths. HD's relative+  `./adom-fonts/...` URLs 404'd for weeks while a Windows-installed copy silently covered+  for them; nothing anywhere admitted it.+- Isolated webviews (the Claude chat panel) do NOT inherit your page's webfonts. Their brand+  faces resolve only from WINDOWS-INSTALLED fonts, so the installer must keep shipping+  Satoshi (and Familjen) as Windows fonts even when the main app uses webfonts.+- A fallback chain never fails, it silently falls through. Any font UI must display the+  RESOLVED family, measured in the document that renders it, not the configured first name.+- VS Code key trap: `chat.fontFamily` is the chat PROSE; `chat.editor.fontFamily` is the+  chat's CODE BLOCKS. They read backwards and were once wired backwards.++## 6. The VS Code theme contract++The editor themes are GENERATED from the tokens (HD `tools/gen-vscode-themes.mjs`), one+theme per scheme, labels identical to the picker labels. Rules:+- An unknown `workbench.colorTheme` name silently falls back to VS Code's DEFAULT LIGHT+  theme. Renames must therefore update the installed pack AND the live setting in one step,+  and a machine-side guard (`check-installed-themes.sh`) should verify the installed pack,+  because repo-vs-repo checks cannot see a stale machine.+- The generator wipes its output dir before writing so a renamed theme cannot leave a stale+  file behind.+- Current pack: adom.adom-theme (Adom Studio / Adom Studio Bright / Adom Studio Dark /+  Adom Kickstand / Adom Slate), version-locked to this package: the extension version and+  the package version are THE SAME NUMBER, bumped together in the same commit, every time.+- The extension is NEVER in any marketplace/gallery, so gallery update checks return null+  for it by design; the only update channel is `adom-wiki pkg update`. Currency check =+  installed adom.adom-theme version vs this package version.+- Legacy: before 2026-08-02 this was `adom-theme-system` + `adom.adom-themes` (7.x line);+  install.sh purges the old extension id on every install.++### Delivering the pack: install it, never copy it++**Copying the pack folder into `~/.local/share/code-server/extensions/` does not+install it.** The folder is absent from that directory's `extensions.json`, and+code-server PRUNES unregistered folders on its next launch. The pack disappears+before the user ever sees it, the picker lists zero "Adom ..." themes, and a+`workbench.colorTheme` of "Adom Studio" then hits the unknown-name rule above and+falls back to stock Light. This shipped in a golden image and rendered the whole+editor off-brand; `install.sh` now packages a `.vsix` and installs it properly.++Three traps worth knowing before you write your own installer:++1. **`code-server --install-extension` takes a `.vsix`, not a directory.** Build one+   at install time: it is a zip of `extension/<the pack>` plus `extension.vsixmanifest`+   and `[Content_Types].xml`. No `vsce`, no network, python's `zipfile` is enough.+2. **The `code-server` on `PATH` inside an editor terminal is the remote-cli shim**+   and cannot install anything. Resolve the real launcher (`/usr/lib/code-server/bin/+   code-server` and friends) and reject any path containing `remote-cli`.+3. **The CLI dies with `error not spawned with IPC`** when it inherits+   `CODE_SERVER_PARENT_PID` (and `VSCODE_IPC_HOOK_CLI`) from the editor terminal that+   is running the installer. `env -u` both before invoking it.++The litmus is registration, not files on disk: assert the `adom.adom-themes` id+appears in `extensions.json` after installing. A directory check passes for a pack+that is about to be deleted, which is exactly how this got past a build gate.+Uninstall through the CLI too, so the registration goes with the folder.++## 7. Implementing in Adom Desktop, the checklist++1. Define the tokens as CSS custom properties on `:root` (the studio-dark values) plus one+   `[data-scheme='<slug>']` block per scheme copied from the table above. Adom Studio's+   block should contain ONLY Bright's text ramp plus the bg/surface swap.+2. Route every colour through the tokens. No hardcoded hex: HD carried 4,641 hardcoded+   values before the sweep and that is why its panels never matched each other.+3. Picker UI: show the LABELS, store the SLUGS, default `studio`, apply via the data+   attribute before first paint (read the cache directly, do not wait for stores).+4. Fonts follow the scheme's pairing; if you expose font pickers, overrides beat the+   pairing, "Match theme" means follow it, and the UI must name what that currently means.+5. Copy the guards: scheme parity, brand-teal component matching (one colour has at least+   five CSS spellings; match rgb components, not strings), installed-theme verification if+   you install editor themes.+6. Do not silently restyle approval/security surfaces with scheme colours that weaken+   semantics: amber stays the heavy-action colour, red stays destructive.++## Version++Spec v1.0.0, extracted from hydrogen-desktop @ 2026-07-26 (pack v7.1.0). When HD's tokens+change, regenerate section 2 from styles.css rather than editing it by hand.
docs/scheme-slate.pngadded
⋯ 1 unchanged line ⋯
install.shadded+206
@@ -0,0 +1,206 @@+#!/usr/bin/env bash+# Install the Adom theme system onto this machine:+#   1. the skill (always) -> ~/.claude/skills/adom-theme/+#   2. the VS Code theme pack (when code-server is present) -> makes the five+#      "Adom ..." themes selectable in the editor. Does NOT change the active+#      theme; that stays the user's choice.+#   3. the brand fonts:+#      - JetBrains Mono + Familjen Grotesk ship IN this package (OFL 1.1).+#      - Satoshi is fetched from Fontshare's OFFICIAL servers at install time;+#        its EULA forbids re-hosting the files publicly but blesses delivery+#        from Indian Type Foundry's own servers. See fonts/satoshi/README.md.+set -euo pipefail+HERE="$(cd "$(dirname "$0")" && pwd)"+log() { echo "[adom-theme] $*"; }++# --- 1. the skill ------------------------------------------------------------+DEST="$HOME/.claude/skills/adom-theme"+# migrate: drop the pre-rename skill dir so only one copy exists+rm -rf "$HOME/.claude/skills/adom-theme-system"+mkdir -p "$DEST"+cp -f "$HERE/SKILL.md" "$DEST/SKILL.md"+log "skill -> $DEST"++# --- 2. the VS Code theme pack ----------------------------------------------+# The pack MUST be installed through code-server's own CLI (`--install-extension+# <vsix>`) and NOT by copying the folder into extensions/. A copied folder is+# absent from extensions/extensions.json, and code-server PRUNES unregistered+# folders on its next launch: the pack silently vanishes and the theme picker+# shows no "Adom ..." entries at all, so a settings.json asking for "Adom Studio"+# falls back to stock Light. That bug shipped in a golden image; see SKILL.md+# "Delivering the VS Code pack". Do not "simplify" this back into a cp -r.+PACK_VERSION="$(python3 -c "import json;print(json.load(open('$HERE/vscode/package.json'))['version'])" 2>/dev/null || echo unknown)"+EXT_DIR="$HOME/.local/share/code-server/extensions"+EXT_ID="adom.adom-theme"+# legacy id from before the 2026-08-02 rename; always purge so the picker never doubles up+LEGACY_EXT_ID="adom.adom-themes"++# The `code-server` on PATH inside an editor terminal is the remote-cli shim; it+# cannot install extensions. Resolve the real launcher instead.+find_code_server() {+    local c+    for c in /usr/lib/code-server/bin/code-server \+             /usr/local/lib/code-server/bin/code-server \+             "$HOME/.local/lib/code-server/bin/code-server"; do+        [ -x "$c" ] && { printf '%s\n' "$c"; return 0; }+    done+    c="$(command -v code-server 2>/dev/null || true)"+    case "$c" in+        ""|*remote-cli*) return 1 ;;+        *) printf '%s\n' "$c" ;;+    esac+}++# code-server's CLI refuses to run ("error not spawned with IPC") when it inherits+# CODE_SERVER_PARENT_PID / VSCODE_IPC_HOOK_CLI from the editor terminal that is+# running this installer. Strip them.+run_code_server() {+    env -u CODE_SERVER_PARENT_PID -u VSCODE_IPC_HOOK_CLI "$@"+}++install_theme_pack() {+    local cs vsix+    cs="$(find_code_server)" || {+        log "no code-server launcher found; skipped the editor theme pack"+        return 0+    }+    command -v python3 >/dev/null 2>&1 || {+        log "python3 not available to package the pack; skipped the editor theme pack"+        return 0+    }++    vsix="$(mktemp /tmp/adom-themes-XXXXXX.vsix)"+    python3 - "$HERE/vscode" "$vsix" <<'PYEOF'+import sys, os, json, zipfile+src, out = sys.argv[1], sys.argv[2]+m = json.load(open(os.path.join(src, "package.json")))+pub, name, ver = m["publisher"], m["name"], m["version"]+esc = lambda s: (s.replace("&", "&amp;").replace("<", "&lt;").replace(">", "&gt;"))+manifest = f'''<?xml version="1.0" encoding="utf-8"?>+<PackageManifest Version="2.0.0" xmlns="http://schemas.microsoft.com/developer/vsx-schema/2011">+  <Metadata>+    <Identity Language="en-US" Id="{name}" Version="{ver}" Publisher="{pub}" />+    <DisplayName>{esc(m.get("displayName", name))}</DisplayName>+    <Description xml:space="preserve">{esc(m.get("description", ""))}</Description>+    <Categories>Themes</Categories>+    <Properties>+      <Property Id="Microsoft.VisualStudio.Code.Engine" Value="{m.get("engines", {}).get("vscode", "^1.70.0")}" />+      <Property Id="Microsoft.VisualStudio.Code.ExtensionDependencies" Value="" />+      <Property Id="Microsoft.VisualStudio.Code.ExtensionPack" Value="" />+    </Properties>+  </Metadata>+  <Installation><InstallationTarget Id="Microsoft.VisualStudio.Code" /></Installation>+  <Dependencies />+  <Assets>+    <Asset Type="Microsoft.VisualStudio.Code.Manifest" Path="extension/package.json" Addressable="true" />+  </Assets>+</PackageManifest>+'''+content_types = '''<?xml version="1.0" encoding="utf-8"?>+<Types xmlns="http://schemas.openxmlformats.org/package/2006/content-types">+  <Default Extension="json" ContentType="application/json" />+  <Default Extension="vsixmanifest" ContentType="text/xml" />+  <Default Extension="md" ContentType="text/markdown" />+  <Default Extension="png" ContentType="image/png" />+</Types>+'''+with zipfile.ZipFile(out, "w", zipfile.ZIP_DEFLATED) as z:+    z.writestr("extension.vsixmanifest", manifest)+    z.writestr("[Content_Types].xml", content_types)+    for root, _, files in os.walk(src):+        for f in files:+            p = os.path.join(root, f)+            z.write(p, "extension/" + os.path.relpath(p, src).replace(os.sep, "/"))+PYEOF++    mkdir -p "$EXT_DIR"+    # Uninstall first so a stale entry is dropped from extensions.json too; a bare+    # `rm -rf` of the folder would leave the registration behind and dangling.+    run_code_server "$cs" --extensions-dir "$EXT_DIR" \+        --uninstall-extension "$EXT_ID" >/dev/null 2>&1 || true+    run_code_server "$cs" --extensions-dir "$EXT_DIR" \+        --uninstall-extension "$LEGACY_EXT_ID" >/dev/null 2>&1 || true+    if run_code_server "$cs" --extensions-dir "$EXT_DIR" \+        --install-extension "$vsix" --force >/dev/null 2>&1; then+        log "VS Code theme pack v$PACK_VERSION installed via code-server -> $EXT_ID"+    else+        log "WARNING: code-server refused the theme pack vsix; the editor will show no Adom themes"+        rm -f "$vsix"+        return 0+    fi+    rm -f "$vsix"++    # Registration is the whole point of this section -- assert it, loudly.+    if python3 - "$EXT_DIR/extensions.json" "$EXT_ID" <<'PYEOF'+import sys, json+try:+    entries = json.load(open(sys.argv[1]))+except Exception:+    sys.exit(1)+sys.exit(0 if any(e.get("identifier", {}).get("id") == sys.argv[2] for e in entries) else 1)+PYEOF+    then+        log "  registered in extensions.json (survives the next editor launch)"+        log "  (five 'Adom ...' themes appear in the theme picker after the editor reloads)"+    else+        log "WARNING: $EXT_ID is NOT in extensions.json -- code-server will prune the pack"+    fi+}++if [ -d "$HERE/vscode/themes" ]; then+    install_theme_pack+fi++# --- 3a. the OFL fonts (bundled) ----------------------------------------------+FONT_DEST="$HOME/.local/share/fonts/adom-theme"+if [ -d "$HERE/fonts" ]; then+    mkdir -p "$FONT_DEST"+    cp -f "$HERE"/fonts/jetbrains-mono/*.woff2 "$FONT_DEST/" 2>/dev/null || true+    cp -f "$HERE"/fonts/familjen-grotesk/*.woff2 "$FONT_DEST/" 2>/dev/null || true+    cp -f "$HERE"/fonts/jetbrains-mono/OFL.txt "$FONT_DEST/JetBrainsMono-OFL.txt" 2>/dev/null || true+    cp -f "$HERE"/fonts/familjen-grotesk/OFL.txt "$FONT_DEST/FamiljenGrotesk-OFL.txt" 2>/dev/null || true+    log "OFL fonts (JetBrains Mono, Familjen Grotesk) -> $FONT_DEST"+fi++# --- 3b. Satoshi (fetched from Fontshare's official servers) -------------------+# Skipped silently when offline or already present; the theme's prose stacks all+# carry system fallbacks, so nothing breaks without it.+SATOSHI_URL="https://api.fontshare.com/v2/fonts/download/satoshi"+if [ "${ADOM_THEME_SKIP_SATOSHI:-0}" = "1" ]; then+    # Image bakes and other PUBLIC artifacts must not carry Satoshi (Fontshare EULA+    # forbids public redistribution). Set ADOM_THEME_SKIP_SATOSHI=1 and let each+    # machine fetch it at first setup. See fonts/LICENSES.md.+    log "Satoshi fetch SKIPPED (ADOM_THEME_SKIP_SATOSHI=1) - fetch per-machine at setup"+elif [ -f "$FONT_DEST/Satoshi-Regular.woff2" ]; then+    log "Satoshi already present -> $FONT_DEST"+elif command -v curl >/dev/null 2>&1 && command -v python3 >/dev/null 2>&1; then+    TMPZ="$(mktemp /tmp/satoshi-XXXXXX.zip)"+    if curl -fsSL --compressed -A "Mozilla/5.0" -o "$TMPZ" "$SATOSHI_URL" 2>/dev/null; then+        python3 - "$TMPZ" "$FONT_DEST" <<'PYEOF'+import sys, zipfile, os+zpath, dest = sys.argv[1], sys.argv[2]+WANT = ['Satoshi-Regular.woff2','Satoshi-Medium.woff2','Satoshi-Bold.woff2','Satoshi-Variable.woff2']+got = 0+with zipfile.ZipFile(zpath) as z:+    for name in z.namelist():+        base = os.path.basename(name)+        if base in WANT and '/WEB/' in name:+            data = z.read(name)+            if data[:4] != b'wOF2':+                print(f"[adom-theme]   {base}: not wOF2, skipped"); continue+            open(os.path.join(dest, base),'wb').write(data)+            got += 1+print(f"[adom-theme] Satoshi: {got}/{len(WANT)} faces from Fontshare (official servers, per its EULA)")+sys.exit(0 if got else 1)+PYEOF+        rm -f "$TMPZ"+    else+        rm -f "$TMPZ"+        log "Satoshi fetch skipped (offline?) - get it later: see fonts/satoshi/README.md on the page"+    fi+else+    log "Satoshi fetch skipped (needs curl+python3) - see fonts/satoshi/README.md on the page"+fi+command -v fc-cache >/dev/null 2>&1 && fc-cache -f "$FONT_DEST" >/dev/null 2>&1 || true++log "done"
package.jsonadded+94
@@ -0,0 +1,94 @@+{+  "slug": "adom-theme",+  "name": "adom-theme",+  "version": "2.0.0",+  "type": "skill",+  "description": "THE Adom application theme: five colour schemes with exact tokens, slugs vs labels, font pairings, the VS Code theme pack (adom.adom-theme, version-locked to this package), migration rules, and the guards. Hydrogen Desktop is the reference implementation.",+  "discovery_triggers": [+    "adom theme",+    "adom themes",+    "theme system",+    "color scheme",+    "colour scheme",+    "theme tokens",+    "adom design tokens",+    "implement adom themes",+    "adom studio theme",+    "kickstand theme",+    "adom slate",+    "bright inverse",+    "scheme slugs",+    "adom fonts",+    "satoshi",+    "jetbrains mono",+    "familjen grotesk",+    "vs code adom theme",+    "dark theme adom"+  ],+  "discovery_pitch": "Implementing or matching Adom's look in any app: load this first. Exact tokens for all five schemes, the slug/label contract, font pairings and delivery traps, and the guard scripts.",+  "files": [+    "SKILL.md",+    "README.md",+    "package.json",+    "install.sh",+    "uninstall.sh",+    "tokens.css",+    "vscode/package.json",+    "vscode/themes/adom-studio-color-theme.json",+    "vscode/themes/adom-studio-bright-color-theme.json",+    "vscode/themes/adom-studio-dark-color-theme.json",+    "vscode/themes/adom-kickstand-color-theme.json",+    "vscode/themes/adom-slate-color-theme.json",+    "fonts/LICENSES.md",+    "fonts/satoshi/README.md",+    "fonts/jetbrains-mono/JetBrainsMono-Regular.woff2",+    "fonts/jetbrains-mono/JetBrainsMono-Italic.woff2",+    "fonts/jetbrains-mono/JetBrainsMono-Bold.woff2",+    "fonts/jetbrains-mono/JetBrainsMono-BoldItalic.woff2",+    "fonts/jetbrains-mono/OFL.txt",+    "fonts/familjen-grotesk/FamiljenGrotesk-Variable.woff2",+    "fonts/familjen-grotesk/OFL.txt",+    "reference/README.md",+    "reference/gen-vscode-themes.mjs",+    "reference/vscode-theme-template.json",+    "reference/install-brand-fonts.sh",+    "reference/check-scheme-parity.sh",+    "reference/check-installed-themes.sh",+    "reference/check-vscode-theme-names.sh",+    "reference/gen-adom-studio-v2.mjs",+    "reference/reference-2026-dark.json"+  ],+  "scripts": {+    "install": "./install.sh",+    "uninstall": "./uninstall.sh"+  },+  "dependencies": {},+  "title": "Adom Theme",+  "sample_prompts": [+    {+      "label": "Implement the themes",+      "prompt": "Implement the Adom theme system in this app: same five schemes, exact tokens, and font pairings."+    },+    {+      "label": "What are the tokens?",+      "prompt": "Show me the Adom Studio token values and what each token drives."+    },+    {+      "label": "Add a scheme picker",+      "prompt": "Add a colour scheme picker that follows the Adom theme system's slug and label rules."+    }+  ],+  "hero": {+    "type": "image",+    "path": "docs/hero.png"+  },+  "tags": [+    "themes",+    "design-system",+    "brand",+    "tokens",+    "fonts",+    "hydrogen-desktop",+    "adom-desktop"+  ]+}\ No newline at end of file
screenshots/hero.pngadded
⋯ 1 unchanged line ⋯
tokens.cssadded+119
@@ -0,0 +1,119 @@+/*+ * Adom theme tokens - all five schemes, extracted VERBATIM from the reference+ * implementation (hydrogen-desktop src/routes/styles.css @ a4c764be, pack v7.2.0).+ * The base :root block IS Adom Studio Dark; each [data-scheme] block overrides it.+ * Apply as <html data-scheme="studio|studio-bright|studio-dark|kickstand|slate">+ * (studio-dark needs no block - it is the base).+ * Comments were stripped mechanically; the values are byte-exact.+ * Living source + full rationale: https://wiki.adom.inc/adom/adom-theme-system+ */+:root {+    +    --font-body: 'DM Sans Variable', -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, Oxygen,+        Ubuntu, Cantarell, 'Open Sans', 'Helvetica Neue', sans-serif;+    --font-mono: 'DM Mono', monospace;+    +    --brand-heading: 'Familjen Grotesk', var(--font-body);+    --brand-body: 'Satoshi', var(--font-body);+    --brand-teal: var(--accent);+    --brand-teal-dark: #003c3f;+    --brand-blue: #0061ef;+    --brand-navy: #00204f;+    --brand-black: #191919;++    +    --bg: #0d1117;            +    --surface: #161b22;       +    --elevated: #1c2128;      +    --overlay: #21262d;       +    --border: #30363d;        ++    --text: #e6edf3;          +    --text-body: #c9d1d9;     +    --text-2: #8b949e;        +    --text-3: #484f58;        ++    --accent: #00b8b1;        +    --accent-hover: #00d4cb;+    --accent-bright: #00e6dc;+    --on-accent: #05221f;     ++    --blue: #64abff;          +    --blue-fill: #0061ef;     +    --purple: #8c6bf7;+    --green: #3fb950;         +    --red: #f85149;           +    --yellow: #d29922;        ++    +    --color-text: rgba(0, 0, 0, 0.7);++    overscroll-behavior: none;+}++:root[data-scheme='studio'] {+    +    --text-2: #c9d1d9;+    --text-3: #6e7681;++    +    --bg: #161b22;            +    --surface: #0d1117;       +}++:root[data-scheme='studio-bright'] {+    --text-2: #c9d1d9;        +    --text-3: #6e7681;        +}++:root[data-scheme='kickstand'] {+    +    --bg: #191919;+    --surface: #202127;+    --elevated: #282a30;+    +    --overlay: #0e1c31;+    --border: #3d3f46;++    --text: #f5f7f9;+    --text-body: #d7dde3;+    --text-2: #97a0aa;+    --text-3: #5a626b;++    --accent: #00b8b1;+    --accent-hover: #00d4cb;+    --accent-bright: #8fd3d4;+    --on-accent: #003c3f;++    --blue: #64abff;+    --blue-fill: #0061ef;+    --purple: #8c6bf7;+    --green: #3fb950;+    --red: #f85149;+    --yellow: #d29922;+}++:root[data-scheme='slate'] {+    --bg: #17212e;+    --surface: #202a37;+    --elevated: #28323f;+    --overlay: #313b48;+    --border: #3d4754;++    --text: #f0f6fc;+    --text-body: #d3e0ef;+    --text-2: #93a6bd;+    --text-3: #4a5a70;++    --accent: #00b8b1;+    --accent-hover: #00d4cb;+    --accent-bright: #5fe6de;+    --on-accent: #04211f;++    --blue: #64abff;+    --blue-fill: #0061ef;+    --purple: #8c6bf7;+    --green: #3fb950;+    --red: #f85149;+    --yellow: #d29922;+}
uninstall.shadded+24
@@ -0,0 +1,24 @@+#!/usr/bin/env bash+rm -rf "$HOME/.claude/skills/adom-theme" "$HOME/.claude/skills/adom-theme-system"++# Remove the theme pack through code-server so extensions.json loses the+# registration too; a bare rm would leave a dangling entry behind.+EXT_DIR="$HOME/.local/share/code-server/extensions"+for cs in /usr/lib/code-server/bin/code-server \+          /usr/local/lib/code-server/bin/code-server \+          "$HOME/.local/lib/code-server/bin/code-server"; do+    if [ -x "$cs" ]; then+        env -u CODE_SERVER_PARENT_PID -u VSCODE_IPC_HOOK_CLI \+            "$cs" --extensions-dir "$EXT_DIR" \+            --uninstall-extension adom.adom-theme >/dev/null 2>&1 || true+            env -u CODE_SERVER_PARENT_PID -u VSCODE_IPC_HOOK_CLI \+            "$cs" --extensions-dir "$EXT_DIR" \+            --uninstall-extension adom.adom-themes >/dev/null 2>&1 || true+        break+    fi+done+rm -rf "$EXT_DIR"/adom.adom-theme-* "$EXT_DIR"/adom.adom-themes-* 2>/dev/null || true++rm -rf "$HOME/.local/share/fonts/adom-theme" "$HOME/.local/share/fonts/adom-theme-system" 2>/dev/null || true+command -v fc-cache >/dev/null 2>&1 && fc-cache -f >/dev/null 2>&1 || true+echo "removed: skill, VS Code theme pack, OFL fonts"