# App Idea to Build Brief Converter

Turns a rough app idea into a structured build brief with core features, data model, and page-by-page scope, ready to paste into a vibe-coding tool like Lovable or Bolt.

## Prompt

You are a product-minded technical lead who turns rough app ideas into clear, buildable briefs for AI app builders like Lovable, Bolt, or v0.

My rough app idea: {{rough_app_idea}}
Who it's for: {{target_users}}
Must-have vs nice-to-have: {{must_have_vs_nice_to_have}}

Do the following:
1. Write a one-paragraph clear product summary restating the idea precisely, so I can confirm you understood it correctly before anything gets built.
2. List the core MVP features only (cut anything not essential to prove the concept), and separately list a 'Phase 2' list of nice-to-have features to build later.
3. Define a simple data model: the main entities/tables needed and their key fields, described in plain language (not code).
4. List the pages/screens needed for the MVP, and for each one, describe its core purpose and the 2-3 key elements it must contain.
5. Format the final output as a single ready-to-paste build prompt I can hand directly to an AI app builder, written in clear instructional language.

## Best for

Founders and non-technical builders using tools like Lovable, Bolt, Replit, or v0 who want to turn a vague idea into a precise, scoped prompt before starting to build, avoiding scope creep and wasted generations.

## Compatible tools

- Claude
- ChatGPT

## How to use

- Describe your rough app idea in a sentence or two, even if it's not fully formed.
- Clarify who the app is for and which features are truly essential versus nice extras.
- Confirm the product summary matches your actual intent before using the build prompt.
- Paste the final consolidated build prompt directly into your AI app builder to start the MVP.

## Customization tips

- If you already know your preferred tech stack or app builder, mention it so the data model and page descriptions match that tool's conventions.
- For apps with a monetization component, add a note about it so pricing/paywall screens are included in the MVP scope if truly essential.
- Ask for a simplified one-page landing version separately if you need marketing copy for the app before it's fully built.

## Example input

Rough idea: An app where students can swap study notes with classmates in the same class. Target users: College students. Must-have vs nice-to-have: Must have uploading and browsing notes; nice to have is a rating system for notes.

## Example output

A product summary confirming the note-swapping concept, an MVP feature list (user accounts, class selection, note upload, note browsing/search) with the rating system moved to Phase 2, a data model with Users, Classes, and Notes entities and their key fields, a page list including Sign Up, Class Selector, Note Upload, and Note Browser screens with core elements for each, and a final consolidated build prompt ready to paste into Lovable.