phoenix-typescript-package-docs
Phoenix TypeScript Package Docs
Keep the curated TypeScript package docs aligned with the real npm package surface area and with the publish-time sync flow.
Quick Reference
| Task | What to inspect | What to update |
|---|---|---|
| Fix a stale example | js/packages/<pkg>/src/ exports and function signatures |
Canonical MDX under docs/phoenix/sdk-api-reference/typescript/packages/<pkg>/ |
| Add or remove a page | Existing package-doc folder and docs.json nav |
Canonical MDX, docs.json, and any landing-page links |
| Add a new package to the bundled-docs system | js/scripts/sync-package-docs.mjs and package package.json |
Sync map, package files, package prepack, and Mintlify nav |
| Verify publish output | node js/scripts/sync-package-docs.mjs and npm pack --dry-run |
Generated js/packages/<pkg>/docs/ contents and tarball entries |
Source Of Truth
The canonical authored docs live in Mintlify pages:
docs/phoenix/sdk-api-reference/typescript/packages/phoenix-client/
More from arize-ai/phoenix
phoenix-cli
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.
496phoenix-tracing
OpenInference semantic conventions and instrumentation for Phoenix AI observability. Use when implementing LLM tracing, creating custom spans, or deploying to production.
489phoenix-evals
Build and run evaluators for AI/LLM applications using Phoenix.
433agent-browser
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.
65vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
63phoenix-skill-development
Develop, refine, and maintain skills in the skills/ directory. Use when creating a new skill, updating an existing skill, adding rule files, or improving skill quality and consistency.
59