workerd / jsg
cloudflare/workerd/src/workerd/jsg/AGENTS.md
unvisited fields across the codebase, enforcing invariants 1 and 2 at build time. ## CODE REVIEW RULE When reviewing changes to JSG code, check whether the change requires updates
How real projects brief Codex, Cursor and every other agent that reads AGENTS.md.
cloudflare/workerd/src/workerd/jsg/AGENTS.md
unvisited fields across the codebase, enforcing invariants 1 and 2 at build time. ## CODE REVIEW RULE When reviewing changes to JSG code, check whether the change requires updates
apify/apify-mcp-server/AGENTS.md
handle similar cases. Ask: "Am I adding code, or fixing the code that's already there?" - **Self-review your diff.** Before declaring done, review: Is this the minimal
freecodexyz/free-code/AGENTS.md
MUST** review every stored reference and asynchronous callback for lifetime, every resource for one clear owner, and every interface for explicit copy/move/ borrow semantics. - **MUST NOT** approve code merely because
mongodb/mongo-go-driver/AGENTS.md
AGENTS.md This file provides guidance to AI agents when working with code in this repository. ## Project Official MongoDB Go Driver (`go.mongodb.org/mongo-driver/v2`). Correctness, backward compatibility, and conformance to [MongoDB Driver
strands-agents/harness-sdk/AGENTS.md
writer`, `pr-feedback`), docs (`docs-writer`, `docs-reviewer`, `docs-audit`, `docs-planner`), and code review (`strands-review`). See [`.agents/skills/README.md`](./.agents/skills/README.md) for what each does and when
strands-agents/harness-sdk/site/AGENTS.md
work", "what docs need writing" | When authoring or reviewing documentation pages, follow the voice guide and the terminology lock. When verifying code examples in docs, follow the tiered procedure
strands-agents/harness-sdk/strands-py/AGENTS.md
means exactly that: no tool catches it, so it is on you and the reviewer. ## Coding Patterns and Best Practices ### Logging Structured logging is a cross-SDK rule
strands-agents/harness-sdk/strands-ts/AGENTS.md
reviewer. ### 5. Testing Guidelines When writing tests, you **MUST** follow the guidelines in [docs/TESTING.md](./docs/TESTING.md); see [Testing](#testing) below. ## Coding Patterns and Best Practices ### Logging Structured logging is a cross
strands-agents/harness-sdk/test-infra/AGENTS.md
package) - Running most integration tests (they don't need provisioned infra) - Reviewing or modifying SDK code, docs, tools, or CLI - Opening a PR — CI runs infrastructure-dependent tests automatically against
max-sixty/worktrunk/AGENTS.md
cargo run -- hook pre-merge --yes for the project test and lint gate. Claude Code web first runs task setup-web; Codex Cloud uses .codex/cloud.sh. Test and coverage recipes live
max-sixty/worktrunk/docs/AGENTS.md
checks built links. Use root-relative links and asset paths. Starlight owns navigation, search, code frames, copy controls, and theme selection; keep overrides narrow. The design uses warm paper, dark
maximhq/bifrost/AGENTS.md
# AGENTS.md — Bifrost AI Gateway > Context for AI agents (Claude Code, Copilot, Cursor, etc.) working
OpenCoworkAI/open-codesign/AGENTS.md
another preset. ### Built-In Starters And Scaffolds - Treat starter/scaffold assets as product code, not prompt filler. Review the actual file contents as well as the manifest before changing or adding
logancyang/obsidian-copilot/AGENTS.md
running a multi-step dev session | [`designdocs/agents/PROCESS_GUIDE.md`](./designdocs/agents/PROCESS_GUIDE.md) | | changing user-facing behavior | [`designdocs/agents/DOCS_GUIDE.md`](./designdocs/agents/DOCS_GUIDE.md) | | reviewing code or preparing an Obsidian submission | [`designdocs/OBSIDIAN_COMMUNITY_REVIEW.md`](./designdocs/OBSIDIAN_COMMUNITY_REVIEW.md) | ## Important notes - The plugin supports multiple
vercel-labs/native/AGENTS.md
Cmd.request`; do not import a service from the core. Do not add Zig app code unless the user explicitly chooses `--template zig-core` or the feature requires a toolkit extension
Gentleman-Programming/gentle-ai/AGENTS.md
Index When working on this project, load the relevant skill(s) BEFORE writing any code. Naming convention: `gentle-ai-*` skills are repo-specific workflow skills. Unprefixed skills are portable writing
Gentleman-Programming/gentle-ai/docs/agents.md
review hooks | | OpenCode | `opencode` | Native task subagents, skills, MCP, managed review plugins and optional background policy | | Kilo Code | `kilocode` | OpenCode-compatible configuration, skills and MCP | | Gemini CLI | `gemini-cli` | Experimental
trailofbits/skills/AGENTS.md
guarantee: - **the two loadability checks**, which need the Claude Code and Codex CLIs installed - **review-walkthrough's browser checks**, which need Chrome or Chromium. Run `node plugins/review-walkthrough/tests/browser-check.mjs /path/to/chromium` locally
NVIDIA/warp/AGENTS.md
files. Rebuild native libraries only after changes to `warp/native/` C++/CUDA code: - Standard build: `uv run build_lib.py` (~5 min) - Quick build: `uv run build_lib.py --quick` (~2-4 min) - Only
tw93/Waza/AGENTS.md
constraints should be extracted from public repository context or user-provided task context. - Treat `code-review` as an invocation alias for Waza `check`, not as a separate generic skill. - Skill
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.