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.
koelCopilot instructionskoel/koel/.github/copilot-instructions.md
concise in your explanations - focus on what's important rather than explaining obvious details. ## Documentation Files - You must only create documentation files if explicitly requested by the user. === boost rules
No other project uses it yet
cephDeletes or force-pushesCopilot instructionsceph/ceph/.github/copilot-instructions.md
Build and utility scripts │ └── vstart.sh # Development cluster script ├── qa/ # Integration test suites (teuthology) ├── doc/ # Documentation (RST format) ├── cmake/ # CMake modules ├── build/ # Build directory (created by do_cmake.sh) ├── CMakeLists.txt # Root CMake configuration
No other project uses it yet
opfCopilot instructionsopf/openproject/.github/copilot-instructions.md
Extended Details #### Service Objects and Result Modeling - Return results using the `ServiceResult` class (well-documented in codebase) - Some services use monads via [dry-monads](https://github.com/dry-rb/dry-monads) for result modeling
Steady6 mentions in 2 weeks
No other project uses it yet
MaterialDesignInXAMLCopilot instructionsMaterialDesignInXAML/MaterialDesignInXamlToolkit/.github/copilot-instructions.md
Only expose what's necessary - **Consistent naming** - Follow WPF and Material Design conventions - **Proper documentation** - XML docs for all public APIs - **Designer support** - Ensure controls work well in Visual Studio
Steady12 mentions in 2 weeks
No other project uses it yet
tracel-aiCopilot instructionstracel-ai/burn/.github/copilot-instructions.md
These notes cover review. ## Priorities Report correctness problems first, then missing test coverage, then documentation that contradicts the code. For correctness findings, identify a failing input or configuration
Steady9 mentions in 2 weeks
No other project uses it yet
scylladbCopilot instructionsscylladb/scylladb/.github/copilot-instructions.md
Python tests ## Code Philosophy - Performance matters in hot paths (data read/write, inner loops) - Self-documenting code through clear naming - Comments explain "why", not "what" - Prefer standard library over custom implementations
No other project uses it yet
MicrosoftCopilot instructionsmicrosoft/pyright/.github/copilot-instructions.md
unreachableCode, deprecated)`. - Sample `.py` files use comments like `# This should generate an error` to document expected diagnostics, but the actual assertion is the count passed to `validateResults`. **Fourslash tests** (`src/tests/fourslash
KoenkkCopilot instructionsKoenkk/zigbee2mqtt/.github/copilot-instructions.md
messages (device names, IEEE addresses, etc.) ## Code Quality Standards ### Maintainability - Write self-documenting code with clear, descriptive names - Keep methods focused on single responsibilities - Abstract classes should define clear contracts
No other project uses it yet
zitadelCopilot instructionszitadel/zitadel/.github/copilot-instructions.md
orchestration targets. - `apps/login/AGENTS.md`: Specifics for the Next.js Login UI. - `apps/docs/AGENTS.md`: Specifics for the Fumadocs documentation. - `console/AGENTS.md`: Specifics for the Angular Console. - `internal/AGENTS.md`: Backend domain and event-sourcing boundaries. - `proto/AGENTS.md
No other project uses it yet
SubtitleEditCopilot instructionsSubtitleEdit/subtitleedit/.github/copilot-instructions.md
this repository, apply the project guidance in `.github/skills/subtitleedit-ai-contributor-guidelines/SKILL.md` for code changes, reviews, refactors, and documentation updates. Keep AI-assisted changes small, verified, and tied directly to the requested issue
Steady3 mentions in 2 weeks
No other project uses it yet
dotnetCopilot instructionsdotnet/efcore/.github/copilot-instructions.md
Types under `.Internal` or marked `[EntityFrameworkInternal]` must use the repository's internal-API XML documentation pattern on all members and they don't need to preserve compatibility. - User-facing messages
Steady2 mentions in 2 weeks
No other project uses it yet
MicrosoftCopilot instructionsmicrosoft/agent-framework/.github/copilot-instructions.md
Python implementation → see [python/AGENTS.md](../python/AGENTS.md) - `dotnet/` - C#/.NET implementation → see [dotnet/AGENTS.md](../dotnet/AGENTS.md) - `docs/` - Design documents and architectural decision records - `skills/` - Public, installable Agent Skills for developers using Agent Framework ## Public
abpframeworkCopilot instructionsabpframework/abp/.github/copilot-instructions.md
TKey>`. - Pass cancellation tokens using `GetCancellationToken(cancellationToken)`. - Ignore `includeDetails` for MongoDB in most cases (documents load sub-collections). - Prefer `GetQueryableAsync()` to ensure ABP data filters are applied. --- ## ABP Module Classes
No other project uses it yet
semaphoreuiCopilot instructionssemaphoreui/semaphore/.github/copilot-instructions.md
golangci-lint if needed: `go install github.com/golangci/golangci-lint/cmd/golangci-lint@v1.57.2` ## Common Tasks ### Repository Structure ``` . ├── README.md - Project documentation ├── CONTRIBUTING.md - Development guidelines ├── Taskfile.yml - Task runner configuration ├── go.mod - Go module dependencies ├── web/ - Vue.js frontend application
No other project uses it yet
Open-LLM-VTuberCopilot instructionsOpen-LLM-VTuber/Open-LLM-VTuber/.github/copilot-instructions.md
integrated into the `frontend/` directory of this backend repository via a git submodule. - Documentation Repository: The official documentation site is hosted in the `open-llm-vtuber.github.io` repository. When asked to generate documentation
Steady5 mentions in 2 weeks
No other project uses it yet
RaspberryPiFoundationCopilot instructionsRaspberryPiFoundation/blockly/.github/copilot-instructions.md
Code review guidelines Repository layout, commands, and coding conventions are documented in [`AGENTS.md`](../AGENTS.md) and the per-package `AGENTS.md` files under `packages/`. Read those for context; this file covers only
No other project uses it yet
debeziumCopilot instructionsdebezium/debezium/.github/copilot-instructions.md
BEFORE you do ANYTHING ELSE, ALWAYS refer to the AGENTS.md document for complete guidelines
Steady4 mentions in 2 weeks
No other project uses it yet
InsForgeCopilot instructionsInsForge/InsForge/.github/copilot-instructions.md
/functions`: Serverless function runtime - `/shared-schemas`: Shared TypeScript schemas - `/docker-init`: Docker initialization scripts - `/openapi`: API documentation in OpenAPI format - `/tests`: Comprehensive test suites ## Libraries and Frameworks ### Backend - Express.js for REST
Steady7 mentions in 2 weeks
No other project uses it yet
dotnetCopilot instructionsdotnet/AspNetCore.Docs/.github/copilot-instructions.md
author: tdykstra ms.author: wpickett ms.date: 08/25/2026 --- # Copilot Instructions for `dotnet/AspNetCore.Docs` ## Introduction This document contains general and repository-specific instructions for GitHub Copilot when assisting with the `dotnet/AspNetCore.Docs` repository. **Unless otherwise
Steady5 mentions in 2 weeks
No other project uses it yet
MicrosoftCopilot instructionsmicrosoft/windows-rs/.github/copilot-instructions.md
rather than the workspace's unified features. Canvas tests use WARP rendering. - **Reactor test documentation**: Keep testing instructions in `crates/tests/libs/reactor/readme.md`, not the library README. `cargo test -p test-reactor` must
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.
