MicrosoftSkillusing-skills
microsoft/FluidFramework/.agency/plugins/nori/skills/using-skills/SKILL.md
Describes how to use abilities. Read before any conversation.
Find the best CLAUDE.md, AGENTS.md and Claude skills
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.
Most stars first · from page 33Worked for most · soon
MicrosoftSkillMicrosoftSkillwebapp-testing
microsoft/FluidFramework/.agency/plugins/nori/skills/webapp-testing/SKILL.md
Use this skill to build features or debug anything that uses a webapp frontend.
MicrosoftSkillwriting-plans
microsoft/FluidFramework/.agency/plugins/nori/skills/writing-plans/SKILL.md
Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps assuming engineer has minimal domain knowledge
MicrosoftCopilot instructionsFluidFramework / build-tools
microsoft/FluidFramework/build-tools/.github/copilot-instructions.md
This is the build-tools release group for the Fluid Framework monorepo. It contains CLI tools and libraries for building, testing, releasing, and managing Fluid Framework repositories. For release documentation, use conventional commits, not changesets. Runtime: Node.js >=22.22.2, pnpm 11.27.0 Language: TypeScript ~5.4.5 Module system: Mix of CommonJS and ESM (see DEV.md for constraints) **Always run from build-tools/ directory. Install dependencies first if node_modules/ doesn't exist.** Packages have workspace dependencies and must build in order: 1. version-tools (no internal deps) 2.…
MicrosoftCLAUDE.mdFluidFramework
microsoft/FluidFramework/.claude/CLAUDE.md
This file is mirrored in .github/copilot-instructions.md. Changes here should be duplicated there, and vice versa. Follow the Coding Guidelines when writing / modifying code. Follow the Documentation Guidelines when writing or modifying code or documentation. Read and follow the linked guides relevant to the task, including the language-specific guides for source-code documentation. These requirements apply to source-code comments and API documentation as well as standalone documentation. Add a changeset for user-facing changes only if the affected release group uses changesets.…
MicrosoftSkillapi-changes
microsoft/FluidFramework/.claude/skills/api-changes/SKILL.md
Use when customer-facing API changes were made — i.e., API report .md files differ from the branch's resolved comparison base. Guides through release tag assignment, API Council review requirements, breaking change classification, deprecation process, and changeset guidance. Triggered automatically by ci-readiness-check when api-report diffs are detected.
MicrosoftSkillci-readiness-check
microsoft/FluidFramework/.claude/skills/ci-readiness-check/SKILL.md
Use when the user explicitly asks for a CI check or to push their branch — e.g. "ci readiness", "check ci", "pre-push check", "ready for CI", "ci check", "ready to push", "push my changes", "push the branch", "let's push". Catches common CI failures before pushing — formatting, stale API reports, missing changesets, policy violations.
MicrosoftSkillcomparison-base
microsoft/FluidFramework/.claude/skills/comparison-base/SKILL.md
Internal reusable workflow for resolving the correct Git comparison base for branch reviews and change analysis. Finds the PR target or canonical Fluid Framework upstream, selects the newest shared target-history commit, and detects substantial divergence.
MicrosoftSkillfluid-pr-guide
microsoft/FluidFramework/.claude/skills/fluid-pr-guide/SKILL.md
Use when composing, writing, drafting, or reviewing a PR title, PR description, or PR body in Fluid Framework — provides title style, body template, and section guidance.
MicrosoftSkillfluid-pr
microsoft/FluidFramework/.claude/skills/fluid-pr/SKILL.md
Use when creating a pull request in the Fluid Framework repo. Composes a PR title and body following Fluid Framework conventions, proposes them to the user, then pushes the branch and creates the PR on GitHub. Triggers on "create a PR", "make a PR", "open a PR", "submit a PR", or "push and create a PR".
MicrosoftSkillfluid-release
microsoft/FluidFramework/.claude/skills/fluid-release/SKILL.md
Fluid Framework client release group — minor releases, patch releases, and post-release type test updates. Covers release prep, branching, version bumps, changelogs, release notes, and type test baselines. In autonomous mode, auto-detects state from the schedule and repo, attempts to execute, and falls back to a GitHub issue on failure. Triggers on "release", "do the release", "release status", version bump, release notes, changelog, release branch, or release engineering.
MicrosoftSkillpipeline-test-triage
microsoft/FluidFramework/.claude/skills/pipeline-test-triage/SKILL.md
Triage test failures in an Azure DevOps pipeline run for Fluid Framework. Use when the user shares an ADO build/pipeline URL or build ID and wants failures analyzed, when they ask "why did this pipeline fail", "summarize the test failures", "is this test flaky or a real bug", "compare these runs", or wants bugs filed for genuine failures. Covers the Real Service End to End Tests pipeline as the worked example but applies to any FF test pipeline.
MicrosoftSkillpolicy-check
microsoft/FluidFramework/.claude/skills/policy-check/SKILL.md
This skill should be used when the user asks to "run policy check", "check policy", "policy-check", or needs to validate package compliance. Provides guidance on running policy checks for specific packages or the entire repository.
MicrosoftSkillreview-pr-local
microsoft/FluidFramework/.claude/skills/review-pr-local/SKILL.md
The authority on pulling a pull request — Azure DevOps or GitHub — into an isolated local worktree so a human can review it in their editor, and on posting human-controlled review comments back to the PR (ADO via the ado PR-thread MCP tools or the Azure DevOps REST API, GitHub via the gh CLI). Auto-detects the platform and all identifiers from the PR URL; not tied to any specific repository. The AI assists an interactive human review and only ever posts comments the human explicitly requests. If you find yourself checking out a PR branch over the user's own working tree, or posting AI-authored review prose the human did not ask for, invoke this skill instead.
MicrosoftSkillreview
microsoft/FluidFramework/.claude/skills/review/SKILL.md
Review changes relative to a prior state, such as a diff, pull request, branch, commit, or working-tree changes. Use for change-focused code review and regression analysis. Do not use to assess an existing file, API, design, implementation, or other artifact without a comparison; if the request is ambiguous, ask whether the user wants a change review and what prior state to compare against.
MicrosoftCopilot instructionsFluidFramework
microsoft/FluidFramework/.github/copilot-instructions.md
This file is mirrored in .claude/CLAUDE.md. Changes here should be duplicated there, and vice versa. Follow the Coding Guidelines when writing / modifying code. Follow the Documentation Guidelines when writing or modifying code or documentation. Read and follow the linked guides relevant to the task, including the language-specific guides for source-code documentation. These requirements apply to source-code comments and API documentation as well as standalone documentation. Add a changeset for user-facing changes only if the affected release group uses changesets.…
MicrosoftCLAUDE.mdFluidFramework / gitrest
microsoft/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.mdFluidFramework / historian
microsoft/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.mdfluentui-blazor
microsoft/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:
MicrosoftSkillFluent UI Blazor v5 — Usage Guide
microsoft/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.
Agent instruction files
What are agent instruction files?
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 or AGENTS.md?
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.
What is a skill?
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.
Can I search my own team's files too?
Your agents already can, over MCP, limited to the files you're allowed to read. Searching them from this page is coming.