Moves components.css into Tailwind utilities inside the components, from 2,718 lines down to 390. There is one commit per stage: page skeleton, rail, controls, chips and type roles, the row, then the view styles.
look.ts builds each control, chip, toggle and row from its whole state, so no two utilities on an element fight over a property. Contextual overrides like .r-morepanel .control and .deck-group .deck-group .deck-head become props and React context.
The theme in style.css holds only tokens and named geometry. Hover is redefined to apply on every pointer, as the old :hover rules did.
Still in CSS: tokens, base rules, .readout and .dim, the lamp glow and power-up, the hero's backdrop scrim, the title placeholder and the reduced-motion override. Those are effects, not layout.
check-tokens treats data-[…]: as a variant, and _ as whitespace in relative colours.
One quirk is kept on purpose: the second chain bus still renders on a phone, as it did before.
Compared every element's computed style against production on 22 pages and interactions at 1280 and 390 wide: all identical. The one exception is a detail page's resolved auto margin, which flickers on both builds depending on when it is read.
Spot-checked hover, keyboard-armed delete, expanded, disclosure and subtitle-chip states against production.
<!-- claude-projects-attribution: {"github_login":"naps62"} -->
_Requested by **naps** · [project thread](https://claude.ai/code/project/chan_01UYLqY2bRGpRgeywoBE6jwE?thread=cmsg_01UYLqY2bRGpRgeywoBE6jwE95cFpdceZzfydH266rwm1d)_
## Summary
Moves `components.css` into Tailwind utilities inside the components, from 2,718 lines down to 390. There is one commit per stage: page skeleton, rail, controls, chips and type roles, the row, then the view styles.
- `look.ts` builds each control, chip, toggle and row from its whole state, so no two utilities on an element fight over a property. Contextual overrides like `.r-morepanel .control` and `.deck-group .deck-group .deck-head` become props and React context.
- The theme in `style.css` holds only tokens and named geometry. Hover is redefined to apply on every pointer, as the old `:hover` rules did.
- Still in CSS: tokens, base rules, `.readout` and `.dim`, the lamp glow and power-up, the hero's backdrop scrim, the title placeholder and the reduced-motion override. Those are effects, not layout.
- `check-tokens` treats `data-[…]:` as a variant, and `_` as whitespace in relative colours.
One quirk is kept on purpose: the second chain bus still renders on a phone, as it did before.
## Issue
Closes #280
## Test plan
- `just ci` passes.
- Compared every element's computed style against production on 22 pages and interactions at 1280 and 390 wide: all identical. The one exception is a detail page's resolved auto margin, which flickers on both builds depending on when it is read.
- Spot-checked hover, keyboard-armed delete, expanded, disclosure and subtitle-chip states against production.
- Keyboard flows (`/`, arrows, Esc layers, back/forward, tab bar search) unchanged.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Decks, page bars, sections, heads, status slots and group notes move
out of components.css into Deck, PageBar, Section, Rows and friends.
The theme gains the geometry tokens and the container widths.
Refs #280
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Phone search mode keys on a named group, and hover is redefined to
apply on every pointer, as the board's own :hover rules always did.
Refs #280
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
look.ts builds each control's class list from its whole state, so no
two utilities fight over a property. The contextual overrides from rows,
trays, page heads and the removal panel become props.
Refs #280
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
A chip's look is read off the data attributes it already carries, in
the order the board always resolved them. Lamps stay in CSS: the glow
and the power-up are effects, not layout.
Refs #280
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Rows, slots, trays, notes, skeletons, scores and the release cells.
The linked-row pointer rules key on the row knowing it is a link, not
on :has().
Refs #280
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
The hero's backdrop scrim and the title placeholder stay in CSS: they
are pseudo-element effects, not layout.
Refs #280
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
naps62-yolo
changed title from Move the page skeleton into Tailwind utilities to Move the web stylesheet into Tailwind utilities2026-11-11 19:19:54 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Requested by naps · project thread
Summary
Moves
components.cssinto Tailwind utilities inside the components, from 2,718 lines down to 390. There is one commit per stage: page skeleton, rail, controls, chips and type roles, the row, then the view styles.look.tsbuilds each control, chip, toggle and row from its whole state, so no two utilities on an element fight over a property. Contextual overrides like.r-morepanel .controland.deck-group .deck-group .deck-headbecome props and React context.style.cssholds only tokens and named geometry. Hover is redefined to apply on every pointer, as the old:hoverrules did..readoutand.dim, the lamp glow and power-up, the hero's backdrop scrim, the title placeholder and the reduced-motion override. Those are effects, not layout.check-tokenstreatsdata-[…]:as a variant, and_as whitespace in relative colours.One quirk is kept on purpose: the second chain bus still renders on a phone, as it did before.
Issue
Closes #280
Test plan
just cipasses./, arrows, Esc layers, back/forward, tab bar search) unchanged.🤖 Generated with Claude Code
Move the page skeleton into Tailwind utilitiesto Move the web stylesheet into Tailwind utilities