Copilot instructions examples

OPCFoundationCopilot instructions

UA-.NETStandard

OPCFoundation/UA-.NETStandard/.github/copilot-instructions.md

integration tests - `tools/` - Source generators, analyzers, and the OPC UA MCP tool - `docs/` - Documentation files - `fuzzing/` - Fuzz targets, corpora, and support scripts ### Build Properties - `Directory.Build.props` - Central build properties - `Directory.Packages.props` - Centralized

touying-typCopilot instructions

touying

touying-typ/touying/.github/copilot-instructions.md

measure`, `layout`, `repeat` - **Text/lists**: `text`, `par`, `list`, `enum`, `item`, `quote`, `raw`, `strong`, `emph` - **Document**: `document`, `page`, `heading`, `outline`, `figure`, `footnote` - **Graphics**: `math`, `rect`, `circle`, `polygon`, `rotate`, `scale`, `fill`, `gradient

dotnetCopilot instructions

iot

dotnet/iot/.github/copilot-instructions.md

DevOps feeds are inaccessible**: Build will fail with "Could not resolve SDK Microsoft.DotNet.Arcade.Sdk" errors. Document this as a known limitation requiring network access to Azure DevOps. ### Alternative Build Approaches When

actionsReads credentialsCopilot instructions

typescript-action

actions/typescript-action/.github/copilot-instructions.md

ESLint Configuration | | `jest.config.js` | Jest Configuration | | `LICENSE` | License File | | `package.json` | NPM Package Configuration | | `README.md` | Project Documentation | | `rollup.config.ts` | Rollup Bundler Configuration | | `tsconfig.json` | TypeScript Configuration | ## Environment Setup Install dependencies by running: ```bash

MicrosoftCopilot instructions

Olive

microsoft/Olive/.github/copilot-instructions.md

package directory with core functionality - `test/` -- Test suite with requirements-test*.txt files - `docs/` -- Documentation - `.github/workflows/` -- CI/CD pipelines (lint.yml, codeql.yml) - `olive/passes/onnx` -- Directory of ONNX transformations passes - `olive/passes/pytorch` -- Directory of Pytorch

No other project uses it yet

kyantechReads credentialsCopilot instructions

Palmr

kyantech/Palmr/.github/copilot-instructions.md

Node.js) with TypeScript, SQLite database, and filesystem/S3 storage - **Frontend**: Next.js 15 + React + TypeScript + Shadcn/ui - **Documentation**: Next.js + Fumadocs + MDX - **Package Manager**: pnpm (v10.6.0) - **Monorepo Structure**: Three main apps (web, server, docs

nelmioCopilot instructions

NelmioApiDocBundle

nelmio/NelmioApiDocBundle/.github/copilot-instructions.md

Contribution Guidelines: Enhanced Follow these mandatory guidelines when contributing code, documentation, and translations to this repository. All contributions will be reviewed for compliance. --- ## General Project Overview * **Project Scope:** This

No other project uses it yet

gookitCopilot instructions

goutil

gookit/goutil/.github/copilot-instructions.md

seconds) - `make csdiff` - Check code formatting issues - `make readme` - Generate README documentation (~0.17 seconds) ### Linting and Quality - `go fmt ./...` - Format code (essential before committing) - `staticcheck ./...` - Run static analysis (has some

No other project uses it yet

knuckleswtfCopilot instructions

scribe

knuckleswtf/scribe/.github/copilot-instructions.md

Copilot Instructions for Scribe ## Project Overview Scribe is a Laravel package that generates API documentation for humans from Laravel codebases. It extracts information from routes, controllers, FormRequests, and other sources

ytsaurusCopilot instructions

ytsaurus

ytsaurus/ytsaurus/.github/copilot-instructions.md

members/khlebnikov/copilot-instructions ``` ## Additional Resources - Project README: `README.md` - Project ROADMAP: `ROADMAP.md` - Building and testing instructions: `BUILD.md` - Documentation README: `yt/docs/README.md` - C++ style guideline: `yt/styleguide/cpp.md` - Python style guideline: `yt/styleguide/python.md` ## Repository Structure - `util/` - Common utility

themactepCopilot instructions

thingino-firmware

themactep/thingino-firmware/.github/copilot-instructions.md

have enough facts, ask user for help. Do not write documentation unless exlicitly asked to. Always test your changes. Write tests when you solve issues to test and confirm

MicrosoftCopilot instructions

pxt

microsoft/pxt/.github/copilot-instructions.md

semantic versioning for all packages - Maintain backward compatibility when possible - Write clear, self-documenting code with JSDoc comments - Follow the existing code style and patterns in each component ## Architecture Principles

mampfesCopilot instructions

hacs_waste_collection_schedule

mampfes/hacs_waste_collection_schedule/.github/copilot-instructions.md

python tests/record_fixtures.py ` and commit `tests/fixtures/ /*.json` (or explain a genuine recording blocker). Pipeline source documentation is generated; do not commit `doc/source/ .md`. Follow the [release branch contribution guide](https://github.com

Microsoft AzureCopilot instructions

azure-sdk-for-js

Azure/azure-sdk-for-js/.github/copilot-instructions.md

canonical home (skills under `.github/skills/`, reviewer instructions under `.github/instructions/reviewer/`, and deep-dive docs under `documentation/`) so the same rule isn't duplicated across files. Start there. This file is intentionally

No other project uses it yet

reubenoCopilot instructions

brush

reubeno/brush/.github/copilot-instructions.md

delegated agents and their tools. ## Code Review Checklist When reviewing PRs, verify: - [ ] **Documentation**: All exported APIs have rustdoc comments (missing docs = CI failure) - [ ] **Forbidden patterns**: No `panic`, `unwrap_in_result

meshtasticDeletes or force-pushesCopilot instructions

meshtastic

meshtastic/meshtastic/.github/copilot-instructions.md

Copilot Instructions for Meshtastic Documentation ## Project Overview This is the official Meshtastic documentation website built with Docusaurus. It contains documentation, guides, resources, and the home page for the Meshtastic mesh

mfemCopilot instructions

mfem

mfem/mfem/.github/copilot-instructions.md

against nearby code and MFEM patterns; flag unmotivated deviations. 6. Check whether tests and documentation were updated appropriately. 7. Review CI results and suggest actions. 8. Produce a structured review

home-assistantCopilot instructions

supervisor

home-assistant/supervisor/.github/copilot-instructions.md

what the code looked like before. - Use American English for all code, comments, and documentation. ## AI policy This project follows the [Open Home Foundation AI Policy](../AI_POLICY.md). Autonomous contributions

LiveHelperChatCopilot instructions

livehelperchat

LiveHelperChat/livehelperchat/.github/copilot-instructions.md

understand the request you MUST only return the corresponding code, not explanation. # REFERENCE DOCUMENTATION # For comprehensive architecture, patterns, and domain knowledge, refer to: # `.github/instructions/` folder which contains: # - 1-techstack.md - Technology stack

LumiwealthCopilot instructions

lumibot

Lumiwealth/lumibot/.github/copilot-instructions.md

tests for any new functionality you add. Additionally, ensure that all tests are well-documented and follow best practices