Prompts tagged "AGENTS.md" in the PromptCraft library.
Borrowing the three-layer architecture from buildermethods/agent-os (Standards / Product / Specs): have AI first scan your codebase to extract existing conventions into documented standards, then auto-inject them every time it writes code — so you never have to re-explain the rules.
Two AGENTS.md templates drawn from Ischca/awesome-agents-md (CC0): "minimal" is a five-line checklist you can run with right away, and "advanced" covers five sections — environment, testing, conventions, safety, and example tasks. They let an AI coding agent know the rules the moment it enters your project.
A breakdown of the AGENTS.md actually in use in OpenAI's official codex repository — see how a project with millions of lines of code writes team conventions like formatting, testing, commits, module size limits, and API naming into an instruction file that an AI agent can understand and follow, plus a Traditional Chinese adaptation template you can apply directly to your own project.
The AGENTS.md file from the official agents.md standard project itself, demonstrating what a 'minimal but complete' agent rules file looks like — telling AI to use the dev server instead of building during development, restart after dependency changes, and which commands run lint/test/build — with a directly reusable template.
Distills 14 classic software engineering books (Clean Code, Refactoring, Domain-Driven Design, The Pragmatic Programmer, Working Effectively with Legacy Code, and more) into imperative rule sets you can paste directly into AGENTS.md / CLAUDE.md / Cursor rules, offered in full / mini / nano sizes so you can pick based on your context budget.
Borrows the approach from the 40k-star awesome-cursorrules repo to codify 'how to write for a given tech stack' into a project rule file, so Cursor / Claude Code / Codex always produce code in your conventions instead of generic boilerplate.
Upgrades OpenAI Codex CLI from 'vibe coding' into a controllable engineering agent: layered AGENTS.md, approval and sandbox settings in .codex/config.toml, and Starlark command gating, paired with a five-stage Research → Plan → Execute → Review → Ship workflow.
Has Claude Code scan your repo and produce a tight, verifiable CLAUDE.md project memory file under 200 lines—covering build/test/lint commands, directory structure, conventions, and prohibitions—while routing anything that doesn't belong there into skills or path-scoped rules instead.
Have the agent interview you about your project, then produce a structured, no-fluff AGENTS.md that spells out build/test commands, code style, commit conventions, and off-limits areas in one shot — auto-loaded every time work starts.
Has Codex do a disciplined code review of your git diff across three tracks (correctness bugs / simplification-and-reuse / security), listing each finding with a confidence level and a pastable fix, and explicitly instructed to say so when nothing's wrong instead of manufacturing complaints.
Has Codex write characterization tests for untested legacy code: it first reads and documents what the code 'actually does right now' (bugs included), systematically covers the happy path plus edge cases and error paths, and is strictly forbidden from modifying the code under test.
Has the agent automatically inventory your Cursor project (.cursorrules, .cursor/rules, .cursor/mcp.json), produce a step-by-step migration plan, and generate the corresponding CLAUDE.md or AGENTS.md, slash commands, and MCP config — so you're not stuck 'dumber than Cursor' on day one.
A Definition of Done template you can paste into any coding agent, turning 'what counts as done' into a checklist the agent must self-verify item by item: behavior meets acceptance criteria, tests/lint/typecheck/build all pass (or it states why they didn't run), risky changes come with a rollback plan, and a final 'verification story' is delivered. Puts an end to agents claiming 'done' while everything is actually broken.