Agent Skills: Phoenix Frontend Development

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.

UncategorizedID: arize-ai/phoenix/phoenix-frontend

Repository

Arize-aiLicense: NOASSERTION
9,073779

Install this agent skill to your local

pnpm dlx add-skill https://github.com/Arize-ai/phoenix/tree/HEAD/.agents/skills/phoenix-frontend

Skill Files

Browse the full folder contents for phoenix-frontend.

Download Skill

Loading file tree…

.agents/skills/phoenix-frontend/SKILL.md

Skill Metadata

Name
phoenix-frontend
Description
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.

Phoenix Frontend Development

Composable rules for building UI in the Phoenix app. Before starting work, explore app/src/components/ and app/package.json to understand existing patterns, packages, and conventions — then follow these rules.

Rule Files

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

| Rule file | When to read | |-----------|-------------| | rules/components.md | Creating, composing, or refactoring components | | rules/relay.md | Using Relay | | rules/accessibility.md | Any interactive element, form, overlay, or semantic markup |

Verification

After visual changes, use agent-browser to verify the UI looks correct. When modifying a shared component, check its usages across the app.