AGENTS.md examples from real projects

gotsonAGENTS.md

komga

gotson/komga/AGENTS.md

Project Guidelines ## Project Structure - `komga`: Backend - `komga-tray`: Desktop application wrapper - `komga-webui`: Legacy frontend - `next-ui`: Frontend

No other project uses it yet

HexletReads credentialsAGENTS.md

ru-test-assignments

Hexlet/ru-test-assignments/AGENTS.md

directory mapping The 19 ` ` sections mostly map to a same-named top-level directory (`Frontend` → `frontend/`, `Android` → `android/`, …). The exceptions: | Section | Directory | | --- | --- | | `Аналитик` | `analytics/` | | `Automation QA`, `Manual QA` | `qa/` (shared

GreptimeTeamAGENTS.md

greptimedb

GreptimeTeam/greptimedb/AGENTS.md

repository; most crates live under `src/` (plus `tests-fuzz`, `tests-integration`, `tests/runner`). Key areas: - **Frontend / protocol**: `src/frontend/` (request orchestration), `src/servers/` (wire protocols), `src/sql/` (SQL parsing) - **Storage engines**: `src/mito2/` (main time

No other project uses it yet

apacheAGENTS.md

zeppelin

apache/zeppelin/AGENTS.md

Java, Scala — versions in root `pom.xml` (`java.version`, `scala.binary.version`) - **Build**: Maven multi-module (wrapper: `./mvnw`) - **Frontend**: Angular + TypeScript in `zeppelin-web-angular/` — versions in its `package.json` - **Version**: see ` ` in root `pom.xml

apacheAGENTS.md

zeppelin / zeppelin-web-angular

apache/zeppelin/zeppelin-web-angular/AGENTS.md

running in CI the day it merges. `frontend.yml` builds this module with `-DskipTests`, which frontend-maven-plugin honours by skipping `test`-phase executions, so all of them run inside `mvnw

FlagsmithAGENTS.md

flagsmith

Flagsmith/flagsmith/AGENTS.md

English. # Tasks Install Git hooks: `make install-hooks` For backend code, read @api/README.md For frontend code, read @frontend/README.md For docs.flagsmith.com source, read @docs/README.md For MCP code, read @mcp/README.md

CodeWithCJReads credentialsAGENTS.md

SparkyFitness

CodeWithCJ/SparkyFitness/AGENTS.md

directory you are changing. ## Package Guides - Repo-root alias: `CLAUDE.md` points to this file. - Frontend: `SparkyFitnessFrontend/AGENTS.md` - Server: `SparkyFitnessServer/AGENTS.md` - Mobile: `SparkyFitnessMobile/AGENTS.md` - Shared: `shared/AGENTS.md` For `docs/` and `SparkyFitnessGarmin/`, there is no package

CodeWithCJAGENTS.md

SparkyFitness / shared

CodeWithCJ/SparkyFitness/shared/AGENTS.md

defines contracts and shared logic, not an app. - Validate changes from consuming packages (server, frontend, mobile), not in isolation. - Every schema change here potentially touches three packages. ## Food Assistant State

CodeWithCJAGENTS.md

SparkyFitness / SparkyFitnessFrontend

CodeWithCJ/SparkyFitness/SparkyFitnessFrontend/AGENTS.md

AGENTS.md _Last updated: 2026-10-29_ SparkyFitness Frontend is the React web app for the SparkyFitness monorepo. Use this file as the primary guide for work inside `SparkyFitnessFrontend

CodeWithCJReads credentialsAGENTS.md

SparkyFitness / SparkyFitnessMobile

CodeWithCJ/SparkyFitness/SparkyFitnessMobile/AGENTS.md

this directory for mobile implementation and validation. If a task crosses into the backend, frontend, or `shared/`, read that package guide too before editing outside mobile. ## Scope And Style - TypeScript

CodeWithCJReads credentialsAGENTS.md

SparkyFitness / SparkyFitnessServer

CodeWithCJ/SparkyFitness/SparkyFitnessServer/AGENTS.md

patterns - `new-migration-checklist.md` — 8-step database change checklist If a task also touches `shared/`, the frontend, or the mobile app, read the relevant package guide before editing outside this directory

orval-labsAGENTS.md

orval

orval-labs/orval/AGENTS.md

Vitest, tsdown, Oxlint, Oxfmt, and Vite Task. Vite+ wraps runtime management, package management, and frontend tooling in a single global CLI called `vp`. Vite+ is distinct from Vite

huangruitengAGENTS.md

loopx

huangruiteng/loopx/AGENTS.md

prose follows this current rule. ## Product Delivery Completeness For product changes, read [task-first frontend delivery](docs/development/frontend-delivery.md#task-first-delivery--从用户任务开始) before implementation. Identify affected frontend/Lark/CLI entrypoints and inspect existing

crestalnetworkReads credentialsAGENTS.md

intentkit / frontend

crestalnetwork/intentkit/frontend/AGENTS.md

Frontend Guide ## Tech Stack - **Next.js 16+** (App Router, SSR mode — NOT static export) - **Shadcn/ui** (components in `src/components/ui/`) + **Tailwind CSS** - **TanStack Query v5** for server state - Agent config forms are hardcoded

elie222Reads credentialsAGENTS.md

rakazo

elie222/rakazo/AGENTS.md

only when it becomes relevant; do not add explainer text that repeats the interface. Frontends express intent and render state; the backend owns orchestration, authorization, validation, retries, recovery, and provider

VercelReads credentialsAGENTS.md

scriptc

vercel-labs/scriptc/AGENTS.md

README there. Before opening a PR that adds or changes corpus, diagnostic, or frontend fixtures, run `pnpm test:ts7 --baselines-only`. This fast completeness check uses the same fixture discovery

Provenance-EmuAGENTS.md

Provenance

Provenance-Emu/Provenance/AGENTS.md

dependency tier that can satisfy the task. ## Project snapshot - Provenance is an iOS/tvOS emulator frontend built from many `PV*` Swift packages plus Objective-C / Objective-C++ bridge layers for emulator

MicrosoftAGENTS.md

aspire

microsoft/aspire/AGENTS.md

csharp // Parse resource log lines emitted as: // [2026-05-10T18:34:22.123Z] frontend stdout: Now listening on: http://localhost:5221 // The message can contain additional ':' characters, so split

PBH-BTNAGENTS.md

PeerBanHelper

PBH-BTN/PeerBanHelper/AGENTS.md

times. This repository contains two components: a Java backend and a Vue.js frontend. The Vue.js frontend is located in the `webui/` directory. This AGENTS.md file will describe the requirements

No other project uses it yet

vllm-projectAGENTS.md

semantic-router

vllm-project/semantic-router/AGENTS.md

every model the router uses - `config/`: canonical configuration, fragments, schemas, and recipes - `dashboard/`: React frontend and Go management backend - `deploy/`: deployment artifacts and operator - `e2e/`: end-to-end framework

No other project uses it yet