Design Principles
The design principles define how Exosuit should feel across documentation and product-adjacent surfaces: local, inspectable, dense, native, and built around developer judgment.
Design Principles
Exosuit should feel like a collaborative cockpit: a compact, high-trust surface that helps humans and agents stay oriented, make decisions, and verify progress.
Augmenting, not autonomous
Exosuit strengthens developer judgment with context, steering, and verification; it does not replace the human decision-maker.
Cockpit, not chatbot
Orientation, signals, controls, and workflow state matter more than a generic conversational shell.
Dense, not cramped
Compact information is good, but hierarchy and scannability must stay intact.
Local and inspectable
State should feel grounded in the workspace, visible to the user, and understandable at every step.
Native, not over-branded
Inside product surfaces, Exosuit should feel at home in developer tools rather than like a flashy SaaS layer.
Tactical, not militarized
Use the language of steering, phases, rails, and signals, while avoiding combat imagery or aggressive futurism.