AGENTS.md examples from real projects

MODSetterAGENTS.md

SurfSense / www

MODSetter/SurfSense/www/AGENTS.md

vertical slice, one responsibility per file. See root `AGENTS.md`. - React/Next, colors, UI polish, motion: `frontend-workflow` skill. - shadcn components (`components.json`): `shadcn` skill after `frontend-workflow`, not instead of it — separate

No other project uses it yet

umijsAGENTS.md

qiankun

umijs/qiankun/AGENTS.md

Commit:** dcc42ae4 · **Branch:** next (qiankun 3.0, active dev) Qiankun is a micro-frontend framework built on [single-spa](https://github.com/single-spa/single-spa). v3 rewrites the runtime around **streaming HTML-entry loading

scalarAGENTS.md

scalar

scalar/scalar/AGENTS.md

Turbo for build orchestration, Vite for Vue packages, and `tsc` for pure TypeScript packages - **Frontend**: Vue 3, Composition API, TypeScript - **Styling**: Tailwind CSS - **Testing**: Vitest (unit), Playwright (E2E) - **Linting**: ESLint

PCSX2AGENTS.md

pcsx2

PCSX2/pcsx2/AGENTS.md

SPU2, input, storage, networking, and hardware device implementations. - `pcsx2-qt/` - Qt desktop frontend, settings dialogs, debugger, game list, translations, and UI resources. - `common/` - Shared utilities and platform abstraction used throughout

No other project uses it yet

KanariesAGENTS.md

pygwalker

Kanaries/pygwalker/AGENTS.md

project is put together, how to run it in **dev mode with live frontend reload**, and where all the logs go. Read this first — it is written to save

open-metadataAGENTS.md

OpenMetadata

open-metadata/OpenMetadata/AGENTS.md

discovery, observability, and governance — a multi-module project with a Java backend, a React/TypeScript frontend, a Python ingestion framework, and Docker infrastructure. ## Stack at a glance - **Backend**: Java 21 + Dropwizard

No other project uses it yet

facebookAGENTS.md

infer

facebook/infer/AGENTS.md

pattern `{lang}_{analyzer}`, e.g., `direct_java_pulse_test`, `direct_cpp_pulse_test`, `direct_c_frontend_test`. These are defined in the `DIRECT_TESTS` variable in the root Makefile. ### Test structure

documensoAGENTS.md

documenso

documenso/documenso/AGENTS.md

Handling & Validation - Use custom AppError class when throwing errors - When catching errors on the frontend use `const error = AppError.parse(error)` to get the error code - Use early returns and guard

No other project uses it yet

zitadelAGENTS.md

zitadel

zitadel/zitadel/AGENTS.md

separate table for history/audit, but events are not the system of record. - **Frontend**: - **Console**: Angular + RxJS. - **Login/Docs**: Next.js + React. ## ZITADEL Domain & Multi-Tenancy Logic ### 1. Hierarchy & Ownership ZITADEL follows

zitadelAGENTS.md

zitadel / packages

zitadel/zitadel/packages/AGENTS.md

ZITADEL Packages Guide for AI Agents ## Context `packages/` contains shared TypeScript libraries used by frontend applications and external consumers. ## Main Packages - **`packages/zitadel-proto`** (`@zitadel/proto`): generated protobuf TypeScript artifacts. - **`packages/zitadel-client`** (`@zitadel/client`): higher

ChocobozzzAGENTS.md

PeerTube

Chocobozzz/PeerTube/AGENTS.md

distributed runners. ## Repository Structure - **apps/** — Standalone CLI applications (`peertube-cli`, `peertube-runner`) - **client/** — Angular frontend SPA (separate build system) - **config/** — YAML configuration files for dev, test, and production - **packages/** — Shared

ChocobozzzAGENTS.md

PeerTube / client

Chocobozzz/PeerTube/client/AGENTS.md

Client — Angular Frontend SPA PeerTube's web client is an Angular single-page application served under `/client/`. It communicates with the backend exclusively through the REST API (`/api/v1/`). A separate

jupyterlabAGENTS.md

jupyterlab

jupyterlab/jupyterlab/AGENTS.md

disposables) - **Extension plugin examples**: `packages/*-extension/src/index.ts` - **TypeScript Style Guide**: https://github.com/jupyterlab/jupyterlab/wiki/TypeScript-Style-Guide ## Technology Stack - Frontend: TypeScript, React 18, Lumino (widgets), CodeMirror 6 - Backend: Python, Jupyter Server, Tornado, Traitlets - Build: Rspack

experientiallabsAGENTS.md

experiential

experientiallabs/experiential/AGENTS.md

explicitly approves one. 15. **All visuals follow the brand system.** Research figures, README/docs images, frontends, and any UI must look clean and minimal — Vercel/Notion/Apple-like: white background, generous whitespace, no chartjunk

alexta69AGENTS.md

metube

alexta69/metube/AGENTS.md

wiki. ## Tech stack - **Backend:** Python 3.13+, aiohttp, python-socketio 5.x, yt-dlp - **Frontend:** Angular 22, TypeScript, Bootstrap 5, SASS, ngx-socket-io - **Package managers:** uv (Python), pnpm (frontend) - **Container

caproverAGENTS.md

caprover

caprover/caprover/AGENTS.md

data contracts. - `src/utils/CaptainConstants.ts`: runtime configuration, identifiers, and filesystem paths. - `tests/`: Jest regression tests. The frontend is maintained in `caprover/caprover-frontend`. User-facing documentation is maintained in `caprover/caprover-website`. For releases, hotfixes

OrchestratorIncAGENTS.md

agent-orchestrator

OrchestratorInc/agent-orchestrator/AGENTS.md

loopback HTTP daemon, services, SQLite storage, lifecycle/reaper, runtime/workspace/agent/tracker adapters, terminal mux, and tests. - `frontend/`: Electron + React supervisor wired to the daemon through the generated typed client. Treat

bytebaseAGENTS.md

bytebase

bytebase/bytebase/AGENTS.md

around it. ## Read before working - Before exploring domain behavior, read [domain guidance](docs/agents/domain.md). - For frontend work, read [frontend/AGENTS.md](frontend/AGENTS.md); before changing UI, also read the [UX contract](docs/agents/frontend-ux.md). - Before adding

bytebaseAGENTS.md

bytebase / frontend

bytebase/bytebase/frontend/AGENTS.md

under `./frontend/`. ## Inheritance - Follow the repository-wide guidance in `../AGENTS.md`. - Treat this file as frontend-specific additions, not a replacement for the root instructions. ## React - All product UI code

siteboonAGENTS.md

claudecodeui

siteboon/claudecodeui/AGENTS.md

Apply it only to backend code; do not impose those architecture rules on the frontend. ## Frontend code For every task that creates, modifies, refactors, or reviews frontend code under

No other project uses it yet