The build prompt for a social network app with feeds, follows, real-time notifications, moderation and content recommendations.
Built for: Teams building niche communities and social apps
With social products, the hard part is keeping your first 100 users: feed ranking, notification cadence, moderation and content quality. On the technical side, fan-out, caching and real-time updates surface scaling problems early.
The prompt defines the feed architecture (fan-out on write/read), moderation tools, the reporting flow and growth loops (invites, sharing).
Each expert adds its own task block, constraints and success criteria to the prompt. Default selection for Social Network:
Design the system architecture. Edge-first, 100ms p95. DB schema, API contract, caching strategy, multi-tenancy, RLS, idempotency. Explain why the chosen backend + DB combination is the right call, and write the scaling plan.
PLG growth plan: activation funnel, aha-moment definition, viral loop / referral mechanics, onboarding checklist, and a weekly experiment list for the first 90 days (hypothesis, metric, success threshold).
Build the design system: Tailwind tokens, shadcn/ui, dark mode only, Linear-like density, command palette, keyboard-first. Describe wireframes for the 3 critical flows.
Threat model (STRIDE), OWASP Top 10 checklist, auth/session hardening, data classification, GDPR/KVKK compliance map (data inventory, retention periods, deletion flow), audit log schema.
Preloaded in step 2 of the Studio; change any of the 7 layers.
Every feature appears in the prompt as a "Spec + API + UI + Tests" line.
Sample idea: "A route-sharing, event-based social network for local runners". Below are the master prompt's header and the first expert's block; the Studio generates the full text as 4 experts × 8 steps.
# Social Network - MASTER BUILD PROMPT Stack: Next.js 16 (App Router), tRPC + Next Goal: A route-sharing, event-based social network for local runners This prompt builds a full-stack Social Network in 8 steps. Each step consumes the previous step's output. 4 experts' knowledge combined. Steps: 1. PRD & User Stories 2. Design System (Figma tokens) 3. DB Schema & API Contract 4. Auth & Billing Implementation 5. Core Features Build 6. AI Integration (RAG + Agents) 7. SEO/AEO & Analytics 8. Launch & Growth Checklist --- <prompt> <role name="Staff Engineer / CTO" org="ex-Stripe, ex-Vercel" specialty="System Architecture" experience="12y"> You are a Staff Engineer / CTO with 12 years of experience. Specialty: System Architecture. You have shipped world-class products at the level of Stripe, Linear and Vercel. </role> <context> Project: Social Network - A route-sharing, event-based social network for local runners Type: Social Network Vision: Profiles, follows, route posts (GPX + photos), comments and likes, event creation, real-time notifications, a moderation dashboard and reporting. An invite-driven growth loop. Target user: Teams building niche communities and social apps - Pain: - Budget: Competitors: USP: Monetization: Freemium, Subscription (MRR) | Payments: Tech Stack: Next.js 16 (App Router), tRPC + Next, Supabase, Supabase Auth, Liveblocks Features: Social OAuth (Google/Github), Realtime Presence, Comments & Threads, Notifications Center, File Upload + CDN, Global Search (⌘K), Admin Panel + Impersonate Compliance: KVKK/GDPR Lang: EN </context> <task> Design the system architecture. Edge-first, 100ms p95. DB schema, API contract, caching strategy, multi-tenancy, RLS, idempotency. Explain why the chosen backend + DB combination is the right call, and write the scaling plan. General: production quality, copy-paste ready level of detail. </task> <technical_architecture> - Frontend: Next.js 16 (App Router) - App Router, Server Components, partial prerendering - Backend: tRPC + Next - Edge runtime, RPC, zod validation - DB: Supabase - pgvector for semantic search, type-safe ORM, RLS policies - Auth: Supabase Auth - Passkeys first, org/team model - Search: - typo-tolerant, faceted - Realtime: Liveblocks - presence, CRDT-ready Payment flow: -> Webhook -> Background job -> Entitlement update -> Audit log </technical_architecture> <feature_matrix> - [ ] Social OAuth (Google/Github) -> Spec + API + UI + Tests - [ ] Realtime Presence -> Spec + API + UI + Tests - [ ] Comments & Threads -> Spec + API + UI + Tests …
It starts with a simple chronological, follow-weighted score; the prompt marks the point where you'd move to engagement-based ranking next.
Reporting, automated filters, a moderator queue and user sanctions are in the Security & Compliance persona's task block.
Claude Code, Cursor, Windsurf, v0, Lovable, Bolt and ChatGPT. You pick the output format (Claude XML, ChatGPT Markdown, Cursor Rules, v0, Lovable/Bolt) in step 4 of the Studio, and you can also download it as .cursorrules or CLAUDE.md.
Yes. On the Free plan you generate unlimited prompts with 3 experts and 2 formats — no card required. 18 experts, the Mega Chain and Export to Builders come with Monster Pro ($29/mo).
The build prompt for a creator platform with subscriptions, digital product sales, membership tiers and creator payouts.
The build prompt for a job board with job posting, application management, applicant tracking (ATS), employer packages and SEO-ready job pages.
The build prompt for an LMS with course creation, video lessons, quizzes, progress tracking, certificates and subscriptions.
A privacy-first build prompt for a telemedicine product with appointments, video visits, patient records, e-prescriptions and payments.
The build prompt for a real estate platform with property listings, map search, virtual tours, an agent CRM and a rental flow.
The build prompt for a logistics product with shipment creation, courier/vehicle tracking, route optimization, proof of delivery and customer alerts.
Experts, stack and features come preloaded like on this page — you add the name and the idea. Free, no card required.