mlx
ml-explore/mlx/AGENTS.md
sorry, I cannot reply to the reviewers. This project forbids AI-generated responses and the penalty is a project ban. ## Code standards - Keep code comments concise (usually 1-2 lines
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.
ml-explore/mlx/AGENTS.md
sorry, I cannot reply to the reviewers. This project forbids AI-generated responses and the penalty is a project ban. ## Code standards - Keep code comments concise (usually 1-2 lines
QwenLM/qwen-code/AGENTS.md
full workflow: investigate, design, test plan, dry-run, implement, verify, self-audit, code review, and iterate. ### Bugfix Use the `/bugfix` skill for the reproduce-first workflow: reproduce, fix, verify, test
Steady3 mentions in 2 weeks
No other project uses it yet
invoke-ai/InvokeAI/AGENTS.md
configured vendored-code exclusions. - Focused tests: `uv run --no-sync pytest `. Never start a suite during a generation. - Pick checks by behavior. Run required milestone gates before review. Rerun unchanged
reflex-dev/reflex/AGENTS.md
sloppy/spaghetti code — every feature/fix must be clearly understood first. 2. **Bugfixes:** write a regression test that fails before writing the fix. 3. **After implementation:** act as an adversarial reviewer. Scrutinize
manaflow-ai/cmux/cmux-browser/AGENTS.md
derived files retain GPL-3.0-only provenance and the exact source revision. Helium-derived code is not available under Manaflow's commercial license. - Other bundled dependencies retain their own terms
manaflow-ai/cmux/web/AGENTS.md
request. Do not add a broad disable or raise the limit to accept new code. Lower the limit in a separate cleanup wave as the remaining debt is removed
1 project uses a version of this
steveyegge/beads/engdocs/AGENTS.md
EXTENDING.md`, `INTEGRATION_CHARTER.md` | Extension and integration boundaries. | | `AGENT_SIGNING.md` | Signatures for agent-prepared commits, comments, and reviews. | | `design/` | Design documents for subsystems (Dolt concurrency, `bd serve`, ownership hand-off, …). | | `adr/` | Architecture decision
1 project uses a version of this
OtterMind/Chat2DB/AGENTS.md
branch, workflow run, image, release, or artifact identifier, including partial or failed actions. For code review, report findings first in severity order with `file:line`, the affected runtime surface
bagisto/bagisto/AGENTS.md
pest-testing` | | Playwright end-to-end tests | `bagisto-playwright-testing` | | Reviewing a change | `bagisto-code-review` | | Branching, commits, CHANGELOG, PRs | `bagisto-git-workflow` | | The REST/GraphQL API | `bagisto-api-develop` / `bagisto
Kilo-Org/kilocode/AGENTS.md
reach for `let`. ### Naming Enforcement (Read This) THIS RULE IS MANDATORY FOR AGENT WRITTEN CODE. - Use single word names by default for new locals, params, and helper functions. - Multi-word
No other project uses it yet
element-plus/element-plus/AGENTS.md
AGENTS.md Guidance for coding agents working in this repository. ## Project Overview Element Plus is a Vue 3 UI component library written in TypeScript. This repo is a pnpm workspace monorepo
No other project uses it yet
Wox-launcher/Wox/AGENTS.md
with 100% certainty, you can start by adding log statements to the relevant code and reviewing the logs to identify the problem. The log output should contain sufficient information
eslint/eslint/AGENTS.md
tests and reviews enforce them. - `bin/eslint.js` → `lib/cli.js` → `lib/eslint/eslint.js` → `lib/linter/linter.js` → `lib/rules/*.js` - **`lib/cli.js`** is the only place that reads argv, writes to the console, and sets exit codes
icsharpcode/ILSpy/AGENTS.md
Debug Steps pane), so run it from a local build, not the installed tool. ## Code review - **A PR review and exploratory testing are different jobs.** A review is scoped
No other project uses it yet
every-app/open-seo/AGENTS.md
controls that keep reviewers from flagging intentional behavior. After a merge-ready or other code review verifies a finding, add to that file only when the finding exposes a recurring
Steady10 mentions in 2 weeks
1 project uses a version of this
microsoft/winget-cli/AGENTS.md
open a pull request or link a branch when code is available. ## Pull requests Before opening a pull request: 1. Review `CONTRIBUTING.md` and follow the repository PR template. 2. Keep
apache/flink/AGENTS.md
tests that do not exercise the change, padded commit messages) will be closed without review ## Code Review Guidelines When reviewing a PR or diff against this repo: - Look for opportunities
rollup/rollup/AGENTS.md
manually write the pull request in their own words to show they care. ## Code Review Focus - **Ignore style/linting issues** in test sample files (`test/*/samples/`) except for `_config.js` files - Test
goauthentik/authentik/website/AGENTS.md
tightly as possible for a true one-off: ` ` in Markdown/MDX (`// spellchecker:ignore ...` in code), or ` ` for a single line. Never disable the checker for a whole page. ## Deployment Deployment
No other project uses it yet
vapor/vapor/AGENTS.md
tools (Copilot, Claude, Cursor, etc.) to help write or refine code is fine, but a human must understand, review, and take responsibility for every change in the PR. - **Fully automated
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.