phoenix-design

v2026.09.24

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 js/app/src/.

GitHub
Install command
npx skhub add arize-ai/phoenix-design
Markdown
SKILL.md

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.

What Are You Doing?

Read the relevant reference(s) based on the task:

TaskReference
Layout stability, scroll behavior, interaction patterns, tooltip placement in tablesreferences/layout.md
Alert and form dialog usage, footer button styling, content writingreferences/dialogs.md
Error scoping, inline alerts, input validationreferences/error-display.md
Naming CSS classesreferences/bem.md
Creating or consuming CSS design tokensreferences/tokens.md
Picking an icon for a noun (project, trace, span, file, etc.)references/icons.md
Displaying counts in tabs, headings, or filter buttonsreferences/counters.md
Choosing or adding an EmptyStateGraphic variant (the per-region/topic empty-state graphics)references/empty-states.md
Discovery
Tags

No tags published for this skill.

Version
Latest version metadata

Version

v2026.09.24

Published

Sep 24, 2026

Category

Uncategorized

License

NOASSERTION

Source path

.agents/skills/phoenix-design

Default branch

main

Latest commit

d7e5aeb

Tree SHA

db9821d