ai / ai
vercel/ai/packages/ai/AGENTS.md
No summary in the file. Open it to read it.
Steady2 mentions in 2 weeks
No other project uses it yet
One search for your own team's files and the public ecosystem. See how real projects write their agent instructions, and bring the good ideas home.
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.
vercel/ai/packages/ai/AGENTS.md
No summary in the file. Open it to read it.
Steady2 mentions in 2 weeks
No other project uses it yet
vercel/ai/skills/add-function-examples/SKILL.md
Guide for adding new AI function examples, for testing specific features against the actual provider APIs.
Steady2 mentions in 2 weeks
No other project uses it yet
vercel/ai/skills/adr-skill/SKILL.md
Create and maintain Architecture Decision Records (ADRs) optimized for agentic coding workflows. Use when you need to propose, write, update, accept/reject, deprecate, or supersede an ADR; bootstrap an adr folder and index; consult existing ADRs before implementing changes; or enforce ADR conventions. This skill uses Socratic questioning to capture intent before drafting, and validates output against an agent-readiness checklist.
Steady2 mentions in 2 weeks
4 projects use a version of this
vercel/ai/skills/capture-api-response-test-fixture/SKILL.md
Capture API response test fixture.
Steady2 mentions in 2 weeks
1 project uses a version of this
vercel/ai/skills/list-npm-package-content/SKILL.md
List the contents of an npm package tarball before publishing. Use when the user wants to see what files are included in an npm bundle, verify package contents, or debug npm publish issues.
Steady2 mentions in 2 weeks
1 project uses a version of this
vercel/ai/skills/major-version-mode/SKILL.md
Context for working on the next AI SDK major release. Only use when explicitly invoked by the user (e.g. via '/major-version-mode'). Do NOT trigger autonomously based on task content.
Steady2 mentions in 2 weeks
No other project uses it yet
vercel/ai/skills/migrate-ai-sdk-v6-to-v7/SKILL.md
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.
Steady2 mentions in 2 weeks
2 projects use a version of this
vercel/ai/skills/update-harness-dependencies/SKILL.md
Update the primary SDK dependencies of harness packages. Use when asked to update the harness SDKs or harness adapter dependencies.
Steady2 mentions in 2 weeks
No other project uses it yet
vercel/ai/skills/update-provider-models/SKILL.md
Add new or remove obsolete model IDs for existing AI SDK providers. Use when adding a model to a provider, removing an obsolete model, or processing a list of model changes from an issue. Triggers on "add model", "remove model", "new model ID", "obsolete model", "update model IDs".
Steady2 mentions in 2 weeks
No other project uses it yet
vercel/ai-chatbot/.cursor/rules/ultracite.mdc
Ultracite Rules - AI-Ready Formatter and Linter
14 projects use a version of this
vercel/vercel/AGENTS.md
Guidelines for AI agents working on the Vercel monorepo. This is a pnpm monorepo containing 44+ packages for the Vercel CLI and runtimes: Run tests for a specific package: Always create a changeset for all PRs. A changeset is a markdown file in .changeset/ with YAML frontmatter listing affected packages and their bump type (patch/minor/major). Example changeset for a package change: Example changeset for an internal package (the public packages that bundle it are added at version time): Example changeset…
vercel/vercel/packages/cli/AGENTS.md
Always-loaded guidance for work inside packages/cli. Keep this file small. The CLI UX design system lives in packages/cli/.agents/skills/cli-ux/ and should be loaded only when the task or code review touches user-facing CLI behavior. Common shared areas:
vercel/vercel/packages/cli/.agents/skills/cli-ux/SKILL.md
Vercel CLI design system, the north-star standard for command names, options, help, prompts, output, copy, errors, JSON, exit codes, and agent/CI behavior in packages/cli. Use when designing, implementing, or reviewing any user-facing CLI surface. Skip implementation-only refactors that leave the CLI surface unchanged.
vercel/vercel/python/AGENTS.md
- Dependencies: PEP 440 compatible release clauses (rich ~= 14.0), avoid pinning patch releases (rich ~= 14.0.0). - Only add code that is actually used. No speculative APIs or exports. - _internal/ is private — no backwards compatibility needed when refactoring. - uv: uv sync, uv run <cmd>, uv add <pkg> - ruff: uv run ruff check . (lint), uv run ruff format . (format) - pytest: uv run pytest, uv run pytest tests/test_foo.py, uv run pytest -k test_name. Tests…
vercel/vercel/skills/vercel-cli/SKILL.md
Guides deployment, configuration, and troubleshooting with the Vercel CLI. Use when operating Vercel projects or resources through the CLI, especially for workflows spanning multiple commands, including deployments, CI, build failures, logs, metrics, Speed Insights, traces, environment variables, domains and DNS, firewall and WAF rules, Global Config (Edge Config), feature flags, storage and Blob, Container Registry (VCR), microfrontends, Sandbox, and `vercel api` fallback.
vercel/vercel/.vc/automations/workflows/flaky-tests/skills/fix-vi-flaky-test/SKILL.md
Set up the Factory sandbox for vercel-internal's tests, then reproduce and fix one flaky test that the flaky-tests workflow found, or add diagnostics for a shard hang.
vercel/vercel/.vc/automations/workflows/melkey-label/skills/author-labels/SKILL.md
Decide which author label, if any, a pull request gets. Load before labeling a pull request.
vercel/eve/AGENTS.md
Guidance for coding agents (and humans) working in this repository. For setup, PR workflow, and release process, see CONTRIBUTING.md. eve is a filesystem-first framework for durable backend AI agents. You author an agent as a directory on disk — instructions, skills, tools, connections, channels, subagents, and schedules are all files — and eve compiles and runs it. See the README for the full overview and docs/ for user-facing documentation. Always style the framework name as eve, lowercase, in user-facing copy,…
Steady4 mentions in 2 weeks
No other project uses it yet
vercel/eve/.agents/skills/gh-pr-description/SKILL.md
Drafts and reviews GitHub pull request descriptions for the eve repository. Use when opening, updating, or reviewing a PR, or when summarizing a branch for reviewers.
Steady4 mentions in 2 weeks
1 project uses a version of this
vercel/eve/.agents/skills/pr-shepherd/SKILL.md
Takes a finished eve branch from review to merge. Opens the PR early, runs a fresh-context reviewer subagent, fixes critical findings, addresses, replies to, and resolves review comments, pushes, monitors CI (rerunning flaky jobs or fixing real failures), then squash-merges or enables auto-merge. Follow only when the user explicitly asks to shepherd, babysit, land, or merge a PR, or to "get a PR green". Do not start it on your own after finishing an implementation or when only asked to open a PR.
Steady4 mentions in 2 weeks
10 projects use a version of this
Plain text files in a repository that tell a coding agent how the project works: commands to run, conventions to follow and things to avoid. CLAUDE.md, AGENTS.md, cursor rules and skills are the common kinds.
CLAUDE.md is read by Claude Code. AGENTS.md is an open format that Codex, Cursor and other agents read. Many projects keep one and point the other at it.
A folder with a SKILL.md that describes one capability, such as filling PDFs or reviewing code. The agent loads it only when the task calls for it.
Your agents already can, over MCP, limited to the files you're allowed to read. Searching them from this page is coming.