phoenix-design
The phoenix-design Claude Code skill provides design system conventions for the Phoenix frontend, covering layout stability, dialog patterns, error display, BEM CSS naming, design tokens, icon selection, and counter display. Use it when building UI components, naming CSS classes, creating design tokens, handling error states, designing dialog interactions, or selecting icons within the Phoenix app/src/ directory.
git clone --depth 1 https://github.com/Arize-ai/phoenix /tmp/phoenix-design && cp -r /tmp/phoenix-design/.agents/skills/phoenix-design ~/.claude/skills/phoenix-designSKILL.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. ## 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 |
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
Build and maintain documentation sites with Mintlify. Use when
Debug LLM applications using the Phoenix CLI. Fetch traces, analyze errors, structure trace review with open coding and axial coding, inspect datasets, review experiments, query annotation configs, and use the GraphQL API. Use whenever the user is analyzing traces or spans, investigating LLM/agent failures, deciding what to do after instrumenting an app, building failure taxonomies, choosing what evals to write, or asking "what's going wrong", "what kinds of mistakes", or "where do I focus" — even without naming a technique.
>
>-
Build and run evaluators for AI/LLM applications using Phoenix.
Frontend development guidelines for the Phoenix AI observability platform. Use when writing, reviewing, or modifying React components, TypeScript code, styles, or UI features in the app/ directory. Triggers on any frontend task — new components, UI changes, styling, accessibility fixes, form handling, or component refactoring. Also use when the user asks about frontend conventions or component patterns for this project. For design system rules (error display, layout, dialogs, tokens), use the phoenix-design skill.
Manage GitHub issues, labels, and project boards for the Arize-ai/phoenix repository. Use when filing roadmap issues, triaging bugs, applying labels, managing the Phoenix roadmap project board, or querying issue/project state via the GitHub CLI.