dbt
dbt-labs/dbt/AGENTS.md
crates/dbt-error/src/codes.rs` (CLI codes `[1000, 8999]`, internal `[9000, 9899]`; frontend codes come from `dbt_frontend_common::error::ErrorCode`, don't add them here). - Why: codes `>= 9000` are reported as Fusion bugs
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.
dbt-labs/dbt/AGENTS.md
crates/dbt-error/src/codes.rs` (CLI codes `[1000, 8999]`, internal `[9000, 9899]`; frontend codes come from `dbt_frontend_common::error::ErrorCode`, don't add them here). - Why: codes `>= 9000` are reported as Fusion bugs
krillinai/KrillinAI/AGENTS.md
Path for Web Changes - When changes affect only pages, template Workspaces, styles, or local frontend state in `apps/web`, without touching Host Bridge, Desktop capabilities, Preload/IPC, Daemon/Runtime, protocols, persistence, or build
Steady4 mentions in 2 weeks
1 project uses a version of this
FujiwaraChoki/MoneyPrinter/AGENTS.md
Repository Layout - `Backend/`: Flask API, DB-backed job queue, and video generation pipeline. - `Frontend/`: static HTML/JS client served by `python -m http.server`. - `docs/`: source-of-truth setup and runtime docs
AgentWrapper/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
Unleash/unleash/AGENTS.md
platform. This repository (OSS) is a monorepo containing: - **Backend**: Node.js/TypeScript REST API (`/src`) - **Frontend**: React/TypeScript single-page application (`/frontend`) **Enterprise** extends OSS via a separate repository (`unleash-enterprise`) using
pinpoint-apm/pinpoint/AGENTS.md
flow:** Agent (bytecode instrumentation on target app) → Collector (gRPC) → HBase/Pinot storage → Web API → React Frontend Core components: - **agent-module/** — Java agent with profiler, bootstrap, SDK, plugin loader, and 90+ instrumentation
No other project uses it yet
mealie-recipes/mealie/AGENTS.md
planner, and shopping list application with a FastAPI backend (Python 3.14) and Nuxt 4 frontend (Vue 3 + TypeScript). It uses SQLAlchemy ORM with support for SQLite and PostgreSQL databases. **Development
No other project uses it yet
cookiecutter/cookiecutter-django/AGENTS.md
Bare metal (needs PostgreSQL and Redis running) sh tests/test_bare.sh sh tests/test_bare.sh use_celery=y frontend_pipeline=Gulp ``` ### Generate a project locally for debugging ```bash uv run cookiecutter . --no-input --output
OpenByteInc/QuantDinger/AGENTS.md
Gateway, and trading documentation. - `docker-compose*.yml` and `scripts/`: deployment topology and lifecycle tooling. - Frontend source is maintained outside this repository. The prebuilt frontend image is configured by the `frontend
1 project uses a version of this
libnyanpasu/clash-nyanpasu/AGENTS.md
review](docs/development/testing.md), [workflow](docs/development/workflow.md), [Rust code guide](docs/development/rust.md), [TypeScript and React code style](docs/development/typescript.md), [frontend packages](docs/development/frontend-packages.md), and [repository scripts](docs/development/scripts.md). Agents MUST strictly follow these development standards together with
datahub-project/datahub/AGENTS.md
Core Services - **GMS (Generalized Metadata Service)**: Java/Spring backend handling metadata storage and REST/GraphQL APIs - **Frontend**: React/TypeScript application consuming GraphQL APIs - **Ingestion Framework**: Python CLI and connectors for extracting metadata from
datahub-project/datahub/datahub-web-react/AGENTS.md
Development Commands From the **repo root**: ```bash # Hot-reload dev server (preferred) scripts/dev/datahub-dev.sh setup frontend # one-time setup scripts/dev/datahub-dev.sh frontend # dev server with hot reload ``` From **`datahub-web-react/`**: ```bash
nearai/ironclaw/AGENTS.md
assistant` owns product-facing orchestration and `ProductSurface`; composition wires dependencies; WebUI owns HTTP/transport and frontend presentation. - Provider-neutral model contracts and provider implementations belong in `ironclaw_llm`; wrappers delegate
Chainlit/chainlit/AGENTS.md
production-ready conversational AI applications. It consists of a Python/FastAPI backend and a React frontend, with a pnpm monorepo for the JS packages. ## Prerequisites - Python: **3.13** (3.10+ is the framework
TwiN/gatus/AGENTS.md
make test` — Run all Go tests with coverage - `make clean` — Remove built binary - `make frontend-install` — Install frontend npm dependencies - `make frontend-build` — Build the Vue.js frontend (**must run after
Steady10 mentions in 2 weeks
No other project uses it yet
jason5ng32/MyIP/AGENTS.md
Express 5 back-end API. Licensed under AGPL-3.0-only (`LICENSE`). ## Stack | Layer | Technology | |---|---| | Frontend
jason5ng32/MyIP/api/AGENTS.md
offline dataset engine and its readers (see "Offline datasets"). - **`common/`** — only what the frontend or the build imports too (`valid-ip.js`, `fetch-with-timeout.js`, `report-schema.js`, …); it never imports from `server/`. It also holds
jason5ng32/MyIP/frontend/AGENTS.md
frontend/AGENTS.md Conventions specific to the Vue 3 SPA under `frontend/`. Universal rules (language, i18n, commits, testing) live in ../AGENTS.md. ## Overview
viarotel-org/escrcpy/AGENTS.md
pnpm build` for packaging, Electron main-process, Vite config, dependency, or release-sensitive changes. ## Frontend Patterns - Vue code uses Vue 3 Composition API with
StarRocks/starrocks/AGENTS.md
nested `AGENTS.md`. 3. For Backend work, read [`handbook/domains/backend.md`](./handbook/domains/backend.md) and [`be/AGENTS.md`](./be/AGENTS.md). 4. For Frontend work, read [`handbook/domains/frontend.md`](./handbook/domains/frontend.md) and [`fe/AGENTS.md`](./fe/AGENTS.md). 5. For SQL tests, docs, generated code, Java
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.