Guard rails for Claude Code. Claude types fast; you decide what ships.
INSTALL
claude plugin marketplace add leandrodalbo/claudio-pluginclaude plugin install claudio@claudio-pluginNeeds Claude Code, git and Python 3.11+. Then run /claudio:init in your project.
ClaudioXP is for software engineers who want AI's speed and keep responsibility for what they ship.
It guides an engineer; it does not stand in for one. If you can't judge a change, ClaudioXP can't help you.
Object-oriented, functional or structured, and why.
Bring the engineering know-how, and ask Claude to explain the language as you go.
Every cycle stops for your decision: the spec, the tests, the review, the commit.
Code is cheap now. What counts is the right problem, solved well.
New tools are here. Use them, keep the craft, and keep creating value.
You judge every change. Your experience is what makes the result good.
ClaudioXP is free and open source. It gets better with every engineer who uses it.
Discord
Ask questions and share how you use it.
X @claudioxpplugin
News and new releases.
GitHub
Star the repo, open an issue, send a pull request, or share the rules you add to your copy.
Free and open source, Apache 2.0.
Extreme Programming gave us small steps, tests first and fast feedback. Claude gives us speed. ClaudioXP brings them together, so you don't have to choose.
Claude writes the code fast: the tests you agreed, the implementation, the clean-up.
Test first, small steps, refactor. The habits from XP, built into every cycle.
You move every phase and you make every commit. You decide what ships.
Work moves in small cycles. Each phase lets Claude do one kind of work, and only you move on. Open a phase to see what it allows.
Once per plan
↻ Every cycle
Each cycle in the plan has a type. The type sets the route.
The full loop. RED expects new tests that fail.
The full loop. RED expects tests for what already works, that pass.
No RED. Tests stay locked the whole cycle.
Only you can skip, and only REVIEW and REFACTOR.
At every phase, Claude gets the craft experienced engineers use. Not as a tip in a prompt, but as rules it reads before it writes.
Test first, behaviour in plain words, small steps and fast feedback.
Names that say what they do, short functions, code the next person can change.
Business rules free of details. Dependencies point inward.
Five checks on coupling and cohesion, run on every change.
The simplest thing that works, one source for each rule, nothing “for later”.
Used when the problem asks for one, with the signs it's overkill.
Tests that make change safe and can't go stale.
Safe by default: inputs checked, nothing outside the project touched, no secrets.
Read when the work needs it
Correct Claude once, and it offers to write the rule down, with the date: in your project's CLAUDE.md, or in your own copy of the skill if you install from a clone. Rules that help everyone? Send them as an issue.
You keep the speed, and your judgement decides what ships. This is how ClaudioXP makes that hold.
Hooks block the wrong move before it happens: files outside the plan, tests outside RED, tests changed in GREEN or REFACTOR.
What Claude sees
Tests are locked in GREEN, and tests/test_order.py is a test file. Go back to RED to change a test.RED, GREEN and REFACTOR end only when your test command gives the right result. Claude saying “done” is not enough.
Claude can't move the phase or write to git. The hooks stop it, so the plan, the spec, the review and the commit stay yours.
One plan, one cycle, one change you can really read.
The craft is there at every step, and your corrections become rules.
Guard rails, not a sandbox. Tests prove behaviour, not design, so REVIEW is still a person reading the change.
Real sessions in a real project. Pick your language, then press play.
The tests already pass, so RED refuses to move on.
In GREEN, a passing test suddenly fails. Claude finds the line that changed, fixes the code, not the test, and tells you.
Claude proposes the behaviour; nothing changes until you agree.
You read the change and decide what gets fixed.
From the spec to the commit, start to finish.