By rizukirr
Run a token-efficient vibe-coding pipeline with hard guardrails: brainstorm, plan, isolate, execute, verify, review, and integrate. Halts on spec mismatches instead of committing bad work.
You MUST use this before any creative or implementation work — creating features, building components, adding functionality, or modifying behavior. Runs a disciplined Socratic brainstorming loop (hard gate, one-question-at-a-time, 2-3 approaches, design doc, user approval) while keeping token overhead minimal. Questions, user answers, approaches, design, and the written spec are never compressed.
Use before dispatching any subagent or task. Compiles a verbose intent into a tight RTCO (Role, Task, Constraints, Context, Output) brief that minimizes tokens while preserving every guardrail. Mandatory before any Task/Agent dispatch.
Use when a verification or test fails and you need a disciplined response instead of guessing — fires as vibekit's pipeline failure branch (verify-gate not-satisfied, exec-dispatch test/build failure) and standalone when the user reports a bug, failing test, or broken build. Finds and proves a root cause with verbatim evidence, then routes the fix through exec-dispatch or plan-write. Never edits code itself.
Use when executing an approved implementation plan task-by-task. Dispatches one fresh subagent per task using an RTCO brief, receives the return through the report filter, runs two-stage review (self + plan-compliance), and only then marks the task complete and moves on. Prevents context pollution, drift across tasks, and silent regressions.
Use after review-pack has returned `yes` and the user has explicitly signed off on the diff. Presents the user with concrete integration options (merge, PR, keep branch, cleanup) and executes only the one the user picks. Never auto-merges, auto-pushes, or auto-PRs. This is the outward-facing endpoint of the vibe pipeline.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Vibekit is a discipline-first vibe-coding plugin for Claude Code, OpenAI Codex, OpenCode, Gemini CLI, and Pi. One command — /vibe <intent> — drives a 7-stage pipeline (brainstorm → plan → isolate → exec → verify → review → integrate) that produces a verified, user-approved feature. For autonomy, /ralph-loop re-runs /vibe across iterations until verify-gate is satisfied, bounded by budgets, and never bypassing sign-off.
Token-efficient per feature: subagent briefs are RTCO-compressed and reports are schema-stripped, while every guardrail — evidence quotes, plans, constraints, degradation warnings — stays verbatim.
Guardrails are non-negotiable. If the plan is wrong or the tests don't pass, the pipeline halts loudly — it does not silently commit the wrong thing.
/vibe <intent> — the full 7-stage pipeline in one command./ralph-loop <intent> — autonomous bounded re-run of /vibe with a blocker classifier and thrashing critic. Same gates, never bypasses sign-off.using-vibekit) that carries the trigger map.@-import, opencode plugin, Pi before_agent_start extension) load using-vibekit into every session so pipeline skills cannot be silently skipped.memory-dual captures durable project knowledge — atomic facts, compound documents, and a working notepad — under one file-backed convention.Vibekit is published to npm as @rizukirr/vibekit — a pinned, versioned alternative to the git and marketplace installs below. The published package bundles all 16 skills plus every runtime adapter (Claude Code, Codex, Gemini, Pi, OpenCode).
npm install @rizukirr/vibekit
# or, to vendor it globally
npm install -g @rizukirr/vibekit
This vendors the full skill set and adapters under node_modules/@rizukirr/vibekit/. Point your runtime at that path using the per-runtime steps below. Reach for npm when you want a specific released version pinned in a project; the marketplace and git methods below track main and are simpler for most setups.
From a marketplace that hosts this plugin:
/plugin marketplace add rizukirr/vibekit
/plugin install vibekit@vibekit
From a local clone:
git clone <this repo>
cd vibekit
# then add the repo path as a plugin source in Claude Code settings
After installation, restart Claude Code. The /vibe command and all skills become available.
Tell the agent:
Fetch and follow instructions from https://raw.githubusercontent.com/rizukirr/vibekit/refs/heads/main/.opencode/INSTALL.md
That keeps installation instructions centralized in one file and avoids README drift.
Install with:
codex plugin marketplace add rizukirr/vibekit
codex plugin add vibekit --marketplace vibekit
Detailed Codex docs are in .codex/INSTALL.md.
Tell Gemini CLI:
Fetch and follow instructions from https://raw.githubusercontent.com/rizukirr/vibekit/refs/heads/main/INSTALL.gemini.md
Detailed Gemini docs: INSTALL.gemini.md.
Tell Pi:
Fetch and follow instructions from https://raw.githubusercontent.com/rizukirr/vibekit/refs/heads/main/.pi-plugin/INSTALL.md
Manual installation is also documented in .pi-plugin/INSTALL.md.
Quick install (global settings):
pi install git:github.com/rizukirr/vibekit
Install into project settings (.pi/settings.json) instead of global settings:
pi install git:github.com/rizukirr/vibekit -l
Useful maintenance commands:
pi list
pi update
pi remove git:github.com/rizukirr/vibekit
npx claudepluginhub rizukirr/vibekit --plugin vibekitTutor mode for AI coding assistants. AI shows code in chat and reviews your work, but never writes to your project files.
Vibe Better With Claude Code - You're not an engineer anymore. You're a prompt jockey with commit access. At least do it properly.
Claude harness - A harness for solo developers (Vibecoders) to handle full-cycle contract development.
Describe your goal, approve the spec, then step away — Claude and Codex loop together until it's right.
VibeFlow skill library: full 16-phase workflow with plan reviews, safety guards, brainstorming, and office-hours.
Self-evolving multi-agent system for Claude Code that enables intuitive, flow-based development without rigid planning.
Multi-agent /workflow development pipeline (planner → plan-review → coder → code-review) with typed handoff contracts, lifecycle hooks, and MCP servers.