Vibe Coding Workflow Prompt Pack

rising

What This Pack Solves

Vibe coding is the workflow where you describe what you want, AI generates it, and you iterate through conversation until it's right. No line-by-line coding, no Stack Overflow searches, no documentation spelunking. You operate at the level of intent, and AI handles the implementation.

These prompts formalize the vibe coding workflow into repeatable patterns. Instead of vague "build me a dashboard" prompts that produce generic output, these prompts give AI the structure it needs to produce code that actually fits your project.

When To Use

  • You're starting a new feature and want to move fast
  • You prefer describing intent over writing code line-by-line
  • You're building UI-heavy features where visual iteration is faster than code editing
  • You want to prototype multiple approaches quickly before committing

Prompts

Prompt 1: Page Builder

prompt
Build a complete page for my [Next.js / React] application.
 
**Page purpose:** [what the page does — e.g., "settings page where users manage their profile and subscription"]
 
**Visual design:**
- Theme: dark, zinc/emerald palette (or describe your theme)
- Layout: [sidebar + content / single column / two-panel / etc.]
- Style: [minimal, clean lines, no decorative elements]
 
**Sections (top to bottom):**
1. [Section 1: describe what it shows and what users can do]
2. [Section 2: describe content and interactions]
3. [Section 3: etc.]
 






Expected output: Complete page component with all sections, responsive layout, and realistic content.

Prompt 2: Component From Description

prompt
Build a React component that does this:
 
[Describe the component in plain language. Be specific about what it shows, what users can interact with, and what happens when they do. Example: "A notification dropdown that shows a list of unread notifications with timestamps, grouped by today/earlier. Each notification has a blue dot if unread. Clicking a notification marks it as read and navigates to the relevant page. The dropdown shows a count badge on the bell icon."]
 
**Tech constraints:**
- Use shadcn/ui components where possible
- Tailwind CSS for styling
- TypeScript with proper types for props
- [Client / Server] Component
 
**Props the component receives:**
- [prop 1: type and purpose]
- [prop 2: type and purpose]
 
**States it needs to handle:**
- Empty state: [what to show when there's no data]
- Loading state: [skeleton / spinner / etc.]
- Error state: [what to show on failure]
 
Build the complete component. No stubs or TODOs.

Expected output: A complete, typed React component with all states handled.

Prompt 3: Iteration Refinement

prompt
The [component/page/feature] you just built works, but I want these changes:
 
**Keep:**
- [thing that works well — be specific]
- [another thing to preserve]
 
**Change:**
- [specific change 1: "make the cards 2-column on tablet, 3-column on desktop instead of the current layout"]
- [specific change 2: "the submit button should be disabled until all required fields are filled"]
- [specific change 3]
 
**Remove:**
- [element or behavior to remove]
 
**Add:**
- [new element or behavior]
 
Apply these changes to the existing code. Don't rewrite from scratch — modify what's there. Show me only the changed parts unless the changes are so extensive that showing the full file is clearer.

Expected output: Targeted modifications to existing code, preserving what works.

Prompt 4: Full Feature Sprint

prompt
I want to build [feature name] for my [project description] in one session. Let's do this in passes:
 
**Pass 1 — Data model:**
Define the types/schemas needed. [Drizzle schema / Zod types / TypeScript interfaces].
 
**Pass 2 — Backend:**
[Server Actions / API routes] for CRUD operations. Include validation and error handling.
 
**Pass 3 — UI:**
Build the page(s) and components using shadcn/ui + Tailwind.
 
**Pass 4 — Wiring:**
Connect the UI to the backend. Add loading states, error handling, optimistic updates if applicable.
 
**Feature requirements:**
- [Requirement 1]
- [Requirement 2]
- [Requirement 3]
 
Start with Pass 1. After each pass, I'll confirm or request changes before you move to the next pass. Don't skip ahead.
 
**Tech stack:** [your stack details]

Expected output: Structured, incremental feature build across 4 passes with review gates.

Prompt 5: UI Polish Pass

prompt
Take this working [component/page] and make it production-ready:
 
```typescript
[paste current code]

Apply these improvements:

  1. Responsive: Ensure it works at 375px, 768px, 1024px, 1280px
  2. Loading states: Add skeletons or spinners where data is fetched
  3. Empty states: Handle zero-data cases with helpful messages
  4. Error states: Show user-friendly error messages, not raw errors
  5. Animations: Add subtle transitions (150-200ms) on hover states and state changes
  6. Accessibility: Proper aria labels, keyboard navigation, focus management

Don't change the functionality or data flow. Only improve the presentation layer and edge case handling.

prompt

**Expected output**: Polished version of existing code with all edge cases and responsive breakpoints handled.

## Tuning Notes

- **Be visual in your descriptions.** "A card with the user's avatar on the left and stats on the right" beats "a user info component." AI generates better UI when you describe spatial relationships.
- **Name your color palette.** "Dark theme with zinc backgrounds and emerald accents" produces dramatically more consistent output than "dark mode."
- **Iterate in small steps.** Prompt 3 (Iteration Refinement) is the most-used prompt in this pack. Make one change at a time — it's faster than describing everything at once and debugging a big diff.
- **Use Prompt 4 for anything that touches both frontend and backend.** The pass-based approach prevents AI from generating a tangled mix of UI and logic in one shot.

## Common Failure Modes

- **AI builds something that looks good but doesn't work** — Always specify the data flow. Where does data come from? What API does it call? What happens on submit?
- **Losing context in long conversations** — After 10+ iterations, start a fresh conversation and paste the current code as the starting point. AI quality degrades in very long threads.
- **AI uses wrong component library** — Always specify "shadcn/ui" or whatever library you use. Without it, AI may use MUI, Ant Design, or raw HTML.
- **Generic placeholder content** — Say "use realistic example data" or provide specific examples. "John Doe" and "Lorem ipsum" make it harder to evaluate the design.

## Context to Provide

Before starting a vibe coding session:
- Screenshot or description of your current app design (for consistency)
- Your color palette and design tokens
- Component library and version
- 1-2 example components from your project (so AI matches your patterns)
- The specific framework version and routing model