wowprompt

Low-fidelity wireframe spec written screen by screen from requirements

Turns a feature description into a text wireframe for each screen: the regions from top to bottom, every element with its label, the primary action, states and where each tap leads, written so a designer can draw it quickly or a developer can build a rough version. Use it at the start of a feature when there is a requirements note but no design yet.

A screen list with a top-to-bottom text wireframe for each, element labels, primary actions, empty and error states and a flow table linking screens
The output this prompt produced, unedited.

The prompt

Role

You are a product designer who writes clear wireframe specs before opening a design tool.

Task

Write a low-fidelity wireframe spec for the feature below.

Inputs

  • Product and platform: [e.g. a society maintenance app, Android first, 360px wide screens]
  • Feature and the user goal: [e.g. pay monthly maintenance and download a receipt]
  • Requirements or user stories: [paste]
  • Existing screens it connects to: [e.g. home, profile]
  • Data available on each screen: [e.g. flat number, dues, payment history]

Steps

  1. List the screens needed, and question any screen that could be merged.
  2. For each screen, describe the regions top to bottom: header, main content, actions, bottom area.
  3. List every element in each region with its exact label text, type (button, list, field, toggle, card) and what it shows.
  4. Mark one primary action per screen.
  5. Describe the empty, loading and error states.
  6. Say where each tap or button leads.

Output format

  1. Screen list with one line each on its purpose.
  2. For each screen, a block like:

Screen: Pay dues Header: back arrow, title "Pay dues" Content: card with flat number and amount due; list of months unpaid Primary action: button "Pay now" fixed at the bottom Empty state: "No dues. You are all paid up." Error state: ...

  1. Flow table: | From screen | Action | To screen |
  2. Open questions for the product owner.

Guardrails

  • Design for one-hand use on a small phone first; primary actions in thumb reach.
  • No colours, fonts or visual styling; this is structure only.
wireframe specificationlow fidelity wireframescreen by screen specux wireframe from requirementsmobile app wireframescreen flow

How to run this

Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.

The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.

Related prompts

All productivity