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.
AvaloniaCommunityCopilot instructionsAvaloniaCommunity/awesome-avalonia/.github/copilot-instructions.md
libraries, tools, samples, and resources maintained in a single README.md file. This is a documentation-only repository with no build processes or code compilation. Always reference these instructions first
SynoCommunityCopilot instructionsSynoCommunity/spksrc/.github/copilot-instructions.md
version requirements in upstream docs - Consider bundling related updates together (e.g., Erlang + RabbitMQ + ejabberd) - Document upgrade warnings in `CHANGELOG` when migrations are needed ### Adding Architecture Support When the limit
subsurfaceCopilot instructionssubsurface/subsurface/.github/copilot-instructions.md
Subsurface AI Coding Agent Guidelines Welcome to the Subsurface codebase! This document provides essential guidelines for AI coding agents to be productive and effective contributors to this project. Subsurface
MicrosoftCopilot instructionsmicrosoft/Generative-AI-for-beginners-dotnet/.github/copilot-instructions.md
organized in numbered folders (`01-IntroductionToGenerativeAI/` through `05-ResponsibleAI/`), each with a `readme.md` for documentation. - All code samples live in the centralized `samples/` directory, organized by category: `CoreSamples/`, `MAF/`, `AppsWithGenAI
MicrosoftCopilot instructionsmicrosoft/agent-skills/.github/copilot-instructions.md
Rust** | `-rust` | `azure-identity-rust`, `azure-cosmos-rust` | ### Featured Skills | Skill | Purpose | |-------|---------| | `azure-search-documents-py` | Search SDK patterns, vector/hybrid search, agentic retrieval | | `azure-ai-agents-py` | Low-level agents
lammpsCopilot instructionslammps/lammps/.github/copilot-instructions.md
specific rules in `.github/instructions/` for the changed files: C++ sources and tests (`source-code`), documentation (`documentation`), KOKKOS (`kokkos`), unit tests (`force-style-tests`), example inputs (`regression-tests`), and the build
MicrosoftCopilot instructionsmicrosoft/mxc/.github/copilot-instructions.md
platform behavior, feature gates, wire compatibility, and failure semantics. ## Before changing code - Read the documentation for the affected subsystem. Start with the references below rather than inferring behavior from names
Steady5 mentions in 2 weeks
No other project uses it yet
Open-Cascade-SASCopilot instructionsOpen-Cascade-SAS/OCCT/.github/copilot-instructions.md
handlers, or special cases for one input. - Input validation is appropriate at a documented boundary. It is not a substitute for fixing an internal invariant that valid input breaks
inspecCopilot instructionsinspec/inspec/.github/copilot-instructions.md
reference repos, and ensure you have the necessary tools installed. The remainder of this document assumes you have done this. ### Customizing the Shared Context Repository The shared-context repository
anandnetCopilot instructionsanandnet/Harmony-Music/.github/copilot-instructions.md
patterns when adding new tests - Use Flutter's widget testing framework ## Additional Resources - [Flutter Documentation](https://docs.flutter.dev/) - [GetX Documentation](https://pub.dev/packages/get) - [Hive Documentation](https://docs.hivedb.dev/) - Project README.md
pulumiCopilot instructionspulumi/kubespy/.github/copilot-instructions.md
will fail due to configuration issues ## Common Tasks ### Repository Structure ``` /home/runner/work/kubespy/kubespy/ ├── README.md # Main project documentation ├── CONTRIBUTING.md # Development guidelines ├── Makefile # Build automation ├── go.mod # Go module definition ├── kubespy.go # Main entry point
dotnetCopilot instructionsdotnet/vscode-csharp/.github/copilot-instructions.md
comments over what comments. For complex logic, include references to related files or documentation. Do not remove existing comments unless they are clearly outdated or incorrect. ## Integration Points - **GitHub Copilot
stacks-networkCopilot instructionsstacks-network/stacks-core/.github/copilot-instructions.md
Review priorities - Determine the intended behavior from the PR description, changed code, tests, and documentation; comment only when the implementation does not safely establish that behavior. - Prioritize defects with
No other project uses it yet
material-extensionsCopilot instructionsmaterial-extensions/vscode-material-icon-theme/.github/copilot-instructions.md
Follow the project style**: Ensure all changes adhere to the existing code and documentation style. Review the [project's codebase](/) to understand the conventions used. 2. **Use Material Design color
Steady13 mentions in 2 weeks
No other project uses it yet
timothystewart6Copilot instructionstimothystewart6/k3s-ansible/.github/copilot-instructions.md
making changes. It is the canonical guide for architecture, safety, implementation, validation, and documentation expectations. Do not duplicate repository guidance here. If instructions need to change, update `AGENTS.md
sonic-netCopilot instructionssonic-net/SONiC/.github/copilot-instructions.md
SONiC (Software for Open Networking in the Cloud) repository — the central hub for project documentation, architecture designs, High Level Design (HLD) documents, roadmaps, governance, and community information. It serves
No other project uses it yet
OpenMindCopilot instructionsOpenMind/OM1/.github/copilot-instructions.md
table-driven tests where appropriate - Mock external dependencies using interfaces ## Comments - Write clear package documentation - Document exported functions and types - Avoid obvious comments - Use godoc conventions
inspektor-gadgetCopilot instructionsinspektor-gadget/inspektor-gadget/.github/copilot-instructions.md
test/ # Gadget-specific tests README.md # Short description with link to full docs README.mdx # Full documentation in MDX format for the website ``` - `gadget.yaml` defines datasources with field annotations (`columns.width`, `columns.hidden`, `columns.alignment
No other project uses it yet
srl-labsCopilot instructionssrl-labs/containerlab/.github/copilot-instructions.md
directory. - The core library code is located in the `core/` directory. - The documentation files are located in the `docs/` directory. - The constants files are located in the `constants/` directory
No other project uses it yet
dotnetCopilot instructionsdotnet/macios/.github/copilot-instructions.md
linker, bgen) - `tests/` - Test suites (unit, introspection, extrospection) - `msbuild/` - MSBuild tasks and targets - `docs/` - Documentation and guides - `runtime/` - Runtime components and native code ## Build System This project uses a Make
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.
