Latebit Io Jean Claude Van Dev
latebit-io-jean-claude-van-dev is a Claude Code plugin for the Build phase that packages hooks, slash commands, and staff-engineer-style roles for architecture, review, refactor, debug, and test work—with strong Go/golan
by latebit-io · github.com/latebit-io/jean-claude-van-dev
Install a staff-engineer style Claude Code configuration with slash commands, hooks, and role presets for architecture, review, refactor, debug, and test workflows—especially when you ship Go services
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install latebit-io-jean-claude-van-dev@latebit-io/jean-claude-van-devBuilt 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:latebit-io/jean-claude-van-dev") and the paste-ready config with skillselion.get_install_config("plugin:latebit-io/jean-claude-van-dev").
What it does
latebit-io-jean-claude-van-dev is a Claude Code plugin bundle marketed as configuration for a high-signal engineering experience. Solo builders and small teams who lean on Claude Code for implementation—not just chat—get structured slash commands, hooks, and rule sets aligned with architecture, code review, refactoring, debugging, and testing. The keyword surface emphasizes Go and golang idioms, staff-engineer judgment, autoquality, and world-class best practices, which makes it a fit when you want the agent to behave like a disciplined backend engineer rather than a generic assistant. Install it when you are actively building or hardening services and want repeatable agent rituals instead of rewriting prompts every session. It is less about shipping a product feature and more about upgrading how Claude Code participates across build and ship work. Pair it with your repo conventions so reviewer and tester flows reinforce your real CI expectations.
Highlights
- Preconfigured Claude Code experience with hooks and slash commands for daily dev
- Role-oriented flows: architect, reviewer, refactorer, debugger, and tester
- Go and golang-focused idiomatic and best-practices keywords baked into the bundle
- Code-review and refactoring commands aimed at staff-engineer quality bar
- Single-plugin bundle (pluginCount: 1) from latebit-io/jean-claude-van-dev
Why builders use it
Generic Claude Code setups waste time re-explaining how you want architecture, review, debug, and test passes to run on every task.
After install, Claude Code follows a consistent killer-dev configuration with role-based commands and hooks so review, refactor, and test loops feel repeatable instead of improvised.
At a glance
- Type - Plugin in Development Tools.
- Adoption - 0 installs, 0 stars, 0 votes.
FAQ
Who is latebit-io-jean-claude-van-dev for?
It is for developers and staff-engineer-minded solo builders who want Claude Code pre-tuned with architecture, review, refactoring, debugging, and testing commands—especially around Go workflows.
When should I use latebit-io-jean-claude-van-dev?
Use it when you start a Claude Code project or refactor cycle and want hooks, rules, and slash workflows to enforce best practices before merge and during debug sessions.
How do I add latebit-io-jean-claude-van-dev to my agent?
Register the latebit-io/jean-claude-van-dev plugin from the Claude Code plugin catalog, enable it for your workspace, then align your project rules with its architect, reviewer, and tester commands.
Comments
Share how you use latebit-io-jean-claude-van-dev, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.