Simple explanation
Welcome to Bonus Week. You finished the 21-day challenge. Now you go deeper. This week covers the topics that separate good Claude Code users from exceptional ones. Every lesson is written in plain English. No technical jargon. No developer assumptions. Today — Hooks. The most powerful feature most non-developers never find. --- Let's start with a story. Imagine you hire a builder to renovate your house. Every single day — before the builder starts work — you want them to: put on a hard hat, check the safety rules, and take a photo of the current state before changing anything. You could remind them every morning. Or you could put a sign on the front door that they MUST read before entering. Every time. Automatically. Without you being there. That sign is a Hook. --- What is a Hook? A Hook is an automatic rule you set once that runs every single time Claude Code does a specific thing. You do not have to ask. You do not have to remember. It just runs. Every time. Automatically. Examples of what a Hook can do automatically: — Every time Claude Code is about to delete a file — pause and ask you to confirm first. — Every time Claude Code finishes building something — automatically run a check to make sure nothing is broken. — Every time Claude Code writes new text on your site — automatically check the spelling. — Every time Claude Code makes any change at all — automatically save a backup copy. You set these rules once. They run forever. Without you doing anything. --- Why non-developers need Hooks more than anyone. Developers can read code and spot when something looks wrong. You cannot. And that is completely fine. But it means you need a safety net that catches problems automatically — because you will not always spot them yourself. Hooks are that safety net. Think of them as the rules you wish Claude Code followed without you having to repeat them every session. --- The 3 Hooks every non-developer should have. Hook 1 — The Confirmation Hook Rule: Before deleting any file — stop and ask me to confirm. Why: Accidental deletions happen. This gives you one last chance to say no. Hook 2 — The Backup Hook Rule: Before making any change — save a copy of the current file. Why: Even with GitHub branches — a local backup before every change adds an extra layer of safety. Hook 3 — The Spell Check Hook Rule: Every time new text is added to the site — check it for spelling mistakes. Why: Claude Code sometimes writes "teh" instead of "the." This catches it automatically.
What to do
Set up the Confirmation Hook using the copy-paste prompt on this page. Then ask Claude Code to delete a test file. Watch the Hook pause the deletion and ask for your confirmation. Type YES and watch it proceed. Then create a Backup Hook by asking: "Create a Hook that saves a copy of any file before Claude Code modifies it. Save this Hook to .claude/hooks/backup-before-change" To see all your current Hooks at any time, ask: "Show me all the Hooks currently set up in my project and explain what each one does in plain English." You now have two automatic safety rules running in the background of every future session.
Copy-paste prompt
Create a Hook for my project that runs before any file is deleted. The Hook should pause the deletion, show me the file name, and ask me to type YES to confirm before proceeding. Save this Hook to .claude/hooks/confirm-before-delete
Course note
Key takeaway
A Hook is an automatic rule that runs every time Claude Code does something — without you asking. Set them once and they protect you forever. The Confirmation Hook and Backup Hook are the two every non-developer should have from the very start.