Jwilger Claude Code Plugins
jwilger-claude-code-plugins is a Claude Code plugin marketplace for the Build phase that bundles architecture, TDD, review, and debugging workflows for a global agent setup.
by jwilger · github.com/jwilger/claude-code-plugins
Install a curated global Claude Code stack that enforces TDD, ADRs, event modeling, code review, and debugging rituals across every project.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install jwilger-claude-code-plugins@jwilger/claude-code-pluginsBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:jwilger/claude-code-plugins") and the paste-ready config with skillselion.get_install_config("plugin:jwilger/claude-code-plugins").
What it does
jwilger-claude-code-plugins is a small community marketplace that packages what one builder actually runs in global Claude Code: architecture discipline, test-driven habits, and review-oriented hooks rather than a single integration. Solo makers who want the agent to respect ADRs, event models, and structured debugging install it to mirror a mature SDLC inside the editor. The two plugins span bootstrap scaffolding, GitHub and worktree workflows, todo enforcement, and language-agnostic modeling helpers described in the keyword set. It suits builders who already treat Claude as a pair programmer and want compile-time and review gates baked into sessions, not one-off prompts. Expect intermediate familiarity with Claude Code plugins, hooks, and optional Nix-based environments. It is not a turnkey SaaS template; it is personal opinionated tooling you adopt wholesale or cherry-pick patterns from.
Highlights
- Two-plugin bundle from a maintainer’s live global Claude Code setup
- Workflow coverage: TDD, ADRs, event modeling, domain modeling, and SDLc-style gates
- Code review, mutation-testing, and compile-time-enforcement hooks
- Nix flake and devshell keywords for reproducible dev environments
- Marvin personality and intelligent debugging-oriented agent styling
Why builders use it
Solo builders lose consistency when every session reinvents how the agent handles ADRs, tests, reviews, and debugging.
After registering the marketplace, Claude Code can follow the maintainer’s enforced workflows, hooks, and modeling rituals across repos and worktrees.
At a glance
- Type - Plugin in Development Tools.
- Adoption - 0 installs, 7 stars, 0 votes.
FAQ
Who is jwilger-claude-code-plugins for?
Claude Code users who want a maintainer-tested global plugin set covering architecture decisions, TDD, review, and debugging rather than assembling skills one by one.
When should I use jwilger-claude-code-plugins?
Use it when you are standardizing how Claude behaves across projects—especially if you care about ADRs, event modeling, mutation testing, and todo enforcement.
How do I add jwilger-claude-code-plugins to my agent?
Add the jwilger/claude-code-plugins repository as a Claude Code plugin marketplace source, then enable the two bundled plugins from your global or project settings.
Comments
Share how you use jwilger-claude-code-plugins, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.