Cyberpunk design is what the future looked like before the future arrived — neon light bleeding through rain-wet streets, corporate interfaces crammed with data that nobody but the operator understands, holographic displays flickering in dark rooms. Blade Runner. Ghost in the Shell. Akira. Cyberpunk 2077. The aesthetic is maximalist in the best sense — it fills every corner of the screen with texture, light, and information, and makes you feel like you're operating something powerful. When built well, a cyberpunk interface makes using mundane software feel like hacking into a corporate mainframe.
Cyberpunk.
Neon light, dark interfaces, and information overload as atmosphere. The aesthetic of Blade Runner terminals and Cyberpunk 2077 for gaming and creative tools.
Light as substance
In cyberpunk design, light doesn't just illuminate — it glows, bleeds, and contaminates. A neon edge doesn't just have a color; it casts that color onto the surfaces around it. Text doesn't just appear on a background; it pulses with a subtle luminous quality. This treatment of light as a physical material rather than a visual property is what gives cyberpunk interfaces their depth. Everything is slightly lit from within.
Information overload is intentional
Where most design removes information to create clarity, cyberpunk adds information to create atmosphere. Secondary data readouts, status tickers, coordinate displays, progress bars that serve no functional purpose — all of these are aesthetic choices that signal the complexity and power of the system. The information doesn't all need to be read. It needs to be felt.
The grid is breaking down
Cyberpunk layouts are grids in decay — elements that almost align, borders that are cut at angles rather than meeting at corners, panels that overlap slightly rather than sitting flush. This controlled imperfection communicates a world where systems are under pressure, where the clean lines of corporate design have been hacked and modified and pushed past their original parameters. Precise imprecision is the technique.
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.
Terminal
The prompt, the cursor, the monospace grid. Terminal design takes the CLI's honest visual vocabulary and turns it into a complete design system.
Matrix
Green on black. One font. One grid. The design language of the digital void — code rain, terminal readouts, and interfaces that feel like they're running the world.
Two files. That's it.
Drop them into your Claude project or Cursor rules and build normally. No CLI, no package manager, no setup.