Troupe themes¶
Troupe ships four themes, each in light and dark, from one token contract. A theme changes what the interface feels like. It never changes what anything means.
themes/
afterglow.tokens.json ../afterglow.dc.html ← default, and the design
footlight.tokens.json Footlight kit.dc.html
limelight.tokens.json Limelight kit.dc.html
signal.tokens.json Signal kit.dc.html
Open any of the three kits in a browser. Each one shows the same mark, status glyphs, cast, live fragments and palette in its own theme, with a light/dark toggle in the header. afterglow.dc.html is not a kit but the comp the app is drawn to — the launcher, the session list, a new session and a session — and it is dark only.
These four files are the only copy in the repository, and three generators read them: pnpm tokens (the GUI's tokens.css and mark.ts), mix troupe.theme at the root (the plane's front page, in Signal) and mix troupe.palette in clients/tui (the TUI's colours in every theme, and its mask). Each has a check CI runs, so a token changed here without regenerating fails the build of every client that wears it.
The contract¶
Every theme exposes exactly the same token names. Components read --waiting-solid, never a hex. Swapping a theme swaps values; it never adds, removes or renames a token.
A theme that needs a new token name is not a theme. It is a redesign.
This is what makes four themes cost almost nothing to maintain: there is one component library, one set of rules, one accessibility audit per theme, and no conditional styling anywhere in the product.
What is shared and not themeable:
- Type. Figtree, DM Mono and VT323, same scale, same measure, in all four.
- Space, radii, borders, motion, breakpoints, z-index. Identical.
pnpm tokensemits all but z-index from the default theme's file, and refuses a theme file whose copy of any of them differs. - The mask. Same path, same stroke weights, same seam, same rule that light falls from the right.
- Structure. Hairlines and alignment, not cards. Every radius is zero. One flat, hard shadow under a tile or a primary button; no gradients.
- Meaning. The reserved colour always means a person must decide. Status is always glyph, then word, then colour.
What a theme actually controls: the temperature of the ground, which hue is reserved for attention, the hues of the other states, the colour of the hard shadow, and the accent — color.accent, the current nav item's edge, which Afterglow spends its reserved pink on and the other three give their link blue.
The four themes¶
Afterglow — the default¶
Void #0B0B12 and pit #12121C under cream #F4ECDB. Reserved colour pink #FF0080 dark / #C4005F light, and it is the brand as well: the mask's lit half, links and the current nav item take it through --accent and --link. Cyan #00C6C9 is the machine working and the one filled button; amber #FFBC56 is this machine; violet is asleep and private; clay is denied, a hotter red is error.
The comp is dark only. The light mode is derived from it: the ground inverts to cream (#E9E0CB stage, #F4ECDB canvas, #FAF5EA panel) and every accent darkens until it clears the same floor as the other themes. Two values are not the comp's: text.muted is #7B7B94 rather than the comp's grey-deep #6A6A82, which sits at 3.7:1 on the void; and bg.sunken, under code, diffs and tool output, is #06060B, a step below the void rather than the void itself, so a frame shows by more than its hairline (troupe #659). queued is the comp's amber — a message held while the troupe works — and a session doing nothing is idle, which is not a state so much as the absence of one and has no colour token: the chrome's label grey on a strong rule, which is how the comp draws STOPPED.
Choose it because it is the design. The other three are what came before it, kept on the same contract.
Cost: pink is the reserved colour and the brand at once, so a pink nav edge and a pink NEEDS YOU pill share a hue and are told apart by shape — the pill is solid, the edge is a line. Black-weight titles and upper-case mono labels are loud; the design pays for that with a near-black ground and a lot of space.
Footlight¶
Ink navy, drafting blue-grey, one stage amber. Reserved colour #FFB43D dark / #B36A00 light.
Cool, quiet, unfussy — a piece of company infrastructure with a single warm light in it. It extends the technical-theatre drawing style the platform's own documentation already uses, so Troupe looks like it belongs next to everything else IT Minds has drawn.
Choose it when the platform should disappear behind the work. It is the safest of the four and the one nobody will object to.
Cost: navy plus amber is the default palette of every operations product. It is the least distinctive option.
Limelight¶
Warm ink — smoked oak, aged paper, the dark of an auditorium rather than the dark of a terminal. Reserved colour #CBEA5C dark / #6E7F12 light: limelight, the pale greenish-white of burning quicklime and the first stage light there ever was. Running goes slate-teal so it never competes; denied moves to a warm brick that sits naturally on this ground.
Choose it for long reading days, and when you want the theme that could only belong to this product — the metaphor, the warmth and the one reserved light all agree.
Cost: yellow-green is the hardest hue to keep legible. It takes dark text in every filled state, and the gap between it and the sage allowed colour has to be policed. Warm grounds also make pasted screenshots look cold by comparison.
Signal¶
True neutral graphite with no blue cast, and a printer's duotone on top: cyan is the machine working, magenta is you being asked. Reserved colour #FF5CB8 dark / #C11A79 light. The default before Afterglow.
The cleanest split of the four, and the one Afterglow's own duotone descends from. Neutral grounds never fight an embedded screenshot, diff or chart.
Choose it when the platform should read modern and technical before it reads theatrical.
Cost: magenta is close enough to red that denied and error have to be pushed towards clay and orange to stay distinct. It carries more consumer energy than an internal consultancy tool may want, and it is the option most likely to date.
Contrast¶
Every theme is audited to the same floor, in both modes:
| Afterglow | Footlight | Limelight | Signal | |
|---|---|---|---|---|
text.primary on canvas |
16.6 / 16.6 | 15.8 / 15.7 | 16.0 / 15.5 | 16.2 / 16.5 |
text.secondary |
7.9 / 7.2 | 9.5 / 7.7 | 9.8 / 8.7 | 9.0 / 9.0 |
text.muted (floor) |
4.7 / 5.2 | 5.5 / 4.8 | 5.2 / 5.6 | 4.9 / 5.6 |
| worst status fg on its own bg, over canvas or panel | 4.7 / 4.5 | 7.0 / 5.4 | 6.3 / 5.7 | 6.3 / 6.0 |
| focus ring, worst surface | 7.9 / 3.9 | 8.0 / 6.8 | 13.3 / 6.2 | 8.9 / 5.8 |
Dark value first, light second, each rounded down, from the token files as they are (October 2026). Body text never below 4.5:1; the focus ring never below 3:1. A theme that cannot hit these numbers does not ship — the fix is the theme's values, never an exception in a component. Afterglow's worst status is waiting in light, at the floor exactly: the reserved pink on its own tint.
Swapping themes¶
During onboarding¶
The theme is chosen once, by the person, on first sign-in — after the identity handshake, before the first session — or, with no plane, as the first step of the first run (Decision 705). It is one screen, four cards, each a live preview of the same session fragment rendered in that theme, with a light/dark toggle on the screen itself.
The screen follows four rules:
- Afterglow is preselected. Someone who presses Continue without reading gets the default and loses nothing.
- The previews are real. Each card shows the session row that needs you, an approval, and the agent list — the three things the person will actually look at all day. Not swatches: swatches tell you nothing about whether you can work in a theme.
- Light and dark are a separate control, not eight cards. Theme and mode are different questions. Mixing them into one grid turns a ten-second choice into a puzzle. The mode control defaults to Follow my system.
- The copy says it is changeable. "You can change this any time in Appearance." One sentence removes all the weight from the decision, which is the point — nobody should spend two minutes here.
Skipping is allowed, and skipping means Afterglow with system mode.
Afterwards¶
Settings → Appearance, same four cards, same live previews, plus the mode control. Changing a theme applies immediately, with no reload and no confirmation — it is a data-theme attribute on the document root and nothing more. The mode is a second attribute, data-mode, which is absent when the answer is "follow my system": no attribute is what lets the media query answer instead.
Where the choice lives¶
- Per person, not per team or per session. A theme is a reading preference, like text size. Two people in the same session see it in their own theme, because the session's content is identical either way and nothing about the theme carries meaning.
- Kept by the person's own daemon, as the
ui.themeandui.modekeys of theirconfig.yaml, so it follows them from the desktop app to the terminal client on that computer (apps/desktop/src/shared.ts). The browser also keeps a copy, so the first paint is already correct and nobody sees a flash of the wrong ground. Nothing is kept on a plane: a person's theme does not follow them to another computer. - Mode may be
follow system,lightordark, independent of the theme. - There is no organisation default: Afterglow is preselected for everyone. Were one added, an administrator could set it and not force it. Removing a person's ability to read comfortably is not a configuration option.
What must not happen¶
- Never swap theme mid-session as a signal for anything. The ground changing under a person who is reading is alarming, and it will be read as an error.
- Never animate the swap beyond the colour transition the browser does for free, and honour
prefers-reduced-motion. - Never let a theme change what a colour means.
waitingis pink in Afterglow, amber in Footlight, lime in Limelight and magenta in Signal — and in all four it means exactly one thing. - Never ship a theme-specific component. If a component needs a special case for one theme, that theme's token values are wrong.
Adding a theme¶
- Copy any
*.tokens.json, change only the values undercolorandshadow.pnpm tokensrefuses a file that changed anything else, and one that added, lost or renamed a colour token. - Nominate the reserved colour and check nothing else in the theme uses it — or, as Afterglow does, lend it to
accentand to nothing else. (Limelight's focus ring is its lime too, whichpnpm tokensworks around; a new theme should not need that.) - Run the contrast table above. Every number must clear the floor in both modes.
- Check the non-reserved statuses are distinguishable from each other in greyscale — the glyphs carry this, but a theme that makes two states the same tone makes the glyph do all the work alone.
- Render a kit with the new palette block. If anything in the kit needs editing beyond the palette, stop: the theme is asking for a redesign.
Decisions¶
-
Four themes, one contract. The alternative — one theme with a colour picker — produces palettes nobody audited and screenshots that cannot be compared. Curated, audited themes give people a real choice without giving them a way to make the product illegible.
-
The reserved-colour rule survives every theme. It is the single most important thing the design does: one colour, product-wide, meaning stopped, a person must decide. Each theme nominates a different hue for it, and no component reaches for it for anything else. Afterglow is the one theme that lends the hue to the brand as well, and it does so through
accentandlink, so the rule holds where it is enforced — in what a component reads. -
Theme and mode are separate questions. Four themes × two modes is eight combinations, but presenting eight cards would make people compare things that are not alternatives. Two controls, ten seconds.
-
Afterglow is the default, because it is the design. Before it, Signal was: the screen people spend the day on is full of other people's colour — pasted screenshots, diffs, charts, terminal output — and a true-neutral graphite was the one of the three that never argued with any of it, with a duotone on top that said the two things a person scans for. Afterglow keeps that duotone — cyan is still the machine, pink is still you — on a near-black ground, and adds the type, the spacing and the square corners that every theme now shares (repository Decision 702). The three earlier palettes stay on the contract, selectable on the redrawn appearance screen (Decision 704); whether they stay at all is a product question this document does not settle.
-
Themes are per person and cannot be enforced. Not even a default is an administrator's today. Colour preference is an accessibility and comfort matter, and taking it away buys nothing.
-
Onboarding preselects rather than asks. The screen is skippable and pre-answered. A first-run screen that blocks on an aesthetic choice teaches people that this product will waste their time.