Six prompts for the thinking that comes before the code: turning a rough idea into a brief, defining who the product is for, mapping the user flow, sorting features into what a first version needs, and converting a specification into a sequence of build prompts.
How to use these prompts
Copy a prompt into any capable AI model, then add your own material underneath it. Most of them are written to work on whatever you paste in: a plan, a draft, a decision you are weighing, a set of notes. The ones marked Assistant run as a conversation rather than a single exchange, so expect the model to ask you questions before it produces anything.
The prompts are deliberately short. They carry a method, not a script. Adapt the wording to your situation and the model you use.
Filter by what the prompt does
Showing all 6 prompts
Build-Prompt Generator
Turns a spec into a sequence of precise prompts for an AI coding tool.
- Communication
- Prompt
Turn the following spec or feature into clear prompts for an AI coding tool (such as Lovable, Cursor, or Claude). Break the build into a logical sequence of steps, and for each write a precise prompt stating what to build, the relevant context, and what 'done' looks like. Note where I should test before moving to the next step. The spec or feature is:
Feature Prioritizer
Sorts features into must / should / could for a first version.
- Evaluation
- Prompt
For the following product and its candidate features, help me prioritize. Sort the features into must-have, should-have, and could-have for a first version, judging each on user value and effort. Recommend what to build first and what to defer, and flag any feature that seems essential but isn't. The product and features are:
Project Brief Builder
Turns a rough product idea into a clear project brief before building.
- Framing
- Assistant
Your role is to help me turn a rough product idea into a clear project brief before any building starts. Ask me focused questions — one at a time — to pin down what we're building, the problem it solves, who it's for, the core outcome, and the constraints. When you have enough, write a concise brief (purpose, users, core features, constraints, success criteria) and check it with me. Start by asking what I want to build and the problem behind it.
Spec / PRD Writer
Turns an idea or brief into a structured build spec a builder could work from.
- Synthesis
- Assistant
Your role is to help me turn an idea or brief into a clear build specification. Working from what I give you, draft a structured spec — purpose, users, features with what each should do, key user flows, requirements, and what's out of scope — asking me about anything ambiguous rather than guessing. Keep it precise enough that a builder (human or AI) could work from it. Start by asking me to share the idea or brief.
User Flow Mapper
Maps the steps a user takes through the product, with drop-off risks.
- Framing
- Prompt
Map the key user flows for the following product. For each main task a user needs to accomplish, lay out the steps from entry to completion, the decisions and screens along the way, and where things could go wrong or users could drop off. Flag the one or two flows that matter most to get right. The product is:
User Personas
Generates relevant user personas and what each would want from the product.
- Framing
- Prompt
For the following product or project, generate the key user personas it needs to serve. Create three or four distinct personas — each with their context, goals, and frustrations — and for each, spell out what they would most want from the product and what would make them abandon it. Flag which persona is the primary one to design for. The product or project is:
Common questions
What should I do before asking AI to build something?
Define what you are building and for whom. Project Brief Builder turns a rough idea into a clear brief, User Personas establishes who it serves, and Spec or PRD Writer produces a structured specification. Most failed AI builds fail at this stage, not at the coding stage.
How do I decide what goes into a first version?
The Feature Prioritizer prompt sorts features into must, should, and could for a first release. Run it after User Flow Mapper, which shows where users are most likely to drop out and therefore which parts of the flow cannot be cut.
Is there a good way to prompt an AI coding tool?
Work from a specification rather than a description. The Build-Prompt Generator prompt takes a spec and turns it into an ordered sequence of precise prompts, which produces far more reliable results than a single long request.