AGENTS.md examples from real projects

dyad-shAGENTS.md

dyad

dyad-sh/dyad/AGENTS.md

wrong results. ## Project context - This is an Electron application with a secure IPC boundary. - Frontend is a React app that uses TanStack Router (not Next.js or React Router). - Data fetching/mutations

No other project uses it yet

handsontableReads credentialsAGENTS.md

handsontable

handsontable/handsontable/AGENTS.md

library plus React, Angular, and Vue 3 wrappers. It runs entirely in the browser — frontend-only, no server-side logic. It cannot access the internet unless explicitly configured (air-gapped

matomo-orgAGENTS.md

matomo

matomo-org/matomo/AGENTS.md

workflow`, and the relevant layer-specific skill when changes touch these areas. ## UI And Frontend - Prefer Vue for new UI work where it fits the surrounding code. - Legacy JavaScript, Twig

teableioAGENTS.md

teable

teableio/teable/agents.md

from `@teable/v2-contract-http` - OpenAPI is generated from the ts-rest contract via `@teable/v2-contract-http-openapi`. ## UI components (frontend) - In app UIs, use local shadcn wrappers (or `@teable/ui-lib`) instead of importing Radix primitives directly

eclipse-theiaAGENTS.md

theia

eclipse-theia/theia/AGENTS.md

backend. This is reflected in the folder structure of extensions: - src/browser: Frontend part of an extensions - src/node: Backend part of an extension. - src/common: Common/shared components, interfaces and protocol information

PydanticAGENTS.md

pydantic-ai / realtime

pydantic/pydantic-ai/docs/realtime/AGENTS.md

rule lives here), `turns.md`, `tools.md` (tools only), `capabilities.md` (per-hook support story), `history.md`, `deployment.md` (frontend transports and hosting), `lifecycle.md` (connection lifecycle only), `observability.md`, `troubleshooting.md` (the symptom-first index — per-page

PydanticAGENTS.md

pydantic-ai / ui

pydantic/pydantic-ai/pydantic_ai_slim/pydantic_ai/ui/AGENTS.md

still earns nothing. ## Round trips are checked with the real JavaScript clients What a frontend sends back is decided by its client library, not by our types: `@ag-ui/client

monkeytypegameAGENTS.md

monkeytype

monkeytypegame/monkeytype/AGENTS.md

extremely concise. Sacrifice grammar for concision. Frontend is partially migrated from vanilla JS to SolidJS — new components use `.tsx`, legacy code remains vanilla. Single test file: `pnpm vitest run path/to/test.ts

JetBrainsAGENTS.md

intellij-community / java

JetBrains/intellij-community/java/AGENTS.md

java-impl` holds the code insight: the completion, the intentions, and the refactorings. - `java-frontend`, `java-backend` and `java-frontback-impl` serve the split mode. Read the code-placement worker

kortix-aiReads credentialsAGENTS.md

suna

kortix-ai/suna/AGENTS.md

yourself: `gh workflow run deploy-dev.yml --repo kortix-ai/CompanyOS -f surface=changed` (`all` or `frontend` force a rebuild). Deploys queue, they never cancel. Wait for the run to finish. `/health

refactoringhqDeletes or force-pushesAGENTS.md

tolaria

refactoringhq/tolaria/AGENTS.md

core Playwright smoke + CodeScene), preferably on three Chunk sidecar lanes for automatic test/coverage work: frontend lint/build/coverage, Rust coverage, and Playwright smoke. The goal is lower wall-clock time than local

agent0aiAGENTS.md

agent-zero / api

agent0ai/agent-zero/api/AGENTS.md

project, plugin, or notification logic in endpoints. - Keep request and response payloads stable; update frontend callers and tests together when payloads change. - Prefer `Response` for files, redirects, status codes

agent0aiAGENTS.md

agent-zero / extensions

agent0ai/agent-zero/extensions/AGENTS.md

plugin extension discovery. ## Ownership - `python/` contains backend lifecycle hooks executed through `helpers.extension`. - `webui/` contains frontend extension contributions loaded through `webui/js/extensions.js`. - Plugin-specific extensions belong inside each plugin's `extensions/` directory

No other project uses it yet

agent0aiAGENTS.md

agent-zero / plugins

agent0ai/agent-zero/plugins/AGENTS.md

Zero log-output cursor, and avoid sending an entire long transcript in one frame. - Frontend plugin HTML extensions live under `extensions/webui/ /`, include a root Alpine scope, and use `x-move

agent0aiAGENTS.md

agent-zero / references

agent0ai/agent-zero/skills/a0-create-plugin/references/AGENTS.md

reuse: framework APIs, authorization/context binding, effect adaptation, native platform commands, and verification. - `webui.md` owns frontend examples, shared `x-overflow` integration, and UI verification. - `review.md` owns evidence-based review; `contribute.md` owns

No other project uses it yet

agent0aiAGENTS.md

agent-zero / references

agent0ai/agent-zero/skills/a0-development/references/AGENTS.md

governed changes. - `tools.md` owns core and plugin tool development contracts. - `extensions.md` owns backend and frontend extension contracts. - `api-webui.md` owns HTTP API handler, WebSocket, and WebUI extension development guidance. - `operate-agent-zero.md` owns

agent0aiAGENTS.md

agent-zero / webui

agent0ai/agent-zero/webui/AGENTS.md

WebUI DOX ## Purpose - Own the Flask-served Alpine.js WebUI shell, frontend modules, components, CSS, static assets, and vendored browser libraries. - Keep the UI coherent with backend APIs, WebSocket state, plugin

No other project uses it yet

compiler-explorerReads credentialsAGENTS.md

compiler-explorer

compiler-explorer/compiler-explorer/AGENTS.md

optional chaining when updating existing code or adding new code ## Architecture Guidelines - **Frontend/Backend Separation**: Frontend code (`static/`) MUST NOT import from backend code (`lib/`) - Frontend should use API calls

No other project uses it yet

lichess-orgAGENTS.md

lila

lichess-org/lila/AGENTS.md

Stack:** - **Backend**: Scala 3.8.2 with Liplay 3.2 (Lichess Play Framework fork), SBT build system - **Frontend**: TypeScript with Snabbdom, PNPM workspace monorepo - **Database**: MongoDB with Elasticsearch indexing - **Real-time**: WebSocket connections

nukeopAGENTS.md

nuclear

nukeop/nuclear/AGENTS.md

backend lives in `packages/player/src-tauri/src/`. Modules: - `bridge/` - bidirectional RPC. Lets Rust servers call into the frontend (`Bridge::call` emits a `bridge:request` event, frontend replies via the `bridge_respond` command). - `http