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.
meshtasticCopilot instructionsmeshtastic/firmware/.github/copilot-instructions.md
WARN…) | `src/DebugConfiguration.h` | > | New module skeleton | inherit `ProtobufModule ` in `src/mesh/ProtobufModule.h` | > | Observer / event wiring | `src/Observer.h` | This document provides context and guidelines for AI assistants working with the Meshtastic firmware codebase. ## Project Overview
No other project uses it yet
MariaDBCopilot instructionsMariaDB/server/.github/copilot-instructions.md
only, never to validate external/untrusted input. Use them also as a self-enforcing code documentation ("note, ptr is never NULL here"). ## Testing - Expect an `mysql-test/` `.test`; it must FAIL
No other project uses it yet
openatxCopilot instructionsopenatx/uiautomator2/.github/copilot-instructions.md
Coverage configuration ### Additional Components - `uibox/` -- Go component for Android binary tools (separate build system) ### Documentation - `README.md` -- Main documentation with usage examples - `DEVELOP.md` -- Development setup instructions - `XPATH.md` -- XPath selector documentation - `CHANGELOG
No other project uses it yet
javalinCopilot instructionsjavalin/javalin/.github/copilot-instructions.md
disable response compression` - `[tests] Add unit tests for new validation logic` - `[github] Update documentation and README files` **Component categories commonly used:** - `[core]` - Core framework functionality - `[context]` - Request/response context changes - `[router
Steady20 mentions in 2 weeks
No other project uses it yet
kyvernoCopilot instructionskyverno/kyverno/.github/copilot-instructions.md
touches one of these, explicitly fetch and read that file first — it documents non-obvious behavior (dispatch order, what's deliberately *not* implemented, generated-file boundaries, concurrency constraints) that
No other project uses it yet
joemccannCopilot instructionsjoemccann/dillinger/.github/copilot-instructions.md
creators who need a distraction-free, cloud-connected markdown editor. They arrive with a document to write or edit, often context-switching from code. The job: write and preview markdown
No other project uses it yet
chefCopilot instructionschef/chef/.github/copilot-instructions.md
Chef ├── chef-utils/ # Utility functions and helpers ├── distro/ # Distribution-specific templates and files ├── docs/ # Documentation and development guides ├── ext/ # External extensions (e.g., win32-eventlog) ├── habitat/ # Habitat packaging configuration ├── kitchen-tests
No other project uses it yet
opencartReads credentialsCopilot instructionsopencart/opencart/.github/copilot-instructions.md
generation } } ``` **Common registry services**: `load`, `db`, `cache`, `config`, `request`, `response`, `session`, `url`, `document`, `language`, `event`, `log`, `template` ### The Loader System `$this->load` is the dynamic loading mechanism: ```php // Model loading
No other project uses it yet
stride3dCopilot instructionsstride3d/stride/.github/copilot-instructions.md
Stride Game Engine Copilot Instructions This document provides guidelines and best practices for using GitHub Copilot and Copilot Chat within the Stride Game Engine repository. The goal is to ensure
No other project uses it yet
OneDragon-AnythingCopilot instructionsOneDragon-Anything/ZenlessZoneZero-OneDragon/.github/copilot-instructions.md
applyTo: "**" --- # General Instructions - **Language**: 请始终使用 **简体中文** 回复。 - **Thinking**: 遇到复杂问题时，优先使用 `sequential-thinking` 工具制定计划。 - **Documentation**: 使用 `context7` 工具查找文档。 - **Environment**: 项目启动前要 `activate uv`，把源根加入 `PYTHONPATH`。 - **项目上下文**: 完整的项目结构、架构概念、编码规范、文档索引请阅读根目录 `AGENTS.md`。 # Coding
No other project uses it yet
go-gitCopilot instructionsgo-git/go-git/.github/copilot-instructions.md
global state, or surprising behavior. - Check whether exported APIs have clear semantics and appropriate documentation. ## Encoding and decoding - Any new encoding or decoding feature must include fuzz tests. - Flag encoding/decoding
No other project uses it yet
MicrosoftCopilot instructionsmicrosoft/TinyTroupe/.github/copilot-instructions.md
applyTo: "**" --- # Guidelines for Code Generation in TinyTroupe This document provides the primary guidelines for generating programs in the TinyTroupe project. It is meant to complement any existing documentation or built
No other project uses it yet
projectcalicoCopilot instructionsprojectcalico/calico/.github/copilot-instructions.md
Done in abc1234"). Explanations, pushback, and questions about review feedback come from the human. ## Documentation map Calico's docs are split by purpose. Architecture lives in `DESIGN.md` files; operational guidance
No other project uses it yet
Ripple-TSCopilot instructionsRipple-TS/ripple/.github/copilot-instructions.md
templates/`: Ripple scaffolding - `playground/ripple/`, `benchmarks/`, `website/`, and `website-new/`: Ripple examples, performance work, and documentation Shared `@tsrx/*` packages are registry dependencies. Do not recreate moved compiler, formatter, linter, language-server
1 project uses a version of this
AlaSQLCopilot instructionsAlaSQL/alasql/.github/copilot-instructions.md
meant to return `undefined` instead of `null` (unline regular SQL engines) ## Resources - [AlaSQL Documentation](https://github.com/alasql/alasql/wiki) - [Issue Tracker](https://github.com/AlaSQL/alasql/issues)
No other project uses it yet
go-co-opCopilot instructionsgo-co-op/gocron/.github/copilot-instructions.md
golangci-lint finds issues (though config compatibility varies) ## Common Tasks ### Repository Structure ``` . ├── README.md # Main documentation ├── CONTRIBUTING.md # Contribution guidelines ├── SECURITY.md # Security policy ├── Makefile # Build automation ├── go.mod # Go module definition ├── .github/ # GitHub
No other project uses it yet
simulotCopilot instructionssimulot/immich-go/.github/copilot-instructions.md
design. don't update the code if not explicitly requested Don't write reasoning documentation except is this is explicitly requested. Write it in the scratchpad folder. When implementing
No other project uses it yet
elementorCopilot instructionselementor/elementor/.github/copilot-instructions.md
plugin. ## Quick Reference ### Core Rules (Apply to ALL code) 1. **No Comments** - Write self-documenting code 2. **No Magic Numbers** - Use named constants for values except
No other project uses it yet
jstedfastCopilot instructionsjstedfast/MailKit/.github/copilot-instructions.md
here. | | `UnitTests/` | NUnit 4, `net8.0` only. | | `AotCompatibility/` | Native-AOT publish probe used by `scripts/test-aot-compatibility.ps1`. | | `Documentation/` | Sandcastle docs project. `Documentation/Examples/*.cs` are *not compiled* but are pulled into XML docs
No other project uses it yet
AethersailorCopilot instructionsAethersailor/Custom_OpenClash_Rules/.github/copilot-instructions.md
actual diff. 2. Identify the primary intentional change. 3. Distinguish: * behavior changes from documentation changes; * source files from generated files; * manual changes from automated refreshes; * implementation changes from accompanying tests
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.
