Atlas workspace
On trackRenewal is due in 18 days. Weekly use is up and two seats were added this month.
- Seats
- 24
- Usage
- +18%
- Renewal
- 18 days
Translucent panels that blur whatever sits behind them, so depth comes from the layer stack rather than from heavy borders.
Also called: frosted glass, glass UI, acrylic, spatial, blur panel
Your Design Kit keeps
Colors, typefaces, the spacing scale, motifs, and brand voice.
Glassmorphism changes
Surface material, borders, shape, depth, component layout, states, and motion.
Renewal is due in 18 days. Weekly use is up and two seats were added this month.
Renewal is due in 18 days. Weekly use is up and two seats were added this month.
Look for: Watch the panel edge and the field behind it: the highlight along the top and the softened backdrop are doing the depth work that a border would do elsewhere. The selected chip keeps a solid edge so it does not rely on opacity alone.
Both panels use the same sample Design Kit and account screen. Only the interface style changes on the right.
Select a scope to create a prompt for your coding agent. Start with one component family or apply the style across the interface.
Apply Glassmorphism to cards, panels, sheets, and modals only. Keep my Design Kit's colors, typefaces, and motifs. Leave navigation, forms, actions, and page structure unchanged. Show me one representative card first, then explain the accessibility trade-offs before changing the rest.The perceptual fingerprint, in the order you notice it.
Where this style tends to fail an audit, and what fixes it.
The site archetypes this render grammar suits. Each opens the catalog on that lane.
A style is a render grammar. A design kit supplies the colour, type and personality it paints.
Frosted translucent panels (backdrop-blur + translucent fill + light hairline) floating over saturated/aurora light fields. visionOS / Big Sur spatial UI.
What an agent needs in order to actually build Glassmorphism on top of your design kit — surface rules, per-component behaviour, responsive behaviour, fallbacks and QA.
The declarations that make the render grammar, stated as CSS.
Nav, action, input, selection, card and status, one rule each.
What has to change as the viewport narrows for the style to survive.
The degraded paths: unsupported effects, weak shadows, reduced motion.
What to verify before shipping an interface in this style.
The vocabulary a coding agent can match this style on.