LoopEngineering-CrashCourse / shared
AGENTS.md16 starsChanged 4 months agoMITView on GitHub
Building the Loop Engineering Crash Course. Master plan: loop-plan.md (root). Day plans: days-plans/. Current phase: Day 1 (see shared/goal.md).
1 other project uses a version of this.
Adopted by
Most recently taken up by
- ayeshakhalid192007-dev/LoopEngineering-CrashCourseword for word, first seen Jul 16, 2026
Other versions1 project uses a version of this.
Word for word · 1
- ayeshakhalid192007-dev/LoopEngineering-CrashCourse★ 15100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,843 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository20 other files it gives its agents.
- .agents/skills/vercel-composition-patterns/AGENTS.mdAGENTS.md
- .agents/skills/vercel-optimize/AGENTS.mdAGENTS.md
- .agents/skills/vercel-react-best-practices/AGENTS.mdAGENTS.md
- .agents/skills/vercel-react-native-skills/AGENTS.mdAGENTS.md
- .agents/skills/vercel-react-view-transitions/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- deploy-to-vercelSkill
- frontend-designSkill
- skill-creatorSkill
- vercel-cli-with-tokensSkill
- vercel-composition-patternsSkill
- vercel-optimizeSkill
- vercel-react-best-practicesSkill
- vercel-react-native-skillsSkill
- vercel-react-view-transitionsSkill
- web-design-guidelinesSkill
- writing-guidelinesSkill
- loop-budgetSkill
- loop-constraintsSkill
- loop-triageSkill
The file
We split this AGENTS.md into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Write ONLY your own state file.
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
AGENTS.md — Rules for any AI agent in this repo
Project
Building the Loop Engineering Crash Course. Master plan: loop-plan.md (root).
Day plans: days-plans/. Current phase: Day 1 (see shared/goal.md).
Test / verify commands
- Link check:
node scripts/link-check.mjs(manual pass if it doesn't exist yet) - Markdown lint: per
.github/workflows/markdown-lint.yml
Loop conventions
- Rules shared by all loops: root
LOOP.md(binding; no loop may edit it). - Binding constraints: root
loop-constraints.md(read at the start of every run). - Each loop lives in
loops/day1/<loop>/with its ownloop.md+state.md. - Write ONLY your own state file; other loops' folders are read-only.
- Report-only first (L1) before enabling any auto-fix (L2).
- One line appended to
shared/loop-run-log.mdper beat — no silent runs. - Budget:
shared/loop-budget.md; goal and definition of done:shared/goal.md.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.