The Build Room

The rules hook.

Claude forgets your rules halfway through a long session. This puts them back in front of it on every message you send. Free, two small files.

Download the hook

Put it in

1. In a terminal, inside your project folder, paste curl -fsSL https://the-build-room.pages.dev/free/rules-hook.tar.gz | tar -xzk && cat .claude/settings.json. It adds RULES.md and .claude/settings.json and never overwrites a file you already have. If what it prints has no UserPromptSubmit in it, you already had a settings file: add the block below to it. Or download the zip and copy the two files in by hand; the .claude folder is hidden on a Mac until you press Command, Shift and full stop in Finder.

2. Edit RULES.md. Keep it short. Five rules it follows beats fifty it forgets.

3. Start claude from that folder, or restart it.

4. Give it a small job, like a script that prints 1 to 5, and read how it tells you it's done. With rule 2 in, it pastes what the script printed instead of telling you it worked.

RULES.md

# My rules

1. One thing at a time. Finish it and show me before you start the next.
2. Never say done until you've run it and pasted what it printed.
3. Do only what I asked. If something else needs doing, ask first.
4. Every fact comes from a file or a page you can name. If you can't name it, say you don't know.
5. Never delete, send, publish or push anything without asking me.

.claude/settings.json

{
  "hooks": {
    "UserPromptSubmit": [
      {
        "hooks": [
          { "type": "command", "command": "cat \"$CLAUDE_PROJECT_DIR/RULES.md\"" }
        ]
      }
    ]
  }
}

What it can't do

It keeps your rules in front of Claude. It can't stop Claude breaking one. The hooks that block it outright, like the ones that stop it saying done before the test ran or writing code before the test exists, are part of Architect.

See Architect