1 min read
Sigil Building
Sigil/Reticle is Kevin's design-system proof: token-first, agent-editable visual identity with enough grammar that agents can build specific interfaces instead of generic ones.
Open this page when public identity, design-system work, Reticle/Sigil, or agent-authored UI taste matters.
What Sigil Proves
| Claim | Proof surface |
|---|---|
| Taste can be encoded | Tokens, presets, components, and visual grammar replace one-off "make it nicer" prompts. |
| Agents need constraints | Agent-authored UI improves when the design system gives names, primitives, states, and examples. |
| Design is infrastructure | Sigil/Reticle should travel through projects, skills, docs, and proof loops. |
| Visual identity can be public proof | Sigil UI and PortfolioMon make taste visible alongside agent-infra work. |
Reticle Relationship
Reticle is the current structural grammar: rails, frames, hatching, bands, compact labels, dense operational panels, and the calmer dashboard variant used in Agent Machines. Use Reticle Design System for implementation detail and Design System Map for category routing.
Agent Use
- For UI work, load Design Taste and relevant design skills before building.
- For public/profile writing, use Sigil/Reticle as proof of taste and agent-editable design, not just "component library."
- For design-system work, connect changes to tokens, components, screenshots, and generated docs where possible.
Timeline
- 2026-07-01 | Refreshed Sigil/Reticle as a USER-level design-system proof connected to current project and design maps. Source: User request, 2026-07-01; Design System Map
- 2026-05-31 | Sigil building angle documented from USER and career-profile. Source: public wiki expansion, 2026-05-31