agentleFS
Sign inStart free
legions-developerlegions-developer/invoicely/.agents/skills/use-ai-sdk/SKILL.md

ai-sdk

Skill923 starsChanged 5 months agoMITView on GitHub

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, embed, or tools, (2) Want to build AI agents, chatbots, RAG systems, or text generation features, (3) Have questions about AI providers (OpenAI, Anthropic, Google, etc.), streaming, tool calling, structured output, or embeddings, (4) Use React hooks like useChat or useCompletion. Triggers on: "AI SDK", "Vercel AI SDK", "generateText", "streamText", "add AI to my app", "build an agent", "tool calling", "structured output", "useChat".

  • Installs packages

We split this skill into the rules it gives an agent

21 rules. 0 are common, 11 are distinctive, and 10 are very specific to this project.

  • 0

    Common

    Most of the 34 edited versions we read keep these.

  • 11

    Distinctive

    This author's own choices. Worth a look.

  • 10

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Before searching docs, check if node_modules/ai/docs/ exists.

    line 8
  2. Very specific:

    Do not install other packages at this stage.

    line 10
  3. Very specific:

    Ensure ai package is installed (see Prerequisites)

    line 18
  4. Very specific:

    Search node_modules/ai/docs/ and node_modules/ai/src/ for current APIs

    line 19
  5. Distinctive:

    If not found locally, search ai-sdk.dev documentation (instructions below)

    line 20
  6. Distinctive:

    Never rely on memory - always verify against source code or docs

    line 21
  7. Very specific:

    useChat has changed significantly: - check Common Errors before writing client code

    line 22
  8. Distinctive:

    When deciding which model and provider to use (e.g.

    line 23
  9. Distinctive:

    Run typecheck after changes to ensure code is correct

    line 25
  10. Distinctive:

    Be minimal: - Only specify options that differ from defaults.

    line 26
  11. Distinctive:

    If you cannot find documentation to support your answer, state that explicitly.

    line 28
  12. Very specific:

    Search bundled docs and source in node_modules/ai/:

    line 34
  13. Distinctive:

    If not found in common-errors.md:

    line 50
  14. Very specific:

    Search node_modules/ai/src/ and node_modules/ai/docs/

    line 52
  15. Distinctive:

    Search ai-sdk.dev (for earlier versions or if not found locally)

    line 53
  16. Very specific:

    Always use the ToolLoopAgent pattern.

    line 59
  17. Very specific:

    Type Safety: When consuming agents with useChat, always use InferAgentUIMessage<typeof agent> for type-safe tool results.

    line 63
  18. Distinctive:

    Before implementing agent consumption:

    line 67
  19. Very specific:

    Check package.json to detect the project's framework/stack

    line 69
  20. Distinctive:

    Search documentation for the framework's quickstart guide

    line 70
  21. Distinctive:

    Follow the framework-specific patterns for streaming, API routes, and client integration

    line 71

“Common” is measured: kept by at least 6 in 10 of the 34 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Prerequisites

Before searching docs, check if node_modules/ai/docs/ exists. If not, install only the ai package using the project's package manager (e.g., pnpm add ai).

Do not install other packages at this stage. Provider packages (e.g., @ai-sdk/openai) and client packages (e.g., @ai-sdk/react) should be installed later when needed based on user requirements.

Critical: Do Not Trust Internal Knowledge

Everything you know about the AI SDK is outdated or wrong. Your training data contains obsolete APIs, deprecated patterns, and incorrect usage.

When working with the AI SDK:

  1. Ensure ai package is installed (see Prerequisites)
  2. Search node_modules/ai/docs/ and node_modules/ai/src/ for current APIs
  3. If not found locally, search ai-sdk.dev documentation (instructions below)
  4. Never rely on memory - always verify against source code or docs
  5. useChat has changed significantly - check Common Errors before writing client code
  6. When deciding which model and provider to use (e.g. OpenAI, Anthropic, Gemini), use the Vercel AI Gateway provider unless the user specifies otherwise. See AI Gateway Reference for usage details.
  7. Always fetch current model IDs - Never use model IDs from memory. Before writing code that uses a model, run curl -s https://ai-gateway.vercel.sh/v1/models | jq -r '[.data[] | select(.id | startswith("provider/")) | .id] | reverse | .[]' (replacing provider with the relevant provider like anthropic, openai, or google) to get the full list with newest models first. Use the model with the highest version number (e.g., claude-sonnet-4-5 over claude-sonnet-4 over claude-3-5-sonnet).
  8. Run typecheck after changes to ensure code is correct
  9. Be minimal - Only specify options that differ from defaults. When unsure of defaults, check docs or source rather than guessing or over-specifying.

If you cannot find documentation to support your answer, state that explicitly.

Finding Documentation

ai@6.0.34+

Search bundled docs and source in node_modules/ai/:

  • Docs: grep "query" node_modules/ai/docs/
  • Source: grep "query" node_modules/ai/src/

Provider packages include docs at node_modules/@ai-sdk/<provider>/docs/.

Earlier versions

  1. Search: https://ai-sdk.dev/api/search-docs?q=your_query
  2. Fetch .md URLs from results (e.g., https://ai-sdk.dev/docs/agents/building-agents.md)

When Typecheck Fails

Before searching source code, grep Common Errors for the failing property or function name. Many type errors are caused by deprecated APIs documented there.

If not found in common-errors.md:

  1. Search node_modules/ai/src/ and node_modules/ai/docs/
  2. Search ai-sdk.dev (for earlier versions or if not found locally)

Building and Consuming Agents

Creating Agents

Always use the ToolLoopAgent pattern. Search node_modules/ai/docs/ for current agent creation APIs.

File conventions: See type-safe-agents.md for where to save agents and tools.

Type Safety: When consuming agents with useChat, always use InferAgentUIMessage<typeof agent> for type-safe tool results. See reference.

Consuming Agents (Framework-Specific)

Before implementing agent consumption:

  1. Check package.json to detect the project's framework/stack
  2. Search documentation for the framework's quickstart guide
  3. Follow the framework-specific patterns for streaming, API routes, and client integration

References

  • Common Errors - Renamed parameters reference (parameters → inputSchema, etc.)
  • AI Gateway - Gateway setup and usage
  • Type-Safe Agents with useChat - End-to-end type safety with InferAgentUIMessage
  • DevTools - Set up local debugging and observability (development only)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free