Your coding agent is a capable generalist. It has not spent years in your framework, your niche or closed source enterprise software. Well Actually brings what the experts there have learned into your agent.
Not hard rules like a linter. Advice, like an expert glancing over a diff who has seen a pattern go wrong twenty times: it is most likely wrong again, and there is a better way. Your agent hears it and decides.
Follow the experts you trust and they join your advisory board. Each of their principles is advice plus a detector that runs sandboxed on every edit. Unlike a rules file, nothing sits in your agent's context up front: the advice only enters it when the detector fires, right when it matters.
The plugin needs Node 20 or newer. In Claude Code, turn on auto-update in /plugin, Marketplaces, wellactually. The install guide explains each step.
An example. Yours is made of the experts whose principles you put on your advisory board, and your agent hears from them while it works.
Every hook event your agent fires runs the detectors listening to it. Only a finding puts the advice in your agent's context.
Avoid late. Make name nullable or set it in the constructor.from @passsy/avoid-late
Advice lands here only when a detector finds something.
Turn the advice you keep giving in code reviews into a principle that runs inside other people's agents. The guide takes you from an idea to a released principle, in the browser or in your editor.
Anything else is in the docs.
Well actually,Then your agent sees both and decides. When two principles fire on the same change, their advice arrives side by side, each signed by the expert who wrote it. Advice is never an order, so your agent weighs both against your task and your code, like a developer does when two senior colleagues disagree.
It rarely comes up. A detector is code that looks for something specific, and two experts writing detectors that fire on the same line with opposite advice is unlikely.
And when a principle keeps getting in your way, switch it off on your advisory board, for one project or for your whole machine.
Well actually,Then your agent sees both and decides. When two principles fire on the same change, their advice arrives side by side, each signed by the expert who wrote it. Advice is never an order, so your agent weighs both against your task and your code, like a developer does when two senior colleagues disagree.
It rarely comes up. A detector is code that looks for something specific, and two experts writing detectors that fire on the same line with opposite advice is unlikely.
And when a principle keeps getting in your way, switch it off on your advisory board, for one project or for your whole machine.
wellactually
