By name: phoenix-design description: Design system conventions for the Phoenix frontend — layout, dialogs, error display, BEM CSS class naming, and CSS design tokens. Use when building UI, naming CSS classes, creating or consuming tokens, handling errors, or designing dialog interactions in app/src/. license: Apache-2.0 metadata: author: oss@arize.com version: "2.0.0" internal: true
Phoenix Design System
The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this specification are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.
Rule Files
Read the relevant file(s) based on the task:
| Rule file | When to read |
|---|---|
rules/layout.md |
Layout stability, scroll behavior, interaction patterns |
rules/dialogs.md |
Alert dialog usage, variants, and content writing |
rules/form-dialogs.md |
Form dialog structure, footer/submit placement, field metadata |
rules/error-display.md |
Error scoping, inline alerts, input validation |
rules/bem.md |
Naming CSS classes |
rules/tokens.md |
Creating or consuming CSS design tokens |
rules/icons.md |
Picking an icon for a noun (project, trace, span, file, etc.) |
rules/counters.md |
Displaying counts in tabs, headings, or filter buttons |