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.
MicrosoftCopilot instructionsmicrosoft/pict/.github/copilot-instructions.md
code patterns and conventions 3. **Test**: Add comprehensive test cases with edge cases 4. **Document**: Update both code comments and user documentation 5. **Validate**: Test on multiple platforms and with
OfficeDevCopilot instructionsOfficeDev/Microsoft-Teams-Samples/.github/copilot-instructions.md
practices. --- ## Development Priority Guidelines ### 1. **Teams-First Approach** - Always reference Microsoft Teams samples and documentation first. - Prioritize Teams Platform APIs over generic Bot Framework patterns. - Use Teams-specific terminology
Gu1llaum-3Copilot instructionsGu1llaum-3/sshm/.github/copilot-instructions.md
m.cursor > 0 { m.cursor-- } case key.Matches(msg, keys.Down): if m.cursor < len(m.items)-1 { m.cursor++ } } ``` --- ## 16) Documentation & Comments * Exported types/functions must have a sentence GoDoc. * At the top of each file, include
justrachCopilot instructionsjustrach/codedb/.github/copilot-instructions.md
tests minimal — only exercise the specific broken code path ### Code Style - No comments or documentation changes unless explicitly asked - Prefer minimal, targeted fixes over refactors - Follow existing patterns
nasirkhanCopilot instructionsnasirkhan/laravel-starter/.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
se2pCopilot instructionsse2p/pynguin/.github/copilot-instructions.md
Project architecture and codebase structure - AI Agent Development Guidelines (code quality, testing, restrictions) - Module documentation and navigation - Code Quality standards, testing requirements, and restrictions If you read this file
HalFrgrdCopilot instructionsHalFrgrd/flyline/.github/copilot-instructions.md
Prefer `anyhow::Result` for fallible functions. - Keep `unsafe` blocks as small as possible and document why each one is necessary. - Do not introduce new dependencies without a clear justification; check
bitfoundationCopilot instructionsbitfoundation/bitplatform/.github/copilot-instructions.md
sample_search` tools of the `bitplatform` MCP server to search Microsoft's latest official documentation for detailed and up-to-date information before responding to specific or narrowly defined questions
reatomCopilot instructionsreatom/reatom/.github/copilot-instructions.md
must add a test that reproduces the bug. - New features must be tested and documented. - Use `@ts-expect-error` for known false positives; `@ts-ignore` only for errors
MicrosoftDocsCopilot instructionsMicrosoftDocs/sql-docs/.github/copilot-instructions.md
These instructions define a unified style and process standard for authoring and maintaining learn.microsoft.com documentation with GitHub Copilot or other AI assistance. ## Learn-wide Instructions Below are instructions that apply
PropertyToolsCopilot instructionsPropertyTools/PropertyTools/.github/copilot-instructions.md
SelectedColor`, `UndefinedColor`) - **Parameters and Local Variables** - Use camelCase (e.g., `color`, `alpha`, `targetType`) 4. **XML Documentation** - Use XML documentation comments (`///`) for public APIs - Include ` `, ` `, and ` ` tags as appropriate - Example: ```csharp /// /// Change
datalayerCopilot instructionsdatalayer/jupyter-mcp-server/.github/copilot-instructions.md
uses a modern Python build system with hatch, and includes comprehensive testing, linting, and documentation. ## Working Effectively ### Environment Setup - **Python Requirements**: Python 3.10 or higher (tested with 3.9-3.13) - **Network
Steady2 mentions in 2 weeks
No other project uses it yet
Capsize-GamesCopilot instructionsCapsize-Games/airunner/.github/copilot-instructions.md
Validate user-controlled file paths with the service file policy in `services/src/airunner_services/runtimes/file_policy.py` and related document-access helpers. - Keep app-managed data under the configured runtime/data layout. Preserve private permissions
SupabaseCopilot instructionssupabase/supabase-swift/.github/copilot-instructions.md
supabase-swift ## Instructions for Code Review - Check for breaking API changes - Check if documentation is up to date - Check if examples are up to date - Check if tests are comprehensive
Steady8 mentions in 2 weeks
No other project uses it yet
mozillazgCopilot instructionsmozillazg/ptcpdump/.github/copilot-instructions.md
test` to validate 5. Add E2E test script in `testdata/` if needed 6. Update documentation in README.md if user-facing ### Fixing a Bug 1. Reproduce the issue
strapiCopilot instructionsstrapi/documentation/.github/copilot-instructions.md
Copilot Instructions This is the Strapi documentation repository (Docusaurus 3, docs.strapi.io). Full agent guidance, conventions, and project rules are in [`AGENTS.md`](../AGENTS.md). ## Quick reference - **Stack**: JavaScript/Node only — no new languages
MicrosoftCopilot instructionsmicrosoft/CSS-Exchange/.github/copilot-instructions.md
Variables in PascalCase pass spell-checking; inconsistency fails the spell check. ### Comments and Documentation - Use `#` for single-line comments - Use `<# #>` for block comments (especially for complex logic) - Use `.SYNOPSIS`, `.DESCRIPTION
micasa-devCopilot instructionsmicasa-dev/micasa/.github/copilot-instructions.md
seeding, backup, full-text search config/ TOML config with env var overrides (MICASA_*) extract/ Document extraction pipeline (text -> OCR -> LLM) llm/ LLM client wrapper and SQL prompts locale/ Currency formatting
No other project uses it yet
MicrosoftCopilot instructionsmicrosoft/griffel/.github/copilot-instructions.md
Linting takes 15-30 seconds. Set timeout to 60+ seconds. ``` ### Development Servers ```bash # Start documentation website (Docusaurus) yarn start # Serves on http://localhost:3000 # NEVER CANCEL: Initial build takes
brenocqCopilot instructionsbrenocq/implot3d/.github/copilot-instructions.md
already be implemented in ImPlot. Before implementing a new feature, check the ImPlot documentation and codebase to see if it can be adapted for ImPlot3D. 4. **Focus on 3D Plotting
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.
