The build prompt for a logistics product with shipment creation, courier/vehicle tracking, route optimization, proof of delivery and customer alerts.
Built for: Shipping, courier and field operations teams
In logistics software, real-time location, status transitions and exception handling (address not found, damaged goods) are the heart of the product. The field app and the operations dashboard have to share the same data.
The prompt defines the shipment state machine, the driver's mobile flow, route optimization, proof of delivery (photo/signature) and the customer tracking page.
Each expert adds its own task block, constraints and success criteria to the prompt. Default selection for Logistics Tracking:
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.
Deployment and operations plan: CI/CD pipeline (preview + production), IaC, secrets management, observability (logs, traces, alerts), SLO/SLA definitions, incident runbook, cost estimate and scaling thresholds.
Write a flawless PRD. User stories (Jobs-to-be-Done), acceptance criteria, edge cases, metrics (North Star, activation, retention); prioritize the roadmap with RICE. Scope an MVP that ships in 7 days.
Event tracking plan: North Star and supporting metrics, event/property dictionary, funnel and retention definitions, data warehouse schema, dashboard list, data quality tests.
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 live tracking and proof-of-delivery platform for urban courier networks". Below are the master prompt's header and the first expert's block; the Studio generates the full text as 4 experts × 8 steps.
# Logistics Tracking - MASTER BUILD PROMPT Stack: Next.js 16 (App Router), Hono + CF Workers Goal: A live tracking and proof-of-delivery platform for urban courier networks This prompt builds a full-stack Logistics Tracking 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: Logistics Tracking - A live tracking and proof-of-delivery platform for urban courier networks Type: Logistics Tracking Vision: Shipment creation and labels, courier assignment, live location, route suggestions, delivery photo/signature, customer tracking links and SMS notifications, exception handling and operations reports. Target user: Shipping, courier and field operations teams - Pain: - Budget: Competitors: USP: Monetization: Usage-Based, Subscription (MRR) | Payments: Tech Stack: Next.js 16 (App Router), Hono + CF Workers, Supabase, Supabase Auth, Resend Features: RBAC + Permissions, Realtime Presence, Notifications Center, File Upload + CDN, Analytics Charts, Webhooks & Events, Audit Logs 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: Hono + CF Workers - 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: Resend - presence, CRDT-ready Payment flow: -> Webhook -> Background job -> Entitlement update -> Audit log </technical_architecture> <feature_matrix> - [ ] RBAC + Permissions -> Spec + API + UI + Tests - [ ] Realtime Presence -> Spec + API + UI + Tests …
Periodic location updates from the mobile client, broadcast to the operations dashboard over WebSocket, and a time-series table; the prompt adds battery and data-usage constraints.
Initially through an external API (e.g. Mapbox Optimization); the prompt marks the point where you'd switch to your own solver.
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 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 an on-demand app with customer, provider and operator roles: matching, live tracking, payments and ratings.
The build prompt for a booking SaaS with calendars, availability rules, an online booking page, reminders and payments or deposits.
The build prompt for a CRM/ERP with customer records, a sales pipeline, a quote-to-order-to-invoice flow, tasks and reports.
Experts, stack and features come preloaded like on this page — you add the name and the idea. Free, no card required.