/workflow

// watch me work

This is what vibe coding looks like when I sit down to build something. Not the theory or the methodology, but the actual setup tour and gameplay footage.

// the setup

Before I type anything, Claude already knows how I work. Three layers of configuration load automatically.

L1Workspace

28 commands, 47 agents, constitution, 40% rule. The foundation that applies to everything.

↓ inherits
L2Container

Personal projects container. Navigation guides, cross-repo workflows, domain skills.

↓ inherits
L3Project

This website. Blog post skill, website design skill, Playwright testing skill.

Result: 8 files in this repo inherit from the full workspace including agents, skills, commands, and progress tracking. Claude knows the voice guide, testing patterns, and commit conventions before I say anything.

// the session

Every session has the same shape: initialize, work, checkpoint. The discipline is in the bookends.

$ /session-start

Loads progress files, shows last session summary, identifies next work item.

... actual work happens here ...
$ /session-end

Checks for uncommitted changes, asks for summary, updates progress, offers bundle save.

The 40% rule: Keep context under 40% utilization. Above 60%, Claude starts forgetting instructions. I save bundles when approaching the limit.More on this →

// the hud

What I'm watching during a session. These tell me if the session is going well.

vibe-check

Trust pass rate, rework ratio, fix spirals. Run after every feature.

progress.json

Current state, blockers, next steps. Updated every 10 messages automatically.

bundles/

Saved context for multi-day work. Pick up exactly where I stopped.

$ npx @boshu2/vibe-check
Trust Pass Rate98%
Rework Ratio12%
Fix Spirals0

// the loadout

Seven commands I use every session. These are my keybinds.

/session-startinitialize
/session-endsave state
/researchexplore first
/planspecify changes
/implementexecute plan
/bundle-savecheckpoint
/bundle-loadresume

// the replays

Real commits from this repository showing the methodology in action.

ab509c0today

Landing page visual overhaul + library question pages

L4 session. 3 commits. CSS grid background, HUD corners, 8 new routes.

30dbb99yesterday

Next.js 16 upgrade + Vibe Ecosystem content refresh

L2 session. Tracer bullets for each upgrade step. 6 features validated.

883e718last week

Unify site around central question

L3 session. 3-agent parallel audit. Homepage, builds, library all aligned.

200+ sessions over the past year. 95% success rate when I follow the discipline.

// the extensions

The patterns encoded as Claude Code plugins. Everything above, packaged for installation.

55
agents
29
commands
7
skills

Code reviewers, language experts, deployment engineers, documentation writers. The RPI workflow, session management, vibe-check integration. All of it.

Browse the marketplace →

// go deeper

Marketplace on GitHub →vibe-check on npm →