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.
nobiyouCopilot instructionsnobiyou/wx_channel/.github/copilot-instructions.md
config changes take effect immediately. Some require restart or manual handler reload. ## Documentation Resources - **Architecture**: `dev-docs/DOCUMENTATION.md` - **API Endpoints**: `dev-docs/api_documentation.md` - **Fix History**: `dev-docs/FIX_HISTORY.md` (reference
flightphpCopilot instructionsflightphp/core/.github/copilot-instructions.md
bloating the core library. - Any new features built into the core should be well-documented and tested. - Any new features should be added with a focus on simplicity and performance
arminkCopilot instructionsarmink/FlashDB/.github/copilot-instructions.md
suggest changes** | | `tests/*_tc.c` | utest cases, executed by CI under QEMU | | `docs/` | docsify documentation, `docs/zh-cn` is the Chinese edition | ## Conventions - C99, 4-space indent, no tabs; functions use Allman braces
MicrosoftCopilot instructionsmicrosoft/DirectXTK/.github/copilot-instructions.md
ASCII characters in source files. HLSL files have separate indent/spacing rules defined in `.editorconfig`. - **Documentation**: The project provides documentation in the form of wiki pages available at [Documentation](https://github.com
dataplatCopilot instructionsdataplat/dbatools/.github/copilot-instructions.md
test file 4. Added new test cases for pattern matching scenarios 5. Updated documentation strings 6. Fixed minor formatting issues ## Detailed Changes by File ### public/Get-DbaDatabase.ps1 - Line 45: Added Pattern parameter
tkemCopilot instructionstkem/cachetools/.github/copilot-instructions.md
every item. `LFUCache` ties discard the least recently used key (documented since 7.3), so check it against a model. - Whatever could not be verified must show up: mark the finding
habitat-shCopilot instructionshabitat-sh/habitat/.github/copilot-instructions.md
tests in `tests/` directory - Mock external dependencies - Test both success and failure cases 3. **Documentation**: - Add rustdoc comments for public APIs - Update relevant markdown documentation - Include examples in documentation when
unpollerCopilot instructionsunpoller/unpoller/.github/copilot-instructions.md
Follow existing plugin patterns 2. Keep core library generic 3. Check all errors 4. Document exported functions 5. Write tests in `_test` packages 6. Consider cross-platform compatibility
Steady11 mentions in 2 weeks
No other project uses it yet
intelCopilot instructionsintel/neural-compressor/.github/copilot-instructions.md
Applies to all Python files except `examples/`, `neural_compressor/torch/algorithms/fp8_quant/`, and `test/torch/`. ## Docstring examples in documentation – blacken-docs - Code blocks inside Markdown and reStructuredText documentation files must also follow **black** formatting
dvorkaCopilot instructionsdvorka/mindforger/.github/copilot-instructions.md
Copilot instructions This document provides instructions to the copilot AI assistants for dvorka/mindforger project. ## General instructions - Always write beautiful, readable, and maintainable code. - Handle errors, exceptions, and corner cases. - Prefer
nteractCopilot instructionsnteract/semiotic/.github/copilot-instructions.md
high-level API does not expose. - Keep public APIs, types, chart specs, schemas, generated documentation, and focused tests synchronized. - Do not hand-edit build output or generated marker sections
pt-pluginsCopilot instructionspt-plugins/PT-depiler/.github/copilot-instructions.md
every visited page pays for them. - **Options page** — `options/`: the Vue 3 SPA. - **Offscreen document** — `offscreen/`: owns IndexedDB and the scanning / social helpers; background and options reach it over messages
rust-crossCopilot instructionsrust-cross/cargo-zigbuild/.github/copilot-instructions.md
pass (tests on Ubuntu, macOS, and Windows with multiple Rust and zig versions) - Update documentation in README.md if adding new features or changing behavior ### Testing Strategy - The CI tests
No other project uses it yet
CommunityToolkitCopilot instructionsCommunityToolkit/Maui/.github/copilot-instructions.md
Overview This document provides guidelines for using GitHub Copilot to contribute to the .NET MAUI Community Toolkit. It includes instructions on setting up your environment, writing code, and following best
pjsipCopilot instructionspjsip/pjproject/.github/copilot-instructions.md
configuration - ICE/NAT: `pjnath/include/pjnath/ice_strmtp.h` - Call handling: `pjsip/src/pjsua-lib/pjsua_call.c` - Transport: `pjsip/include/pjsip/sip_transport.h` ## Coding Conventions Follow: https://docs.pjsip.org/en/latest/get-started/coding-style.html Documentation source (for when the docs site is not directly accessible): https://github.com/pjsip/pjproject_docs ### Essentials - **ANSI
vczh-librariesCopilot instructionsvczh-libraries/GacUI/.github/copilot-instructions.md
found in `REPO-ROOT/Project.md`. - Following `Leveraging the Knowledge Base`, find the knowledge and documents for this project in `REPO-ROOT/.github/KnowledgeBase/Index.md`. - Before writing to a source file, read
flexpilot-aiCopilot instructionsflexpilot-ai/flexpilot-ide/.github/copilot-instructions.md
types they occur on but in the best matching namespace. For instance, document changes aren't sent by a document but via the `workspace.onDidChangeTextDocument` event. The event will contain
homebridgeCopilot instructionshomebridge/docker-homebridge/.github/copilot-instructions.md
information here is incomplete or incorrect. Most development tasks can be accomplished using the documented build scripts and testing procedures below. ## Repository Overview This repository creates the official multi-architecture
cloudscape-designCopilot instructionscloudscape-design/components/.github/copilot-instructions.md
cite the rule and say why. These are the repo's house conventions. ## Comments & documentation - Comment only the non-obvious WHY (why a warning is suppressed, why a workaround exists
Steady18 mentions in 2 weeks
No other project uses it yet
open-telemetryCopilot instructionsopen-telemetry/opentelemetry-java-instrumentation/.github/copilot-instructions.md
published contract and intended external use, not source path or visibility alone. Symbols explicitly documented as internal, unsupported, and subject to change are not supported public APIs merely because their
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.
