Development guide for the @arizeai/phoenix-client TypeScript SDK — run and resume experiments, manage OpenTelemetry tracer providers with stack-based attach/detach, and write vitest unit and integration tests. Use when adding features to phoenix-client, debugging experiment lifecycle or provider cleanup, modifying dataset/prompt/session/span APIs, or writing tests for the js/packages/phoenix-client/ directory.
79
85%
Does it follow best practices?
Impact
92%
1.21x2 of 3 eval scenarios. Add 1 more for a full score.
Passed
No findings from the security scan
TypeScript SDK for Phoenix AI observability: datasets, experiments, prompts, sessions, spans, traces.
Read existing code in the directory you're working in before writing new code.
| Rule file | When to read |
|---|---|
rules/experiments.md | Experiment execution, task runners, evaluator wiring |
rules/prompts.md | Prompt helpers, selector shapes, server version gating |
rules/tracing.md | OpenTelemetry tracer providers, span export, global state |
rules/testing.md | Unit tests, integration tests, test fixtures |
cd js/
pnpm --filter phoenix-client testTests use vitest. Test files live in test/ named *.test.ts.
Arize-ai/phoenix
8ac3caf
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.