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.
VercelAGENTS.mdvercel/next.js/evals/next-upgrade/evals/future-cache-components/AGENTS.md
You may edit this application and create local commits. Do not push or create pull requests. Use npm. Preserve the behavior described in README.md.
VercelAGENTS.mdvercel/next.js/evals/next-upgrade/evals/future-cache-components-nudge/AGENTS.md
Do not push or create pull requests. Use npm.
VercelAGENTS.mdvercel/next.js/evals/next-upgrade/evals/latest-nudge/AGENTS.md
You may edit this application. Do not push or create pull requests. Use npm. Preserve the behavior described in the user prompt.
VercelAGENTS.mdvercel/next.js/.github/AGENTS.md
Set permissions: {} at the workflow level and grant the minimum needed per-job. Prefer GitHub-provided (actions/*) and Vercel-owned actions. For third-party actions: ${{ ... }} is interpolated into the script before bash runs, so untrusted values (PR title, branch name, issue body) can break out and execute. Route them through an env var and quote on use:
VercelAGENTS.mdvercel/next.js/packages/next/AGENTS.md
This version has breaking changes — APIs, conventions, and file structure may all differ from your training data. Read the relevant guide in dist/docs/ before writing any code. Heed deprecation notices.
VercelSkillvercel/next.js/skills/next-cache-components-adoption/SKILL.md
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the `cacheComponents` flag, work through a flood of blocking-prerender / instant validation errors, run the `cache-components-instant-false` codemod, or decide between opting routes out with `export const instant = false` and fixing them in place.
VercelSkillvercel/next.js/skills/next-dev-loop/SKILL.md
Verify Next.js runtime behavior after editing app code. Use this skill to confirm a change actually works in a running app — not just that it compiles or type-checks. Combines /_next/mcp (Next.js's view) with agent-browser (the browser's view). Requires a running `next dev`.
VercelSkillvercel/next.js/skills/next-partial-prefetching-adoption/SKILL.md
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the `partialPrefetching` flag, opt routes in with `export const prefetch = 'partial'`, audit `Link prefetch={true}` behavior, preserve existing prefetched UI with `instant()` tests, or resolve the instant-link-prefetch-partial and instant-shell-url-data insights.
VercelSkillvercel/next.js/skills/next-partial-prefetching-optimizer/SKILL.md
Optimize what selected Next.js client navigations include before the click under Partial Prefetching. Use after Cache Components and Partial Prefetching are adopted when the user wants selected URL-specific UI to be instant, wants reusable content to wait for navigation, or needs to choose between default, viewport, and intent prefetching. Requires Next.js 16.3+.
VercelAGENTS.mdvercel/next.js/test/AGENTS.md
No summary in the file. Open it to read it.
VercelAGENTS.mdvercel/next.js/turbopack/AGENTS.md
Turbopack is a general-purpose bundler that is built and designed for Next.js, but is not necessarily Next.js-specific. Keep Next.js concepts out of it.
GitHubAGENTS.mdgithub/spec-kit/AGENTS.md
GitHub Spec Kit is a comprehensive toolkit for implementing Spec-Driven Development (SDD) - a methodology that emphasizes creating clear specifications before implementation. The toolkit includes templates, scripts, and workflows that guide development teams through a structured approach to building software. Specify CLI is the command-line interface that bootstraps projects with the Spec Kit framework. It sets up the necessary directory structures, templates, and AI agent integrations to support the Spec-Driven Development workflow. The toolkit supports multiple AI coding assistants, allowing…
GitHubSkillgithub/spec-kit/.github/skills/add-community-extension/SKILL.md
Add a community extension to the Spec Kit catalog from a GitHub issue submission. USE FOR: processing extension submission issues, validating catalog entries, updating catalog.community.json and docs/community/extensions.md, creating PRs. DO NOT USE FOR: creating new extensions from scratch, or first-party extension work.
GitHubSkillgithub/spec-kit/.github/skills/code-review/SKILL.md
Reviews Spec Kit code changes for positive and negative test coverage, regression evidence for bug fixes, and consistent repository terminology. Use when reviewing a diff or pull request. Do not use for implementing changes or posting GitHub review actions.
MicrosoftAGENTS.mdmicrosoft/PowerToys/AGENTS.md
Top-level AI contributor guidance for developing PowerToys - a collection of Windows productivity utilities
MicrosoftCLAUDE.mdmicrosoft/PowerToys/.claude/CLAUDE.md
../.github/copilot-instructions.md
MicrosoftCopilot instructionsmicrosoft/PowerToys/.github/copilot-instructions.md
PowerToys AI contributor guidance
MicrosoftSkillmicrosoft/PowerToys/.github/skills/powertoys-verification/SKILL.md
Verify PowerToys behavior end-to-end with the winapp CLI across two scenarios: (A) a module's release checklist against the installed build; (B) PR validation — derive each PR's checklist from its description + diff, then drive it against the installed build (a merged/shipped PR, or a whole release/hotfix set) or by building + sideloading the module when the PR isn't in the build yet (unmerged or not-yet-released). Drive each item via UIA invoke / Named Events / settings.json edits / clipboard / GPO / SendInput, and emit a structured PASS / FAIL / BLOCKED verdict per item with evidence (FAIL distinguishes product defects from stale/ambiguous checklist items). Use when asked to verify a module checklist, validate a PR, sign off a release/hotfix's PRs, or QA installed/sideloaded PowerToys bits. Combines generic winapp ui mechanics (references/winapp-ui-testing.md) with PT-specific recipes, per-scenario playbooks (references/scenarios/), and the helper .ps1 files shipped with this skill.
MicrosoftSkillmicrosoft/PowerToys/.github/skills/release-note-generation/SKILL.md
Toolkit for generating PowerToys stable or preview release notes from GitHub milestones, commit ranges, or Azure DevOps release-candidate builds. Use when asked to create release notes, summarize milestone PRs, generate changelog, prepare a draft preview release, calculate PR deltas across main and stable, update release documentation, manage PR milestones, or prepare and validate release assets.
MicrosoftSkillmicrosoft/PowerToys/.github/skills/ui-tests-local-vm/SKILL.md
Run PowerToys UITest.Next suites in persistent Hyper-V VMs over PowerShell Direct. Validate full default and constrained suites on Windows 10 and Windows 11, plus applicable ARM64 guests, then automatically hand implementation tasks to ui-tests-pipeline-ci for commit/push and CI validation. Local green is not end-to-end completion. Use for agentic UI-test iteration, reusable standard-user desktops, payload staging, evidence export, VM customization, clean baselines, or hosts without nested virtualization. Keywords: Hyper-V, local VM, virtual machine, PowerShell Direct, Copy-VMFile, VMBus, checkpoint, unattend, autounattend, ISO, Windows 10 LTSC, Windows 11, ARM64, Windows on ARM, UI tests, UITest.Next, winappcli, TRX, CI handoff.
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.
