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.
MicrosoftCLAUDE.mdmicrosoft/FluidFramework/server/gitrest/CLAUDE.md
GitRest provides a REST API to Git repositories, modeled after GitHub's REST APIs. It is part of the Fluid Framework server infrastructure. Endpoints follow the GitHub API pattern:
MicrosoftCLAUDE.mdmicrosoft/FluidFramework/server/historian/CLAUDE.md
Historian is a service that tracks the historical record for a Fluid document. It acts as a proxy to the underlying git repository that maintains versioned snapshots. This is a release group root with two packages: Runtime config is in packages/historian/config.json and loaded via nconf.
MicrosoftAGENTS.mdmicrosoft/fluentui-blazor/AGENTS.md
This file provides context and instructions for AI coding agents working on the Microsoft Fluent UI Blazor components library. This is a .NET Blazor component library that provides Fluent UI design system components for Blazor applications. The library wraps Microsoft's official Fluent UI Web Components and provides additional components leveraging the Fluent Design System. Unit tests are in tests/Core/Components/ mirroring the component structure in src/Core/Components/. Follow Conventional Commits:
Steady10 mentions in 2 weeks
No other project uses it yet
MicrosoftSkillmicrosoft/fluentui-blazor/examples/Demo/FluentUI.Demo.Client/wwwroot/skills/fluentui-blazor-usage/SKILL.md
Provides accurate coding patterns for building Blazor applications with the Microsoft.FluentUI.AspNetCore.Components v5 NuGet package. Covers service registration, theming (CSS-based, no FluentDesignTheme), layout, navigation, dialogs, data grid, forms, icons, and common pitfalls.
Steady10 mentions in 2 weeks
No other project uses it yet
MicrosoftCopilot instructionsmicrosoft/fluentui-blazor/.github/copilot-instructions.md
No summary in the file. Open it to read it.
Steady10 mentions in 2 weeks
No other project uses it yet
MicrosoftSkillmicrosoft/fluentui-blazor/.github/skills/csharp-naming-conventions/SKILL.md
C# and .NET naming conventions, coding best practices, layout rules, unit testing, and Blazor component guidelines. Use when writing, reviewing, or refactoring C# / .NET / Blazor code or writing unit tests with xUnit and bUnit.
Steady10 mentions in 2 weeks
No other project uses it yet
MicrosoftSkillmicrosoft/fluentui-blazor/.github/skills/update-dependencies/SKILL.md
Update repository NuGet and NPM dependencies and lockfiles to the latest compatible versions, then validate library builds and bUnit tests. Use when asked to update or upgrade repository dependencies.
Steady10 mentions in 2 weeks
20 projects use a version of this
MicrosoftCopilot instructionsmicrosoft/PyRIT/.github/copilot-instructions.md
PyRIT (Python Risk Identification Tool for generative AI) is an open-source framework for security professionals to proactively identify risks in generative AI systems. PyRIT uses a modular pluggable-brick design. doc/code/framework.md is the canonical reference for how these pieces fit together. It defines each component's responsibilities — what it owns and, critically, what it does not own — and how scenarios, attack techniques, executors, and the core/shared layers relate. Read it before adding or reviewing components so new code lands in…
MicrosoftCopilot instructionsmicrosoft/msquic/.github/copilot-instructions.md
MsQuic is Microsoft's cross-platform C implementation of the IETF QUIC protocol. It also has C++ API wrappers and Rust/C# interop layers. The codebase targets Windows (user & kernel mode), Linux, macOS, and FreeBSD. The primary language is C (C17), with C++ (C17) for tests/tools, Rust bindings, and C# interop. Build system: CMake + PowerShell scripts. Key files: CMakeLists.txt (root build), version.json (version info), .clang-format (C/C++ style), src/.editorconfig (editor settings), Cargo.toml (Rust crate config), rust-toolchain.toml (Rust 1.93.1). Always use PowerShell 7+…
MicrosoftSkillmicrosoft/msquic/.github/skills/cherry-pick-to-release/SKILL.md
Cherry-pick a merged main-branch PR onto a MsQuic release branch (release/X.Y).
MicrosoftSkillmicrosoft/msquic/.github/skills/investigate-ci-failure/SKILL.md
Guide systematic investigation of MsQuic CI test failures reported by GitHub Actions.
MicrosoftCopilot instructionsmicrosoft/perfview/.github/copilot-instructions.md
PerfView is a Windows performance-analysis tool for investigating CPU and memory issues, built on the TraceEvent library for parsing ETW and EventPipe trace data. The solution (PerfView.sln) contains the WPF GUI application, the cross-platform TraceEvent library, and several supporting libraries. Follow existing patterns — when in doubt, match the surrounding code.
No other project uses it yet
MicrosoftAGENTS.mdmicrosoft/WindowsAppSDK/AGENTS.md
Comprehensive guidance for AI contributions to the Windows App SDK. The SDK follows this organization: For C#/C++/IDL files: For XAML files:
MicrosoftAGENTS.mdmicrosoft/WindowsAppSDK/dev/Templates/Dotnet/templates/blank-app/AGENTS.md
This is a WinUI 3 app built with the Windows App SDK. The WinApp CLI handles the Windows-specific parts of app development. Install it with: A sample of the commands it provides: Prefer these over hand-rolled scripts for packaging, signing, and UI verification. 1. From the project directory, run dotnet build and fix any build errors. 2. Launch with dotnet run. Keep the app running and use another terminal for UI verification. 3. Run winapp ui inspect -a <app> --interactive,…
MicrosoftAGENTS.mdmicrosoft/WindowsAppSDK/dev/Templates/Dotnet/templates/reactor-blank-app/AGENTS.md
This is a WinUI 3 app built with Microsoft.UI.Reactor and the Windows App SDK. The UI is declared in pure C# — there is no XAML in this project, so don't add .xaml files or convert components to XAML. The WinApp CLI handles the Windows-specific parts of app development. Install it with: A sample of the commands it provides: Prefer these over hand-rolled scripts for packaging, signing, and UI verification. 1. From the project directory, run dotnet build and fix…
MicrosoftCopilot instructionsmicrosoft/WindowsAppSDK/.github/copilot-instructions.md
Windows App SDK AI contributor guidance
MicrosoftSkillmicrosoft/WindowsAppSDK/.github/skills/issue-triage-report/SKILL.md
Generate comprehensive GitHub Feature Area Status reports for the Windows App SDK repository. Use when asked to create triage reports, identify high-priority issues, analyze feature area health, find issues needing attention, or generate status dashboards. Triggers on requests involving issue triage, area status, priority analysis, bug tracking reports, or engineering team focus areas.
MicrosoftSkillmicrosoft/WindowsAppSDK/.github/skills/triage-meeting-prep/SKILL.md
Prepare weekly triage meeting summary for WinAppSDK Needs-Triage issues. Use when preparing for triage meetings, reviewing Needs-Triage issues, generating diff reports since last triage, summarizing new or updated issues, or creating action item recommendations. Triggers on requests involving triage preparation, Needs-Triage review, meeting summary, triage diff, or weekly issue analysis.
MicrosoftSkillmicrosoft/WindowsAppSDK/.github/skills/worktree-manager/SKILL.md
Create and manage Git worktrees for parallel development workflows. Use when multiple self-contained issues should NOT be fixed in a single branch, when human-Copilot iteration requires isolated environments with separate chat history and commits, or when parallel work items need independent build/test results. Triggers on requests involving branch isolation, work item separation, parallel development, or avoiding messy branch switching.
MicrosoftSkillmicrosoft/flint-chart/agent-skills/flint-board-author/SKILL.md
Use when: several Flint charts should be read together in one view: a dashboard, KPI tiles over a trend, a side-by-side comparison, an overview with its detail; or a board on screen should change (add, retitle, resize, reconnect a chart). Produce one board spec whose headline, chart choice, layout and connected fields are decided, check and refine it with validate_board, then put it on screen once with show.
Steady3 mentions in 2 weeks
No other project uses it yet
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.
