What you are doing

Turning Recall into a project that a fresh agent can work on well, with no explanation from
you.

Step 1 — Write AGENTS.md

Use the example in Lesson 6.2 as a starting point, but write yours from your own project.
Include:

  • What the project is, in two sentences.
  • The commands to run and test it.
  • Where things live.
  • The scheduling rules, marked as not changeable without asking.
  • Your rules, each one earned by something that actually happened.
  • What is deliberately not in the project.

Keep it to one page.

Step 2 — Make one command check everything

npm test

Type check, lint, tests. If it is not all behind one command, the agent will not run all of
it.

Step 3 — Add your review command

From Lesson 6.6. Commit it with the project.

Step 4 — The real test

This is the part that matters, and it is why this lab exists.

Start a completely fresh session. Give it a task cold, with no explanation:

Add a page at /stats showing three numbers: total cards, cards due today,
and cards reviewed today.

Say nothing else. No context, no rules, no reminders.

What to watch

Question Yes or no
Did it read AGENTS.md on its own?
Did it follow your file layout?
Did it use plain HTML and CSS, without being told?
Did it avoid adding libraries?
Did it run npm test before saying it was done?
Did it write a test?
Did it work on a 390 pixel screen?

Reading your results

Mostly yes. Your rules file works. This is what “ready for agents” means, and you can
now hand work over with much less typing.

Mostly no. Do not add more rules yet. Find out why. Usually one of:

  • The rule was a feeling, not something checkable (Lesson 6.3).
  • The file is too long and the important lines are buried.
  • The rule is in a document the agent never reads.

Some yes, some no. Normal. Fix the specific misses, one line each. That is how the file
is supposed to grow.

Step 5 — Commit

npm test
git add -A
git commit -m "AGENTS.md, review command, one-command checks"

Before Module 7

  1. Complete the table honestly. A “no” is information, not failure.
  2. Fix your two worst misses and run the cold test again with a different task.
  3. Read AGENTS.md once more and cut any line that has never actually mattered.
PreviousNext