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.
MicrosoftCopilot instructionsmicrosoft/microsoft-ui-xaml/src/.github/copilot-instructions.md
For detailed instructions on building and testing, see the skills defined in .github/skills/: - .github/skills/build/SKILL.md - Build commands and file-to-project mappings
MicrosoftSkillmicrosoft/microsoft-ui-xaml/src/.github/skills/bt-build/SKILL.md
Fast incremental C++/MSBuild builds using bt. Use when the user wants to compile, build, check what's dirty, or query build dependencies in a repo that has .vcxproj files. Prefer bt over invoking MSBuild directly for inner-loop source changes (.cpp, .h, .idl, .xaml, .appxmanifest).
MicrosoftSkillmicrosoft/microsoft-ui-xaml/src/.github/skills/test-suite-setup/SKILL.md
Complete end-to-end setup and execution of the WinUI3 test suite locally. Delegates building to the build skill, then handles test payload creation, machine setup, and running all tests.
MicrosoftAGENTS.mdmicrosoft/Mastering-GitHub-Copilot-for-Paired-Programming/AGENTS.md
This is Mastering GitHub Copilot for Paired Programming, an open-source educational repository maintained by Microsoft. It is a multi-module, 10-hour course that teaches developers how to use GitHub Copilot as an AI coding partner — from beginner to advanced topics including Agent Mode. The repository is documentation-centric: most content is Markdown-based lesson guides. A small number of code samples exist within specific lessons. Each lesson module follows a consistent structure: Most exercises reference external Codespaces template repos (e.g., github/dotnet-codespaces) rather…
MicrosoftCopilot instructionsmicrosoft/TinyTroupe/.github/copilot-instructions.md
This document provides the primary guidelines for generating programs in the TinyTroupe project. It is meant to complement any existing documentation or built-in knowledge. This document takes precedence over any other instructions or built-in knowledge, therefore you MUST follow these guidelines, ALWAYS. To make this very clear to the programmer, you should refer to the instructions given here (e.g.," ... as per my primary guidelines, I will avoid a complex solution to this problem, unless you explicitly ask me to…
MicrosoftCopilot instructionsmicrosoft/GSL/.github/copilot-instructions.md
No summary in the file. Open it to read it.
MicrosoftCopilot instructionsmicrosoft/vscode-docs/blogs/2025/03/.github/copilot-instructions.md
This project is a web application that allows users to create and manage tasks. The application is built using React and Node.js, and it uses MongoDB as the database.
MicrosoftAGENTS.mdmicrosoft/vscode-docs/docs/agents/concepts/agents.md
An agent is an AI system that uses a language model and tools to complete a goal on your behalf. A language model generates responses based on the information in…
MicrosoftCopilot instructionsmicrosoft/vscode-docs/.github/copilot-instructions.md
Follow the documentation writing guidelines when reviewing or writing documentation.
MicrosoftSkillmicrosoft/vscode-docs/.github/skills/blog-writer/SKILL.md
Plan, write, and review VS Code blog posts. ALWAYS use this skill when the user asks to "write a blog post", "draft a blog", "add a blog post for", "review this blog post", or provides a feature/issue/PR to announce on the VS Code blog. For new posts, it proposes an outline and asks clarifying questions first, and does not edit any files until you approve the plan.
MicrosoftSkillmicrosoft/vscode-docs/.github/skills/content-redirect/SKILL.md
Create and manage redirects in VS Code documentation when pages are moved, renamed, or deleted. Use when moving docs pages, renaming files, restructuring content, or when the user asks about redirects.
MicrosoftSkillmicrosoft/vscode-docs/.github/skills/daily-docs-audit/SKILL.md
Audit recently merged microsoft/vscode pull requests for documentation impact, stage deduplicated issue proposals, and create confirmed issues in microsoft/vscode-docs. ALWAYS use this skill when asked to run or configure a daily docs audit, identify documentation work from merged VS Code PRs, review pending docs issue proposals, or create docs issues for product updates.
MicrosoftSkillmicrosoft/vscode-docs/.github/skills/docs-product-alignment/SKILL.md
Audit and update docs/copilot/ documentation to accurately reflect current VS Code AI capabilities. Use when: competitive analysis reveals gaps, product launches new features, docs use outdated framing, or keyword coverage needs strengthening for discoverability by users and AI agents. Produces a gap analysis plus targeted edits across affected files.
MicrosoftSkillmicrosoft/vscode-docs/.github/skills/doc-writer/SKILL.md
Plan and write VS Code documentation for a new or updated feature. ALWAYS use this skill when the user asks to "document", "add docs for", "write docs for", or "update the docs for" a feature, or provides a GitHub issue/PR link to document — even if the change seems small. Proposes a documentation plan and asks clarifying questions first — it does not edit any files until you approve the plan.
MicrosoftSkillmicrosoft/vscode-docs/.github/skills/frontmatter-description/SKILL.md
Check and optimize MetaDescription frontmatter fields in VS Code documentation. Use when auditing, adding, or improving page descriptions for SEO and discoverability. Apply this when making content changes to markdown articles.
MicrosoftSkillmicrosoft/vscode-docs/.github/skills/pr-review/SKILL.md
Verify the technical accuracy of a vscode-docs pull request against the VS Code source code in microsoft/vscode and microsoft/vscode-copilot-chat. Use when reviewing a docs PR for factual correctness — setting names, command IDs, default values, API shapes, keybindings, versioned availability, and described behavior.
MicrosoftSkillmicrosoft/vscode-docs/.github/skills/release-note-writer/SKILL.md
Guidelines for writing and reviewing Insiders and Stable release notes for Visual Studio Code. This also includes instructions for updating release notes for recovery releases.
MicrosoftSkillmicrosoft/vscode-docs/.github/skills/review-agent-corrections/SKILL.md
Review locally captured corrections to agent edits and propose reusable repository guidance. Use when asked to review agent corrections, learn from feedback, inspect pending correction events, or improve future agent edits from prior feedback.
MicrosoftSkillmicrosoft/vscode-docs/.github/skills/write-my-release-notes/SKILL.md
Generate VS Code release notes for the features you worked on in a milestone. ALWAYS use this skill when the user asks to "write release notes for my features", "document my milestone features", or "generate release notes from my issues". It gathers the milestone features you own from GitHub, analyzes each feature and its related issues, and writes user-focused feature sections into the milestone release notes file.
MicrosoftAGENTS.mdmicrosoft/rushstack/build-tests/rushd-wire-e2e-test/AGENTS.md
This package is governed by an ultra-strict lint policy for generated code. All of the rules below are enabled to error in eslint.config.js via the shared local-node-rig/profiles/default/includes/eslint/flat/mixins/strict-codegen.js mixin. They apply…
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.
