How real projects brief GitHub Copilot, from .github/copilot-instructions.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.
simulotCopilot instructionssimulot/immich-go/.github/copilot-instructions.md
design. don't update the code if not explicitly requested Don't write reasoning documentation except is this is explicitly requested. Write it in the scratchpad folder. When implementing
No other project uses it yet
elementorCopilot instructionselementor/elementor/.github/copilot-instructions.md
plugin. ## Quick Reference ### Core Rules (Apply to ALL code) 1. **No Comments** - Write self-documenting code 2. **No Magic Numbers** - Use named constants for values except
Steady4 mentions in 2 weeks
No other project uses it yet
HaxeFoundationCopilot instructionsHaxeFoundation/haxe/.github/copilot-instructions.md
tabs for indentation (as seen in existing files) - Keep functions focused and modular - Document complex algorithms or non-obvious logic ### Haxe Code (Standard Library & Tests) - Use tabs for indentation - Follow
No other project uses it yet
MicrosoftCopilot instructionsmicrosoft/GSL/.github/copilot-instructions.md
small and focused with clear preconditions/postconditions - Include comments for complex code, but prefer self-documenting code - Use the Expects() and Ensures() macros for contract verification ### Style Guidelines - Use 4 spaces
No other project uses it yet
AethersailorCopilot instructionsAethersailor/Custom_OpenClash_Rules/.github/copilot-instructions.md
actual diff. 2. Identify the primary intentional change. 3. Distinguish: * behavior changes from documentation changes; * source files from generated files; * manual changes from automated refreshes; * implementation changes from accompanying tests
No other project uses it yet
rizonesoftCopilot instructionsrizonesoft/Notepad3/.github/copilot-instructions.md
auto-loaded MRU). Runtime toggle never auto-pastes. Preserve this asymmetry. - `Settings2.PasteBoardSeparator`: `\x01` = one document EOL; `\0` = none; else verbatim. Also suppressed on first paste after enable and when caret
No other project uses it yet
pardeikeCopilot instructionspardeike/Harmony/.github/copilot-instructions.md
version features. - do not add obvious comments. - when adding new methods, provide docfx documentation. - respect .editorconfig (for example, tab instead of spaces). For editing .github/actions or .github/workflows: - make sure
No other project uses it yet
MicrosoftCopilot instructionsmicrosoft/vscode-docs/.github/copilot-instructions.md
Code Docs Writing Guidelines Follow the [documentation writing guidelines](instructions/docs-writing.instructions.md) when reviewing or writing documentation
No other project uses it yet
CodeWithCJReads credentialsCopilot instructionsCodeWithCJ/SparkyFitness/.github/copilot-instructions.md
entry**: `SparkyFitnessServer/SparkyFitnessServer.js` (route registration, middleware setup) - **Frontend entry**: `src/App.tsx` (context providers, query client setup) - **Documentation site**: `docs/` - Comprehensive Nuxt Content documentation (https://codewithcj.github.io/SparkyFitness) ## Documentation Structure ### Developer Documentation The developer
Steady18 mentions in 2 weeks
No other project uses it yet
doxygenCopilot instructionsdoxygen/doxygen/.github/copilot-instructions.md
Instructions for Doxygen ## Project Overview Doxygen is the de facto standard tool for generating documentation from annotated source code. It supports C++, C, Objective-C, C#, PHP, Java, Python
No other project uses it yet
open-telemetryCopilot instructionsopen-telemetry/opentelemetry-go/.github/copilot-instructions.md
update benchmarks for performance-sensitive changes. - Follow [CONTRIBUTING.md Design Choices](../CONTRIBUTING.md#design-choices). ## Documentation and repository conventions - Non-internal, non-test packages should have Go doc comments, usually in `doc.go
No other project uses it yet
MicrosoftCopilot instructionsmicrosoft/rushstack/.github/copilot-instructions.md
Execute operations affecting the entire repository or multiple projects - Features: - Strict parameter validation and documentation - Support for global and batch commands - Suitable for standardized workflows - Use cases: Dependency installation, building
No other project uses it yet
MicrosoftCopilot instructionsmicrosoft/agent-governance-toolkit/.github/copilot-instructions.md
consistent but externally unverifiable claims (IETF drafts, NIST submissions, patent filings), projects with elaborate documentation but no real users, landing pages with "design partner" CTAs for projects created days
No other project uses it yet
devloopedReads credentialsCopilot instructionsdevlooped/moq/.github/copilot-instructions.md
must pass on all target frameworks - Follow existing patterns and conventions in the codebase ## Documenting Work Project implemention details, design and key decisions should be documented in a top-level
Steady25 mentions in 2 weeks
No other project uses it yet
rundeckCopilot instructionsrundeck/rundeck/.github/copilot-instructions.md
should be applied: # Product Naming Guidelines Always use the correct product names in descriptions, documentation, and API specifications: - **Open Source Product**: "Rundeck" - **Commercial Product**: "Runbook Automation" - **Combined Reference**: "Rundeck / Runbook
Steady2 mentions in 2 weeks
No other project uses it yet
FlorianBruniauxCopilot instructionsFlorianBruniaux/claude-code-ultimate-guide/.github/copilot-instructions.md
CHANGELOG.md` under `[Unreleased]` for any file modifications. - Keep changes minimal and aligned with existing documentation style
1 project uses a version of this
Microsoft AzureCopilot instructionsAzure/Azure-Sentinel/.github/copilot-instructions.md
Analyzer/` in the current branch - This is the normal case when developing/testing - **Never generate documentation here** 2. **Output worktree (publishing CSVs):** `C:\Users\ofshezaf\GitHub\Azure-Sentinel-solution-analyzer-output
No other project uses it yet
Microsoft AzureCopilot instructionsAzure/Azure-Sentinel/Tools/Microsoft-Sentinel-Classic-CLv1-Tables-Impact-Assessment/.github/copilot-instructions.md
github/workflows/update-solution-mapping.yml # Weekly GitHub Action to refresh mapping data LICENSE # MIT License README.md # Full project documentation ``` ## Architecture ### Single-script design The entire tool is a single PowerShell script (`Invoke-TableMigrationReview
No other project uses it yet
open-edge-platformCopilot instructionsopen-edge-platform/anomalib/.github/copilot-instructions.md
config from root project) - `tests/` — unit and integration tests (`tests/unit/`, `tests/integration/`) - `docs/` — Sphinx documentation under `docs/source/` - `.agents/skills/` — detailed review policy per topic (authoritative reference) For `src/anomalib/`, architectural rules are strict
No other project uses it yet
graphql-javaCopilot instructionsgraphql-java/graphql-java/.github/copilot-instructions.md
Flag any breaking changes in public APIs so we can call this out in documentation
No other project uses it yet
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.
