How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
MicrosoftCopilot instructionsmicrosoft/tyger/.github/copilot-instructions.md
surface is versioned via `Tyger.ControlPlane.Versioning`; new endpoints should be registered inside `app.ConfigureVersionedRouteGroup(...)` and documented in OpenAPI (`server/ControlPlane/OpenApi/`). Integration tests diff the generated spec against [cli/integrationtest/expected_openapi_spec.yaml](../cli/integrationtest/expected_openapi_spec.yaml); regenerate it when changing
vitaecontextCopilot instructionsvitaecontext/vitaecontext/.github/copilot-instructions.md
contain the core engine, CLI, and stateless MCP server. - `mcp/` contains Model Context Protocol documentation, configs, and schema contracts. - Human-readable Knowledge Hub docs live under `hub/`, such as `hub/context-builder
uuczCopilot instructionsuucz/moyu/vscode/copilot-instructions.md
line change - Add abstractions (interface, factory, base class) without being asked - Add comments, JSDoc, documentation, or tests without being asked - Import new dependencies when built-in features work - Change formatting
bug-opsCopilot instructionsbug-ops/mcpls/.github/copilot-instructions.md
transpositions a compile error. Encode protocol state in the type system where possible. A document that has been opened and one that has not should ideally be different types
mgiffordCopilot instructionsmgifford/ACCESSIBILITY.md/.github/copilot-instructions.md
models, or preview features can become outdated. Verify current behavior in [official GitHub Copilot documentation](https://docs.github.com/en/copilot) before recommending, copying, or enabling them. ## Where New Copilot Guidance Belongs
eduardo-slCopilot instructionseduardo-sl/go-agent-skills/.github/copilot-instructions.md
Generics, slog, errors.Join, slices/maps, iterators - **go-data-structures** — Slices, maps, sets, aliasing, preallocation - **go-documentation** — Godoc conventions, examples, deprecation ### Architecture & Design - **go-architecture-review** — Package layout, dependency direction, layering
excalimateCopilot instructionsexcalimate/excalimate/.github/copilot-instructions.md
emoji characters, Unicode symbols, or other icon libraries for UI icons. ## Key References | Document | Purpose | | ------------------------- | ------------------------------------------------------- | | `docs/mantine-library.md` | Mantine component library API reference and usage guide | ## Coding Conventions - **TypeScript** — strict types, avoid
lucapohl-angelCopilot instructionslucapohl-angel/ATLAS_OS/.github/copilot-instructions.md
user workflow:** [context/tui-workflow.md](../context/tui-workflow.md). Read it before adding or changing any TUI screen. It documents the canonical command list, popup sizing, color invariants (green=connected, accent=headers, warning=popular, success
Microsoft AzureCopilot instructionsAzure/PSDocs.Azure/.github/copilot-instructions.md
build utilities - `.github/workflows/**` - CI/CD workflows - `.github/skills/**` - Copilot skills - `packages/psdocs-azure/**` - Core PSDocs.Azure module - `MONOREPO_MIGRATION.md` - Migration documentation ### Treat these paths as imported/vendored (git subtree). Do not leave review comments unless there
MicrosoftCopilot instructionsmicrosoft/winget-studio/.github/copilot-instructions.md
Telemetry service - **`src/services/WinGetStudio.Services.VisualFeedback`** - UI feedback/animation helpers - **`src/WinGetStudio.Tests.MSTest`** - MSTest-based unit tests - **`docs/`** - User-facing documentation (getting started, DSC concepts, migration, CLI reference) ## Building, Testing, and Running ### Initial Setup Apply
MicrosoftCopilot instructionsmicrosoft/omnichannel-chat-sdk/.github/copilot-instructions.md
format 3. **Testing**: Include comprehensive tests for any new functionality or bug fixes 4. **Documentation**: Update documentation if necessary, including JSDoc comments 5. **Test Verification**: Ensure all tests pass before
MicrosoftCopilot instructionsmicrosoft/teams.py/.github/copilot-instructions.md
release scripts ├── pyproject.toml # Workspace and tool configuration ├── uv.lock # Dependency lock file └── README.md # Main documentation ``` ### Essential Files - **pyproject.toml**: Workspace configuration, dependencies, tool settings - **uv.lock**: Locked dependency versions (do not edit manually
stbenjamCopilot instructionsstbenjam/skillsaw/.github/copilot-instructions.md
exit 0. ## Pre-PR Checklist Follow these checks before opening a PR: - Check whether documentation is up to date for the changes on this branch. - Example
avelinoCopilot instructionsavelino/mcp/.github/copilot-instructions.md
cache:tools:{server_name}` | Serialized `BackendToolCache` | **New consumers must** define a unique prefix and document it in this table. ### Read/Write Patterns - **Read:** `db.get(&key, None)` returns `serde_json::Value`. Deserialize
brunoborgesCopilot instructionsbrunoborges/jdb-agentic-debugger/.github/copilot-instructions.md
repo contains no application code; it consists entirely of agent definitions, skill documents, and Bash scripts. ## Architecture ``` User → JDB Debugger (orchestrator agent) ├── jdb-session → Interactive debugging (launch/attach, breakpoints, stepping
swimmwatchCopilot instructionsswimmwatch/cloakbrowser-mcp/.github/copilot-instructions.md
Repository Instructions Follow `AGENTS.md` for project-wide coding, testing, documentation, changelog, and commit rules. For release preparation, publishing, verification, or recovery tasks, read `.agents/skills/project-release/SKILL.md` before making changes. That file
MicrosoftCopilot instructionsmicrosoft/qdk-ec/.github/copilot-instructions.md
deterministic inputs for reproducibility - When adding new functionality, include relevant unit tests and documentation. - Avoid inline commments. They are usually redundant and often wrong. Prefer clear code and good variable
MicrosoftCopilot instructionsmicrosoft/Agent365-devTools/.github/copilot-instructions.md
code does provides no regression protection. If a test needs to be updated, explicitly document the requirement the new assertion encodes (use `because:` in FluentAssertions). If you cannot articulate
aryanbriteCopilot instructionsaryanbrite/openrabbit/.github/copilot-instructions.md
corporate tone, no over-explaining. - Never write comments in code. Ever. - Never generate documentation files. - You are a senior developer who is writing code for a project
MicrosoftCopilot instructionsmicrosoft/terraform-provider-power-platform/.github/copilot-instructions.md
sets `TF_ACC=1` (no need to set it manually). - `make userdocs` to regenerate documentation - `make precommit` to run all checks once code is ready to commit. As a copilot
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.
