When you make a game with AI, the numbers end up scattered everywhere.
Attack power in the code, health in the instructions, drop rates somewhere in a chat.
A few days later nobody knows which one is right. Not the AI, not me.
So I made one rule. Numbers live in a single Notion table.
- When planning, I change the values in the table
- The instructions only say “how it works.” No numbers
- Every time Claude Code starts work, it checks the table against the code. If they differ, it tells me first
Now there’s only one place to ask “what was that number again?”
The rules I gave Claude Code (part)
Always do this at the start of a session (every time, no exceptions)
1. Open the tracker page and check the current stage and the latest decision log.
2. Open the current stage's instructions and check the latest content.
3. Read the balance master DB and compare it with the code config.
- If values differ, report to the user first; after confirmation, sync the config to the DB values.
- If you find a hard-coded balance constant, move it into config and register it in the DB.
Instructions describe only "how it works". Numbers come only from the balance master DB.