A Claude Code plugin marketplace. The rule that shapes it: knowledge lives in each repository; the machinery that reads and grows it lives here. A plugin here never carries facts about one codebase.
| Plugin | What it does |
|---|---|
lode |
Three layers. Memory: lode/ per repo (Lode Coding by fjzeit), with lode/review/ holding accepted review findings as rules. Gate: fresh-context reviewers check the branch diff against the repo's rules and lode, every new test is proven to fail without the change, and a hook refuses any push until the gate has passed. Workflows: /lode:lfg, /lode:review-pr, /lode:finish-prs, /lode:debug-flaky, /lode:tdd, /lode:plan, one copy for every repository, reading lode/workflow.md for what differs. Its Rigor tier (critical, standard or light, per path) sets how much review the gate, /lode:lfg, /lode:review-pr, /lode:finish-prs and /lode:plan buy a change. |
Commit this in the repository's .claude/settings.json; everyone who clones it gets the plugin:
{
"extraKnownMarketplaces": {
"zoolutions": { "source": { "source": "github", "repo": "zoolutions/claude-plugins" } }
},
"enabledPlugins": { "lode@zoolutions": true }
}Then, once per repository, /lode:seed builds the lode, writes lode/workflow.md, leaves the repo's local workflow commands in place as the fallback, and opens the PR that turns the gate on. /lode:seed does that settings edit for you. A repository that already has a lode runs /lode:seed workflow to add the profile.
claude plugin marketplace add zoolutions/claude-plugins
claude plugin install lode@zoolutionsThird-party marketplaces do not auto-update. claude plugin marketplace update zoolutions then claude plugin update lode@zoolutions, or turn on auto-update for this marketplace under /plugin. The checklists in plugins/lode/checklists/ change most often; a repo's gate reads whatever version is installed.
/lode:learn in any repository opens a PR here when a finding applies to more than one codebase. Hand-written PRs follow the same rule: one bullet per PR, in the matching checklist, describing the failing case and the safe direction without naming the repository it came from. Changes to the agents or skills are deliberate and reviewed by a maintainer.