How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
a1st-devCopilot instructionsa1st-dev/aix/.github/copilot-instructions.md
comparison details. ### Brand Personality Clear, concise, helpful. ### Aesthetic Direction Keep the documentation product-like and trustworthy rather than flashy. The pages should feel structured, scannable, and calm, with obvious hierarchy
Microsoft AzureCopilot instructionsAzure/FederalAVD/.github/copilot-instructions.md
customer/artifacts/ before use parameters/ ← reference parameter files; copy to customer/parameters/ before use docs/ ← all documentation deployments/shared/modules/orchestration/sessionHostPolicy/ ← Canonical session-host policy definitions, initiatives, assignments, and nested templates tools/ ← utility scripts ``` --- ## Common
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.
