The prompts I wish I'd had at prompt one.

Build me a web app called [YOUR APP NAME]. In one sentence, it helps [YOUR USERS] do [WHAT IT DOES]. The homepage should have a clear headline, a short subheadline, one primary call-to-action button that says [BUTTON TEXT], and three sections underneath that explain how it works. Use a clean, modern design that would look at home in 2026. Do NOT add authentication, a database, or any backend yet. Just build the front-end shell so I can see it and react to it.

I have an idea for an app that does [WHAT YOUR APP DOES] for [YOUR USERS]. I''m not technical. I want to ship the smallest useful version first. Ask me 5 clarifying questions to help you understand what really matters. Then, based on my answers, propose an MVP that has no more than 3 core features. For each feature, tell me why it made the cut and what I''d cut if I had to cut one more.

I''m a non-technical founder trying to decide what to build next. Here are my options: [LIST YOUR IDEAS, ONE PER LINE]. For each idea, rate it 1-10 on: (1) how much I''d actually use it, (2) how obvious the customer is, (3) how likely I am to finish it, (4) how much I''ll learn along the way. Then recommend ONE to start with and explain why. Be honest — if one is a bad idea, say so.

Look at the current [PAGE NAME] page. It works but feels generic. I want it to look intentional and modern — like a real product, not a template. Improve the visual hierarchy, spacing, typography, and use of color. Keep the same features and content, don''t remove anything. Explain briefly what you changed and why. Don''t use generic AI-looking gradients (purple to indigo, etc).

Something is broken. Here''s what I expected to happen: [WHAT SHOULD HAPPEN]. Here''s what actually happened: [WHAT DID HAPPEN]. Here''s the error message if there was one: [PASTE ERROR]. Before you change any code, tell me: (1) what you think the cause is, (2) what you''d check first to confirm, (3) the smallest fix. Wait for me to confirm before making changes.

Add user accounts to my app. I need: (1) email/password sign-up and sign-in, (2) Google sign-in as an option, (3) a simple profile page where the logged-in user can see their name and email and sign out. Protect these pages from non-logged-in users: [LIST YOUR PROTECTED PAGES]. Leave the rest of the site public. Use the built-in backend, don''t ask me for API keys.

Here''s an error I''m getting: [PASTE FULL ERROR MESSAGE]. I''m not a developer. Explain in plain English: (1) what this error actually means, (2) what likely caused it in MY app specifically (look at my code), (3) what happens if I ignore it. Don''t suggest a fix yet — I just want to understand it first.

Review my entire app for mobile. Assume the user is on an iPhone with a narrow screen. Find every place where: text is too small to read, buttons are too small to tap, layout breaks, or something is hidden off-screen. List them all first. Then fix them one by one, starting with the most important. Don''t make desktop worse in the process.

Write and build a landing page for [YOUR APP NAME]. It''s for [YOUR TARGET USER] who struggles with [THEIR PROBLEM]. The app solves this by [YOUR SOLUTION]. Include: a headline that names the problem, a subheadline that names the outcome, one primary CTA that says [BUTTON TEXT], three benefits (not features) written as short paragraphs, one section of social proof or trust signals (leave placeholders if I don''t have any yet), and a simple footer. Write it in a warm, human voice — no marketing jargon, no "revolutionize," no "seamless."

Here''s what my app does today: [PASTE OR DESCRIBE]. Here''s a list of things I''ve been considering adding: [LIST 3-7 IDEAS]. For each one, tell me: (1) how much it would meaningfully change the user''s experience, (2) how much complexity it adds behind the scenes, (3) whether I should do it now, later, or never. Then recommend the single next thing worth building and why.