Building Sigil Nights
Late sessions building Sigil were Kevin's answer to agent-default UI: not prettier Tailwind, but a token-first design language agents can edit without wrecking the grid.
Sigil UI is Kevin's opinionated framework for agent-first design. The Greatness Trap records his distinction: Sigil is not a bid for greatness identity. It is an expression of a strong opinion about how design should work when LLMs author the components. Source: The Greatness Trap
The technical spine is Sigil Token Architecture: roughly 519 tokens across 33 categories compile from a single DESIGN.md into CSS variables, Tailwind v4 @theme, and W3C design-token JSON. Source: Sigil Token Architecture Reticle Design System supplies the structural-visibility aesthetic (grid lines, margin rails, cross marks) that agents port into products like Agent Machines. Source: Reticle Design System
Kevin's brief rejects "pick some Tailwind classes and vibe." Source: raw/obsidian/What websites I like..md via Reticle Design System Sigil nights are where that brief becomes CLI commands (sigil design sync, doctor passes) and twelve agent skills for tokens, presets, and adapters.
The career angle: Career Profile lists "building Sigil" as a conversation starter that separates Kevin from generic SWE profiles. Source: Career Profile
Timeline
- 2026-04-06 | Reticle/Sigil taste direction captured from Obsidian frontend brief. Source: Reticle Design System
- 2026-05-17 | Sigil cited in greatness-trap philosophy as opinionated-building example. Source: The Greatness Trap
- 2026-05-31 | Sigil token architecture page documents 519/33 scale. Source: Sigil Token Architecture
- 2026-05-31 | Story page compiled. Source: compiled from wiki graph