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.
dotnetCopilot instructionsdotnet/maui-samples/.github/workflows/instructions/copilot-instructions.md
applyTo: '**' --- # GitHub Copilot Development Environment Instructions This document provides specific guidance for GitHub Copilot when working on the .NET MAUI Samples repository. It serves as context for understanding the project
Myriad-DreaminCopilot instructionsMyriad-Dreamin/tinymist/.github/copilot-instructions.md
Specification.md](editors/neovim/Specification.md)) - `tools/editor-tools`: utility GUI tools for typst - `tools/typst-preview-frontend`: Preview GUI for typst - `docs/`: documentation for the project - `locales/`: localization files for the entire project - `tests/`: integration tests
Steady8 mentions in 2 weeks
No other project uses it yet
DetachHeadCopilot instructionsDetachHead/basedpyright/.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
No other project uses it yet
pgmodelerCopilot instructionspgmodeler/pgmodeler/.github/copilot-instructions.md
initialization MyClass::MyClass() : is_protected(false), system_obj(false), code_invalidated(true) { // constructor code } ``` ## Documentation and Comments ### Doxygen Headers ```cpp /** \ingroup libcore \brief Implements operations to manipulate database tables. \note
crmneCopilot instructionscrmne/zapfast/.github/copilot-instructions.md
implementation limits. Missing features, codec restrictions, and download limits are not permanent exclusions. When documentation conflicts with the code, flag the stale claim instead of using it to reject supported
tvheadendCopilot instructionstvheadend/tvheadend/.github/copilot-instructions.md
Makefile.common) - Configure system: `configure` script (uses support/configure.inc) - Web UI build: `Makefile.webui` (builds compressed JS/CSS) - Documentation build: Converts markdown docs to C code during build - Build output directory: `build.linux/` (contains tvheadend
No other project uses it yet
agavraCopilot instructionsagavra/tuicr/.github/copilot-instructions.md
Plain `gh pr diff` returns the cumulative diff. ### Updating docs after user-facing changes | Document | Update when… | |---|---| | `README.md` | Keybindings, `:*` commands, CLI flags, features, installation | | `src/ui/help_popup.rs` | Keybindings or commands (update `help
No other project uses it yet
fluentmigratorCopilot instructionsfluentmigrator/fluentmigrator/.github/copilot-instructions.md
Guidelines for contributing to FluentMigrator - a database migration framework for .NET
BelphemurCopilot instructionsBelphemur/SoundSwitch/.github/copilot-instructions.md
tasks and recurring operations ## Development Guidelines ### Coding Standards 1. Classes should use proper XML documentation 2. Follow C# naming conventions (PascalCase for public members, camelCase for private) 3. Extract interfaces
lakehqCopilot instructionslakehq/sail/.github/copilot-instructions.md
protocol implementation. - `sail-sql-*`: Sail SQL parser and analyzer. - `sail-telemetry`: OpenTelemetry integration. - `docs/`: Documentation site built with VitePress. - `python/`: Source code for the `pysail` Python package. - `scripts/`: Various scripts
wikimediaCopilot instructionswikimedia/wikipedia-ios/.github/copilot-instructions.md
suppress concurrency warnings with `@preconcurrency` or `nonisolated(unsafe)` unless absolutely necessary and documented with a comment explaining why if possible. - Prefer `async`/`await` over completion handlers for all new asynchronous
delta-ioCopilot instructionsdelta-io/delta-rs/.github/copilot-instructions.md
Public API docs: new public structs, enums, functions, and non-obvious members need documentation in the crate's style, and names should be self-explanatory without abbreviations. - Error handling
pesterCopilot instructionspester/Pester/.github/copilot-instructions.md
next to the code with `[Diagnostics.CodeAnalysis.SuppressMessageAttribute('Pester.BuildAnalyzerRules\ ', ' ', Justification = '...')]`, matching the existing suppressions in `src/`. ## Documentation - Documentation is written in Markdown; update it when behavior changes. - Use fenced code blocks
apacheCopilot instructionsapache/gravitino/.github/copilot-instructions.md
test classes (e.g., `TestMetalake`). - **Dependencies**: Do NOT add new dependencies without explicit user request. - **Documentation**: JavaDoc is required for all public APIs. ## Language Specifics - **Java**: - Use `@Nullable` for optional fields/params
TanStackCopilot instructionsTanStack/ai/.github/instructions/copilot-instructions.md
there's a strong reason to introduce breaking changes. If breaking changes are necessary, document them clearly in the relevant documentation files. Under no circumstances should casting
Steady7 mentions in 2 weeks
No other project uses it yet
serverpodCopilot instructionsserverpod/serverpod/.github/copilot-instructions.md
format ` : ` 4. **Complete checklists**: Mark appropriate items in the pre-launch checklist 5. **Document breaking changes**: Always fill in the breaking changes section if applicable ### PR Template Enforcement - **Never create
Steady3 mentions in 2 weeks
No other project uses it yet
stellarCopilot instructionsstellar/stellar-core/.github/copilot-instructions.md
other simple text search tools when seeking information about the codebase. Especially use `lsp_document_symbols` for an overview of any given file
music-assistantCopilot instructionsmusic-assistant/server/.github/copilot-instructions.md
Actionable feedback, not observations. One sentence where one sentence does the job. On documentation or user-facing text, flag wording only when it's genuinely confusing or could mislead someone
Steady7 mentions in 2 weeks
No other project uses it yet
FluidInferenceCopilot instructionsFluidInference/FluidAudio/.github/copilot-instructions.md
types - Error handling: Use proper Swift error handling, no force unwrapping in production - Documentation: Triple-slash comments (`///`) for public APIs - Thread safety: Use actors, `@MainActor`, or proper locking - never `@unchecked
Steady22 mentions in 2 weeks
No other project uses it yet
MicrosoftCopilot instructionsmicrosoft/litebox/.github/copilot-instructions.md
affects public interfaces. - Extremely simple changes do not require explicit unit tests. 5. Document all public APIs and non-trivial implementation details. 6. Avoid introducing new dependencies unless strictly necessary
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.
