How real projects brief Codex, Cursor and every other agent that reads AGENTS.md.
OthmanAdiAGENTS.mdOthmanAdi/planning-with-files/AGENTS.md
comes after shipping. Never batch all communication to the end. 2. `python -m pytest tests/ -q` is green before and after the merge. 3. Merge the contributor commits as above
VercelAGENTS.mdvercel/ai/AGENTS.md
Level Commands | Command | Description | | ------------------------ | ----------------------------------------------------------------- | | `pnpm install` | Install dependencies | | `pnpm build` | Build all packages | | `pnpm test` | Run all tests (excludes examples) | | `pnpm check` | Run linting (oxlint) and formatting (oxfmt) checks | | `pnpm
VercelAGENTS.mdvercel/ai/apps/docs/AGENTS.md
blocker, and localhost fallbacks must not ship in production metadata. - Run `pnpm validate:site` (tests + production build) after changing routes, config, source setup, MDX components, or package versions
deepset-aiAGENTS.mddeepset-ai/haystack/AGENTS.md
install it. For installation instructions, refer to https://hatch.pypa.io/latest/install/#installation. ### Run scripts with test dependencies hatch -e test run python SCRIPT.py ### Open a shell with test dependencies hatch -e test
deepset-aiAGENTS.mddeepset-ai/haystack/test/AGENTS.md
test/ Guidelines ## Testing - Name tests after the behavior they verify and group them by behavior in the existing file mirroring the source layout (`test/components/ /test_{component}.py`); keep the suite
MicrosoftAGENTS.mdmicrosoft/winget-cli/AGENTS.md
template. 2. Keep each PR focused on one logical change. 3. Include or update tests and documentation when the change affects behavior, command output, user guidance, or public APIs
EveryIncAGENTS.mdEveryInc/compound-engineering-plugin/AGENTS.md
this checkout is also the plugin root. ## Quick Start ```bash bun install bun run test # full test suite (also runs in CI; `--parallel` across worker processes) bun run release:validate
agentskillsAGENTS.mdagentskills/agentskills/AGENTS.md
policy here. ## Authority and boundaries `docs/specification.mdx` is authoritative for format requirements. Explanatory documentation, examples, tests, and implementations do not add requirements to the format. Preserve the distinction between the format
activepiecesAGENTS.mdactivepieces/activepieces/AGENTS.md
isNil()`, `spreadIfDefined()`, `spreadIfNotUndefined()`, `ActivepiecesError({ code, params })`, `SeekPage `, `formErrors`, `BaseModelSchema`, `chunk()`, `partition()`, `unique()`, `omit()`, `sanitizeObjectForPostgresql()` ## Testing ```bash npm run test-unit # Vitest: engine + shared npm run test-api # API integration
letta-aiAGENTS.mdletta-ai/letta/AGENTS.md
applications - benchmarks, evaluations, experiments, or academic research - comparisons with other agent or memory systems - testing current Letta behavior, performance, memory, APIs, or model support - building a new integration, adapter, fork
Model Context ProtocolAGENTS.mdmodelcontextprotocol/python-sdk/AGENTS.md
pass `--frozen` so uv doesn't rewrite `uv.lock` as a side effect. - Cross-version testing: `uv run --frozen --python 3.10 pytest ...` to run against a specific interpreter (CI covers
NirDiamantAGENTS.mdNirDiamant/GenAI_Agents/AGENTS.md
scripts for notebooks that need them. | | `data/` | Shared sample data. | | `scripts/` | Repository-level tooling. | | `tests/` | Import and smoke tests. Not a behavioral suite. | | `images/` | Diagrams referenced from notebooks
nocobaseAGENTS.mdnocobase/nocobase/AGENTS.md
docker container when start). So no need to create migration files in these cases. ## Testing Rules - Run single test file: `yarn test ` - Client example: `yarn test packages/core/flow-engine/src/__tests__/flow-engine.test.ts --run --reporter=verbose
SuperClaude-OrgAGENTS.mdSuperClaude-Org/SuperClaude_Framework/AGENTS.md
Guidelines ## Project Structure & Module Organization - `src/superclaude/` holds the Python package and pytest plugin entrypoints. - `tests/` contains Python integration/unit suites; markers map to features in `pyproject.toml`. - `pm/`, `research/`, and `index/` house
coleam00AGENTS.mdcoleam00/Archon/AGENTS.md
archon/engineering.md), user documentation in the docs site, and machine-checkable rules in code, types, tests, lint, or CI. ## Read before changing code - Treat the source, its call sites
microAGENTS.mdmicro/go-micro/AGENTS.md
prompt. 2. Run the relevant verification commands and capture their results (`go build ./...`, `go test ./...`, `golangci-lint run ./...`). 3. Check `git status --short` and review the diff before finishing
czlonkowskiAGENTS.mdczlonkowski/n8n-mcp/AGENTS.md
HTTP transports and session persistence - `src/mcp-engine.ts` and `src/mcp-tools-engine.ts` — APIs for embedding the server Tests mirror the source areas in `tests/unit/` and `tests/integration/`, with fixtures, factories, helpers, and mocks under `tests
1Panel-devAGENTS.md1Panel-dev/MaxKB/AGENTS.md
type-check # vue-tsc ``` Python linting: `ruff` (line-length 120, config in `pyproject.toml`). No test runner is configured; per-app `tests.py` files are empty stubs. Dependencies are managed with
NVIDIAAGENTS.mdNVIDIA/NemoClaw/AGENTS.md
Status: Active development. Interfaces may change without notice. ## Product Scope Gate Technical correctness, passing tests, and green CI do not establish product approval. Before implementing or approving a change that
NVIDIAAGENTS.mdNVIDIA/NemoClaw/.dsh/tools/AGENTS.md
harness, rely on ordinary review and repository hooks, and do not add repository tests or a catalog-specific test framework. 1. Read only the changed tool, this guide
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.
