komga
gotson/komga/AGENTS.md
Project Guidelines ## Project Structure - `komga`: Backend - `komga-tray`: Desktop application wrapper - `komga-webui`: Legacy frontend - `next-ui`: Frontend
Steady8 mentions in 2 weeks
No other project uses it yet
How real projects brief Codex, Cursor and every other agent that reads AGENTS.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.
gotson/komga/AGENTS.md
Project Guidelines ## Project Structure - `komga`: Backend - `komga-tray`: Desktop application wrapper - `komga-webui`: Legacy frontend - `next-ui`: Frontend
Steady8 mentions in 2 weeks
No other project uses it yet
stagewise-io/stagewise/AGENTS.md
strict mode) - **Linting/Formatting**: Biome 2 (NOT ESLint or Prettier) - **Desktop**: Electron with Electron Forge - **Frontend**: React 19, Tailwind CSS 4 - **Website**: Next.js 16 - **Testing**: Vitest ## Code Style Enforced by Biome
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
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
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
CodeWithCJ/SparkyFitness/SparkyFitnessFrontend/AGENTS.md
AGENTS.md _Last updated: 2026-11-13_ SparkyFitness Frontend is the React web app for the SparkyFitness monorepo. Use this file as the primary guide for work inside `SparkyFitnessFrontend
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
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
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
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
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
huangruiteng/loopx/AGENTS.md
release, paid-execution or sensitive-publication authority. ## Product Delivery Completeness For product changes, read [frontend delivery](docs/development/frontend-delivery.md#task-first-delivery--从用户任务开始) before implementation. Identify affected frontend/Lark/CLI entrypoints and inspect existing
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
3 projects use a version of this
ArcReel/ArcReel/AGENTS.md
ArcReel AI 视频创作平台,将小说、剧本或创作构想转化为短视频。三层结构:`frontend/`(React SPA)→ `server/`(FastAPI,`agent_runtime/` 封装 Claude Agent SDK)→ `lib/`(核心库)。内嵌创作 Agent 的配置源在 `agent_runtime_profile/`,与开发态 `.claude/` 分离。uv workspace
Steady2 mentions in 2 weeks
No other project uses it yet
vercel-labs/scriptc/AGENTS.md
what removes it. 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
bookorbit/bookorbit/AGENTS.md
libraries. Avoid unbounded queries, loading entire libraries into memory, returning full collections to the frontend, N+1 query patterns, or expensive client-side processing over full result sets. - Use user
No other project uses it yet
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
vllm-project/semantic-router/AGENTS.md
models in VS Code - `config/`: canonical configuration, fragments, schemas, and recipes - `dashboard/`: React frontend and Go management backend - `deploy/`: deployment artifacts and operator - `e2e/`: end-to-end framework and profiles
DetachHead/rebased/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 `remote-dev-code
wesm/agentsview/AGENTS.md
toolchains, CI build tags, or dependencies | `docs/agents/build.md` | | S3 ingest, `S3Provider`, or `Source.S3Discovery` | `docs/agents/s3-providers.md` | | Any frontend file | `frontend/AGENTS.md` | | Frontend controls, styling, or reusable components | `frontend/AGENTS.md` and `DESIGN.md` | The `README.md` and `Makefile
An open format for instructions to coding agents, read by Codex, Cursor and others. Think of it as a README written for agents.
At the repository root, with more specific files in subdirectories. Agents read the one closest to the file they're editing.
Setup and test commands, code style, and the rules a new contributor would need to know.
Claude Code reads CLAUDE.md. A one-line CLAUDE.md that points at AGENTS.md covers both.