Vibe Coding
Rapidly prototype modern web applications from scratch with creative flow and quick iteration.
Inputs
Gather before starting (ask if not provided):
- App description: Purpose, key features, target users
- Tech preferences: Framework (React/Next.js/Vue/Svelte), styling (Tailwind/CSS modules)
- Feature requirements: Core functionality, user flows
- Design direction: Style, colors, reference sites
- Deploy target: Vercel, Netlify, self-hosted, etc.
Workflow
Think through the build step-by-step:
- Research: Search official docs for current initialization commands and patterns
- Never hardcode outdated commands; always verify current best practices
- Initialize: Run framework init, set up TypeScript + ESLint + Prettier + git
- Design system: Set up styling, define tokens (colors, spacing, typography), build base components
- Features: Build incrementally - one feature at a time, test as you go
- Polish: Accessibility (ARIA, keyboard nav), performance (code splitting, image optimization), error boundaries
- Document: README with setup, dev commands, env vars, deployment
Architecture Principles
- Component-based: Small, reusable components
- Type-safe: TypeScript throughout
- Mobile-first: Responsive by default
- Accessible: Semantic HTML, ARIA labels, keyboard navigation
- Performance-conscious: Code splitting, lazy loading, optimized images
In Scope
- Full-stack web apps (frontend + API routes/server components)
- Any modern framework (React, Next.js, Vue, Svelte, Astro, etc.)
- Database integration (Prisma, Drizzle with type-safe ORMs)
- Authentication flows
- SEO optimization (meta tags, structured data, sitemaps)
Out of Scope
- Production infrastructure management
- Complex backend microservices (use separate skill)
- Native mobile apps (iOS/Android)
Styling
- Tailwind CSS recommended for rapid development
- Consistent design tokens for colors, spacing, typography
- Light/dark mode support when appropriate
- Proper contrast ratios (WCAG AA minimum)
State and Data
- State: React Context / Zustand / Redux based on complexity
- Data fetching: React Query, SWR, or framework built-ins
- Always handle: loading states, error states, empty states
Backend
- API routes or server components as appropriate
- Type-safe ORMs (Prisma, Drizzle) for databases
- Proper validation at API boundaries
SEO (public-facing apps)
- Meta tags: title, description, Open Graph, Twitter cards
- Structured data: JSON-LD for rich search results
- Core Web Vitals: optimize LCP, FID, CLS
- Sitemap and robots.txt
npm install # or bun install
npm run type-check # tsc --noEmit
npm run lint # eslint
npm test # vitest / jest
npm run build # production build
npm run dev # development server
Complete when:
- All commands succeed without errors
- App builds and runs in dev mode
- Core features work across screen sizes
- Accessibility checks pass
- Tests cover critical paths
- README is clear and complete
SaaS landing page
User: "Build a landing page - hero, features, pricing, contact form"
Steps:
1. Search nextjs.org/docs for current create-next-app command
2. npx create-next-app@latest --typescript --tailwind --app
3. Create components: Hero, Features, PricingTable, ContactForm
4. Implement responsive grid layout, form validation
5. Add SEO: metadata API, Open Graph images
6. Deploy config for Vercel
Admin dashboard
User: "Prototype an admin dashboard - auth, data tables, charts"
Steps:
1. Next.js App Router + NextAuth.js for authentication
2. shadcn/ui for component library
3. Protected route middleware
4. Data tables with tanstack-table (sorting, filtering, pagination)
5. Charts with recharts or chart.js
6. Tests for auth flow and data display
Documentation References
Always search current docs before implementing:
1---2name: vibe-coding-23description: Rapidly prototype and build modern, responsive web applications from scratch using current frameworks and libraries. Use when you want to quickly create a new web app with full local control, creative flow, and modern best practices. Local alternative to Lovable, Bolt, and v0.4---5
6# Vibe Coding
7
8Rapidly prototype modern web applications from scratch with creative flow and quick iteration.
9
10<instructions>
11
12## Inputs
13
14Gather before starting (ask if not provided):
15- **App description**: Purpose, key features, target users
16- **Tech preferences**: Framework (React/Next.js/Vue/Svelte), styling (Tailwind/CSS modules)
17- **Feature requirements**: Core functionality, user flows
18- **Design direction**: Style, colors, reference sites
19- **Deploy target**: Vercel, Netlify, self-hosted, etc.
20
21## Workflow
22
23Think through the build step-by-step:
24
251. **Research**: Search official docs for current initialization commands and patterns
26 - Never hardcode outdated commands; always verify current best practices
272. **Initialize**: Run framework init, set up TypeScript + ESLint + Prettier + git
283. **Design system**: Set up styling, define tokens (colors, spacing, typography), build base components
294. **Features**: Build incrementally - one feature at a time, test as you go
305. **Polish**: Accessibility (ARIA, keyboard nav), performance (code splitting, image optimization), error boundaries
316. **Document**: README with setup, dev commands, env vars, deployment
32
33## Architecture Principles
34
35- **Component-based**: Small, reusable components
36- **Type-safe**: TypeScript throughout
37- **Mobile-first**: Responsive by default
38- **Accessible**: Semantic HTML, ARIA labels, keyboard navigation
39- **Performance-conscious**: Code splitting, lazy loading, optimized images
40
41</instructions>
42
43<scope>
44
45## In Scope
46- Full-stack web apps (frontend + API routes/server components)
47- Any modern framework (React, Next.js, Vue, Svelte, Astro, etc.)
48- Database integration (Prisma, Drizzle with type-safe ORMs)
49- Authentication flows
50- SEO optimization (meta tags, structured data, sitemaps)
51
52## Out of Scope
53- Production infrastructure management
54- Complex backend microservices (use separate skill)
55- Native mobile apps (iOS/Android)
56
57</scope>
58
59<conventions>
60
61## Styling
62- Tailwind CSS recommended for rapid development
63- Consistent design tokens for colors, spacing, typography
64- Light/dark mode support when appropriate
65- Proper contrast ratios (WCAG AA minimum)
66
67## State and Data
68- State: React Context / Zustand / Redux based on complexity
69- Data fetching: React Query, SWR, or framework built-ins
70- Always handle: loading states, error states, empty states
71
72## Backend
73- API routes or server components as appropriate
74- Type-safe ORMs (Prisma, Drizzle) for databases
75- Proper validation at API boundaries
76
77## SEO (public-facing apps)
78- Meta tags: title, description, Open Graph, Twitter cards
79- Structured data: JSON-LD for rich search results
80- Core Web Vitals: optimize LCP, FID, CLS
81- Sitemap and robots.txt
82
83</conventions>
84
85<required_artifacts>
86- Fully initialized project with all config files
87- Clean component and page structure
88- Styling implementation (Tailwind config or chosen approach)
89- Tests for critical user flows
90- README.md with: description, setup, dev commands, env vars, deployment
91- Properly configured .gitignore
92- package.json with clear scripts
93</required_artifacts>
94
95<verification>
96
97```bash
98npm install # or bun install
99npm run type-check # tsc --noEmit
100npm run lint # eslint
101npm test # vitest / jest
102npm run build # production build
103npm run dev # development server
104```
105
106Complete when:
107- All commands succeed without errors
108- App builds and runs in dev mode
109- Core features work across screen sizes
110- Accessibility checks pass
111- Tests cover critical paths
112- README is clear and complete
113
114</verification>
115
116<examples>
117
118### SaaS landing page
119```
120User: "Build a landing page - hero, features, pricing, contact form"
121
122Steps:
123 1. Search nextjs.org/docs for current create-next-app command
124 2. npx create-next-app@latest --typescript --tailwind --app
125 3. Create components: Hero, Features, PricingTable, ContactForm
126 4. Implement responsive grid layout, form validation
127 5. Add SEO: metadata API, Open Graph images
128 6. Deploy config for Vercel
129```
130
131### Admin dashboard
132```
133User: "Prototype an admin dashboard - auth, data tables, charts"
134
135Steps:
136 1. Next.js App Router + NextAuth.js for authentication
137 2. shadcn/ui for component library
138 3. Protected route middleware
139 4. Data tables with tanstack-table (sorting, filtering, pagination)
140 5. Charts with recharts or chart.js
141 6. Tests for auth flow and data display
142```
143
144</examples>
145
146<safety>
147- Verify package security before adding dependencies (check npm audit)
148- Never commit API keys or secrets (use .env.local, document in README)
149- If requirements exceed framework capabilities, suggest alternatives
150</safety>
151
152## Documentation References
153
154Always search current docs before implementing:
155- React: https://react.dev
156- Next.js: https://nextjs.org/docs
157- Vue: https://vuejs.org/guide
158- Svelte: https://svelte.dev/docs
159- Tailwind CSS: https://tailwindcss.com/docs
160- TypeScript: https://www.typescriptlang.org/docs