agentleFS

AGENTS.md examples from real projects

How real projects brief Codex, Cursor and every other agent that reads AGENTS.md.

Worked for most · soon
jhy0285AGENTS.md

monofield / apps

jhy0285/monofield/apps/AGENTS.md

Follow the root AGENTS.md first. This file only records module-level boundaries for apps/.

66mo agoReviewMountCreate a free account to mount
jhy0285AGENTS.md

monofield / design-templates

jhy0285/monofield/design-templates/AGENTS.md

This directory holds design templates — packaged "shapes" the agent renders into a project artifact (decks, prototypes, image/video/audio templates, …). Each entry is a folder with a SKILL.md (same shape as functional skills) plus rendering side files (example.html, assets/, references/, …). If the entry primarily does work on user input — utilities, briefs, asset packagers, fidelity audits — it belongs under ../skills/ instead. See specs/current/skills-and-design-templates.md for the full split. - Listed under /api/design-templates. The shape mirrors /api/skills (same SkillSummary/SkillDetail types)…

66mo agoReviewMountCreate a free account to mount
jhy0285AGENTS.md

monofield

jhy0285/monofield/.github/AGENTS.md

This directory is still only partially standardized. Several historical workflows and helper locations do not yet follow one uniform shape. Do not copy old patterns blindly. For new work, bug fixes, and cleanup, use the ci.yml + comment.atom.yml + autofix.atom.yml + report.atom.yml + .github/scripts/handoff.py system as the reference topology unless a maintainer explicitly chooses a different boundary. Before changing GitHub automation, read the current versions of: If the change affects cross-workflow behavior, update the topology tests instead of relying only…

66mo agoReviewMountCreate a free account to mount
jhy0285AGENTS.md

monofield / packages

jhy0285/monofield/packages/AGENTS.md

Follow the root AGENTS.md first. This file only records module-level boundaries for packages/.

66mo agoReviewMountCreate a free account to mount
jhy0285AGENTS.md

monofield / plugins

jhy0285/monofield/plugins/AGENTS.md

This directory owns MonoField plugin content and plugin authoring material. For plugin content changes, run: When the daemon CLI is built and available, also validate runnable plugin folders with:

66mo agoReviewMountCreate a free account to mount
jhy0285AGENTS.md

monofield / skills

jhy0285/monofield/skills/AGENTS.md

This directory holds functional skills — capabilities the agent invokes mid-task to do work on user input. Each skill is a folder with a SKILL.md (frontmatter + body) and any side files (assets/, references/, scripts, …) the workflow needs. If the entry primarily renders a design artifact (deck, prototype, image/video/audio template) it belongs under ../design-templates/ instead. See specs/current/skills-and-design-templates.md for the full split. - Listed under /api/skills (functional only). User-imported skills shadow built-in entries with the same frontmatter name. - Asset…

66mo agoReviewMountCreate a free account to mount
jhy0285AGENTS.md

monofield / tools

jhy0285/monofield/tools/AGENTS.md

Follow the root AGENTS.md first. This file only records module-level boundaries for tools/.

66mo agoReviewMountCreate a free account to mount
CLAUDE.md vs AGENTS.md

About AGENTS.md

What is AGENTS.md?

An open format for instructions to coding agents, read by Codex, Cursor and others. Think of it as a README written for agents.

Where does it go?

At the repository root, with more specific files in subdirectories. Agents read the one closest to the file they're editing.

What should it contain?

Setup and test commands, code style, and the rules a new contributor would need to know.

Does Claude Code read it?

Claude Code reads CLAUDE.md. A one-line CLAUDE.md that points at AGENTS.md covers both.