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.
HerbHallCopilot instructionsHerbHall/samverk/.github/copilot-instructions.md
ESLint catches unused imports) ## Testing - Go: table-driven tests, `testutil.NewStore(t)` for SQLite fixtures - Frontend: Vitest + Testing Library - Run `go build ./...`, `go test ./...`, golangci-lint before committing
hlsitechioCopilot instructionshlsitechio/claude-skills-security/.github/copilot-instructions.md
security-pack/` — 9 audit-domain skills (RLS, supply chain, tenant isolation, code review, API, frontend, IaC, compliance, GitHub repo hardening). Each emits findings with a 3-5 letter prefix (`SUPA
iamcaominhtienCopilot instructionsiamcaominhtien/kanban-board-mcp/.github/copilot-instructions.md
state should reflect the MCP server's state — avoid duplicating business logic in the frontend ## Prompt Writing Principles These apply whenever any agent writes or updates a prompt (agent file
LDKTCCopilot instructionsLDKTC/Agent-P-FullStack/.github/copilot-instructions.md
interaction, layout, or information-architecture pattern before building it → `agents/ui-ux-researcher.md` — hands the recommendation to `frontend-dev` (or `skills/html-css/SKILL.md`) next. - UI/component/page/client-state work → `agents/frontend-dev.md`. - Raw HTML/CSS authoring or review with no framework
OuroborosCollectivePipes a download into a shellCopilot instructionsOuroborosCollective/Sovereign-Studio-ato/.github/copilot-instructions.md
stale SHAs, image digests, ports or old issue lists presented as current. ## Repository map - Frontend: `src/` - Product runtime: `src/features/product/runtime/` and related runtime modules - Canonical backend agent runtime: `backend/agent_runtime/` - Governed backend
stevemarksavaCopilot instructionsstevemarksava/superteam/.github/copilot-instructions.md
documentation lead | Documentation, a report, a README, or an ADR needs writing | | **Pixel** | Frontend Developer in Eric's pod | React, TypeScript, or Tailwind UI components must be built | | **Diesel** | Backend
tomer1983Copilot instructionstomer1983/swagger2mcp/.github/copilot-instructions.md
Protocol (MCP) servers from OpenAPI/Swagger schemas. The system uses a microservices architecture with separate frontend, backend API, background worker, Redis queue, and PostgreSQL database - all orchestrated via Docker Compose. ## Architecture
vortegCopilot instructionsvorteg/swagentics/.github/copilot-instructions.md
definitions, scripts, and manifest. > **Note:** Users can add their own agents (e.g., `@backend-coder`, `@frontend-coder`) via `/copilot-init` based on their project's needs. See `docs/creating-agents.md` for guidance
amitchorasiyaCopilot instructionsamitchorasiya/antivibe-rails-starter/.github/copilot-instructions.md
variables. NEVER place secrets in client-side code, config files committed to git, or frontend bundles. - Confidential data (email, PII, private messages) MUST be encrypted at rest and in transit
andersonjopeCopilot instructionsandersonjope/AI-Structure/.github/copilot-instructions.md
shared libraries without service-specific business rules. - `apps/mobile-app`: Ionic Angular mobile application. - `libs/frontend-common`: shared frontend libraries. - `infra`: Docker, Kubernetes, Nginx, and observability. ## Skills Agent skills live in `.agents/skills/ /SKILL.md
AryanRajMauryaCopilot instructionsAryanRajMaurya/shipfree/.github/copilot-instructions.md
request path into a queue consumer. Never put a provider API key in the frontend. Proxy through a Worker and keep the key in `wrangler secret put`. Full limits, workflow
daudibrahimhasanCopilot instructionsdaudibrahimhasan/false9/.github/copilot-instructions.md
analysis - `f9-backend.md` — Backend API auditing - `f9-database.md` — Database query optimization - `f9-security.md` — Security vulnerability scanning - `f9-frontend.md` — Frontend completion and wiring - `f9-performance.md` — Performance profiling - `f9-testing.md` — Test quality analysis - `f9-llm-validator.md` — LLM feature validation - `f9-devops.md
EdwinDigitalCopilot instructionsEdwinDigital/agent-skill-management-center/.github/copilot-instructions.md
logic graphs, and Skill.md translations. Technology stack: - Runtime/API: Node.js, Express, native `node:sqlite` `DatabaseSync`. - Frontend: React 19, Vite, TypeScript, Tailwind CSS v4, shadcn/Radix UI primitives, lucide icons, Sonner. - Local database
GagauzSergiiCopilot instructionsGagauzSergii/data-center-healthcheck/copilot-instructions.md
Example tasks: - "Get last 50 lines from the backend container" - "Summarize incidents for the frontend container" - "Run triage_incident on backend" ## Workflow Examples **Incident response (full flow):** 1. Call `docker
goharabbas321Copilot instructionsgoharabbas321/zeoel-framework/.github/copilot-instructions.md
ALWAYS** create ALL mandatory documents at each phase boundary. 5. Code **MUST** live in `frontend/` or `backend/`. No other code directories. 6. When the user says "build X" → Start with
ikan-tech1Copilot instructionsikan-tech1/eg-design-system/.github/copilot-instructions.md
Design System & Frontend Guidelines > **Drop-in file.** Place this `CLAUDE.md` in a project root (or merge it into an existing one) and Claude Code will load it automatically. It defines
IsIntegrandoSolucoesCopilot instructionsIsIntegrandoSolucoes/cci-ca-docs/.github/copilot-instructions.md
Gerais Siga as diretrizes de desenvolvimento e qualidade definidas em: - [DIRETRIZES.instructions.md](../instructions/DIRETRIZES.instructions.md) - [GUIA_DESENVOLVIMENTO.instructions.md](../instructions/GUIA_DESENVOLVIMENTO.instructions.md) ## Frontend (Admin & Portal Aluno) - Padrões React: [BOAS_PRATICAS_REACT.instructions.md](../instructions/BOAS_PRATICAS_REACT.instructions.md) - Styled Components: [STYLED-COMPONENTS.instructions.md](../instructions/STYLED-COMPONENTS.instructions.md) - Hooks: [GUIA_USO_HOOKS.instructions.md](../instructions/GUIA_USO_HOOKS.instructions.md) ## Backend
KoshuxCopilot instructionsKoshux/agentic-sdlc-scaffold/.github/copilot-instructions.md
database.instructions.md](instructions/database.instructions.md) | `**/prisma/**` | on matching files | | [backend.instructions.md](instructions/backend.instructions.md) | `apps/**` | on matching files | | [frontend.instructions.md](instructions/frontend.instructions.md) | `frontend/**` | on matching files | | [ux.instructions.md](instructions/ux.instructions.md) | frontend component paths | optional module | | [windows-wsl2.instructions.md](instructions/windows-wsl2.instructions.md) | on demand | optional
michelveCopilot instructionsmichelve/draft_v0/.github/instructions/copilot-instructions.md
performance claims - **#NoMessLeftBehind** - Never leave broken builds, every error must be resolved ## Tech Stack - Frontend: React 19, TypeScript, TanStack Router/Query, Bootstrap 5.3, DSAi Design System - Backend: Node.js, Express, TypeScript - Database
MicrosoftCopilot instructionsmicrosoft/FixLab/.github/copilot-instructions.md
product-neutral Agency Copilot plugin and CLI for evidence-backed defect validation across React frontends and .NET backends. Consumer-specific product names and boundaries must remain outside the reusable product
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.
