OpenParable
Skip to content
← Back to skills

Phoenix Frontend

Development
phoenix-frontend

Phoenix Frontend is an Agent Skill for development published in the Arize-ai/phoenix repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/Arize-ai/phoenix/blob/HEAD/.agents/skills/phoenix-frontend/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/phoenix-frontend, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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.

Reference Files

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

ReferenceWhen to read
references/components.mdCreating, composing, or refactoring components
references/relay.mdUsing Relay
references/accessibility.mdAny interactive element, form, overlay, or semantic markup
references/test-ids.mdAdding or changing data-testid attributes for E2E tests
references/resize-svg-logo-assets.mdAdding or updating provider/integration logo icons

Verification

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

Route Metadata

When adding, removing, renaming, or materially changing what a page contains, update the route's handle.agentRoute metadata in app/src/Routes.tsx if an assistant agent should be able to link users to that destination. Keep metadata small and search-oriented:

  • label: human page name.
  • description: concise page purpose based on what the page now contains, including user phrases PXI might hear when looking for that page.

If a content change makes an existing route easier or harder to find by natural language, adjust description in the same change.

URL State

Significant view state must be recreatable from the URL. If a user can select a tab, sub-view, or detail state that should survive reloads, sharing, or adjacent-record pagination, encode it in route params or search params and preserve the relevant URL state during navigation.