skills/ai-sdk/SKILL.md
Answer questions about the AI SDK and help build AI-powered features. Use when developers: (1) Ask about AI SDK functions like generateText, streamText, ToolLoopAgent, or tools, (2) Want to build AI agents, chatbots, or text generation features, (3) Have questions about AI providers (OpenAI, Anthropic, etc.), streaming, tool calling, or structured output.
npx skillsauth add pedronauck/skills ai-sdkInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
When you need up-to-date information about the AI SDK:
Search the bundled documentation and source code in node_modules/ai/:
grep "your query" node_modules/ai/docs/grep "your query" node_modules/ai/src/To find specific files:
glob "node_modules/ai/docs/**/*.mdx" for documentation filesglob "node_modules/ai/src/**/*.ts" for source filesProvider packages (@ai-sdk/openai, @ai-sdk/anthropic, etc.) also include bundled docs in their respective node_modules/@ai-sdk/<provider>/docs/ directories.
When in doubt, update to the latest version of the AI SDK.
https://ai-sdk.dev/api/search-docs?q=your_query.md.md URLs directly to get plain text content (e.g. https://ai-sdk.dev/docs/agents/building-agents.md)Use these resources for current API details, examples, and usage patterns.
For common errors and troubleshooting, see Common Errors Reference.
For using Vercel AI Gateway, see AI Gateway Reference.
For questions about specific providers (OpenAI, Anthropic, Google, etc.), search their dedicated packages:
grep "your query" node_modules/@ai-sdk/<provider>/docs/grep "your query" node_modules/@ai-sdk/<provider>/src/To find provider files:
glob "node_modules/@ai-sdk/<provider>/docs/**/*.mdx" for provider documentationglob "node_modules/@ai-sdk/<provider>/src/**/*.ts" for provider source filesThis is especially important for providerOptions, which are provider-specific settings passed to model calls. Each provider has unique options documented in their package.
development
Deep review of branch diffs, working trees, or GitHub PRs at any size. Use when the user asks for CodeRabbit-grade review, an incremental re-review after new pushes, publication of findings to a PR, a cross-LLM peer-review verdict round, or conformance review against spec artifacts. Don't use for applying fixes, reviewing specs or PRDs as documents, or quick single-file feedback.
tools
Orchestrate Claude and Codex worker TUIs from a controller agent through herdr panes and the herdr socket CLI. Use when delegating bounded tasks to herdr worker panes, running user-activated plan-first delegations (Claude Code plan mode, Codex Plan mode), waiting on native agent status (idle, working, blocked, done), or verifying worker reports. Workers launch as interactive TUIs via herdr agent start — never through headless runners (compozy exec, claude -p, codex exec). Not for cmux workspaces (see cmux-orchestration) and not for end-user herdr control.
tools
TanStack Query, Router, and Form patterns for React. Use when writing useQuery/queryOptions, mutations, caching, file-based routes, search params, loaders, or TanStack Form validation. Don't use for TanStack Start, TanStack DB/collections, Zustand client state, or non-TanStack routing.
development
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.