How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
bytedanceCopilot instructionsbytedance/deer-flow/.github/copilot-instructions.md
super agent harness". - Backend: Python 3.12, LangGraph + FastAPI gateway, sandbox/tool system, memory, MCP integration. - Frontend: Next.js 16 + React 19 + TypeScript + pnpm. - Local dev entrypoint: root `Makefile` starts backend + frontend + nginx
ClineCopilot instructionscline/cline/.github/copilot-instructions.md
types for simple data. 2. **Generate**: `bun run protos`. 3. **Backend handler**: `src/core/controller/ /`. 4. **Frontend call**: `UiServiceClient.myMethod(Request.create({...}))`. - Adding enums (e.g. `ClineSay`) → also update `src/shared/proto-conversions/cline-message.ts`. ## Adding API Providers (silent failure
open-metadataCopilot instructionsopen-metadata/OpenMetadata/.github/copilot-instructions.md
data governance. This is a multi-module project with Java backend services, React frontend, Python ingestion framework, and comprehensive Docker infrastructure. ## Architecture Overview - **Backend**: Java 21 + Dropwizard REST API framework
InsForgeCopilot instructionsInsForge/InsForge/.github/copilot-instructions.md
database. ## Architecture This is a monorepo containing: - **Backend**: Node.js with Express.js, providing RESTful APIs - **Frontend**: React with Vite, offering an admin dashboard - **Functions**: Serverless function runtime using Deno - **Shared-schemas
omnigent-aiCopilot instructionsomnigent-ai/omnigent/.github/copilot-instructions.md
change needs a test, raise it as a question rather than a required change. ## Frontend Test Coverage A pull request that changes behaviour under `web/` should add or update
MicrosoftCopilot instructionsmicrosoft/PyRIT/.github/copilot-instructions.md
tests/**` → also read `test.instructions.md` - Editing/code-reviewing `doc/**/*.py` or `doc/**/*.ipynb` → also read `docs.instructions.md` - Editing/code-reviewing `frontend/**/*.{ts,tsx}` → also read `frontend-style-guide.instructions.md` - Editing/code-reviewing `frontend/**/*.test.{ts,tsx}` → also read `frontend-test.instructions.md` Follow every
MicrosoftCopilot instructionsmicrosoft/skills/.github/copilot-instructions.md
bundle has skills/, commands/, agents/ ├── prompts/ # Reusable prompt templates ├── agents/ # Agent persona definitions (backend, frontend, infrastructure, planner, presenter) ├── scripts/ # Automation scripts (doc scraping) ├── workflows/ # GitHub Actions (daily doc updates) └── copilot-instructions.md
MicrosoftCopilot instructionsmicrosoft/vscode-jupyter/.github/copilot-instructions.md
side webview logic │ │ └── ipywidgets/ # IPython widgets (interactive Notebook outputs) in extension-side │ └── webview-side/ # Frontend React/HTML components │ └── ipywidgets/ # IPython widgets (interactive Notebook outputs) in webview └── test/ # Integration, unit
MicrosoftCopilot instructionsmicrosoft/BuildXL/.github/copilot-instructions.md
Copilot Instructions for BuildXL ## BuildXL context BuildXL is a distributed, cached, incremental build engine. Frontends construct a pip graph, then the scheduler executes it. Pips declare inputs and outputs
MicrosoftCopilot instructionsmicrosoft/qdk/.github/copilot-instructions.md
Runtime evaluation and simulation - **qsc_fir/**: Flat IR - **qsc_formatter/**: Q# code formatter - **qsc_frontend/**: Compiler frontend components - **qsc_hir/**: High-level Intermediate Representation - **qsc_linter/**: Code quality and style
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.
