Style guide
The style guide is implemented as the same kind of editorial sheet shown in the mockups: page chrome, a dark cockpit hero, compact panels, semantic signal marks, and product-adjacent examples. These are site primitives, not decorative one-offs.
Collaborative cockpit
Exosuit
A fitted control surface for developer judgment.
Local-first by design
Human + agent collaboration
Inspectable by default
Brand premise
Augmentation, not automation
Strengthen developer judgment with shared context, steering, verification, and visible next actions.
Cockpit, not chatbot
Prioritize state, controls, rails, signal surfaces, and review handoffs over personality or chat decoration.
Dense, not cramped
Use compact modules, clear hierarchy, thin rules, and generous outer margins so dense state remains readable.
Exosuit turns a workspace into a portable collaboration boundary. The documentation should make phases, goals, tasks, RFCs, signals, and verification feel inspectable before they feel branded.
Operational, calm, local, technical, and explicit.
Restrained signal colors: blue, green, yellow, and red carry state.
Pattern rules
Section titled “Pattern rules”- Use page chrome, dark orientation bands, compact rails, and thin dividers for major visual moments.
- Show what is active, what changed, and what needs attention before adding decorative polish.
- Use semantic color roles, but never rely on color alone.
- Keep Starlight native; the brand follows the host.