Client Onboard — Freelance Project Onboarding Generator

Why This Exists

Trigger

Invoked as: /client-onboard [project description]

Process

Step 1: Parse the Project

From $ARGUMENTS, extract:

• - Project type: web app, API, automation, audit, mobile, data pipeline, etc.
• Client industry: SaaS, ecommerce, healthcare, finance, creator economy, etc.
• Timeline hints: "need this in 2 weeks", "no rush", "ASAP", specific dates mentioned
• Budget hints: hourly rate mentioned, fixed price, "small budget", enterprise
• Tech constraints: "must use React", "we're on AWS", "no vendor lock-in"
• Team context: "solo founder", "we have a dev team", "replacing a contractor"

Default assumptions when not specified:

• - Timeline: 4-6 weeks (reasonable for most web projects)
• Budget: $75/hr or $2,000-5,000 fixed (Kevin's standard range)
• Stack: Next.js + Supabase + Stripe + Python (Kevin's default)
• Deployment: Vercel (frontend) + Railway or Supabase (backend)

Step 2: Create the Output Directory

Create CLIENT_ONBOARD/ in the current directory.

CODEBLOCK0

If a client name is identifiable from $ARGUMENTS, use: [ClientName]_ONBOARD/ instead.

Step 3: Write PROJECT_BRIEF.md

CODEBLOCK1

Step 4: Write TECH_STACK.md

CODEBLOCK2

Customize the stack to the project — if the client specifies AWS, remove Vercel; if they need mobile, add React Native; etc.

Step 5: Write MILESTONES.md

CODEBLOCK3

Adjust milestone count and timeline to match project scope. Small projects (1-2 weeks): 2 milestones. Large projects (8+ weeks): 5-6 milestones.

Step 6: Write FOLDER_STRUCTURE.md

Generate a proposed directory layout tailored to the project. Standard Next.js + Supabase layout:

CODEBLOCK4
[project-name]/
├── src/
│ ├── app/ # Next.js App Router pages
│ │ ├── (auth)/ # Auth-gated routes
│ │ │ ├── dashboard/
│ │ │ └── settings/
│ │ ├── (public)/ # Public routes
│ │ │ ├── page.tsx # Landing page
│ │ │ └── pricing/
│ │ ├── api/ # API routes
│ │ │ └── webhooks/
│ │ ├── layout.tsx
│ │ └── globals.css
│ ├── components/
│ │ ├── ui/ # Shadcn/UI base components
│ │ └── [feature]/ # Feature-specific components
│ ├── lib/
│ │ ├── supabase/ # DB client + type-safe helpers
│ │ ├── stripe/ # Stripe client + webhook handlers
│ │ └── utils.ts
│ ├── hooks/ # Custom React hooks
│ └── types/ # Shared TypeScript types
├── supabase/
│ ├── migrations/ # SQL migration files
│ └── functions/ # Edge functions
├── scripts/ # One-off scripts + automation
├── docs/ # Client-facing documentation
│ └── ADMIN_GUIDE.md
├── .env.local # Local env vars (not committed)
├── .env.example # Template for env vars
├── CLAUDE.md # Claude Code context for this project
├── SPEC.md # Project specification
└── package.json
CODEBLOCK5

Adjust to the actual stack. Python-only projects get a different layout.

Step 7: Write CLAUDE.md (Project Starter)

CODEBLOCK6bash
npm run dev # start local dev server (localhost:3000)
npm run build # production build
npm run lint # ESLint check
supabase start # start local Supabase (Docker required)
supabase db push # apply migrations to remote

## Environment Variables
See `.env.example` for required vars. Local values in `.env.local` (not committed).

## Conventions
- TypeScript strict mode — no `any`, no unchecked nulls
- Components: PascalCase, one component per file
- DB types: generate from Supabase dashboard → TypeScript types
- API routes: validate input with Zod before touching DB
- RLS: every table has Row Level Security enabled

## Current Status
[Today's date] — Project just started. Milestone 1 in progress.

## Known Gotchas
- [Any project-specific things Claude should know]

Step 8: Write KICKOFF_MSG.md

Write a message Kevin can send directly to the client — professional, warm, no fluff:

CODEBLOCK8

Step 9: Print Summary

CODEBLOCK9

Error Handling

• - Very vague description ("build me an app"): Generate with defaults + add 5 open questions to PROJECTBRIEF.md under "Open Questions" — flag that client answers are required before kicking off
• Multiple possible stacks: Choose Kevin's default stack, add "Alternatives Considered" section explaining why alternatives were skipped
• Unclear budget: Leave payment schedule with placeholder percentages, note "confirm rate with client before sending"
• CLIENTONBOARD/ already exists: Add timestamp suffix CLIENT_ONBOARD_[YYYY-MM-DD]/ to avoid overwriting
• Missing tech details: Generate best-guess and mark assumptions clearly with [ASSUMED] inline

Kevin's Voice — Don't Forget

• - Direct, confident, no corporate fluff
• "I'll build X using Y because Z" — not "I would suggest potentially leveraging..."
• Milestones are concrete with clear handoff criteria, not vague "phase" labels
• Kickoff message reads like a text from a capable contractor, not a formal business letter