vllm
vllm-project/vllm/AGENTS.md
submitting human must review every changed line and run relevant tests. - PR descriptions for AI-assisted work **must** include: - Why this is not duplicating an existing PR. - Test commands
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.
vllm-project/vllm/AGENTS.md
submitting human must review every changed line and run relevant tests. - PR descriptions for AI-assisted work **must** include: - Why this is not duplicating an existing PR. - Test commands
vllm-project/vllm/csrc/AGENTS.md
unit compiles without a dispatch arm. - **Call every variant from one test, and measure cold.** A build-time claim needs ccache off, `MAX_JOBS` fixed, before and after, naming
vllm-project/vllm/rust/AGENTS.md
official chat templates and real generation produce. Handcrafted malformed inputs are fine for robustness tests but are not regressions without a real trigger. - When writing parsers with `winnow`: - Prefer
2 projects use a version of this
vllm-project/vllm/tests/AGENTS.md
tests - **Test real objects on the lightest real path.** Construct vLLM objects with their real constructors; do not stand them in with `SimpleNamespace` or `MagicMock`, set private attributes, or patch
Surging2 mentions in 2 weeks
1 project uses a version of this
tt-a1i/archify/AGENTS.md
scoped [PR improvement check](CONTRIBUTING.md#pr-improvement-check) using the project Skills when applicable. ## Test selection Before running tests, read [Choose evidence by impact](CONTRIBUTING.md#choose-evidence-by-impact
Steady14 mentions in 2 weeks
No other project uses it yet
Stirling-Tools/Stirling-PDF/AGENTS.md
project uses [Task](https://taskfile.dev/) as a unified command runner. All build, dev, test, lint, and docker commands can be run from the repo root via `task `. Run `task
nexu-io/open-design/AGENTS.md
login + models + ACP), built from anonymized Langfuse traces — PATH-overlay drop-in for tests and self-validation; see `mocks/README.md`). - `apps/web` is the Next.js 16 App Router + React 18 web runtime
Steady8 mentions in 2 weeks
No other project uses it yet
nexu-io/open-design/apps/AGENTS.md
behavior to `apps/desktop`. ## Daemon layout - `apps/daemon/src/` contains only daemon app source. - `apps/daemon/tests/` contains daemon tests. - `apps/daemon/src/sidecar/` contains the daemon sidecar entry. - CLI/agent argument definition changes belong in `apps/daemon/src/runtimes/defs/`; stdout parser
Steady8 mentions in 2 weeks
No other project uses it yet
nexu-io/open-design/e2e/AGENTS.md
Follow the root `AGENTS.md` first. This package owns user-level end-to-end smoke tests and Playwright UI automation only. For the current coverage posture, recent hardening work, grouped
Steady8 mentions in 2 weeks
No other project uses it yet
nexu-io/open-design/.github/AGENTS.md
fork PR approval behavior If the change affects cross-workflow behavior, update the topology tests instead of relying only on workflow YAML review. ## Architecture GitHub automation uses two layers. Business
Steady8 mentions in 2 weeks
No other project uses it yet
nexu-io/open-design/packages/AGENTS.md
runtime code goes in `sidecar`; generic OS/process code goes in `platform`. ## Boundary checklist - Package tests live in each package's `tests/` directory, sibling to `src/`; keep `src/` source-only
Steady8 mentions in 2 weeks
No other project uses it yet
nexu-io/open-design/shells/AGENTS.md
Shell-specific environment variables, workflow contexts, and storage credentials must not enter package contracts. - Tests live in `shells/ /tests`, sibling
Steady8 mentions in 2 weeks
No other project uses it yet
nexu-io/open-design/tools/AGENTS.md
source packages and `pnpm tools-pack ...` for packaged artifact build/install/release flows. ## Orchestration boundary - Tool tests live in each tool's `tests/` directory, sibling to `src/`; keep `src/` source-only
Steady8 mentions in 2 weeks
No other project uses it yet
nvm-sh/nvm/AGENTS.md
with specific Node.js versions - **Bash completion**: `bash_completion` - Provides tab completion for bash users - **Tests**: Comprehensive test suite in `test/` directory using the [urchin](https://www.npmjs.com/package/urchin) test framework
No other project uses it yet
zed-industries/zed/docs/AGENTS.md
without behavioral changes - Performance optimizations (unless user-visible) - Bug fixes that restore documented behavior - Test changes - CI/CD changes ## Output Format ### Phase 4 Documentation Plan When generating a documentation plan
1 project uses a version of this
iluwatar/java-design-patterns/AGENTS.md
language used for pattern implementations. - **Maven**: Dependency management and build tool. - **JUnit 5**: The testing framework used to verify pattern behaviors. - **Mockito**: Used for mocking dependencies in unit tests. - **Lombok
No other project uses it yet
infiniflow/ragflow/AGENTS.md
implementations coexist, converge to one path unless an external contract forces compatibility. - Remove dead tests, commented-out code, stale docs, and "move later" notes instead of preserving them. - Reduce public
infiniflow/ragflow/web/AGENTS.md
build # Production build npm run lint # oxlint npm run format # oxfmt npm run test # Jest tests ``` ## Development Conventions ### Pre-commit Format Validation (Mandatory) Frontend code changes **must pass the lefthook
All-Hands-AI/OpenHands/AGENTS.md
delete the whole locale block from translation.json, then `make-i18n`, then remove any test-mock entries (tests inline a `translations` map in the `useTranslation` vi.mock). ## Commit messages - The persistent shell
1 project uses a version of this
louislam/uptime-kuma/AGENTS.md
assistant, but you must personally understand all changes, review the generated code, and manually test it before submitting a pull request. You will be BANNED immediately if you submit generated
Steady6 mentions in 2 weeks
No other project uses it yet
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.