teams.ts
microsoft/teams.ts/AGENTS.md
No summary in the file. Open it to read it.
How real projects brief Codex, Cursor and every other agent that reads AGENTS.md.
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.
microsoft/teams.ts/AGENTS.md
No summary in the file. Open it to read it.
microsoft/Microsoft-AI-Decision-Framework/.github/AGENTS.md
This file tells AI coding assistants (Codex CLI, GitHub Copilot, Cursor, etc.) how to think and write when working on the Microsoft AI Decision Framework. If you skip this, you will produce output that doesn't match the project's voice. That matters more here than in most repos. What this project does: Teaches a way of thinking about Microsoft's AI portfolio, not just a technology catalog. It uses mental models, analogies, and narrative arcs to help architects and builders make evidence-based…
microsoft/agentic-agile-template/AGENTS.md
Universal agent entry point. Any agent reading this repository cold starts here. This file is both orientation reference and onboarding orchestrator. This repository is built on the Agentic-Agile Template — a starter framework for teams adopting structured human-agent collaboration. It provides the process layer that makes agent partnerships repeatable: structured backlogs, spec-first stories, platform adapter context files, built-in governance, and continuous measurement. This file (AGENTS.md) is the single canonical entry point for all AI coding agents. Read it completely before…
microsoft/scope/website/AGENTS.md
Project context for AI coding agents working on scope-doc, the Starlight-based documentation site for Scope. A static documentation site published to GitHub Pages, within the microsoft/scope monorepo. - Framework: Astro 6.x + @astrojs/starlight - Package manager: pnpm (pinned via packageManager in package.json) - TypeScript strict - Lives under the website/ directory of the repo (all site sources, config, and package.json are rooted here; run every command from website/ unless explicitly directed to the repository root). The site has its own…
microsoft/vscode-azureresourcegroups/AGENTS.md
For implementation, testing, and review rules, read .github/copilot-instructions.md. This map identifies code ownership, not additional product requirements. Start with the narrowest affected route. package.json contribution -> src/extension.ts / command registration -> handler or API adapter -> resource/subscription service or branch provider -> tree refresh, activity/output, or webview -> test. - Azure Resources supplies the shared Azure sign-in/subscription path used by consuming extensions. src/extension.ts -> getSubscriptionProviderFactory.ts -> Resources' VSCodeAzureSubscriptionProvider.ts -> @microsoft/vscode-azext-azureauth -> vscode.authentication -> VS Code's built-in Microsoft Authentication provider (microsoft,…
microsoft/power-cat-skills/AGENTS.md
A plugin marketplace for Power CAT development by Microsoft. The marketplace manifest (.claude-plugin/marketplace.json) references individual plugins in plugins/. Each plugin has its own AGENTS.md with plugin-specific guidance.
microsoft/power-cat-skills/plugins/powercat-admin-digest/AGENTS.md
This file provides guidance to AI Agents when working with the powercat-admin-digest plugin. A plugin for Power Platform admins and partner SAs that produces a production-impact digest by synthesizing Message Center notices, Service Health incidents, Known Issues, and deprecations from the user's M365 mailbox and public Microsoft sources. Default output is customer-shareable (Tier 1 + Tier 2 only); Tier 3 (NDA / Microsoft-internal) content is stripped unless the user explicitly asks for the internal variant. Skills delegate .docx / .pptx…
microsoft/power-cat-skills/plugins/powercat-adoption/AGENTS.md
This file provides guidance to AI Agents when working with the powercat-adoption plugin. A plugin for Power Platform adoption storytelling. It helps Microsoft field teams, partners, and customer success professionals turn raw customer stories into polished, on-brand presentation assets — without design tools or build steps. Skills orchestrate specialist agents via the Task tool. Agents are not invoked directly by users. Test this plugin locally: Drop in a customer name (and optionally a story source — public case study, internal…
microsoft/power-cat-skills/plugins/powercat-architecture-advisor/AGENTS.md
A plugin that emulates a Power CAT Solution Architect discovery and recommendation process. It collects scenario requirements through a structured questionnaire and outputs a comprehensive Power Platform architecture recommendation with explicit design decisions and risks. Test this plugin locally:
microsoft/power-cat-skills/plugins/powercat-canvas-apps/AGENTS.md
This file provides guidance to AI Agents when working with the powercat-canvas-apps plugin. A plugin for authoring Power Apps Canvas Apps. The Canvas Authoring MCP server (CanvasAuthoringMcpServer) exposes tools that agents use to generate, validate, and compile Canvas App YAML files (.pa.yaml) in conjunction with a running coauthoring studio session. The Power Apps Studio browser tab must remain open for the duration of the session — closing it ends the coauthoring session, which breaks compile_canvas and sync_canvas operations. Skills orchestrate…
microsoft/power-cat-skills/plugins/powercat-code-apps/AGENTS.md
This file provides guidance to AI Agents when working with the powercat-code-apps plugin. A plugin for generating brand-aligned design guides for Power Apps code apps. It extracts brand tokens (colours, typography, spacing, layout patterns) from customer-provided assets and produces a design-guide.md that is consumed by the code-apps plugin (/create-code-app) to scaffold and build the app. Skills orchestrate specialist agents via the Task tool. Agents are not invoked directly by users. Test this plugin locally: The code-apps plugin from the official…
microsoft/power-cat-skills/plugins/powercat-dataverse/AGENTS.md
This file provides guidance to AI Agents when working with the powercat-dataverse plugin. A plugin for authoring and troubleshooting Microsoft Dataverse queries. It helps developers, makers, and architects write correct Web API URLs, convert FetchXML, target the right Power Apps surface, and diagnose common errors — without falling into the recurring traps that cause 90% of Dataverse Web API support threads. Skills orchestrate specialist agents via the Task tool. Agents are not invoked directly by users. Test this plugin locally:
microsoft/power-cat-skills/plugins/powercat-governance/AGENTS.md
This file provides guidance to AI Agents when working with the powercat-governance plugin. A plugin for Power Platform governance and administration. It helps Power Platform admins provision and manage environments consistently — replacing multi-step manual admin center workflows with a single prompt while enforcing organizational governance defaults. Skills orchestrate specialist agents via the Task tool. Agents are not invoked directly by users. Test this plugin locally: Spin up a fully-configured Power Platform Developer environment for any teammate in under 2…
microsoft/power-cat-skills/plugins/powercat-overflow/AGENTS.md
This file provides guidance to AI Agents when working with the powercat-overflow plugin. A plugin for Power Platform makers, ALM owners, and CoE reviewers that audits every Power Automate cloud flow inside a Power Platform solution .zip against Microsoft's published coding guidelines. The skill unpacks the solution, walks each flow, classifies findings by impact (low / medium / high), writes a single [SolutionName].findings.json next to the uploaded ZIP, and opens the hosted PowerCAT-Overflow viewer (<https://microsoft.github.io/power-cat-skills/PowerCAT-Overflow.html>) with both the solution and…
microsoft/power-cat-skills/plugins/powercat-overpage/AGENTS.md
This file provides guidance to AI Agents when working with the powercat-overpage plugin. A plugin for Power Pages makers, ALM owners, and CoE reviewers that audits a Power Pages site export (.zip produced by pac powerpages download, zipped) against Power Pages best practices across Security, Accessibility, Performance, Maintainability, SEO and Reliability. The agent unpacks the export, reads and reasons about the pages, templates, settings, web files and table permissions, writes a single [SolutionName].findings.json (validated against findings.schema.json) next to the uploaded…
microsoft/power-cat-skills/plugins/powercat-pcf/AGENTS.md
This plugin authors virtual Power Apps Component Framework controls for model-driven apps. There is no plugin build step: the deliverables are skill instructions and reference documentation. Validate JSON metadata, skill frontmatter, resource links, and marketplace registration when editing this plugin. Write references independently from official documentation, cite the relevant sources, and distinguish platform guarantees from project policies. Do not borrow third-party skill text, examples, or organization. Generated PCF projects must use their own build, lint, and tests plus verification in…
microsoft/accordant/agent/AGENTS.md
This project uses Accordant — a model-based testing framework for .NET. Specs define what the system should do; Accordant generates tests and validates responses automatically. When the user asks about Accordant, read the relevant skill before answering:
microsoft/accordant/Microsoft.Accordant.Cli/Templates/AGENTS.md
This project uses Accordant for model-based testing. Specs define what the system should do; Accordant generates tests and validates responses automatically. When the user asks about Accordant, read the relevant skill before answering: Skills are installed at {{SkillsPath}}.
microsoft/winget-studio/AGENTS.md
Follow .github/copilot-instructions.md for repository-specific development guidance. Before filing a GitHub issue in this repository: Before opening a pull request:
microsoft/vscode-team-kit/AGENTS.md
Each top-level directory containing a plugin.json is an Agent Plugins 1.0 package. Plugins are self-contained. Do not add legacy manifests or compatibility paths. The canonical manifest schema is closed. Keep categories, status, maintainers, and evals only in marketplace.json. The manifest's optional extensions field is an object keyed by client namespace, never a component path. SDK canvas extensions use the fixed com.github.copilot/extensions/ directory; manifest settings cannot redirect discovery. Use Copilot's native hook contract: version: 1, camelCase lifecycle keys such as preToolUse…
An open format for instructions to coding agents, read by Codex, Cursor and others. Think of it as a README written for agents.
At the repository root, with more specific files in subdirectories. Agents read the one closest to the file they're editing.
Setup and test commands, code style, and the rules a new contributor would need to know.
Claude Code reads CLAUDE.md. A one-line CLAUDE.md that points at AGENTS.md covers both.