Work With Me / Vibe Coding Onboarding plugin
A Claude Code plugin

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.

Part of the two-session Vibe Coding flavor · $650

Fig. P.a — What it does

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.

01

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 dev script 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
02

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
Fig. P.b — The intake

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.

  1. 01 What are you trying to ship in the next two weeks?
  2. 02 Where should the first version live (your domain, a subdomain, a temp Cloudflare URL)?
  3. 03 Which stack feels right — Astro, Next.js, Python? (We can change after.)
  4. 04 What does Claude need to know about you to be useful here?
  5. 05 Who else, if anyone, will read the repo or the docs?
Fig. P.c — Stacks supported

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.

Astro
Recommended

Recommended — content sites, landing pages, small tools, fast deploys.

Next.js

For React-shaped projects — dashboards, lead-magnet tools, mini-apps.

Python

For scrapers, automations, data pipelines, anything CLI-shaped.

Fig. P.d — What it leaves you with

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.
Fig. P.e — Field photos

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.

Screenshot · 01 The Hazel Q Vibe Coding Onboarding plugin running in Claude Code, working through the intake. /images/vibe-code-setup/plugin-running.png
Onboarding plugin · running The Hazel Q Vibe Coding Onboarding plugin running in Claude Code, working through the intake.
Screenshot · 02 Your starter repo with CLAUDE.md, deploy config, and the first-ship roadmap in place. /images/vibe-code-setup/repo-scaffolded.png
Repo · scaffolded Your starter repo with CLAUDE.md, deploy config, and the first-ship roadmap in place.
Screenshot · 03 The small thing we shipped together at the end of Session 1 — running on the open internet. /images/vibe-code-setup/first-ship.png
First ship · live The small thing we shipped together at the end of Session 1 — running on the open internet.
Screenshot · 04 Session 2: working the vibe-coding loop on the next thing, with the plugin's starter prompts in hand. /images/vibe-code-setup/loop-running.png
Loop · in motion Session 2: working the vibe-coding loop on the next thing, with the plugin's starter prompts in hand.
Fig. P.f — Past ships

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.

A landing page Astro + Cloudflare Pages
A lead-magnet tool Next.js + Vercel
An internal dashboard Astro + D1
A scraper Python + Cron
A booking tool Astro + Stripe
A content pipeline Next.js + Notion
Fig. P.g — How to get it

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.

$650
Fig. P.h — FAQ

Common questions.

Anything not covered? Drop me a note — I read everything.

Can I buy the plugin separately?
Not right now. The plugin is designed to run inside Session 1 of the Vibe Code Setup — the value is in the live install + first ship together, not the file on its own. If that changes I'll list it here.
What if I already have a repo?
Tell me on the booking form. The plugin can scaffold over an existing repo or skip the scaffolding step and just write CLAUDE.md + the roadmap. We'll decide live in Session 1.
Does it work with Cursor / VS Code / other editors?
Yes. The plugin is a Claude Code plugin specifically — it runs in your terminal, alongside whatever editor you use. We set up the editor of your choice in Session 1.
Will it work on a Windows machine?
Yes. Mac, Windows, or Linux — Claude Code runs on all three. The scaffolded repo will use whatever path conventions your machine expects.
What if my project isn't web-shaped?
Pick Python in the intake. The plugin scaffolds a CLI- or script-shaped project (scrapers, automations, data pipelines, small tools) instead of a web project. If your project is truly weird, tell me on the booking form and we'll figure it out before Session 1.
Is there a Cowork equivalent?
Yes — Hazel Q Cowork Onboarding, which ships with the $20 Cowork Starter. Different plugin, different lane: that one sets up Claude as a productivity partner (Notion / Sheets / Excel) rather than scaffolding a coding project.
Not ready to book?

Get the weekly field notes.

One short email each Friday — what I'm building, what's breaking, what's actually working with Claude.