Vibe coding that survives contact with reality.
Drop into a new project to scaffold from scratch — or into an existing one to bring it under sane conventions without rewriting it. The same bootstrap I use on consulting engagements, priced so you get a stable setup from day one without hiring me.
One-time · yours forever · works with Claude, Codex, Cursor, Copilot & Gemini.
The problem
The fast part is easy. Keeping it maintainable isn't.
The demo works. Then the codebase grows faster than its conventions, the agent loses the thread, and changes start breaking things you'd already finished.
No conventions to follow
Without steering docs, every session re-litigates structure, naming, and tests — and contradicts decisions you made last week.
Hard to vouch for
You end up shipping code you can't fully stand behind, and hoping it holds.
Fast or solid, pick one
It starts to feel like you have to choose between moving fast and ending up with something you can maintain.
Why listen to me
This is the setup I actually use.
This is how I bootstrap vibe-coding projects for myself and my customers. It's the same setup I drop into consulting work — packaged so you get a stable start from day one without hiring me.
The plan
Three steps to a setup that holds
Drop it in
Add the bootstrap folder to a new project or an existing one. Takes a minute.
Your agent picks it up
It picks up the rules, skills, and conventions automatically — every session, every tool.
Build with confidence
Ship features that hold up — and a codebase you'd be glad to hand to someone else.
Inside the kit
7 items · 5 free · 2 with purchase
Skills your agent learns
Reusable commands your agent already knows how to run. Invoke by name or in plain language — your AI follows the skill's playbook either way.
/jgl-checkRun the full verification suite — tests, build, and dependency audit./jgl-commitStage and commit changes locally with a meaningful message. Does NOT push./jgl-pushPush committed changes to the remote, with branch-aware safety./jgl-review-codeReview the codebase for structural issues — duplication, large files, dead code, dependency health — using LLM analysis, static analysis, and coverage data. Produces a refactor plan if warranted./jgl-review-testingAudit the test suite for substantive quality using LLM analysis, static analysis, and coverage data. Produces a plan to improve testing if warranted./jgl-scopeGuided-start interview for a new project — a 15-20 minute conversation about what you're building, for whom, goals, constraints, brand, and stack that produces docs/SCOPE.md (and docs/BRAND.md when there's a brand), adds a Project context section to CLAUDE.md, and picks the first milestone./jgl-setup-secretsSet up encrypted-in-repo secrets management (SOPS + age) with separate dev/prod keys, verified key rotation, and a pre-commit guard./jgl-setup-testingWire up a test framework, write a meaningful starter test, and set up coverage and CI./jgl-statusSession checkpoint — what changed, what's still open, anything risky uncommitted.
Wait, what's a "skill"?
From Napoleon Dynamite (2004): “I don't even have any good skills. You know like num-chuk skills, bow hunting skills, computer hacking skills. Girls only want boyfriends who have great skills!”
Modern AI coding tools let you teach your agent skills — named playbooks it can recognize and follow. Each card above is one your agent gets when you install the kit.
What's at stake
The difference a system makes
Without a system
- A rewrite at every milestone
- Security holes you find in production
- An agent that contradicts itself
- An app you're reluctant to change
With the Starter Kit
- Conventions that survive scale
- A security baseline from day one
- An agent that stays on-rails
- An app you can hand off and trust
Get started
A stable setup from day one.
Drop in the same bootstrap I use on consulting work and get a stable, maintainable setup from the start — without hiring me.
Already own this kit? The Code Review & Security Audit drops to a bundle price — automatically.
Pairs well with
Building Fusion 360 add-ins instead of (or alongside) regular web/backend projects? The Fusion Add-in kit applies the same playbook to that domain.