Visual tokens and component rules

Use the existing Storybook token contract where available. The following are semantic roles, not replacement hard-coded colors:

Role Guidance
Page background Existing Avelx dark surface
Card surface One step above page background; no glow
Border Low-contrast hairline, visible against both surfaces
Accent Existing Avelx blue for actions, focus, and selected state
Primary text High-contrast neutral text
Supporting text Muted neutral text with readable contrast
Success Text plus status dot/icon; never color alone
Warning/error Text plus icon and recovery action

Component rules:

  • Use the existing Storybook card, button, badge, dialog, and input primitives.
  • Do not create a one-off card style for clusters.
  • Keep the card border radius and spacing aligned with the homepage card

component.

  • Use a full-width primary button only inside the card when the card is in a

narrow layout; on desktop, allow the secondary Manage action beside it.

  • Keep the vertical divider inside the empty-state chooser, not between every

card in the saved-cluster grid.

  • Reserve space for status and action rows so checking states do not shift the

layout.