Written by someone who needed it first.

Alexandre Mallet

Senior software craftsman, founder of BULDEE, based in France. Fifteen years and more of production systems, mostly Symfony and PHP on the back, React and TypeScript on the front, and for the last stretch a great deal of time spent watching what happens when a language model is allowed to write into a real codebase.

github.com/woprrr, an account that has been open since 2014 and whose history is public. That link is the point of this page: you should be able to check the person telling you their code is disciplined.

Why this exists

The rules this plugin enforces were a personal CLAUDE.md first. They worked, for a while, in the way an instruction works: the model read them, agreed with them, and followed them until the context filled up or the task got long. Around the tenth file of a refactor, the domain layer would quietly acquire an import it should not have, and the answer to "why did you do that" was always reasonable and always too late.

That is not a discipline problem, and it is not a prompt problem. Nothing in the loop was checking. So the rules moved out of the paragraph and into a hook, then into the CI, then into a committed baseline that cannot loosen without someone writing down why. Everything this plugin does grew from that one observation.

How to check this page

As of 11 August 2026, the plugin carries 457 commits, of which 449 are mine. It is Apache 2.0 and the entire history is at github.com/BULDEE/ai-craftsman-superpowers: the rules, the tests, the ADRs recording decisions that were later reversed, and a CHANGELOG that documents the plugin's own defects in more detail than most projects document their features.

That CHANGELOG is the honest measure of what is here. It says, in writing, that a static analysis adapter ran for months without ever producing a verdict, that a review command returned nothing at all one run in two, and that a test suite trained the learning loop on its own fixtures. Those are not entries a project writes to look good. They are what it looks like when the person who built the gate keeps walking into it.

Getting in touch

contact@buldee.com for anything about the plugin, the packs, or an engagement. Bugs, questions and disagreements are better asissues, where the answer helps the next person too.

If you write a pack for a stack that has none, say so. Right now the packs that ship cover the stacks I work in, which is exactly the limitation an ecosystem is supposed to fix.