← Commit history

Publish 2.2.3

John Lauer ·c3c2dfdb5e · ·parent 44f207b
4 files changed +31−47
README.md+25−43
@@ -1,6 +1,6 @@-# Adom Theme System+# Adom Theme -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`).+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/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. @@ -61,53 +61,35 @@ How we got here: the chat body is painted by Claude Code's webview with `--vscod  Two operational notes for future auditors: VS Code caches computed theme data per extension VERSION, so editing theme files under an unchanged version renders nothing (bump to bust); and right after a theme switch, webviews restyle asynchronously, so tabs can wear different themes for a beat. Both are normal. -### The five schemes, side by side (real screenshots)--The comparison that actually matters when you pick a theme: the same live Claude chat, same content, captured five times with only `workbench.colorTheme` changed (applied live through adom-vscode, no reload). The background is what dominates your eye all day; the text color is what you read non-stop. Exact values under each column.--![The five schemes side by side](https://wiki.adom.inc/api/pages/adom/adom-theme/files/docs/theme-compare-v3.png)--### Validation: does the active tab flow into the chat body?--The design intent (John, 2026-08-02): the active tab should share the chat body's background so the active conversation reads front-and-center, the tab flowing into its content. Verified against the LIVE workbench, all five themes plus stock Dark 2026 as the control, by reading the computed colors from the DOM, not by eyeballing screenshots:--- **Every Adom theme passes its half of the contract.** The active tab computes to exactly `editor.background` in all five (that equality is enforced by the generator and asserted in its sanity log).-- **The seam is Claude Code's chat CSS, not the theme and not VS Code.** The chat's `messagesContainer` paints `--app-primary-background`, which Claude maps to `--vscode-sideBar-background`. Their own `.fullEditor` variant maps to `--vscode-editor-background` (which would flow perfectly), but that class is not applied in this hosting mode. The control column proves it: stock Dark 2026 shows the identical seam (`#121314` tab vs `#191a1b` body).-- If the editor ever looks *randomly* inconsistent right after a theme switch, that is webview theme propagation lag: each chat webview restyles asynchronously, so for a moment different tabs can wear different themes. It settles within a second.--![Active tab vs chat body, measured](https://wiki.adom.inc/api/pages/adom/adom-theme/files/docs/seam-validation.png)--Fix path: get the chat container onto `editor.background` when hosted as an editor tab (the `.fullEditor` styling Claude already ships), tracked in hydrogen-desktop. Flattening `sideBar.background` into `editor.background` in the themes would "fix" it at the cost of the whole chrome-vs-content architecture, so the themes stay correct instead.--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.+Each screenshot below is the real Hydrogen Desktop window, captured 2026-07-27 when the schemes shipped app-wide. The editor-side details have evolved since (the Dark/Brighter rebrand and the 2.2.0 tab contract), so treat these as the whole-app look and the side-by-side section above as the current editor truth. Each is the real 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)+![Adom Studio](https://wiki.adom.inc/api/pages/adom/adom-theme/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 Dark (Brighter Text) -![Adom Studio Dark (Brighter Text)](https://wiki.adom.inc/api/pages/adom/adom-theme-system/files/docs/scheme-studio-bright.png)+![Adom Studio Dark (Brighter Text)](https://wiki.adom.inc/api/pages/adom/adom-theme/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)+![Adom Studio Dark](https://wiki.adom.inc/api/pages/adom/adom-theme/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)+![Adom Kickstand](https://wiki.adom.inc/api/pages/adom/adom-theme/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)+![Adom Slate](https://wiki.adom.inc/api/pages/adom/adom-theme/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. @@ -117,7 +99,7 @@ Cool blue-grey (`#17212e` ground) for people who find the black-on-black familie  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)+![Token sheet for all five schemes](https://wiki.adom.inc/api/pages/adom/adom-theme/files/docs/tokens.png)  How to read it: @@ -126,7 +108,7 @@ How to read it: - **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).+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/files/SKILL.md).  --- @@ -154,11 +136,11 @@ Who installs what, and where: - **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.+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/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/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)+![Hydrogen Desktop settings, Appearance section at defaults](https://wiki.adom.inc/api/pages/adom/adom-theme/files/docs/settings.png)  --- @@ -190,13 +172,13 @@ The three surfaces a user actually looks at are Hydrogen Desktop, Adom Desktop,  **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)+![Adom Desktop v1.9.198](https://wiki.adom.inc/api/pages/adom/adom-theme/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.+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/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/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)+![wiki.adom.inc home](https://wiki.adom.inc/api/pages/adom/adom-theme/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. @@ -219,15 +201,15 @@ The places a person meets Adom before installing anything should look like the s  **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)+![adom.inc homepage](https://wiki.adom.inc/api/pages/adom/adom-theme/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)+![Adom auth page](https://wiki.adom.inc/api/pages/adom/adom-theme/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)+![adom.inc/login renders a default 404](https://wiki.adom.inc/api/pages/adom/adom-theme/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. @@ -237,13 +219,13 @@ Two cheap fixes, either works: redirect `/login` to [hydrogen.adom.inc/auth/logi  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.+- [SKILL.md](https://wiki.adom.inc/api/pages/adom/adom-theme/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/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/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/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/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/files/reference/README.md).+- [install.sh](https://wiki.adom.inc/api/pages/adom/adom-theme/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/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): 
package.json+1−1
@@ -1,7 +1,7 @@ {   "slug": "adom-theme",   "name": "adom-theme",-  "version": "2.2.2",+  "version": "2.2.3",   "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": [
page.json+4−2
@@ -52,7 +52,7 @@     "path": "screenshots/hero-v5.png"   },   "name": "adom-theme",-  "version": "2.2.2",+  "version": "2.2.3",   "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_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": [@@ -83,7 +83,9 @@     "reference/install-brand-fonts.sh",     "reference/check-scheme-parity.sh",     "reference/check-installed-themes.sh",-    "reference/check-vscode-theme-names.sh"+    "reference/check-vscode-theme-names.sh",+    "reference/gen-adom-studio-v2.mjs",+    "reference/reference-2026-dark.json"   ],   "scripts": {     "install": "./install.sh",
vscode/package.json+1−1
@@ -2,7 +2,7 @@   "name": "adom-theme",   "displayName": "Adom Theme",   "publisher": "adom",-  "version": "2.2.2",+  "version": "2.2.3",   "description": "The Adom brand theme family for VS Code. Generated from the Adom theme tokens and version-locked to the adom-theme wiki package, so the editor and the app can never disagree about a colour.",   "engines": {     "vscode": "^1.70.0"