Recommended — content sites, landing pages, small tools, fast deploys.
Hazel Q Vibe Coding
Onboarding.
Custom Claude Code plugin. Runs in Session 1 of the two-session Vibe Coding flavor, reads a short intake, and on autopilot: scaffolds your repo, writes CLAUDE.md, wires a deploy target, and plans the small first thing we're going to ship together.
Two jobs. One short intake.
The plugin reads a 5-question intake, picks the stack with you, then runs both jobs back to back. You watch in Session 1. By the time we're done with the intake, the next 60 minutes of session is shipping the small first thing.
Scaffolds your project.
Initializes the repo, drops in sensible defaults for the stack you picked, writes CLAUDE.md tuned to the project, wires the deploy target so the first push lands on a real URL.
- Working
devscript on first try - Preview deploy live by the end of the intake
- Conventions Claude should follow, written down
- The do/don't list for the project
Plans your first ship.
Picks one small thing — a landing page, a tool, a scraper, whatever you said in the intake — and breaks it into a roadmap.md (or GitHub Issues) you can actually finish in Session 1.
- Each step small enough to verify
- Acceptance criteria, not just “build the thing”
- An explicit “done” for Session 1
- A “next” list for Session 2
Five questions. Then it runs.
The whole intake takes about three minutes. You can rough-answer everything — the plugin teaches you what's important to be specific about, and we re-tune in the live call if needed.
- 01 What are you trying to ship in the next two weeks?
- 02 Where should the first version live (your domain, a subdomain, a temp Cloudflare URL)?
- 03 Which stack feels right — Astro, Next.js, Python? (We can change after.)
- 04 What does Claude need to know about you to be useful here?
- 05 Who else, if anyone, will read the repo or the docs?
Three stacks. Pick during intake.
The plugin can scaffold any of these. If you don't know which fits, the intake recommends one based on the thing you want to ship.
For React-shaped projects — dashboards, lead-magnet tools, mini-apps.
For scrapers, automations, data pipelines, anything CLI-shaped.
Five files. One working setup.
Everything the plugin produces lives in your repo. You can run it, edit it, delete it, fork it. There's no service to keep paying for — once it's run, it's yours.
- Scaffolded repo
- Initialized with sensible defaults for your stack — folder structure, package.json or requirements.txt, a working dev script, a deploy script.
- CLAUDE.md, tuned
- Project-scoped brain file — your goal, your voice, the conventions Claude should follow, and the do/don't list specific to this project.
- Deploy target wired
- Cloudflare Pages, Vercel, or Fly — picked during intake. Auth + a working preview deploy on day one.
- First-ship roadmap
- A roadmap.md (or GitHub Issues, your call) with the small first ship broken into checkable items. The plan you run through in Session 1.
- Starter prompts
- The handful of prompts that get the most leverage out of Claude Code for this specific project — saved to the repo, ready to paste.
What it actually looks like.
Four shots from a real run. The plugin scaffolds, we ship together in Session 1, the loop keeps turning in Session 2.
/images/vibe-code-setup/plugin-running.png /images/vibe-code-setup/repo-scaffolded.png /images/vibe-code-setup/first-ship.png /images/vibe-code-setup/loop-running.png What people have shipped on the first run.
Six shapes the first-ship plan has taken. The plugin builds to whatever you put in the intake — these are just the ones it's seen before.
The plugin is the Vibe Coding flavor of the two sessions.
Two 70-minute sessions, a week of async in between, and a year in the Slack. Session 1 runs the plugin live and ships your first thing together. Session 2 runs the loop on the next.
Common questions.
Anything not covered? Drop me a note — I read everything.
Can I buy the plugin separately?
What if I already have a repo?
Does it work with Cursor / VS Code / other editors?
Will it work on a Windows machine?
What if my project isn't web-shaped?
Is there a Cowork equivalent?
Get the weekly field notes.
One short email each Friday — what I'm building, what's breaking, what's actually working with Claude.