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.
MicrosoftReads credentialsCopilot instructionsmicrosoft/prompty/.github/copilot-instructions.md
separate migration) │ └── promptyjs/ # Hand-written JS runtime (separate migration) ├── vscode/prompty/ # VS Code extension └── web/ # Documentation site ``` --- ## Python Package Layout All source code lives under `runtime/python/prompty/prompty/`. The package is organized into
No other project uses it yet
MicrosoftCopilot instructionsmicrosoft/CSS-Exchange/.github/copilot-instructions.md
Variables in PascalCase pass spell-checking; inconsistency fails the spell check. ### Comments and Documentation - Use `#` for single-line comments - Use `<# #>` for block comments (especially for complex logic) - Use `.SYNOPSIS`, `.DESCRIPTION
micasa-devCopilot instructionsmicasa-dev/micasa/.github/copilot-instructions.md
seeding, backup, full-text search config/ TOML config with env var overrides (MICASA_*) extract/ Document extraction pipeline (text -> OCR -> LLM) llm/ LLM client wrapper and SQL prompts locale/ Currency formatting
No other project uses it yet
MicrosoftCopilot instructionsmicrosoft/griffel/.github/copilot-instructions.md
Linting takes 15-30 seconds. Set timeout to 60+ seconds. ``` ### Development Servers ```bash # Start documentation website (Docusaurus) yarn start # Serves on http://localhost:3000 # NEVER CANCEL: Initial build takes
brenocqCopilot instructionsbrenocq/implot3d/.github/copilot-instructions.md
already be implemented in ImPlot. Before implementing a new feature, check the ImPlot documentation and codebase to see if it can be adapted for ImPlot3D. 4. **Focus on 3D Plotting
vitejsCopilot instructionsvitejs/rolldown-vite/.github/copilot-instructions.md
pnpm run build` - Test: `pnpm run test` (uses Vitest and Playwright) ## Repository Structure - `docs/`: Documentation. - `packages/create-vite`: Contains the source code for the `create-vite` command. - `packages/plugin-legacy`: Contains the source code
icflorescuCopilot instructionsicflorescu/mantine-datatable/.github/copilot-instructions.md
dual-purpose repository containing both the **Mantine DataTable** component package and its documentation website. Understanding this hybrid architecture is crucial for effective development. ## Project Architecture ### Dual Repository Structure - **Package code
KLayoutCopilot instructionsKLayout/klayout/.github/copilot-instructions.md
posts. Open a pull request only when the maintainer asked for one, or for documentation fixes, build breaks with new toolchains, or a few-line fix of an unambiguous
zwave-jsReads credentialsCopilot instructionszwave-js/zwave-js-ui/.github/copilot-instructions.md
data') // Use the libraries... } ``` ### Keep Code Slim, Clean, and Readable - Write concise, self-documenting code - Use meaningful variable and function names - Avoid unnecessary complexity - Keep functions focused on a single
No other project uses it yet
suzuki-shunsukeCopilot instructionssuzuki-shunsuke/pinact/.github/copilot-instructions.md
GitHub Copilot Instructions for pinact This document contains GitHub Copilot-specific instructions. For general project guidelines, see [AI_GUIDE.md](../AI_GUIDE.md). ## Core Guidelines Refer to [AI_GUIDE.md](../AI_GUIDE.md) for all project conventions, including
Steady3 mentions in 2 weeks
No other project uses it yet
KelvinTegelaarCopilot instructionsKelvinTegelaar/CIPP/.github/copilot-instructions.md
must be one of: - `feat` — a new feature - `fix` — a bug fix - `docs` — documentation only - `style` — formatting, whitespace, no code-behavior change - `refactor` — code change that neither fixes
SandakanDeletes or force-pushesCopilot instructionsSandakan/Nora/.github/copilot-instructions.md
class) this.emit('queueChange', this.queue); this.emit('positionChange', this.currentSongIndex); ``` **Pattern**: Use event emitters (PlayerQueue) and CustomEvents (document-level) for real-time updates without tight coupling. ### 5. Data Fetching with TanStack Query
symfonyReads credentialsCopilot instructionssymfony/ai/.github/copilot-instructions.md
using the `empty()` function; prefer explicit checks like `[] === $array`, `'' === $string`, or `null === $value` ## Version Documentation ### UPGRADE.md - Document breaking changes in the root `UPGRADE.md` file - Format: Use version headers like `UPGRADE
No other project uses it yet
LogExpertsCopilot instructionsLogExperts/LogExpert/.github/copilot-instructions.md
LogExpert.UI` project 2. Follow Windows Forms patterns 3. Be aware of High DPI considerations (documented in README) 4. Test on different Windows versions if possible #### Adding Dependencies 1. Update `src/Directory.Packages.props
taranis-aiCopilot instructionstaranis-ai/taranis-ai/.github/copilot-instructions.md
introduce `pip`-based setup or ad hoc dependency installation. - Keep changes small, reversible, and documented when behavior or setup changes
syntaxfmCopilot instructionssyntaxfm/website/.github/copilot-instructions.md
over code duplication. - Structure files: types, component logic, markup, styles. - Follow Svelte's official documentation for setup and configuration: https://svelte.dev/docs/svelte/overview Naming Conventions - Use PascalCase for component files
AvdLeeCopilot instructionsAvdLee/Xcode-Build-Optimization-Agent-Skill/.github/copilot-instructions.md
variant analysis Do not turn the repository into general iOS architecture guidance or product documentation. ## Agent Skill Requirements - Every skill directory must contain a `SKILL.md` with valid `name` and `description
lichtblick-suiteCopilot instructionslichtblick-suite/lichtblick/.github/copilot-instructions.md
quotes - **Semicolons**: Yes - **Trailing commas**: All - **Line endings**: LF > Full code style standards are documented in [CONTRIBUTING.md](../CONTRIBUTING.md). --- ## Project Structure ``` packages/ suite-base/ # Core application logic, components, panels suite/ # Entry
Microsoft AzureCopilot instructionsAzure/agent-landing-zone/.github/copilot-instructions.md
converted before merging into `main`. --- ### Version Header Format ```md ## [vX.Y.Z] - YYYY-MM-DD ``` --- ## Documentation Consistency (Mandatory) Documentation must always reflect the **current, shipped** implementation. Whenever a change in this repository
TheAlgorithmsCopilot instructionsTheAlgorithms/R/.github/copilot-instructions.md
algorithm in the appropriate section ## Modifying Existing Algorithms When modifying existing algorithms: - Clearly document the changes in your pull request description - Ensure that your modifications do not break existing functionality
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.
