@vincemask: Many people don’t know when to use Hooks. My rule is simple: anything you find yourself repeatedly reminding Claude about should be taken out of the prompt and handed to a Hook. For example: 1. Formatting code after every edit 2. Running lint/tests before every commit 3. ...

Many people don’t know when to use Hooks. My rule is simple: anything you find yourself repeatedly reminding Claude about should be taken out of the prompt and handed to a Hook. For example: 1. Formatting code after every edit 2. Running lint/tests before every commit 3. Prohibiting modifications to certain directories or config files 4. Automatically checking for type errors after code generation 5. Intercepting and confirming before operating on high-risk files 6. Auto-injecting project context at the start of a session 7. Automatically recording change summaries at the end of a task Prompts are for expressing intent; Hooks are for solidifying rules. The more stable, repetitive, and easy to forget a process is, the more it should be handed over to the environment to execute by default.