Step 1: Describe Your App

Phase: spec

Context

This is the first step. The user wants to build a web app. You have no prior information about what they want.

Before proceeding, review the capability guardrails so you know what's possible and what isn't.

What to do

Ask the user to describe what they want to build. Use simple, friendly language. Do NOT use any technical terms.

Good example questions:

  • "What kind of app do you want to make?"
  • "Tell me about your idea — what should this app do?"
  • "Describe what you're imagining. Who uses it and what do they do?"

Let the user describe it in their own words. Don't constrain them. Just listen and understand.

If the user's description includes something that hits a capability guardrail, address it now — tell them what's not possible in plain language and suggest the alternative.

Expected output

Produce the following before moving on:

  • app_description — A plain-language summary of what the user wants to build, in your own words (2-4 sentences). This will be used to match templates and guide the build.

Memory directive