How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
MicrosoftCopilot instructionsmicrosoft/PowerToys/src/modules/cmdpal/ExtensionTemplate/TemplateCmdPalExtension/.github/copilot-instructions.md
commands - Pages are **ICommand** implementations — they can be used anywhere commands are used - Always **Deploy** (not just Build) to register the MSIX package - After deploying, use the **Reload** command
MicrosoftCopilot instructionsmicrosoft/autogen/.github/copilot-instructions.md
applications and complex multi-agent workflows with support for various LLM providers, tools, and deployment patterns
aaif-gooseCopilot instructionsaaif-goose/goose/.github/copilot-instructions.md
Updates with Code Changes - PRs with code changes shouldn't update `/documentation` - docs deploy on merge, code on release. Use `unlisted: true` or remove/hide docs. ## Project-Specific Context - This
MicrosoftCopilot instructionsmicrosoft/WSL/.github/copilot-instructions.md
TAEF framework) - `test/linux/unit_tests/` — Linux unit test suite - `doc/` — Documentation source (MkDocs) - `tools/` — Build and deployment scripts - `distributions/` — Distribution validation and metadata - `localization/` — Localized string resources ### Namespace → Directory Map | Namespace | Location
MicrosoftCopilot instructionsmicrosoft/winget-cli/.github/copilot-instructions.md
uses: - MSBuild - vcpkg for C++ dependencies - NuGet for C++ and .NET dependencies ### Running/Debugging 1. Deploy solution: Build > Deploy Solution 2. Run from command line: `wingetdev` 3. For debugging: - Right-click
open-metadataCopilot instructionsopen-metadata/OpenMetadata/.github/copilot-instructions.md
production - Database migrations are automatically applied on startup - HTTPS is required for production deployments ## UI Pull Request Review Guidelines **IMPORTANT: When reviewing UI pull requests, you MUST follow the comprehensive
MicrosoftCopilot instructionsmicrosoft/agent-framework/.github/copilot-instructions.md
GitHub Copilot Instructions Microsoft Agent Framework - a multi-language framework for building, orchestrating, and deploying AI agents. ## Repository Structure - `python/` - Python implementation → see [python/AGENTS.md](../python/AGENTS.md) - `dotnet/` - C#/.NET implementation
MicrosoftCopilot instructionsmicrosoft/fluentui-system-icons/.github/copilot-instructions.md
importer/generateFont.js` (Regular/Filled/Light/Resizable) feeding React font condition and Flutter/iOS/Android. - Native (Android/iOS/Flutter): Produced by `importer` deployment scripts (`deploy:android`, `deploy:ios`, `deploy:flutter`) which transform assets into vector drawables / PDF assets / Dart
MicrosoftCopilot instructionsmicrosoft/rushstack/.github/copilot-instructions.md
global`: Global commands, executed once for the entire repository ```json { "commandKind": "global", "name": "deploy", "summary": "Deploy application", "shellCommand": "node common/scripts/deploy.js" } ``` - Parameter types: ```json "parameters": [ { "parameterKind": "flag", // Switch parameter --production "longName
MicrosoftCopilot instructionsmicrosoft/agent-governance-toolkit/.github/copilot-instructions.md
fast-track. - **Verify claims**: If the PR cites benchmarks, adoption numbers, or production deployments, spot-check them. Unverifiable claims are a red flag. - **Scope proportionality**: A small or unknown project
Microsoft AzureCopilot instructionsAzure/Azure-Sentinel/Tools/Microsoft-Sentinel-Classic-CLv1-Tables-Impact-Assessment/.github/copilot-instructions.md
dependencies beyond `Az.Accounts`. All helper functions are defined inline. This is intentional — it keeps deployment simple (copy one file). ### Execution flow 1. **Authenticate** — Validates `Az.Accounts` context, refreshes ARM bearer token
geekjourneyxCopilot instructionsgeekjourneyx/md2wechat-skill/.github/copilot-instructions.md
prove semantic markers/stable content with no raw fence; local validation alone is not remote deployment proof. The 4 `serves` values that every module is mapped to: `attention` | `readability` | `memorability` | `conversion
MicrosoftCopilot instructionsmicrosoft/WinUI-Gallery/.github/copilot-instructions.md
controls, theming, input handling) - **[microsoft/WindowsAppSDK](https://github.com/microsoft/WindowsAppSDK)** — Windows App SDK (app lifecycle, windowing, deployment) - **[microsoft/WindowsAppSDK-Samples](https://github.com/microsoft/WindowsAppSDK-Samples)** — Official samples demonstrating Windows App SDK features - **[microsoft/ai-dev-gallery](https://github.com/microsoft/ai-dev-gallery)**
MicrosoftCopilot instructionsmicrosoft/skills/.github/copilot-instructions.md
credential ) ``` ### Environment Variables ```bash AZURE_AI_PROJECT_ENDPOINT=https:// .services.ai.azure.com/api/projects/ AZURE_AI_MODEL_DEPLOYMENT_NAME=gpt-4o-mini ``` --- ## Conventions ### Code Style - Prefer `async/await` for all Azure
Microsoft AzureCopilot instructionsAzure/AKS/.github/copilot-instructions.md
node**: Lowercase. A worker machine in Kubernetes (physical or virtual). **pod**: Lowercase. The smallest deployable unit in Kubernetes, containing one or more containers. **container**: Lowercase. A lightweight, standalone executable package
Microsoft AzureCopilot instructionsAzure/iotedge/.github/copilot-instructions.md
with three main components: - **Edge Agent** (`edge-agent/`) — C# service that manages module lifecycle, deployments, and desired-state reconciliation via IoT Hub twin - **Edge Hub** (`edge-hub/`) — C# service acting
MicrosoftCopilot instructionsmicrosoft/pict/.github/copilot-instructions.md
MSBuild - **Cross-platform**: CMake (minimum version 3.13) - **Unix/Linux**: Traditional Makefile - **Container**: Containerfile for containerized deployment ## Coding Standards & Conventions ### Language & Standards - **C++17** standard required (set via `CMAKE_CXX_STANDARD`) - Cross
MicrosoftCopilot instructionsmicrosoft/gctoolkit/.github/copilot-instructions.md
channel classes - Implement proper lifecycle management (open/close) - Use Vert.x deployVerticle for async operations - Handle deployment IDs for proper cleanup ### Error Handling - Use java.util.logging.Logger for logging - Log warnings/errors with proper context
datalayerCopilot instructionsdatalayer/jupyter-mcp-server/.github/copilot-instructions.md
jupyter lab \ --port 8888 \ --ip 0.0.0.0 \ --ServerApp.root_dir ./dev/content \ --IdentityProvider.token MY_TOKEN ``` #### Docker Deployment ```bash # Build Docker image (NEVER CANCEL: Build takes 10-15 minutes) make build-docker # Takes
Microsoft AzureCopilot instructionsAzure/GPT-RAG/.github/copilot-instructions.md
noise to operators. Use generic phrasing instead: "a validation environment", "a fresh Basic deployment", or "the validation resource group". Region names (`swedencentral`, `francecentral`) and feature flags (`NETWORK_ISOLATION=false`, `BUILD
Repository-wide instructions for GitHub Copilot, kept in .github/copilot-instructions.md.
How to build and test, the project's structure, and the conventions Copilot should follow in suggestions and reviews.
No. Copilot's coding agent also reads AGENTS.md, so many projects keep the shared rules there.
Open a file to see its discussion. Reports from people and their agents are coming.
