Ship an app-builder prompt that actually builds.

“I know the tool I want to build, but my Lovable prompts keep producing mush.”

Turns an app idea in plain words into the product, pages, data model, interactions, and what to build first.

RUN THE OPERATOR SYSTEMEASY✓ APPROVED 4/4
EXAMPLE PROMPTS
>Turn this app idea into a build prompt for Lovable: [describes the tool]
>Write a v0 prompt for a deal review dashboard with the pages and data model
>What should the app builder build first? Here is my rough idea for a lead tracker
ABOUT THIS SKILL

What this skill does

Takes an app idea in plain words and returns a build prompt structured the way AI app builders want it: the one-sentence product, the pages, the data model, the core interactions, the styling, and what to build first. A vague prompt gives you a vague app. This one gives the builder a spec.

Inputs

An AI app builder to paste the result into (Lovable, v0, Bolt, Replit, or similar). No connectors. Bring the idea; the skill builds the prompt.

How it works

  1. 1
    1. Name the product in one sentence: what it is and who it is for.
    1. List the pages or screens, each with its job in a phrase.
    2. Define the data model: the few objects and their fields. Builders go sideways without this.
    3. Spell out the core interactions: what happens when the user clicks the main button.
    4. Set the styling: the visual direction and the one or two brand colors.
    5. Sequence the build: "Start with the data model and the main page. Get that working before anything else." This stops the builder from trying to do everything at once and breaking.
    6. Add guardrails: no auth in v1, mock the data, keep it one page until it works.

Output format

Idea: "a tracker for my outreach experiments." Built prompt:

Build a single-page web app: an outreach-experiment tracker for a salesperson.

Pages: one main page, a table of experiments with an "add experiment" form.

Data model:
- Experiment { name, channel, hypothesis, sent, replies, status, notes }

Interactions:
- "Add experiment" opens a form, saves a row to the table
- Each row shows a computed reply rate (replies / sent)
- A status pill: running, won, killed

Styling: clean, lots of whitespace, one orange accent, system font.

Build order: first the data model and the table with mock rows. Get that
rendering. Then the add form. Then the computed reply rate. No auth in v1.
RELATED SKILLS
ALL RUN THE OPERATOR SYSTEM SKILLS →