AGENTS.md examples from real projects

serverlessReads credentialsAGENTS.md

serverless

serverless/serverless/AGENTS.md

call sites. Keep `esbuild` listed in `external` in `packages/sf-core/esbuild.js` — bundling esbuild's own code breaks the worker it spawns (see the comment there). `packages/framework-dist` is an empty shell

No other project uses it yet

files-communityAGENTS.md

Files

files-community/Files/AGENTS.md

changes, run the focused build that can prove it and report anything left unverified. ## Code Review Rules ### Native interop - Reject new uses of `DllImport`. Prefer existing interop wrappers or CsWin32

sickn33AGENTS.md

agentic-awesome-skills

sickn33/agentic-awesome-skills/AGENTS.md

Before PRs, run `npm run validate && npm run test && npm run security:docs`. ## Coding Style & Naming Conventions Use Markdown for skills and docs, JavaScript/Node for most tooling, and Python

No other project uses it yet

streamlitAGENTS.md

streamlit

streamlit/streamlit/AGENTS.md

short doc note, or leaving the code as is. Security issues and data loss still need a real fix. This applies to review feedback too: a reviewer, human

No other project uses it yet

streamlitAGENTS.md

streamlit / agents

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

review comments | | `qa-testing-feature` | QA test features using Playwright | | `reviewing-local-changes` | Code review for quality, security, best practices, and product/API alignment | | `simplifying-local-changes` | Simplify and refine code

No other project uses it yet

streamlitAGENTS.md

streamlit / skills

streamlit/streamlit/.claude/skills/AGENTS.md

third person** in descriptions (e.g., "Validates code changes" not "I validate code changes") - **Keep file references one level deep** from SKILL.md - **Use sentence casing** for titles and headers - Capitalize only

No other project uses it yet

streamlitAGENTS.md

streamlit / frontend

streamlit/streamlit/frontend/AGENTS.md

Data fetching without race protection (stale response can overwrite newer data). ### Rewrite patterns (preferred code) - Derived value during render: ```tsx // ❌ Avoid // const [fullName, setFullName] = useState("") // useEffect(() => setFullName(`${firstName} ${lastName}`), [firstName

No other project uses it yet

streamlitReads credentialsAGENTS.md

streamlit / workflows

streamlit/streamlit/.github/workflows/AGENTS.md

Description | |----------|---------|-------------| | `ai-pr-review.yml` | `ai-review`/`ai-final-review` label or manual | AI-powered code and product-alignment review using Cursor CLI | | `ai-qa-testing.yml` | `ai-qa-test` label or manual | AI-powered

streamlitAGENTS.md

streamlit / specs

streamlit/streamlit/specs/AGENTS.md

template 3. Create PR titled `[spec] Feature name` (keep in Draft until ready for review) ## Spec Guidelines ### Problem First, Solution Second Never start with what you want to build. Start

payloadcmsReads credentialsAGENTS.md

payload

payloadcms/payload/AGENTS.md

state who is affected and what to do, with a `diff` block when user code changes. Without the section, the release notes show the first paragraph of the body. ## Additional

amruthpillaiReads credentialsAGENTS.md

reactive-resume

amruthpillai/reactive-resume/AGENTS.md

package name and export map, never through a `src` path or path alias. Runtime-specific code sits behind explicit subpaths (`@reactive-resume/pdf/browser`, `@reactive-resume/pdf/server`, `@reactive-resume/env/server`); root exports

SentryAGENTS.md

sentry

getsentry/sentry/AGENTS.md

user requests like PR review, branch audit, and Warden follow-up. - If a downstream review harness controls the final response shape, do not hardcode a competing output format

No other project uses it yet

ColorlibHQAGENTS.md

AdminLTE

ColorlibHQ/AdminLTE/AGENTS.md

indentation, UTF-8, LF endings, and final newlines as defined in `.editorconfig`. Follow neighboring code and repository ESLint/Stylelint rules. Prettier is configured with single quotes, semicolons, and a 100-character

No other project uses it yet

logseqAGENTS.md

logseq

logseq/logseq/AGENTS.md

bodies, trailers, branch names, PR titles, or PR descriptions. - PR titles must describe the code change only. - Before creating or updating commits or PRs, verify that the generated metadata does

No other project uses it yet

AmruthPillaiReads credentialsAGENTS.md

Reactive-Resume

AmruthPillai/Reactive-Resume/AGENTS.md

package name and export map, never through a `src` path or path alias. Runtime-specific code sits behind explicit subpaths (`@reactive-resume/pdf/browser`, `@reactive-resume/pdf/server`, `@reactive-resume/env/server`); root exports

meteorAGENTS.md

meteor

meteor/meteor/AGENTS.md

codebase](.github/skills/codebase/SKILL.md) | Build system, CLI, isobuild, tools/ directory | | [conventions](.github/skills/conventions/SKILL.md) | Writing packages, CLI commands, code patterns | | [testing](.github/skills/testing/SKILL.md) | Writing tests, debugging failures, test infrastructure | | [packages](.github/skills/packages/SKILL.md) | Finding packages by feature

No other project uses it yet

K-Dense-AIReads credentialsAGENTS.md

scientific-agent-skills

K-Dense-AI/scientific-agent-skills/AGENTS.md

scripts/`, or `assets/` only when they earn their place. 4. Run the commands and code you document. Scope claims to the release you actually tested ("targets stable GeoPandas

apacheAGENTS.md

spark

apache/spark/AGENTS.md

Apache Spark ## Pre-flight Checks Before the first code edit or running test in a session, ensure a clean working environment. DO NOT skip these checks: 1. Run `git remote

No other project uses it yet

Niko1221AGENTS.md

Strata

Niko1221/Strata/AGENTS.md

server ([docs/MCP_SERVER.md](docs/MCP_SERVER.md)) offers the same steps as tools. ## Working on the code - How the engine works, every measured number, the API and all settings: [docs/DETAILS.md](docs/DETAILS.md) and the [paper

colinhacksDeletes or force-pushesAGENTS.md

zod

colinhacks/zod/AGENTS.md

review the maintainer's changes — they are final, not a proposal. Don't thank them for "letting" the maintainer rewrite their work. - When posting comments with code samples

No other project uses it yet