Setup Project

Setup Project Workflow

On "set up" or "setup"

Step 1: Stack Detection

Scan for dependency files and detect the project stack:

Check for: package.json, pyproject.toml, Cargo.toml, go.mod

If package.json exists, read dependencies and devDependencies to detect:

Also check for config files:

• vercel.json or .vercel/ -> Vercel deployment
• netlify.toml -> Netlify deployment
• Dockerfile -> Container deployment
• supabase/ directory -> Supabase project
• .github/workflows/ -> CI/CD pipelines

Step 2: Project Type Classification

Based on detected signals + user description, classify the project:

If unclear, ask:

question: "What best describes this project?"
options:
  - { label: "E-commerce", description: "Online store with payments" }
  - { label: "SaaS", description: "Subscription app with auth" }
  - { label: "Marketing site", description: "Landing pages, SEO focus" }
  - { label: "Full-stack app", description: "Web app with database" }

Step 3: Generate CLAUDE.md

Create a project-level CLAUDE.md with:

# [Project Name]

## Overview
[One-line description from user or package.json]

## Stack
[Detected technologies]

## Key Commands
- `npm run dev` - Start development server
- `npm run build` - Production build
- `npm run test` - Run tests
[Add detected commands from package.json scripts]

## Key Directories
[Map out src/ structure if it exists]

## Patterns
[Stack-specific patterns based on detected technologies]

Step 4: Recommend Skills

Based on detected stack, list relevant auto-dev skills:

Always relevant: review, commit, fix

Conditional recommendations:

Output format:

Detected: Next.js + Supabase + Stripe + Tailwind

Recommended skills for this project:
- supabase — database, RLS policies, migrations
- stripe — payments, webhooks, checkout
- seo — meta tags, schema markup, Open Graph
- design — UI patterns, design tokens
- deploy — Vercel deployment
- security — pre-deploy scanning
- perf — Core Web Vitals

These load automatically when you use their trigger words.

Step 5: Environment Setup

Create .env.example based on detected services:

# Generated based on detected stack

# Supabase (if @supabase/supabase-js detected)
NEXT_PUBLIC_SUPABASE_URL=
NEXT_PUBLIC_SUPABASE_ANON_KEY=

# Stripe (if stripe detected)
STRIPE_SECRET_KEY=
NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY=
STRIPE_WEBHOOK_SECRET=

# Auth (if next-auth detected)
NEXTAUTH_SECRET=
NEXTAUTH_URL=

# App
NEXT_PUBLIC_APP_URL=

Ensure .gitignore includes:

• .env.local, .env
• node_modules/
• .next/ (for Next.js)
• .claude/ (auto-dev artifacts)

Step 6: Create prd.json

Based on project type, create initial stories:

E-commerce starter:

• Product listing page with schema markup
• Shopping cart
• Stripe Checkout integration
• Order confirmation and webhooks
• SEO: meta tags, Open Graph, sitemap

SaaS starter:

• Auth flow (signup, login, logout)
• Subscription billing with Stripe
• Dashboard layout
• User settings and profile
• Protected API routes

Marketing site starter:

• Landing page with hero section
• SEO: meta tags, Open Graph, JSON-LD
• Contact form
• Responsive design
• Sitemap and robots.txt

Step 7: Report

Project setup complete:
- CLAUDE.md: Created with [detected stack] context
- prd.json: [N] initial stories based on [project type]
- .env.example: Configured for [detected services]
- .gitignore: Updated

Recommended skills: [list]

Next: Say 'auto' to start working through tasks,
or 'brainstorm' to scan for more improvements.

Quick Setup

If user provides a description: "Set up this project - I want to build [description]"

1. Run stack detection (Steps 1-2)
2. Generate all files using smart defaults (Steps 3-6)
3. Skip questions when the description provides enough context
4. Show the report (Step 7)