Vibe Check
>-
Ship
Use when work should go live — commit, push, deploy per recipe, cache-busted live verify, smoke, screenshot. Blocks the "shipped" claim on the live check.
The Humanizer
A Claude skill from artttj/rapid-stack.
Plan
Use when an approved spec needs its build plan — writes docs/specs/<slug>/plan.md pinned to the spec body hash, with a sign-off gate.
Build
Use when executing work — a signed-off plan (gate mode) or a routed small fix (direct mode). TDD, capped review, verification, proof.
Spec
Use when a feature needs its spec — short clarifying Q&A, then docs/specs/<slug>/spec.md with a one-keypress self-approval gate.
Design
Enforces precise, minimal design for dashboards and admin interfaces. Use when building SaaS UIs, data-heavy interfaces, or any product needing pixel-level discipline.
Sync
Use when localhost should match prod — pulls db, images, feed, data per the recipe sync map. One direction only: prod → local.
Project Recipes
Use when an op command needs a per-project operation (serve, build, test, deploy, sync, release, live URL) — reads, discovers, and heals .claude/op.json in the target repo.
Show
Use when a change needs visual proof — serve locally per recipe, screenshot the standard responsive breakpoints (mobile, tablet, desktop), short verdict.
Using Op
Use when starting any conversation — the op operator rules. Route work through /op:go, quote a repo convention before code, prove every claim, print the git status line after tree changes.
Prompt Optimizer
>-
Go
Use when any work ask arrives — classifies it (bug / small fix / feature), confirms the route, and hands off to debugging, direct build, or the spec gate.
Release
Use when publishing a version — bump version files, write humanized notes, tag, publish per recipe, verify the published artifact.