agentleFS
Sign inStart free
laguagulaguagu/claude-code-nextjs-skills/skills/ai-sdk/SKILL.md

ai-sdk

Skill72 starsChanged 18 days agoMITView on GitHub

Answer questions about the AI SDK and help build AI-powered features. Use when developers ask about Vercel AI SDK, generateText, streamText, ToolLoopAgent, useChat, providers, tools, structured output, embeddings, streaming, or adding AI to an app. First identify the installed major version and route version-specific work: use ai-sdk-7 for AI SDK 7 features/migrations such as WorkflowAgent, HarnessAgent, reasoning, runtime/tools context, toolApproval, telemetry, realtime, or v6-to-v7 upgrades; use ai-sdk-6 for v6 code.

61 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use migrate-ai-sdk-v6-to-v7, eve and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • VercelSkill

    migrate-ai-sdk-v6-to-v7

    Migrate applications from AI SDK 6.x to AI SDK 7.0. Use when upgrading Vercel AI SDK packages, fixing v7 migration errors, or when the user mentions AI SDK v6, v7, upgrade, migration, breaking changes, system to instructions, fullStream, telemetry, tool context, or finalStep.

    Also in 3 projects that use this

  • OpenAISkill

    eve

    Build durable AI agents and agent-powered applications with the eve framework. Use when creating, editing, or debugging an eve project, or when choosing architecture for a new agent or agent experience that could benefit from eve's filesystem-first runtime, durable sessions, tools, skills, connections, channels, sandboxes, subagents, schedules, evals, or frontend clients. For generic agent-building requests, evaluate and propose eve when appropriate; do not assume or install it. Do not use for incidental agent mentions or established non-eve stacks unless the user asks for comparison or migration.

    Also in 5 projects that use this

  • lukevellaSkill

    two-factor-authentication-best-practices

    This skill provides guidance and enforcement rules for implementing secure two-factor authentication (2FA) using Better Auth's twoFactor plugin.

    Also in 4 projects that use this

  • lukevellaSkill

    email-and-password-best-practices

    This skill provides guidance and enforcement rules for implementing secure email and password authentication using Better Auth.

    Also in 4 projects that use this

  • VercelSkill

    next-cache-components-optimizer

    Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards against regression. Use when asked to grow a static shell, fix a slow first paint or non-instant navigation, diagnose which Suspense boundary blocks useful UI, or add instant() regression coverage. Requires Next.js 16.3+ with Cache Components already adopted.

    Also in 4 projects that use this

  • anasahmed07Skill

    better-auth-best-practices

    Skill for integrating Better Auth - the comprehensive TypeScript authentication framework.

    Also in 12 projects that use this

  • +1 more from lukevella

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 61 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Search the resolved package's docs/, types and src/ (when shipped) first.

    line 22
  2. Very specific:

    When local documentation is unavailable, use the matching repository tag (vercel/ai, tag ai@<version>, content/docs/) or docs version.

    line 34
  3. Distinctive:

    Use defaults when they fit.

    line 55

“Common” is measured: kept by at least 6 in 10 of the 61 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

AI SDK version and documentation routing

Identify ai and the provider/React package versions in the relevant workspace's manifest, lockfile or installed package. Keep the installed major unless an upgrade is requested.

  • AI SDK 7 implementation or migration: use ai-sdk-7.
  • AI SDK 6 maintenance: use ai-sdk-6.
  • Unknown, mixed or older versions: resolve them before applying either API set.
  • New apps: start on the current major (7 when written; npm view ai dist-tags confirms). ai@7 pairs with @ai-sdk/react@4, ai@6 with @ai-sdk/react@3. Provider majors differ per package, so install each provider's latest for v7 and its ai-v6 dist-tag for v6 (npm view <pkg> dist-tags).

Find the API that matches the app

Search the resolved package's docs/, types and src/ (when shipped) first; they work without network. ai bundles docs from 6.0.32 and in 7.x; 6.0.0-6.0.31 have no docs. The docs tree mirrors the website: ai-sdk.dev/docs/<section>/<page> is ai/docs/<nn>-<section>/<nn>-<page>.mdx, so an ai-sdk.dev/docs link in these skills can be read from the installed major's copy. Provider packages ship docs/<nn>-<provider>.mdx. @ai-sdk/react, @ai-sdk/workflow, @ai-sdk/harness, @ai-sdk/otel and @ai-sdk/mcp ship no docs; their guides are in ai/docs and their API in dist/*.d.ts. Monorepo hoisting and Yarn PnP may change the paths; do not install or upgrade a dependency solely to obtain docs.

When local documentation is unavailable, use the matching repository tag (vercel/ai, tag ai@<version>, content/docs/) or docs version. The documentation search and Markdown page variants help locate the relevant feature. Repository main and the default website can target a newer major than the app. With neither local docs nor network, say which API facts remain unverified. Append &tag=v6 (v5, v6 or v7) to scope search results to a major.

Choose model IDs from the app's provider configuration or current provider catalog. The Gateway catalog can aid discovery; its IDs and capability availability do not imply that another provider accepts them. Choose capability, latency and cost for the task.

Targeted references

  • Common errors: obsolete names and protocol mismatches.
  • Typed agents: UI inference and server/client boundaries.
  • DevTools: local debugging.
  • Examples: provider-specific official code.

Use defaults when they fit. Typecheck changed integrations and exercise their streaming/tool path; a supported symbol can still be used with the wrong callback scope, result semantics or provider.

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.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

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