Make Claude Code follow your rules on its own
Hooks on the lifecycle events, settings.json, JSON input, and responses via exit code and JSON.
The problem
Claude Code does a lot. You only see what it did afterward.
The problems below show up for people who use Claude Code every day. All of them are solved with a hook or a mod, and the program teaches you to make both.
- An rm -rf or a push --force runs before you realize how much damage it does.
- Two sessions edit the same file and one undoes the other's work.
- You don't know how much of the context has filled up until the session compacts.
- The rule you wrote in CLAUDE.md is followed almost always, not always.
- Formatting, notifying, and logging still depend on you remembering to ask.
After the training
By the end of the 4 courses, you will be able to:
Block the dangerous before it runs
Locks with exit 2, reading the command before execution, and allow, ask, and deny decisions.
Build a production plugin
SPEC first, state machine, stop hook with a loop, personas, and a security pass before publishing.
Create your own mod
Manifest, event map, state that survives, bars, panels, buttons, and custom commands.
Test and distribute
claude plugin test, debugging the gotchas, and a final project ready for someone else to install.
Put guards and panels on agents
Autonomy policy, the agent proposes and you approve, and guards with panels in practice.
4 courses in order · 73 lessons and modules
Four courses, from the first hook to the distributed mod.
The area page marks the first two as "before the mods": they teach the hooks and the plugin that the mod uses under the hood. If you already write hooks, you can start at course 3.
- 1
HooksPT · EN · ES
Claude Code hooks
The lifecycle events, locks with exit 2, formatting on save, notifying when done, injecting context at session start, and versioned hooks for the team and CI.
17 modulesOpen course 1 - 2
Plugin
Engineering with Claude Code
From prompt to production plugin: hooks, slash commands, state, SPEC first, fail-open patterns, and a complete plugin built in five prompts.
24 modulesOpen course 2 - 3
Mods
Claude Code mods — technical course
Anatomy of a mod, event and state map, ui.render with bars, panels, and buttons, tests with claude plugin test, and distribution in the final project.
16 modulesOpen course 3 - 4
Guard and panelPT · EN · ES
Agent Runtime
MCP bridges, a browser with policy, a three-role team, a long-running agent with verification, and, in track 4, autonomy policy with guard and panel.
16 modulesOpen course 4
Who it's for
Made for you if
- You use Claude Code every day and want to see what it is doing while it does it.
- You want Claude Code to ask before deleting, force-pushing, or calling a paid service.
- You have a rule that must not be broken and you want it to become code, not a reminder.
- You want to create mods for your team and distribute them with tests.
Not for you yet if
- You have never opened a terminal: start with the From Chat to Agent area.
- You just want to install ready-made mods: the inema-mods and Starter Kit guides cover that without a course.
Included in the training
The 28 ready-made mods come along.
18 INEMA mods in Portuguese and 10 from the Claude Mods Starter Kit, with guides in PT, EN, and ES and prompts that interview you and point you to the right ones. Use the ready-made ones while you study and open each one up to see inside.
Projects and kits
Videos
Why this training
What changes compared to copying mods from the internet.
You understand what you install
A mod runs with your access. After the courses, you read the hooks/ folder and know what each line does.
Verified examples
The technical course was checked against the current version of Claude Code; the mods were tested on Claude Code 2.1.289.
Practice in every lesson
Each hooks lesson closes with a "practice now": a real hook you paste into your project and watch run.
From hook to product
The four courses cover the whole ladder: simple rule, lock, plugin, mod with a screen, and agent with a guard.
Questions
Before you start.
What do I need to get started?
Claude Code installed and a project to test on. Courses 1 and 3 start from zero in hooks and mods.
Do I need to follow the order?
The suggested order is 1 → 4. If you already write hooks, you can go straight to course 3 and come back to course 2 whenever you want to build a complete plugin.
Are a mod and a hook the same thing?
No. A hook runs a command when an event happens. A mod uses those events to change the screen and the workflow: a panel, a banner, a notice, a button.
How long does it take?
There are 73 modules across 4 courses: 17 on hooks, 24 on plugins, 16 on mods, and 16 on Agent Runtime.
What if a mod breaks my Claude Code?
Open it with claude --safe-mode, which starts without plugins, and disable the mod. The area explains the step-by-step process before you install anything.
Your Claude Code can ask before the damage is done and show you what it is doing.
Start with course 1. In 17 modules you write the hooks that become the foundation of every mod.