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.
ardalisCopilot instructionsardalis/CleanArchitecture/.github/copilot-instructions.md
coding) - **Domain Level**: Business invariants throw exceptions, assume pre-validated input ## Essential Commands ### Build & Test ```bash dotnet build Clean.Architecture.slnx dotnet test Clean.Architecture.slnx ``` ### Entity Framework Migrations ```bash # From Web project directory
No other project uses it yet
dotnetCopilot instructionsdotnet/runtime/.github/copilot-instructions.md
anything touching behavior, codegen, or a public contract gets the build and the relevant tests before you call it done. A comment or doc fix rarely needs a build, though
No other project uses it yet
labringCopilot instructionslabring/sealos/.github/copilot-instructions.md
downloads that may fail in restricted environments. Document as "network-dependent" if install fails. ### Testing and Validation #### Unit Tests (limited due to environment requirements) ```bash cd lifecycle go test ./pkg/utils
No other project uses it yet
sweetalert2Copilot instructionssweetalert2/sweetalert2/.github/copilot-instructions.md
Setup commands - Install deps: `bun install` - Start dev server: `bun run dev` - Run tests: `bun run test` ## Code style - TypeScript strict mode - Single quotes, no semicolons - Use functional patterns where
No other project uses it yet
MicrosoftCopilot instructionsmicrosoft/react-native-windows/.github/copilot-instructions.md
React Native runtime - **JavaScript/TypeScript tooling** for development experience - **Sample applications** and test suites - **Documentation** and build tools ### Key Architecture Components - **Paper Architecture** (legacy): UWP XAML-based renderer - **Fabric Architecture
No other project uses it yet
vitest-devCopilot instructionsvitest-dev/vitest/.github/copilot-instructions.md
when working with code in this repository. ## Codebase Overview Vitest is a next-generation testing framework powered by Vite. This is a monorepo using pnpm workspaces. ## Essential references - Agent-specific
No other project uses it yet
koelCopilot instructionskoel/koel/.github/copilot-instructions.md
writing a new one. ## Verification Scripts - Do not create verification scripts or tinker when tests cover that functionality and prove it works. Unit and feature tests are more important. ## Application
Steady2 mentions in 2 weeks
No other project uses it yet
cephDeletes or force-pushesCopilot instructionsceph/ceph/.github/copilot-instructions.md
main codebase - follows Google C++ Style Guide with modifications) - Python 3 (management tools, tests) - CMake (build system using Ninja) - Bash (scripts and utilities) **Key Components:** - **MON (Monitor)**: Cluster membership
No other project uses it yet
zephyrproject-rtosCopilot instructionszephyrproject-rtos/zephyr/.github/copilot-instructions.md
violation with the rule, a bug with the input that triggers it, a missing test with the untested behavior. Skip praise and summaries. - Do not request changes for anything
No other project uses it yet
triggerdotdevCopilot instructionstriggerdotdev/trigger.dev/.github/copilot-instructions.md
prefer using isomorphic code like fetch, ReadableStream, etc. instead of Node.js specific code. Our tests are all vitest. We use prisma in internal-packages/database for our database interactions using
Steady7 mentions in 2 weeks
No other project uses it yet
ast-grepCopilot instructionsast-grep/ast-grep/.github/copilot-instructions.md
build: `cargo build --release` - takes 2m 26s. **NEVER CANCEL.** Set timeout to 180+ seconds. - Test suite: `cargo test` - takes 48 seconds, runs 94+ tests. **NEVER CANCEL.** Set timeout
No other project uses it yet
alshedivatCopilot instructionsalshedivat/al-folio/.github/copilot-instructions.md
starter, not a theme**. It owns starter wiring (`Gemfile`, `_config.yml`), example content, docs, integration tests, and visual parity tests. All runtime — layouts, includes, Sass, Liquid tags, filters, feature JS — lives
Steady2 mentions in 2 weeks
No other project uses it yet
MaterialDesignInXAMLCopilot instructionsMaterialDesignInXAML/MaterialDesignInXamlToolkit/.github/copilot-instructions.md
Visual Studio Code** with C# extension - **PowerShell** - For build scripts ### Build and Test ```powershell # Restore dependencies dotnet restore MaterialDesignToolkit.Full.slnx # Build (requires Windows) dotnet build MaterialDesignToolkit.Full.slnx --configuration Release --no-restore
Steady11 mentions in 2 weeks
No other project uses it yet
tracel-aiCopilot instructionstracel-ai/burn/.github/copilot-instructions.md
architecture, and conventions. 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
Steady2 mentions in 2 weeks
No other project uses it yet
mikefarahCopilot instructionsmikefarah/yq/.github/copilot-instructions.md
name working, warn on stderr, document, remove in a later major release). ## Tests as a compatibility signal 1. **Modified expectations.** Explicitly call out any PR that updates, loosens, skips
Steady3 mentions in 2 weeks
No other project uses it yet
beetboxCopilot instructionsbeetbox/beets/.github/copilot-instructions.md
trick" - Prefer readable code over clever one-liners: name intermediate variables, easier debug - Integration tests are sweet spot — not unit tests (break on refactor), not e2e (hard debug) - When
Steady2 mentions in 2 weeks
No other project uses it yet
scylladbCopilot instructionsscylladb/scylladb/.github/copilot-instructions.md
recommended for development (fastest compilation) # Build Scylla binary only (sufficient for Python integration tests) ninja build/ /scylla # Build specific test ninja build/ /test/boost/ ``` ### Using frozen toolchain (Docker) Prefix any build
No other project uses it yet
AgriciDanielCopilot instructionsAgriciDaniel/claude-obsidian/.github/copilot-instructions.md
lint/query read-only. - Preserve vault path containment and product/vault separation. - Add hermetic regression tests for behavior changes and run `make test`. - Do not add secrets, private paths, unsupported capability claims
No other project uses it yet
MicrosoftCopilot instructionsmicrosoft/pyright/.github/copilot-instructions.md
drafts; the coordinator owns the final assessment and explicitly authorized publication. ## Build and Test ```bash # Install all packages (from repo root) pnpm install # Build the core library cd packages/pyright-internal && pnpm
No other project uses it yet
zitadelCopilot instructionszitadel/zitadel/.github/copilot-instructions.md
schema and generation guidance. - `packages/AGENTS.md`: Shared client/proto package workflows. - `tests/functional-ui/AGENTS.md`: Cypress functional UI test workflows. - `deploy/compose/AGENTS.md`: Docker Compose deployment invariants, file conventions, and rejected alternatives. ## Behavior - Before Go-related work
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.
