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.
home-assistantPipes a download into a shellCopilot instructionshome-assistant/core/.github/copilot-instructions.md
issue: - Link to documentation pull request: - Link to contributors documentation pull request: - Link to frontend pull request: ## Checklist - [ ] I understand the code I am submitting and can explain
No other project uses it yet
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
Steady8 mentions in 2 weeks
No other project uses it yet
vitejsCopilot instructionsvitejs/vite/.github/copilot-instructions.md
This is a TypeScript project that implements a frontend build tooling called Vite. Please follow these guidelines when contributing: ## Code Standards - Run `pnpm run lint` to ensure that your code
No other project uses it yet
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
Steady3 mentions in 2 weeks
No other project uses it yet
streamlitCopilot instructionsstreamlit/streamlit/.github/copilot-instructions.md
data apps and internal tools. ## Tech Stack - **Backend (Server):** Python, Starlette/Uvicorn server, pytest - **Frontend (Web UI):** TypeScript, React, Emotion (CSS-in-JS), Vite, Vitest - **Communication:** Protocol Buffers (protobuf) over WebSocket
directusCopilot instructionsdirectus/directus/.github/copilot-instructions.md
utilities ## Technology Stack - **Language**: TypeScript, JavaScript - **Runtime**: Node.js 26 - **Package Manager**: pnpm (>=12 <13) - **Frontend Framework**: Vue.js 3 - **Build Tools**: Vite, Rollup, esbuild - **Testing**: Vitest - **Database Support**: PostgreSQL, MySQL, SQLite
No other project uses it yet
keycloakCopilot instructionskeycloak/keycloak/.github/copilot-instructions.md
Main server/runtime work is centered around `quarkus/`, `services/`, `server-spi*`, `model/`, and `tests/`. - Frontend code lives in `js/` (PNPM workspace with apps/libs). ## Required toolchain - Use Maven Wrapper, not system Maven
No other project uses it yet
plotlyCopilot instructionsplotly/dash/.github/copilot-instructions.md
dash/dependencies.py` - `Input`, `Output`, `State`, wildcards - `dash/development/base_component.py` - Component base class, `to_plotly_json()` - `dash/dash-renderer/` - TypeScript/React frontend - `components/` - Component packages (dcc, html, table
No other project uses it yet
temporalioCopilot instructionstemporalio/temporal/.github/copilot-instructions.md
Code follows the patterns already established in the codebase. For example, libraries pass the frontend request through as other libraries do. - Existing utilities are reused before new ones are created
No other project uses it yet
marimo-teamCopilot instructionsmarimo-team/marimo/.github/copilot-instructions.md
instead of just the direct problem it addresses. For example, if there is a frontend change to make a border thicker, how does this look in run mode, app-view
No other project uses it yet
comet-mlCopilot instructionscomet-ml/opik/.github/copilot-instructions.md
Copilot Code Review Instructions > **Scope:** These guidelines apply to all Opik applications including backend, frontend, and SDKs. Use the appropriate sections based on the code being reviewed. When Copilot automatically
Steady19 mentions in 2 weeks
No other project uses it yet
foremCopilot instructionsforem/forem/.github/copilot-instructions.md
Follow Test Patterns**: Use `create(:factory)` syntax (FactoryBot) and standard RSpec expectations. - **Frontend vs Backend**: We are currently focused on robust backend regression tests. Frontend changes require more manual user
wavetermdevCopilot instructionswavetermdev/waveterm/.github/copilot-instructions.md
kilocode/skills/electron-api/SKILL.md` | Guide for adding new Electron APIs to Wave Terminal. Use when implementing new frontend-to-electron communications via preload/IPC. | | waveenv | `.kilocode/skills/waveenv/SKILL.md` | Guide for creating WaveEnv narrowings in Wave Terminal
Steady5 mentions in 2 weeks
1 project uses a version of this
litCopilot instructionslit/lit/.github/copilot-instructions.md
repository is a monorepo that uses Lit for building web components and no other frontend frameworks unless otherwise specified. ## Coding Patterns - Uses standard ESM imports - TypeScript imports end with
No other project uses it yet
monkeytypegameCopilot instructionsmonkeytypegame/monkeytype/.github/copilot-instructions.md
extremely concise. Sacrifice grammar for the sake of concision. ## Architecture **Monorepo**: pnpm + Turborepo with frontend (Vite + SolidJS), backend (Express + MongoDB + Redis), and shared packages. ## Commands All commands support
No other project uses it yet
labringCopilot instructionslabring/sealos/.github/copilot-instructions.md
overlay driver support) - **Go**: Version 1.23+ (validated with go1.24.6) - **Node.js**: Version 20.4.0+ for frontend (validated with v20.19.4) - **Package Managers**: Make, pnpm (for frontend), npm - **Container Tools**: Docker (optional for local
No other project uses it yet
koelCopilot instructionskoel/koel/.github/copilot-instructions.md
base folders without approval. - Do not change the application's dependencies without approval. ## Frontend Bundling - If the user doesn't see a frontend change reflected in the UI, it could
No other project uses it yet
zitadelCopilot instructionszitadel/zitadel/.github/copilot-instructions.md
ZITADEL monorepo. This codebase uses specific conventions for its Go backend and Angular/Next.js frontends. **CRITICAL**: Read `AGENTS.md` in the root first, then the nearest scoped `AGENTS.md` for changed files
No other project uses it yet
semaphoreuiCopilot instructionssemaphoreui/semaphore/.github/copilot-instructions.md
Ansible, Terraform, PowerShell, and Bash scripts. It's built with Go (backend) and Vue.js (frontend), using Task runner for build automation. ## Working Effectively ### Bootstrap, build, and test the repository: - Install
No other project uses it yet
Open-LLM-VTuberCopilot instructionsOpen-LLM-VTuber/Open-LLM-VTuber/.github/copilot-instructions.md
Offline-Ready:** Core functionality MUST work without an internet connection. - **Separation of Concerns:** Strict frontend-backend separation. - **Clean code:** Clean, testable, maintainable code, follows best practices of python
Steady5 mentions in 2 weeks
No other project uses it yet
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.
