Oracle UI style guide
Oracle is a calm, precise workspace built from near-black graphite surfaces, restrained gradients, thin chamfered frames with subtle top-right hexagonal details, cyan focus, dark translucent-looking blue controls, and sparse semantic color. Square-profile controls such as tab headers keep only a top-right cutout. One language governs graphical applications and terminal interfaces.
Read the guide
| Topic | What it defines |
|---|---|
| Principles | Identity, hierarchy and the rules that govern every other page |
| Color | Authoritative dark palette, semantic pairs and permitted roles |
| Surfaces and depth | Exact gradients, layering, translucency and overlays |
| Shape | Chamfer geometry, outlines, connected tabs and corner details |
| Typography | Font families, weights, sizes, line heights and text treatment |
| Layout and density | Spacing, shell dimensions, adaptive layouts and scroll ownership |
| Icons and graphics | Icon geometry, symbols, connectors and data graphics |
| Interaction states | Focus, hover, press, selection, disabled and busy treatments |
| Motion | Meaningful motion vocabulary, timing, progress and reduced-motion behavior |
| Components and patterns | Application recipes, control inventory, and complete workspaces |
| Terminal | Character-cell equivalents, widths, colors and fallback behavior |
| Accessibility and content | Contrast, keyboard use, text, scaling and acceptance checks |
| Token contract | Naming, ownership, units and implementation-independent roles |
| Glyph guide | Copyable legacy computing symbols and Nerd Font UI glyphs |
Start with principles, color, surfaces and shape. Use component recipes to compose an app; use the terminal chapter whenever translating a recipe to the terminal.
Authority and scope
“MUST” and “must” identify requirements; “should” identifies the preferred default with a concrete contextual reason needed to depart. Unqualified numeric values are the specified defaults.
Within this guide, the topic page owns its values: color owns palette roles; surfaces owns gradient stops; shape owns contour dimensions; typography owns type metrics; layout owns spacing and density; motion owns time. Components combine those decisions rather than establishing competing tokens. The token contract indexes these authorities.
The dark theme is the specified theme. It applies to web/Electron, native graphical Oracle UIs, and terminals. Logical geometry and semantic roles are shared; pixel rendering, text metrics and terminal capability differ.
Light themes and custom brand themes require complete paired-role specifications before adoption. Every surface is built from the specified tokens.