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.
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
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
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
afreakyelfCopilot instructionsafreakyelf/Pdf-Viewer/.github/copilot-instructions.md
propagate results to main for UI. - LRU cache size tuned to device memory class; document rationale. - Prefetch window reasonable (e.g., ±2–3 pages) and adaptive to zoom/velocity. - Handle scale changes
integrationsCopilot instructionsintegrations/terraform-provider-github/.github/copilot-instructions.md
Behavior change without a corresponding test change. - Resource that supports import but has no documented import ID format. ### Output discipline - If there are no HIGH or MEDIUM findings, the review
Steady2 mentions in 2 weeks
No other project uses it yet
MicrosoftDocsCopilot instructionsMicrosoftDocs/microsoft-365-docs/.github/copilot-instructions.md
These instructions define a unified style and process standard for authoring and maintaining learn.microsoft.com documentation with GitHub Copilot or other AI assistance. ## Learn-wide Instructions Below are instructions that apply
mongodb-jsCopilot instructionsmongodb-js/mongodb-mcp-server/.github/copilot-instructions.md
Atlas. - `create`: Creates resources, like a collection or a cluster. - `delete`: Deletes resources or documents, like collections, documents or clusters. - `update`: Modifies resources or documents, like collections, documents or clusters
zigpyCopilot instructionszigpy/zha-device-handlers/.github/copilot-instructions.md
fallback_name="Valve") .skip_configuration() .add_to_registry() ) ``` See `tuya.md` for detailed Tuya quirk documentation including finding DPs and all available methods. ### V1 Quirks (Legacy) V1 quirks inherit from `CustomDevice
whisper-moneyCopilot instructionswhisper-money/whisper-money/.github/copilot-instructions.md
build`, `npm run dev`, or `composer run dev`. Ask them. ## Documentation Files - You must only create documentation files if explicitly requested by the user. ## Replies - Be concise in your explanations
vndeeCopilot instructionsvndee/llm-sandbox/.github/copilot-instructions.md
deptry .` - Dependency validation ### Testing ```bash make test # Run all tests with coverage ``` ### Documentation ```bash make docs # Build and serve documentation locally make docs-test # Verify documentation builds without errors ``` ### Commit
No other project uses it yet
community-shadersCopilot instructionscommunity-shaders/skyrim-community-shaders/.github/copilot-instructions.md
context gathering if the information is incomplete or found to be in error.** ## Primary Documentation **For comprehensive development guidance, architecture details, and complete build instructions, see:** - **`.claude/CLAUDE.md`** - Concise guide
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.
