AI Prompt for Vibe Coding
Vibe code a quick prototype of a social media platform using Django + PostgreSQL in under an hour.
More prompts for Vibe Coding.
Generate a working prototype with mock data and core interactions in under 10 minutes using AI coding tools.
Use Claude Code to scaffold and build a complete application from a single detailed specification prompt.
Generate a comprehensive Bolt.new prompt that produces a complete SaaS application with auth, billing, and dashboard.
Build a complete REST API server in JavaScript from scratch using AI-assisted vibe coding.
AI-assisted coding session to rapidly implement a dark mode toggle feature using Java.
Build a complete real-time chat server in R from scratch using AI-assisted vibe coding.
You are a creative full-stack developer known for innovative approaches to rapid application development. Your work stands out for its originality and effectiveness. Let's speed-build a prototype of a social media platform using Django + PostgreSQL. This is a rapid prototyping session -- we prioritize shipping over perfection. **What we are building:** social media platform **Stack:** Django + PostgreSQL **Industry context:** event-management **Time constraint:** Prototype-speed (under 60 minutes of AI-assisted coding) ## Prototype Scope Definition Before writing any code, define: - The 3 core screens or views the prototype needs - The single most important user flow to nail - What we are intentionally leaving out of v0.1 - The "wow moment" that makes this prototype impressive in a demo ## Speed-Build Plan ### Minute 0-10: Foundation - Scaffold the project with the fastest approach for Django + PostgreSQL - Install only essential dependencies (list them with one-line justifications) - Set up the database schema or data structures for the core entity - Create seed data or mock data so the app feels populated ### Minute 10-30: Core User Flow - Build the primary screen that users will interact with most - Implement the main CRUD or interaction pattern - Connect the frontend to the backend (or data layer) - Get the happy path working end-to-end without any styling ### Minute 30-45: Visual Polish - Apply a consistent design system or component library - Add navigation and routing between screens - Implement loading states and empty states - Make it look professional enough for a demo ### Minute 45-60: Demo Prep - Add 3-5 realistic data entries that tell a compelling story - Fix any broken flows or dead-end screens - Add one "delight" feature (animation, smart default, keyboard shortcut) - Test the complete flow from landing to core action ## Trade-off Decisions For each of these, pick the faster option and explain why: - Authentication: full auth vs. hardcoded user - Database: real database vs. in-memory or JSON file - Styling: CSS framework vs. custom styles - State management: simple local state vs. global store - Error handling: basic try-catch vs. comprehensive error boundaries ## What to Build Next (v0.2 Backlog) - List 5 features that would make this prototype production-ready - Prioritize them by user impact vs. development effort Structure as a playbook with: Overview, Prerequisites, Step-by-step Plays, Metrics to Track, and Troubleshooting Guide.