AGENTS.md examples from real projects

DIYgodAGENTS.md

RSSHub

DIYgod/RSSHub/AGENTS.md

Functions**: Always use parentheses around arrow function parameters, even for single parameters. 50. **No Tests for Routes**: Do not write test files for routes under `lib/routes/`. Route tests only encode

No other project uses it yet

mitmproxyAGENTS.md

mitmproxy

mitmproxy/mitmproxy/AGENTS.md

Always use `uv run pytest` and don't run pytest directly. - To run all tests: `uv run tox`. - When adding new source files, additionally run: `uv run tox -e individual

No other project uses it yet

danny-avilaAGENTS.md

LibreChat

danny-avila/LibreChat/AGENTS.md

reject what is obsolete in a reply that says why. After each round: focused tests, `npx tsc --noEmit` in every workspace you changed, push, then request the next review naming

files-communityAGENTS.md

Files

files-community/Files/AGENTS.md

runtime CsWin32 APIs to `src/Files.Storage/NativeMethods.txt` or the owning app project's `NativeMethods.txt`, and keep test-only APIs in the relevant test project's `NativeMethods.txt`; do not edit generated CsWin32 output

No other project uses it yet

sickn33AGENTS.md

agentic-awesome-skills

sickn33/agentic-awesome-skills/AGENTS.md

docs/`; localized docs live in `docs_zh-CN/` and `docs/vietnamese/`. Maintenance scripts and tests are in `tools/scripts/` and `tools/scripts/tests/`. The hosted catalog app is in `apps/web-app/`. Registry outputs such

No other project uses it yet

streamlitAGENTS.md

streamlit

streamlit/streamlit/AGENTS.md

widgets. - `streamlit/runtime/`: App runtime and execution logic. - `streamlit/web/`: Web server and CLI implementation - `tests`: Python unit tests (pytest). - `frontend/`: All frontend code and assets. - `app/`: Streamlit application UI. - `lib/`: Shared

No other project uses it yet

streamlitAGENTS.md

streamlit / agents

streamlit/streamlit/.claude/agents/AGENTS.md

failures, resolve merge conflicts with the base branch, and address PR review comments | | `qa-testing-feature` | QA test features using Playwright | | `reviewing-local-changes` | Code review for quality, security, best

No other project uses it yet

streamlitAGENTS.md

streamlit / e2e_playwright

streamlit/streamlit/e2e_playwright/AGENTS.md

Streamlit E2E Tests We use playwright with pytest to e2e test Streamlit library. E2E tests verify the complete Streamlit system (frontend, backend, communication, state, visual appearance) from a user

No other project uses it yet

streamlitAGENTS.md

streamlit / frontend

streamlit/streamlit/frontend/AGENTS.md

Formatter: oxfmt v0.x - Framework: React v18 - Styling: @emotion/styled v11 - Build tool: vite v8 - Testing: vitest v5 & react testing library v16 - Package manager: yarn v4 with workspaces ## Key TypeScript Principles - Prefer

No other project uses it yet

streamlitAGENTS.md

streamlit / lib

streamlit/streamlit/lib/AGENTS.md

root `pyproject.toml`) - Type Checker: mypy 2.x + ty 0.x (config in root `pyproject.toml`) - Testing: pytest 9.x (config in root `pyproject.toml`) ## Key Principles - PEP 8 Compliance: Adhere

No other project uses it yet

streamlitAGENTS.md

streamlit / scripts

streamlit/streamlit/scripts/AGENTS.md

Scripts should be either Python (preferred) or Bash (`.sh`). - Python scripts do not require tests, but should follow the best practices defined in lib/AGENTS.md. - Keep scripts focused on a single

No other project uses it yet

LeafletAGENTS.md

Leaflet

Leaflet/Leaflet/AGENTS.md

public options, methods and events as user-facing docs. Indent with tabs. ## Commands - `npm test -- spec/suites/path/to/FooSpec.js`: run one spec file (specs run in real browsers through Vitest). `npm test` runs

No other project uses it yet

mifiAGENTS.md

lossless-cut

mifi/lossless-cut/AGENTS.md

describing the impact for users in one line. Omit it for internal changes (refactors, tests, CI, dependency bumps). ``` Validate --settings-json with zod ... Changelog: `--settings-json` is now validated; invalid

No other project uses it yet

SentryAGENTS.md

sentry

getsentry/sentry/AGENTS.md

Prefix the full relative path, or source the activate script: ```bash cd /path/to/sentry && .venv/bin/pytest tests/... cd /path/to/sentry && source .venv/bin/activate && pytest tests/... ``` For AI agents: always use `required_permissions

No other project uses it yet

SentryAGENTS.md

sentry / src

getsentry/sentry/src/AGENTS.md

Backend Development Guide > For setup, lint, and test commands, see the "Command Execution Guide" section in `/AGENTS.md` in the repository root. ## Security Guidelines ### Preventing Indirect Object References (IDOR) Multi-tenant

No other project uses it yet

SentryAGENTS.md

sentry / static

getsentry/sentry/static/AGENTS.md

Frontend Development Guide > For critical commands and testing rules, see the "Command Execution Guide" section in `/AGENTS.md` in the repository root. ## Frontend Tech Stack - **Language**: TypeScript - **Framework**: React 19 - **Build

No other project uses it yet

SentryAGENTS.md

sentry / tests

getsentry/sentry/tests/AGENTS.md

Python Testing Guide > For test commands (`make test-selective`, `pytest`), see the "Command Execution Guide" section in `/AGENTS.md` in the repository root. > > This guide covers Python tests. For frontend React/TypeScript

No other project uses it yet

ColorlibHQAGENTS.md

AdminLTE

ColorlibHQ/AdminLTE/AGENTS.md

other static assets. - `src/config/`: Rollup, Astro, PostCSS, and asset-build configuration. - `tests/unit/`: unit tests and shared setup; `tests/a11y.mjs` checks built pages. - `dist/` and `src/html/public/`: generated output. Edit source files; exclude

No other project uses it yet

logseqAGENTS.md

logseq

logseq/logseq/AGENTS.md

Repository Guidelines ## Build, Test, and Development Commands - `bb dev:lint-and-test` runs linters and unit tests. - `bb dev:test -v <namespace/testcase-name>` runs a single unit test (example

No other project uses it yet

logseqAGENTS.md

logseq / cli

logseq/logseq/cli/AGENTS.md

methods to cast types. - Platform-specific code must only appear under `lib/platform/`. - Only keep test cases related to business logic. - Do not keep temporary tests added during refactoring

No other project uses it yet