القائمة
Guide for the phoenix-otel TypeScript package — OTel registration, stack-based global provider management, and provider lifecycle.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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/.
Open-source AI observability platform for tracing, evaluating, and improving LLM applications with OpenTelemetry integration
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.
TypeScript conventions and patterns for any TypeScript code in the Phoenix monorepo — including js/packages/, app/, and any other TS directories. Use this skill whenever writing, reviewing, or modifying TypeScript code — new functions, types, exports, tests, or refactors. Also trigger when the user asks about TS patterns, naming conventions, or best practices for this project.
Build and run evaluators for AI/LLM applications using Phoenix.
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.
| name | phoenix-otel-development |
| description | Guide for the phoenix-otel TypeScript package — OTel registration, stack-based global provider management, and provider lifecycle. |
| license | Apache-2.0 |
| metadata | {"author":"oss@arize.com","version":"1.0.0","languages":"TypeScript","internal":true} |
OpenTelemetry registration and provider lifecycle layer for Phoenix. Single source of truth for OTel configuration — other Phoenix packages delegate here rather than importing OTel packages directly.
Read existing code in the directory you're working in before writing new code.
| Rule file | When to read |
|---|---|
rules/global-provider-lifecycle.md | Global provider attachment, detachment, snapshot/restore, mount stack |
rules/register-api.md | register(), span processor setup, public API surface |
rules/testing.md | Tests for provider lifecycle, registration, span export |
cd js/
pnpm --filter phoenix-otel test
Dual-module output (CJS + ESM). Tests use vitest.