How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
adezeCopilot instructionsadeze/raindrop-mcp/.github/instructions/copilot-instructions.md
protocol objects. - **Configuration**: Use environment variables and config files for secrets, endpoints, and options. - **Documentation**: Document all public classes, methods, and schemas. ## Tool Implementation Patterns - **Tool Registration**: Register each tool
cortex-tmsCopilot instructionscortex-tms/cortex-tms/.github/copilot-instructions.md
syntax: `[Description]` - Templates MUST be framework-agnostic (users customize them) - Templates MUST include inline documentation comments - Never hardcode specific tech stacks in templates ### CLI Tool (`bin/`, `src/`) - CLI MUST work
MicrosoftCopilot instructionsmicrosoft/Agents-for-net/.github/copilot-instructions.md
work across M365, Teams, Copilot Studio, and other platforms. **Current State:** Generally Available (GA) **Documentation:** https://learn.microsoft.com/en-us/microsoft-365/agents-sdk/ ## Build and Test ```bash # Build entire solution dotnet build src/Microsoft.Agents.SDK.sln # Build
MicrosoftCopilot instructionsmicrosoft/fabric-cli/.ai-assets/context/copilot-instructions.md
Help ```bash fab --help # General help fab --help # Command-specific help fab docs # Open documentation
pi22by7Copilot instructionspi22by7/In-Memoria/.github/copilot-instructions.md
token-efficient responses** - tools automatically limit output for LLM efficiency ## 📚 Additional Resources - Full API documentation: See tool schemas in `src/mcp-server/tools/` - Implementation roadmap: `IMPLEMENTATION_ROADMAP.md` - Architecture overview: `README.md` --- **Remember**: In Memoria learns
stacklokCopilot instructionsstacklok/toolhive-studio/.github/copilot-instructions.md
Mocking API responses are mocked using MSW with `AutoAPIMock` fixtures. See `docs/mocks.md` for full documentation and `renderer/src/common/mocks/` for implementation. - Fixtures are in `renderer/src/common/mocks/fixtures/` and use named exports - Override responses
Azure-SamplesCopilot instructionsAzure-Samples/eShopLite/copilot-instructions.md
lesson folder 4. Write unit tests for new features (prefer xUnit or MSTest) 5. Document public APIs, sample usage, and complex logic. Update lesson `readme.md` files as needed
YosefHayimCopilot instructionsYosefHayim/ebay-mcp/.github/copilot-instructions.md
args, run one endpoint Effect, and return the generated eBay DTO without response reshaping. ## Documentation and tests - Endpoint-backed API methods need TSDoc with `@param`, `@returns`, a small `@example
call518Copilot instructionscall518/MCP-PostgreSQL-Ops/.github/copilot-instructions.md
compatibility matrix in `README.md`: - Classify as Extension-Independent, Version-Aware, or Extension-Dependent - Document PostgreSQL version support (12-17) - List system views/tables used - Update tool count statistics ### Recent Major Changes
MicrosoftCopilot instructionsmicrosoft/Huabu/.github/copilot-instructions.md
docs/README.md`) to understand the current design, then act. **After changing architecture, behaviour, or a documented contract, update the matching doc in the same change** — fold shipped behavior into `docs/architecture/`, keep
ever-worksCopilot instructionsever-works/ever-works/.github/copilot-instructions.md
open-source work builder platform with AI-powered content generation. - **Repository**: https://github.com/ever-works/ever-works - **Documentation**: https://docs.ever.works (source: `apps/docs/` + `docs/`) ### Quick Facts - **Monorepo**: Turborepo + pnpm workspaces - **Backend**: NestJS 11 + TypeScript
MicrosoftCopilot instructionsmicrosoft/cloudcloak/.github/copilot-instructions.md
Node's built-in test runner for automated coverage in `tests/*.test.mjs`. - For documentation-only or metadata-only changes, do not add tests. - For behavior changes, prefer extracting small pure
MicrosoftCopilot instructionsmicrosoft/vscode-mypy/.github/copilot-instructions.md
repo test structure. - Always make sure all tests pass before submitting changes. - Always ensure documents and code are linted before submitting. - Do multiple rounds of review and refinement
AiTerminalFoundationCopilot instructionsAiTerminalFoundation/ai-terminal/.github/copilot-instructions.md
/ai-terminal/src/app/` - Tauri backend code in `/ai-terminal/src-tauri/src/` - Shared types and interfaces should be well-documented - Keep configuration files in their conventional locations ## Important Notes for Copilot - This is a **hybrid application
forefyCopilot instructionsforefy/.context/.github/copilot-instructions.md
Content, make sure it is updated and reflects the changes made in the document. Do not use emojis in content you generate, ever, and do not add comments
tacticlaunchCopilot instructionstacticlaunch/mcp-linear/.github/copilot-instructions.md
ships a stale query. If you do this, keep the query narrow and document why. - Keep service methods responsible for returning normalized plain objects, not raw SDK entities. - Keep handlers
MicrosoftCopilot instructionsmicrosoft/github-copilot-vibe-coding-workshop/docs/custom-instructions/containerization/copilot-instructions.md
Dockerfile, Docker Compose and Kubernetes. ## General Guidelines ### Basic Principles - Use English for all code, documentation, and comments. - Prioritize modular, reusable, and scalable code. - Follow naming conventions: - camelCase for variables, functions
MicrosoftCopilot instructionsmicrosoft/github-copilot-vibe-coding-workshop/docs/custom-instructions/dotnet/copilot-instructions.md
stateless API authentication. - Use HTTPS and enforce SSL. - Implement proper CORS policies. ## API Documentation - Use built-in OpenAPI package for API documentation. - Provide XML comments for controllers and models
MicrosoftCopilot instructionsmicrosoft/github-copilot-vibe-coding-workshop/docs/custom-instructions/java/copilot-instructions.md
JUnit, and related Java technologies. ## Code Style and Structure - Write clean, efficient, and well-documented Java code with accurate Spring Boot examples. - Use Spring Boot best practices and conventions throughout
MicrosoftCopilot instructionsmicrosoft/github-copilot-vibe-coding-workshop/docs/custom-instructions/python/copilot-instructions.md
operations. - Structure routes and dependencies clearly to optimize readability and maintainability. Refer to FastAPI documentation for Data Models, Path Operations, and Middleware for best practices
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.
