Mike Coulbourn Claude Vibes
mike-coulbourn-claude-vibes is a Claude Code plugin for the Build phase that bundles production-grade vibe coding workflows from discovery through deployment.
by mike-coulbourn · github.com/mike-coulbourn/claude-vibes
Install one plugin that gives structured vibe-coding workflows from discovery through refactor and deployment inside Claude Code.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install mike-coulbourn-claude-vibes@mike-coulbourn/claude-vibesBuilt 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:mike-coulbourn/claude-vibes") and the paste-ready config with skillselion.get_install_config("plugin:mike-coulbourn/claude-vibes").
What it does
mike-coulbourn-claude-vibes is a Claude Code plugin marketed as a production-grade vibe coding suite with structured workflows from discovery to deployment. Solo and indie builders install it when they want Claude Code to behave like a coherent toolchain—commands, agents, and related servers—rather than a loose collection of one-off prompts. It fits the Build phase shelf under agent tooling because most day-to-day use happens while shipping features, refactors, and integrations, even though the narrative explicitly covers earlier discovery and later deployment steps. Compared with a narrow integration skill, this is a breadth-first workflow layer for people who live in Claude Code and need guardrailed paths from idea exploration into shippable code. Expect intermediate familiarity with Claude Code plugins, custom commands, and when to lean on bundled agents versus manual edits.
Highlights
- Production-oriented vibe coding suite packaged as a single Claude Code plugin
- Structured workflows spanning discovery, build, refactor, and deployment
- Command- and agent-oriented tooling with MCP/server-style integration keywords
- Suited to solo builders who want repeatable sessions instead of ad-hoc prompting
- Community plugin (1 bundle entry in catalog metadata)
Why builders use it
Solo builders lose speed when every Claude Code session reinvents how to discover requirements, build, refactor, and deploy without a shared workflow suite.
After installing the plugin, Claude Code sessions can follow structured discovery-to-deployment workflows with commands and agents aligned to a complete coding suite.
At a glance
- Type - Plugin in Development Tools.
- Adoption - 0 installs, 15 stars, 0 votes.
FAQ
Who is mike-coulbourn-claude-vibes for?
It is for solo and indie builders who use Claude Code daily and want structured, production-oriented workflows instead of unstructured prompting.
When should I use mike-coulbourn-claude-vibes?
Use it when you are moving from discovery or scoping into implementation, refactors, and deployment and want repeatable commands inside Claude Code.
How do I add mike-coulbourn-claude-vibes to my agent?
Install or register the plugin from the mike-coulbourn/claude-vibes repository in Claude Code, then invoke its bundled commands and agents from your session per the repo README.
Comments
Share how you use mike-coulbourn-claude-vibes, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.