How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
MicrosoftCopilot instructionsmicrosoft/SqlNexus/.github/copilot-instructions.md
local. - **Be explicit about data handling.** If a change imports or persists new data, document what is stored and why in the PR description. - **Redaction:** when logging for diagnostics, prefer
NVIDIACopilot instructionsNVIDIA/aicr/.github/copilot-instructions.md
commit signing, and the pull request process. - **[docs/contributor/index.md](../docs/contributor/index.md)** — detailed system architecture and component documentation. Tool versions and quality thresholds are defined once in [`.settings.yaml`](../.settings.yaml) (the single source
LangChainCopilot instructionslangchain-ai/docs/.github/copilot-instructions.md
LangChain Documentation Guidelines Documentation for LangChain products hosted on Mintlify. These guidelines apply to manually authored content under `src/`, not Mintlify `build/` output. `AGENTS.md` in the repository root
laradashboardCopilot instructionslaradashboard/laradashboard/.github/copilot-instructions.md
tool from Boost. - Only recent browser logs will be useful - ignore old logs. ## Searching Documentation (Critically Important) - Boost comes with a powerful `search-docs` tool you should use before
Community-AccessCopilot instructionsCommunity-Access/accessibility-agents/.github/copilot-instructions.md
System Auditor | Color token contrast, focus ring tokens, spacing tokens, Tailwind/MUI/Chakra/shadcn | | Markdown Accessibility | Markdown document accessibility - links, alt text, headings, tables, emoji, mermaid diagrams, dashes, anchors | | Web Accessibility Wizard | Full
ruilisiCopilot instructionsruilisi/lsbot/.github/copilot-instructions.md
skip a tier or change the resolution order. This is a core architectural invariant. ## Documentation Placement - **Project-wide docs** (applicable to all platforms/modes) go at the repo root alongside `README.md
jamditisCopilot instructionsjamditis/claude-skills-journalism/.github/copilot-instructions.md
trailers, or any "AI-assisted"/"Generated by"-style notes. Mentioning model/company names in technical documentation is fine; the ban is on authorship credits. - **Public-facing HTML pages** must include
MicrosoftCopilot instructionsmicrosoft/mssql-django/.github/copilot-instructions.md
reason is a permanent platform limitation or an unimplemented capability — the comment is documentation future maintainers rely on. ### Regex Support `python manage.py install_regex_clr ` installs a CLR assembly enabling
Tiberriver256Copilot instructionsTiberriver256/mcp-server-azure-devops/.github/copilot-instructions.md
utilities (auth, errors, types, config) - `src/clients/azure-devops.ts` - Azure DevOps client - `tests/setup.ts` - Test configuration - `docs/` - Comprehensive documentation (authentication, testing, tools) ## Adding a New Feature Follow the Feature Module pattern used throughout
NVIDIACopilot instructionsNVIDIA/NVSentinel/.github/copilot-instructions.md
system, debugging - [CONTRIBUTING.md](../CONTRIBUTING.md) — contribution workflow, review process, DCO - [docs/](../docs/) — architecture and design documentation
mrwoguCopilot instructionsmrwogu/promptscript/.github/copilot-instructions.md
configuration-files ### eslint ESLint: inherit from eslint.base.config.cjs ### vite-vitest Vite root: \_\_dirname (not import.meta.dirname) ## documentation-verification - Review README.md and the affected pages under docs/ before changing behavior - Update README.md
MicrosoftCopilot instructionsmicrosoft/iq-series/.github/copilot-instructions.md
keys - **Environment variables**: Loaded from `.env` files using `python-dotenv` - **Key packages**: `azure-search-documents`, `azure-ai-projects`, `azure-identity` - **Agentic retrieval**: Knowledge sources → Knowledge bases → `KnowledgeBaseRetrievalClient.retrieve()` - **Agent integration**: Knowledge
ttommythCopilot instructionsttommyth/interactive-mcp/.github/copilot-instructions.md
Feel free to ask for more information if you need it ## AI Notes - Cursor Documentation System - Always read .notes/README.md - Update the files in .notes folder when you learn something - when
awizemannCopilot instructionsawizemann/harness/.github/copilot-instructions.md
memophant` MCP tools** for every read/write (search/read/write/edit/move) — read each tool's description (they document their args). The engine is the gate: the tool/app entry points carry the guards (slug
andrea9293Copilot instructionsandrea9293/mcp-documentation-server/.github/copilot-instructions.md
Documentation Server - AI Coding Agent Instructions ## Architecture Overview This is a **TypeScript-based Model Context Protocol (MCP) server** providing document management and semantic search capabilities using local AI embeddings
MicrosoftCopilot instructionsmicrosoft/lisa/.github/copilot-instructions.md
LISA Testing Guidelines for Pull Requests This document provides comprehensive guidelines for generating test suggestions for pull requests (PRs) in the LISA project. These guidelines ensure thorough validation while maintaining
MicrosoftCopilot instructionsmicrosoft/ApplicationInsights-node.js/.github/workflows/copilot-instructions.md
standard APIs - Verify API availability in the target Node.js version before suggesting - Prefer stable, documented APIs over cutting-edge features ### 2. Type Safety (TypeScript) - Avoid any types and type assertions
MicrosoftCopilot instructionsmicrosoft/fabric-cicd/.github/copilot-instructions.md
check` (Verify formatting is correct) | 60s | | Docs build | `uv run mkdocs build --clean` (Build documentation) | 60s | | Docs serve | `uv run mkdocs serve` (Start local documentation server) | 60s | **Mandatory Validation (ALWAYS
Microsoft AzureCopilot instructionsAzure/azure-monitor-baseline-alerts/.github/copilot-instructions.md
Infrastructure as Code (IaC) templates for Azure resources. The project includes a Hugo-based documentation website, Azure ARM/Bicep templates, and Python tooling for alert management. **CRITICAL**: Always reference these instructions
MicrosoftCopilot instructionsmicrosoft/Tools-for-Health-Data-Anonymization/.github/copilot-instructions.md
StyleCop configuration) - **Release Pipeline:** `release.yml` (Azure DevOps build pipeline) - **NuGet:** `nuget.config` (package source configuration) ### Documentation - **Main README:** `README.md` (overview and contributing guidelines) - **FHIR Documentation:** `docs/FHIR-anonymization.md` - **DICOM Documentation:** `docs/DICOM-anonymization.md` - **DICOM Configuration
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.
