The problem

You have worked out a good way to ask for something. It takes a paragraph. You will need it
again next week, and you will not remember the wording.

The fix

Most agent tools let you save a request as a command you can run by name. They are usually
just markdown files in a folder in your project, which means they follow the rule from
Lesson 3.7: plain text, in your repo, readable by any tool.

Commands worth having

A review command. Your checklist from Lesson 5.6, as one instruction:

Review the current uncommitted changes against these seven checks:

1. Does it do more than was asked?
2. Are the scheduling rules implemented exactly as written in AGENTS.md?
3. What happens with empty, zero, missing or very large values?
4. Is anything hard-coded that should be a setting?
5. Does any error handling hide an error?
6. Do the tests check the requirement, or just repeat the code?
7. Did any file change that was not part of the task?

Report problems only. Do not fix anything.

“Report problems only, do not fix anything” matters. You want to decide.

A new slice command. Your method from Module 4, saved:

Build the next slice of this feature. Follow these rules:

- Change as little as possible.
- End with something I can run and look at.
- Run npm test before saying you are done.
- Never change a test to make it pass.
- Show me the diff summary when finished.

A “start here” command that reads AGENTS.md, runs the tests, and reports the current
state of the project in three lines. Good first move in any fresh session.

Why this is worth the effort

You are turning a thing you did well once into a thing that happens the same way every time.

That is the whole idea of this module, applied to your own habits instead of the agent’s
knowledge.

Keep them in the project

Not in an account, not in a personal folder. In the repository, committed, so they are
versioned and shared and survive a tool change.

Try this before the next lesson

  1. Create the review command. Run it on your last commit.
  2. Find a request you have typed more than twice. Save it as a command.
  3. Delete a command you thought you would use and never did. Keeping it short matters.
PreviousNext