Dark-native developer console

What you see

The perceptual fingerprint, in the order you notice it.

• Near-black surfaces that are tinted, never pure #000
• Elevation shown by a lighter surface step rather than by a shadow
• Monospace numerals and identifiers sitting inside proportional prose
• Accent colour used sparingly, as signal rather than decoration
• Thin low-contrast dividers marking dense regions

Best for

• Developer tools, logs, consoles and monitoring surfaces
• Data-dense screens used for long sessions in low light
• Products whose audience already lives in a dark editor

Avoid when

• The audience reads long prose — sustained body text is measurably harder light-on-dark
• The brand's colour identity depends on light, airy surfaces
• You cannot commit: a half-designed dark theme is worse than a good light one

Accessibility

Where this style tends to fail an audit, and what fixes it.

• Pure white on pure black causes halation. Use `--foreground` at around 90% lightness on a surface near 8–12%, not the extremes.
• Dark surfaces need bigger contrast steps between elevation levels than light ones do; 3:1 between adjacent surfaces is the floor, not a goal.
• Saturated accents vibrate on dark. Desaturate the accent for dark surfaces rather than reusing the light-mode value.