---
name: v0-lovable-app-spec
description: "Turns an app idea into a build prompt for a prompt-to-app tool that fixes layout, empty states and error handling up front. Use when a founder or designer is about to describe an app to a prompt-to-app builder and needs a precise first build prompt. Do not use for writing production specs for engineers or reviewing generated code. Related topics: AI, Coding, No Code."
---

# v0 / Lovable App Spec

Turns an app idea into a build prompt for a prompt-to-app tool that fixes layout, empty states and error handling up front.

## When to use

Use this skill when a founder or designer is about to describe an app to a prompt-to-app builder and needs a precise first build prompt. Do not use it for writing production specs for engineers or reviewing generated code.

## Workflow

1. Ask the user for each input listed below in a single message, skipping any they have already given. Where options are listed, offer them, but accept other answers too.
2. Summarise the app in one paragraph naming the user and the core job.
3. List each screen with its contents and layout in one or two lines.
4. State the visual direction, framework and platform, and the auth method if accounts are needed.
5. Write the v1 feature list and an explicit out-of-scope list.
6. Add empty, loading and error states for each screen and some sample data, then confirm no screen is left undefined.

## Inputs

- **What the app does** (longer free text)
- **Main screens** (longer free text)
- **Look and feel** (free text, e.g. "clean and minimal or playful or like Linear")
- **Must-have features for the first version** (longer free text)
- **Needs accounts or login** (choose one: Yes, No)
- **Where it will run** (choose one: Web app, Mobile, Both, Not sure yet)
- **Framework preference** (free text, e.g. "React or Next or plain HTML or no preference")

## Output

A build prompt with a summary paragraph, a screen-by-screen list, visual direction, v1 and out-of-scope lists, and empty, loading and error behaviour.

## Prompt template

Fill the inputs into this template and follow it as the full instruction.

### App Build Prompt

Write the description of an app for a prompt-to-app builder so the first generation comes back close to what is wanted.

- What the app does: {{What the app does}}
- Main screens: {{Main screens}}
- Look and feel: {{Look and feel}}
- Must-have features for the first version: {{Must-have features for the first version}}
- Needs accounts or login: {{Needs accounts or login}}
- Where it will run: {{Where it will run}}
- Framework preference: {{Framework preference}}

Turn this into a clear build prompt with a one-paragraph summary, the screens and what is on each, the visual direction, and the v1 feature list with an explicit out-of-scope list. Front-load what these tools get wrong when left vague: the layout of each screen, the empty state of every list, what happens on error and while loading, and the sample data to show. If login is needed, name the auth method. Keep the prompt to what the builder can do in one pass.

## Pitfalls

- Listing features beyond v1, which makes the generator produce shallow versions of everything.
- Leaving empty and error states unspecified so the first screen looks broken.
- Describing the look with only an adjective rather than a reference or concrete choices.
