Quick Start
Ship production feature in 15 minutes. No boilerplate, no setup hell.
Prerequisites
- ClaudeKit CLI installed (
ck --versionworks) - Claude Code running
- Project initialized with ClaudeKit
Donβt have these? See Installation Guide
Your First Feature
Add user authentication to Next.js app in 15 minutes.
Step 1: Bootstrap Project
ck new my-app --kit engineer
cd my-app
Created:
.claude/- 14 AI agents, 30+ commands, 45 skillsdocs/- Auto-generated project docsplans/- Implementation plans storage
Step 2: Plan Authentication
/plan add user authentication with email/password and OAuth
What happens (30 seconds):
planneragent spawns 3researcheragents in parallel- Researches Next.js 15 + Better Auth best practices
- Analyzes your codebase structure
- Creates detailed implementation plan
Output:
β planner: Research complete (3 sources analyzed)
β planner: Plan created
π plans/251030-auth-implementation.md
Summary:
β’ Better Auth with credentials + OAuth (Google, GitHub)
β’ Session management with JWT
β’ Login/signup/reset pages
β’ Protected routes middleware
β’ Files to create: 8
β’ Files to modify: 4
β’ Tests: 12 test cases
β’ Estimated: 2 hours manually, 5 minutes with ClaudeKit
Next: /code plans/251030-auth-implementation.md
Step 3: Review Plan
cat plans/251030-auth-implementation.md
Scan the plan. Architecture solid? Continue.
Step 4: Implement
/cook implement the auth plan
What happens (5 minutes):
Clarification (15 sec):
cook: Which OAuth providers?
You: Google and GitHub
Implementation (4 min):
- Installs
better-auth+ dependencies - Creates auth config with providers
- Generates login/signup/reset pages with shadcn/ui
- Adds API routes
- Implements middleware for protected routes
- Writes 12 test cases
- Updates documentation
Real-time output:
β Installing dependencies... (15s)
β Creating auth.ts config
β Generating UI components
β’ app/login/page.tsx (Google OAuth button)
β’ app/signup/page.tsx (Email + OAuth)
β’ app/reset-password/page.tsx
β Creating API routes
β’ app/api/auth/[...all]/route.ts
β Adding middleware.ts (protect /dashboard/*)
β Writing tests (12 cases)
β Updating docs/system-architecture.md
tester: Running test suite...
β Unit tests: 45 passed
β Auth tests: 12 passed
β Coverage: 89%
code-reviewer: Quality check...
β No security issues
β Type-safe (0 errors)
β Performance: Fast (< 100ms auth check)
β Implementation complete (4m 32s)
Step 5: See It Work
npm run dev
Visit:
http://localhost:3000/login- Login with email or OAuthhttp://localhost:3000/signup- Create accounthttp://localhost:3000/dashboard- Protected route (redirects if not logged in)
Try it:
- Sign up with email
- Login redirects to dashboard
- Logout, try OAuth with Google
- Check session persistence
Step 6: Commit
/git:cm
Output:
git-manager: Analyzing changes...
β Staged: 12 files
β Secret scan: Clean
β Commit message generated
feat(auth): add Better Auth with email and OAuth
- Add Better Auth configuration
- Implement login/signup/reset pages
- Add Google and GitHub OAuth
- Protect routes with middleware
- Add 12 auth test cases
- Update documentation
β Committed: abc1234
β Pushed to origin/main
Done!
What Just Happened?
Traditional approach (8-12 hours):
- Research auth libraries (1h)
- Read documentation (1h)
- Setup configuration (1h)
- Build UI components (3h)
- Implement OAuth flows (2h)
- Write tests (1h)
- Debug issues (1h)
- Documentation (30min)
ClaudeKit approach (6 minutes):
- Plan: AI researches, analyzes, designs (30s)
- Implement: AI codes, tests, documents (4m)
- Review: AI validates security, performance (30s)
- Commit: AI creates professional commit (30s)
Time saved: 8-12 hours β ~800% faster
Why It Works
14 Specialized Agents
- planner: Creates implementation plans
- researcher: Finds best practices (3 run in parallel)
- tester: Validates everything works
- code-reviewer: Security + performance checks
- git-manager: Professional commits
- docs-manager: Keeps docs current
- β¦and 8 more
45 Built-in Skills
- better-auth: Auth implementation expertise
- shadcn-ui: Pre-configured UI components
- nextjs: Next.js 15 best practices
- gemini-image-gen: Generate logos, assets
- β¦and 41 more
Living System
- Updates with Claude improvements
- No tech stack lock-in
- Learns your patterns
- Gets smarter over time
Next: Real Work
Try more complex features:
# Add payment processing (Stripe + webhooks)
/cook add Stripe payment with subscriptions and webhooks
# Build REST API with validation
/cook create REST API for blog posts with Zod validation
# Implement real-time chat
/cook add real-time chat using WebSockets
# Database migrations
/cook migrate from SQLite to PostgreSQL with zero downtime
Each takes 5-20 minutes instead of days.
Learn Workflows
Full Feature Cycle
/plan [feature] # Research + plan
/code [plan] # Implement
/test # Validate
/fix:fast [issue] # Quick fixes
/git:cm # Commit
Debug + Fix
/debug [issue] # Root cause analysis
/fix:hard [complex-issue] # Multi-agent fix
/fix:ci [actions-url] # Fix failing CI/CD
Design + Content
/design:good [feature] # UI/UX design
/content:good [page] # Marketing copy
/brainstorm [idea] # Explore solutions
Common Questions
Q: Does it work with my tech stack? A: Yes. Next.js, Django, Laravel, Go, Rust, Flutter - any stack. ClaudeKit adapts to your patterns.
Q: What if AI makes mistakes?
A: code-reviewer catches issues before commit. Plus, you review PRs as normal. AI augments, doesnβt replace judgment.
Q: Do I need API keys? A: For basic features, no. For advanced skills (Gemini, Search), yes. See API Key Setup.
Q: Can I customize agents?
A: Yes. Edit .claude/agents/*.md to tune behavior. See Custom Agents.
Explore More
Core Concepts:
- Architecture - How ClaudeKit works
- Agents Overview - Meet your AI team
- Commands Guide - All 30+ commands
Real-World Uses:
Troubleshooting:
You just shipped production auth in 6 minutes. Boilerplates canβt do that. AI chat assistants canβt do that. Only ClaudeKit.
Ready to ship? Your AI dev team is waiting.