Deep space design takes its visual language from the places humans have only ever seen through screens — the interior of space stations, the instrument panels of spacecraft, the visualization interfaces of observatories and mission control rooms. It's darker and more considered than cyberpunk, more technical and precise than dark luxury. There's something meditative about it — the vastness implied by the aesthetic makes even small apps feel like they're doing something important. HAL 9000's interface. The Expanse's ship screens. Interstellar's Cooper Station readouts. Serious, beautiful, and unlike anything in mainstream consumer software.
DeepSpace.
The visual language of spacecraft panels and mission control — dark, precise, meditative. For tools where users need to feel like they're operating something significant.
The silence of space
Deep space design uses negative space the way space itself uses it — not as emptiness to fill, but as the primary substance. Elements are placed like stars: precisely, with great distances between them that make each one feel important. The silence of the interface communicates the gravity of what's happening inside it. This is design that asks users to pay attention.
Every element earns its light
In deep space, light is precious. Interfaces take their cue from instrument panels and radar screens — most of the surface is dark, and the elements that are lit are lit because they carry information. A glowing ring means something. A lit indicator means something. Nothing emits light decoratively. This discipline means users always know where to look, because light itself is the navigation system.
Precision is the aesthetic
Mission-critical interfaces must be right. Deep space design communicates precision through tight typographic hierarchies, consistent grid structures, and a restraint around color that says "every value here means something." Numbers are displayed with full decimal places. Labels are in uppercase monospace. Progress is shown on arcs and gauges, not just bars. The aesthetic communicates that the software was built by people who don't tolerate approximation.
Before building with Claude Code, drop SKILL.md and DESIGN.md into Claude Design first. Use it to generate mockups and nail the visual direction — then hand those references to Claude Code. You'll get significantly higher quality output than going straight to code.
Two files. That's it.
Drop them into your Claude project or Cursor rules and build normally. No CLI, no package manager, no setup.