Find your idea
If you want help thinking of an idea
I'd like to build an app or website, but I need help thinking of an idea.
Ask me one question at a time about things I care about. It could be my family, school, work, a hobby, or something I wish was easier.
When you know a bit about me, suggest a few ideas. Tell me who each one could help and what a small first version could do.
Use simple words. If you do not understand what I mean, ask me. Help me talk through the ideas so I can choose one that feels right to me.
Before you start, repeat back what you understand in 3 sentences or less, in simple words, and wait for me to say yes.
See what similar apps do
Idea phase. Use an AI that can search the web.
I'm making [app name]: [what it does], for [who it's for]. Help me learn from similar apps.
1. Find several apps or websites that try to solve this problem. Link to their real pages.
2. Read their recent reviews. What do people like, dislike or ask for? Give short quotes only when useful and link to where they came from.
3. Tell me what these sources show, and keep your guesses separate. Do not invent reviews, numbers or features.
4. Tell me what these apps do well, and where they leave a gap my app could fill.
Use everyday words. Tell me if you cannot open a source. Give me a short list of links I should check myself.
Pressure test my idea
At the end of the idea work, before you plan screens. Use an AI that can search the web.
I'm thinking about building [app name]: [what it does], for [who it's for]. Help me pressure test it against what real people say. I want what's true, not a yes.
Use my notes, what people told me and my "My app is different because" sentence. Ask me one question at a time about anything missing. Don't fill gaps with guesses.
1. Find real people talking about this problem. Use Reddit as one source, plus app reviews, forums and any posts I paste in. Real posts only. For each one, give a short quote (under 20 words), the link and the date. Never make up a post, a quote, a link or a number. If you can't open Reddit or a page, tell me, and I'll paste posts I found myself.
2. What do people keep asking for? Group it. Say how often each thing came up in what you read: once, a few times, or over and over.
3. What do they use or do today instead? What do they like about it, and what bugs them?
4. What am I guessing without checking? Who might not want this, and why? Why would someone switch from what they do now?
5. Suggest changes or additions that would make my app more useful, based on what people actually said. Mark each one "first version" or "later", and say why. Keep the first version to one useful job that works all the way through.
Keep facts and guesses apart. Use plain words. Don't agree just to be nice. Finish with what I should check with real people next.
Before you start, repeat back what you understand in 3 sentences or less, in simple words, and wait for me to say yes.
Name it
Foundation phase, "Lock it in"
Give me 20 name ideas for [app name], which [what it does]. It's for [who it's for].
Names should be short, easy to say and spell, and not close to a big existing app. Group them by feel (warm, clever, simple, premium). Flag any that seem likely taken as a domain or App Store name, so I know which ones to check first.
Design direction
Plan the screens phase. Attach screenshots and colors you like.
I'm designing [app name]: [what it does]. It's for [who it's for], on [website or phone choice].
I attached screenshots of apps I love and photos with colors I like. Here's what I love about each: [one line per picture].
If [app name] were a person, this is who it would be: [3 to 5 sentences about their energy, how they talk, dress and move, and what they would never do].
The mood: [calm / playful / serious / bold / minimal / cozy].
Build me 3 different design directions. For each one give me:
- A set of colors with their exact color codes, for light and dark mode
- 2 Google Fonts: one for headings, one for paragraphs
- Button and card style: corner roundness, shadows or none, spacing
- Icon style
- 3 words for its personality
Then mock up the home screen for each direction as one HTML file I can open on my phone, side by side, with real example content. Make it feel like the person I described, using our own words and design.
Before you start, repeat back what you understand in 3 sentences or less, in simple words, and wait for me to say yes.
Draft the main screens
After choosing how the app should look
Using our agreed look, make drafts of the main screens in [app name], for [who it's for]. Start with only the screens needed to finish the main task.
Give me a single HTML web-page file I can open. Use realistic made-up example content, not filler words. Explain how to open it on my phone and computer. Tell me which buttons are just for show.
Under each screen, say what a person is trying to do and where they go next. Do not add features we have not agreed on.
Before you start, repeat back what you understand in 3 sentences or less, in simple words, and wait for me to say yes.
Create your appβs instruction folder
After the full plan, look, and voice are agreed on
Help me write the instruction folder for [app name]: [what it does], for [who it's for], on [website or phone choice].
Use our agreed plan, voice, chosen look and the two architecture guides. Ask about missing decisions rather than inventing them. Work on one file at a time. Show it to me in plain English and wait for my corrections before the next.
Pass 1: purpose and person. vision.md: why it exists. product.md: the first useful version and what waits. user.md: who it helps.
Pass 2: experience. voice.md: how it speaks. design-canon.md: agreed visual rules. non-negotiables.md: promises we must keep.
Pass 3: working parts. architecture.md: how the parts fit together. privacy.md: what information we keep and why. safety-rules.md: the safety rules for this app (see below). build-order.md: the order of work and how we check each part.
For safety-rules.md, use my answers about where people use the app, private or shared, sign-in and saving, and phone features, plus the login, sharing, payments, AI and phone features in our plan. Keep it short. Include:
- Who can see, add, change and delete each kind of saved information.
- Where information is saved, and what never leaves the device.
- Collect only what a feature needs.
- Secret keys never go in a chat, the code or the files people download.
- Each phone feature we use, why, and what happens if someone says no.
- One rule for each of these that our plan includes, and nothing for the ones it doesn't: sign-in, sharing between people, posts or uploads, kids or teens, AI, payments.
- What we must test before any real person's information goes in.
Keep the files short enough to read. Explain technical words. Mark questions we have not answered. For each choice, say why it supports the person using the app. Save the approved files in a folder named docs. Use Markdown, ordinary text with headings and lists. Do not build app code yet.
Before you start, repeat back what you understand in 3 sentences or less, in simple words, and wait for me to say yes.
Open my first test version
After the foundation files. Before saved information and working screens
Read the foundation files for [app name]. Use the platform and tools in our agreed plan.
Make the smallest real project that runs on the phone or browser we chose. Explain what you need to install before you do it. Do not add features yet.
Keep secret settings out of GitHub and out of code sent to the browser or phone. Use made-up test information.
Write a README, a file explaining the project, with the steps to install, run, and check this starting version. Tell me what I should see. If it fails, stop and help me fix that first.
Once it opens, help me check the changes. Save a version of the working files and send it to my current working version on GitHub. Your tools call these steps commit and push. Give me a link so I can check that the files arrived. Check whether sending the files would also publish them; do not publish unless I asked you to.
Before you start, repeat back what you understand in 3 sentences or less, in simple words, and wait for me to say yes.
Make a real test version
Before inviting testers
Read the foundation files for [app name]. We chose [website or phone choice].
Help me make a real test version for that platform. Check the current official instructions first. Explain any account or approval we still need. Do not treat a website preview as an installed phone app.
For a website, help me open the exact preview on my phone and computer. For an installed phone app, guide me through preparing the files, confirming who made them, sending them to the testing service and installing the test version. Explain the tool labels build, sign and upload when they appear. Explain the test group rules that apply to my account.
Use made-up test information. Check the main task, saved information after reopening, sign-in if needed, private-data access, and account deletion if the app has accounts. Check that error reporting works. Record the version and results.
Check that our privacy and support pages work before we invite anyone. Stop and explain any failed check. Do not publish a public release or send invitations yet.
Before you start, repeat back what you understand in 3 sentences or less, in simple words, and wait for me to say yes.
Make the screens easy to read and use
Before adding more working screens
For [app name], set up these basics using the devices in our plan:
1. Keep words shown on screen in shared text files, so we can change or translate them later.
2. Support light and dark mode using shared named colors, sometimes called design tokens.
3. Make text readable when the person increases text size or browser zoom.
4. Make buttons easy to reach and tap. Give them names a screen reader can read aloud. Use colors with enough difference between text and background. Support keyboard use where it applies.
Check the current accessibility guidance for our devices. Use it to choose sizes and behavior, rather than assuming one measurement fits every device.
Explain each choice in everyday words. Show me how to try it, what I should see and what still needs checking.
Before you start, repeat back what you understand in 3 sentences or less, in simple words, and wait for me to say yes.
Write my building prompt
Build the screens phase. One working task at a time
Write me a prompt for my chosen building AI to build [feature] in [app name], following docs/architecture.md, docs/design-canon.md and docs/build-order.md.
Use the storage and access rules we already built. Make this one task work from start to finish before adding more.
Check add, save, close and reopen, load, edit, and delete where this task needs them. Check what a person sees when nothing is saved yet, something is loading, a save fails or an action is not allowed. If accounts are part of the plan, check that another account cannot reach private data.
Break it into small steps I can test one at a time. After each step, tell me exactly what I should see if it worked, and what to paste back if it did not. Fix failed checks before moving on. Help me check the work, save a version and send it to GitHub. Check whether sending it would also publish it; do not publish unless I asked you to.
Before you start, repeat back what you understand in 3 sentences or less, in simple words, and wait for me to say yes.
Something broke
Any time. Paste the exact error
Something broke in [app name].
What I did: [steps]
What I expected: [...]
What happened: [...]
Exact error text: [paste it]
Explain in plain English what the error means, the most likely cause, and the fix. Don't touch files that aren't related. If you're guessing, say so.
Ask another AI to check the work
After a few small changes
Review the latest changes in [app name] against its instruction folder. I will share the changed files, what the task should do and the test results.
Find bugs, missing checks and changes that do not match the plan. Point to the file or result that supports each concern. Say if you need more information.
Explain the most important problems in plain English. For each, give me one small fix and a way to check it. I will take the fixes to my planning partner, which writes the prompts for my building AI. Do not change the app or claim it is safe just because the review found nothing.
Explain it more simply
Whenever a word, step or answer is still unclear
Explain [word, step or error] in even plainer English. Use short sentences and everyday words. Explain any new words you need to use. If a word is shortened, like API or CSS, give its full name and then explain what it does.
My app is [app name]: [what it does]. Show me an example from my app. Then tell me one small step I can try and how I can check that it worked. If I do not need this yet, tell me it can wait.
If I am still unsure, try a different example.
Check private information and account access
After saved information is set up, and again before real people try the app
Check the parts of [app name] we have built. Read the plan and actual files first. Explain what you can and cannot check.
Look for:
- Secret keys or passwords in chats, public app files or GitHub. Explain which settings are public and which must stay secret.
- Rules for who may add, read, change or delete each saved item. If we use Supabase, check Row Level Security (RLS) and other needed permissions. Turning RLS on alone is not the whole check.
- Sign-in, sign-out, getting back in and deleting an account, if we have accounts.
- Private information reachable from another account or while signed out. Test the rules behind the screens as well as the screens themselves.
- Information we collect but do not need.
Use made-up test information. Show what passed and failed. Explain the most important fixes and how to test them again. Tell me where a qualified person needs to review the work. An AI review alone is not proof of safety.
Check that people with different needs can use it
Before sharing a test version
Help me check that [app name] is easy to use for people with different needs.
Try the main task on each device in our plan. Check larger text, light and dark colors, button sizes and anything explained only by color. Check keyboard use for the website.
A screen reader reads the screen aloud. Help me try VoiceOver on Apple devices or TalkBack on Android, as needed. Show how to turn it off too. Check that buttons have clear names and are read in a sensible order.
Tell me what you actually tried and what still needs a person to test. Explain each problem and fix in plain English.
Prepare the appβs store page
App Store and Google Play phase
Help me prepare the App Store page for [app name]: [what it does], for [who it's for].
Read Apple's current official requirements for the app name, subtitle, description, search words and screenshots. Explain the limits in plain English.
Draft those fields using only tested features. Ask about missing facts. Check the app and its connected services before drafting the privacy answers.
Explain any review rules we still need to meet and how to check each one. Leave the page ready for me to read. Do not submit it yet.
Privacy and support pages
Website phase. Before you send it to the stores
Help me write two simple pages for [app name]: [what it does], for [who it's for]. Platform: [website or phone choice].
1. A privacy policy in plain English. Ask me first exactly what the app collects (email, name, photos, location, health info, anything else), where it's stored, who can see it, and which outside services touch it (like Supabase, Sentry, PostHog, Stripe). Then write: what we collect, why, where it lives, who we share it with and whether we sell it; do not assume the answer, how long we keep it, how someone can delete their account and data, and how to contact us.
2. A support page: our support email, 5 common questions with short answers, and step by step how to delete an account.
Keep both warm and short, at a sixth grade reading level. Flag anything that should be checked by a lawyer. This is a starting draft, not legal advice.
Launch story and posts
Launch phase
Help me launch [app name]: [what it does], for [who it's for].
First, interview me with 5 short questions about why I made it and what was hard. Then write:
1. My "why" in 3 sentences, in my own voice. Use my words, not marketing words.
2. A one line bio for Instagram and X.
3. 8 posts for the two weeks around launch: the problem, me building it, a behind the scenes moment, the demo, the first person using it, launch day, a thank you, and one asking for feedback.
4. A 30 second demo video script: what to show on screen, and what to say.
No hype words, no fake numbers, no testimonials I don't have. Plain, warm and specific.
Help the AI understand your idea
When its feedback misses what you mean
I think you may have missed part of my idea for [app name]: [what it does].
Here is what matters to me: [why I care].
Here is what I think you got wrong: [the point you missed].
Here is the full picture: [who it helps, what they need, and how the app helps].
First, tell me what you now think my app does. Ask me about anything you still do not understand. Then look at the idea again.
Tell me which concerns still matter and why. Do not agree just to be nice. Help me check the facts and choose what to keep or change. Use simple words.
Write the full plan
After choosing your idea, look, and voice
Help me write a full plan for [app name]: [what it does]. It is for [who it's for], on [website or phone choice]. This plan is called a specification, or spec.
Use what we have agreed on, my design examples, my brand voice, and the two architecture guides I attached. If you cannot see one of them, tell me. Ask one question at a time about missing choices.
Build the plan in small parts so I can read it:
1. Who this is for and what it helps them do.
2. What the first version does, and what can wait.
3. Each main screen: what it is for, what is on it, and what each button does.
4. The steps a person takes to finish the main job.
5. What they see when there is no data, when something is loading, or when something fails.
6. What data we keep, where it lives, and who can see or change it.
7. The look and voice we chose, plus what makes it easy to read and use.
8. Any login, sharing, payments, AI, or phone features we chose. Leave out what we do not need.
9. What to build first and how we will know each part works.
Use words a sixth grader can understand. Point out open questions. Do not guess or write code yet. Let me fix the plan before we turn it into the foundation files.
Before you start, repeat back what you understand in 3 sentences or less, in simple words, and wait for me to say yes.
Save and check my work
When a small change works, or before adding it to the main version
Help me save and check the latest work on [app name].
First, read the project rules and tell me which working version we are on (the branch). Show me what changed. Check the parts that changed and run the checks the project needs. Tell me what passed, failed, or could not be checked.
Keep passwords, secret keys, and private data out of the code. Save a version with a note about what changed (a commit). Send that saved version to GitHub if the project is connected (a push). Before sending it, check whether this would also put the change online. Do not publish unless I asked you to. Give me a link to the saved files so I can check they arrived.
If this is ready to add to the main version (a merge), explain what it would add. Check that it is the same version you just reviewed. Tell me if this step would also put the change online. Only add it to the main version or publish it if I asked you to. Otherwise, leave it ready for review.
Use simple words. Do not call the app tested if you only checked that the code builds.
Help me stop here
When you need to leave or switch AI tools
I need to stop working on [app name] for now. Help me leave a short note so I can come back later or use another AI.
Tell me:
- What we changed and where the files are.
- What we checked, what worked, and what is still untested.
- The last choice we made and why.
- Where to find the working version and its latest saved copy on GitHub. Include the exact working-version name (branch) and saved-version label (commit ID) for the next AI.
- What still needs saving or fixing.
- The next small step and the prompt to start it.
List the files the next AI needs. Give me those files or links I can use. Do not include passwords, secret keys, or private user data. Keep the note short and easy to read. Do not mark unfinished work as done.
Make clean files of my existing logo
Website module, already have a logo
Here's my current logo for [app name]: [attach it]. My business: [what it does], for [who it's for].
My colors: [hex codes, or "use the colors in my logo"]. My fonts: [if you know them].
1. Turn it into a clean, shape-based SVG picture file that stays sharp at any size. Keep it looking exactly like my logo unless I ask for changes.
2. [Keep it exactly the same / Refine it a little: describe what you want, like "cleaner lines," "a more modern font," "simpler shape"]. If refining, give me 3 options, from a tiny tweak to a bigger refresh, so I can pick.
3. Make every version I need: light and dark, with and without a background, a square icon, and a favicon, the small icon in a browser tab.
4. Only if I need printed items, make simple versions: one color only (black, white, and my main color), a stacked version and a wide version, and a tiny mark for small things like pens. Tell me which version works best on a tote bag, a coffee mug, a hat and a sticker.
Don't change my business name or invent a new logo unless I ask. Give me each file with a clear name, like lunchbox-logo-dark.svg.
Logo ideas
Website module, make your logo
Help me design a logo for [app name]: [what it does], for [who it's for].
I attached logos I love. Here's what I love about each: [one line per logo].
My colors: [color codes, or attach a picture of the colors]. My fonts: [heading font] and [paragraph font].
If my app were a person: [paste your app's personality].
Give me 5 different logo ideas. For each one:
- Draw it as a shape-based SVG picture file I can open in my browser
- A version for light backgrounds and one for dark
- Show how it looks tiny, as an app icon and a browser tab icon
- One sentence on why it fits my app
Keep them simple and easy to recognize small. Don't copy any logo I attached. Once I pick one, help me make every file: SVG and PNG, light and dark, transparent and with a background, an app icon at the current size my chosen store requires, and a favicon, the small icon in a browser tab.
What people google
Website module, plan your pages
My app is [app name]: [what it does], for [who it's for].
Suggest questions people with this problem might type into a search tool. Use their everyday words.
Check a few actual searches and source pages if you can browse. Separate those findings from your guesses. Do not invent search counts.
Choose up to five questions my website could answer well. For each, suggest a clear page title and the helpful answer the reader should get, even if they never use my app. Link the sources I should check.
Website mockup
Website module, mock it up
I'm making a website for my app [app name]: [what it does], for [who it's for].
I attached screenshots of websites I love. Here's what I love about each: [one line per site].
My app's colors: [paste color codes or attach your color examples].
My app's fonts: [heading font] and [paragraph font].
If my app were a person: [paste your app's personality].
The one thing I want visitors to do: [join the waitlist / download the app].
Build 3 different directions for the home page. Each one is a single HTML file I can open on my phone, with real example words (no filler words). Use my colors and fonts, and make it feel like the person I described. Borrow the feeling of the sites I love, but don't copy any of them.
It has to work on a phone AND a computer: one website that rearranges itself to fit, phone first. Nothing cut off, nothing too small to tap, and no scrolling sideways unless I ask for a horizontal scroll.
Every page needs a footer, the area at the bottom, with: my app's name and a one-line description, links to every page, privacy, support and terms, my support email, my company name and the year.
Before you start, repeat back what you understand in 3 sentences or less, in simple words, and wait for me to say yes.
Phone and computer
Website module, check it on your phone and your computer
Make sure my website works beautifully on a phone AND a computer. Same website, same words, same links. It just rearranges itself to fit, like Gap or Banana Republic. Here's what looks wrong right now: [describe it, or say "nothing yet, just check it"]. I attached screenshots from my phone and my computer.
Follow these rules:
1. Phone first. Design for a phone about 375 pixels wide, then let it grow for bigger screens.
2. One layout that adapts. Don't hide important things on phones. Everything on the computer version is also on the phone version.
3. No sideways scrolling, unless I ask for a horizontal scroll or a carousel on purpose (a row of photos or cards I can swipe through). Then only that one row scrolls, it snaps neatly to each card, and it shows a hint like "Swipe β". Never the whole page. Nothing else is wider than the screen. Pictures shrink to fit. Long words, links and email addresses wrap.
4. Side-by-side columns stack into one column on phones. Rows of buttons and cards wrap instead of squishing.
5. Text is at least 16 pixels on phones. Paragraphs have a max width on computers so lines don't get too long. Big titles shrink smoothly on small screens.
6. Buttons and links are easy to tap: at least 44 pixels tall, with space between them. Nothing needs a mouse held over it to work.
7. No fixed heights on boxes with words in them, so text never gets cut off or stuck.
8. The menu fits on a phone. If it doesn't, use a simple menu button, and every page is still easy to reach.
9. A menu that stays at the top while scrolling (a sticky header) never covers the content. Leave room for the iPhone notch and the bar at the bottom.
10. Pictures have a set shape (aspect ratio) so the page doesn't jump while it loads.
Then check it yourself at 320, 390, 768, 1280 and 1440 pixels wide, and on a phone turned sideways. Tell me what you changed, and anything I should double-check on my real phone.
Before you start, repeat back what you understand in 3 sentences or less, in simple words, and wait for me to say yes.
Phone shell
Website module, show your app in a phone shell
Put my app inside a phone shell on my website. My app: [app name]: [what it does]. My website's colors: [color codes, or attach a picture of the colors].
I attached: [screenshots of my app screens / the HTML code of my app screens from HTML Lens].
Please:
1. Make a phone shell (a realistic phone frame, no brand logos) that fits my website's style, light and dark.
2. Put my real app screens inside it. If I gave you HTML, make it scrollable inside the phone, so people can scroll my app right on my website.
3. If I have more than one screen, make it a carousel with little dots, or a horizontal scroll on phones that snaps to each screen and shows "Swipe β". On a computer, show them side by side.
4. Also give me each screen as a PNG with a transparent background, so I can use it anywhere.
5. Make sure it works on a phone and a computer, and never makes the whole page scroll sideways.
Use my real screens only. Don't invent features my app doesn't have.
Before you start, repeat back what you understand in 3 sentences or less, in simple words, and wait for me to say yes.
Ask for a tweak
Whenever a page needs a small change
Please make one change to my website. Keep other working parts as they are.
Where: [page and part, such as the button under the price]
Device: [phone, computer or both]
What I see: [for example, the words touch the edge of the button]
What I want: [for example, more space around the words]
I attached a screenshot. Use everyday words to explain the change. You can tell me the technical term too, but explain it.
Check the page at narrow phone and computer sizes, including bigger text. Show what changed and tell me how to try it on my real device.
Before you start, repeat back what you understand in 3 sentences or less, in simple words, and wait for me to say yes.
Write page titles and search descriptions
Website module, write what shows up on Google
Help me write a short title and description for each page of [app name]'s website. The app: [what it does], for [who it's for]. My pages: [list].
Give three choices for each page. Use words a visitor would understand. Keep the title short and the description to one or two useful sentences. Google may choose different wording in its search results.
For Lunchbox, the feeling is: βChoose five school lunches and make one shopping list.β
Only promise what the app and page really do today. Explain which choice you prefer and why. Tell me where these words go in the site files and how to check that they were added.
Browser tab icon (favicon)
Website module, make the small icon for your browser tab
Make the favicon for my website. It is the tiny icon in the browser tab. My app: [app name]: [what it does], for [who it's for].
My colors: [color codes, or attach a picture of the colors]. My logo: [attach it].
- Made from my logo: [whole logo / first letter / a simple shape]
- An SVG favicon, a 32 by 32 favicon, a 180 by 180 Apple touch icon, and a 512 by 512 icon
- Make sure it's easy to see in light and dark browser tabs
- Add the page settings that tell the browser where to find the icons
Then tell me where to look for the favicon so I can check it.
Before you start, repeat back what you understand in 3 sentences or less, in simple words, and wait for me to say yes.
Share picture that works everywhere
Website module, make the picture for shared links
Make the share picture for my website. It is also called an OG image. It is the small preview people see when my link is sent in a text or posted somewhere.
My app: [app name]: [what it does], for [who it's for]. My website address: [your address].
My brand kit: [paste it from the Brand tab, or give your colors and fonts]. My logo: [attach it].
It has to look right everywhere a link can show up: text messages on iPhone and Android, WhatsApp, LinkedIn, Facebook, Instagram messages, Threads, X, Reddit, Slack and Discord. So follow these rules:
1. Size: 1200 by 630 pixels, wide. One picture for every place.
2. Safe middle: keep my logo and every word in the middle of the picture, away from all four edges. Some places cut the sides, and some show only a square from the middle. Nothing important can be lost when that happens.
3. Readable small: a few big words and strong contrast. I should be able to read it when it is the size of a postage stamp in a text.
4. File: JPG or PNG. Keep it light, under 300 KB if you can, because some messaging apps skip heavy pictures. No WebP, SVG or AVIF.
5. Personality: give me 3 different ideas. It should feel like my brand, not a template.
Before you make the final file, show me each idea three ways: full size, cut to a square from the middle, and small like a text preview.
Then add the settings to my site so every place can find the picture:
- og:title, og:description, og:url and og:image
- og:image:width, og:image:height and og:image:alt (words that describe the picture)
- twitter:card set to summary_large_image
- The picture's address must be a full https address that opens without signing in
- Put these settings in the page's own code, so they are there before any scripts run. Some apps never run scripts.
Then check it and show me proof:
1. Open the live page and list the settings you find.
2. Open the picture's address by itself.
3. Tell me how to test it: text the link to myself, and use LinkedIn's Post Inspector and Facebook's Sharing Debugger.
4. If a place shows an old picture, tell me how to ask it to look again.
Check the current rules for the places I named and tell me if any of them needs something different. Ask me before you guess.
Before you start, repeat back what you understand in 3 sentences or less, in simple words, and wait for me to say yes.
Website words
Website module, write the words
Write the words for my website's [page name] page.
My app: [app name]: [what it does]. For: [who it's for].
What people searched to land here: [the search].
My real story and facts: [paste them].
Rules:
- Plain English, short sentences, a sixth grade reading level.
- Sound like me talking to a friend, warm and a little excited, not like an ad.
- Answer the question they searched first, and really help. Mention my app only where it honestly fits.
- One main heading that says what the page is about in their words.
- No em dashes. No fake reviews, no made-up numbers, no features I haven't built.
- End with one clear next step.
Also give me a short page title and description that search tools may choose to show.
Make it stand out
When the draft is accurate but could be clearer
Help me make these words clearer and more like me talking to a friend. This is for [app name]: [what it does], for [who it's for].
The feeling I want: [three words, such as warm, clear, funny].
My draft: [paste it].
Give three choices: a simpler version, a warmer version and a bolder version. Explain which one you would choose and why.
Keep every fact true. Do not add numbers, reviews, promises or features. Use short sentences and everyday words. No em dashes or sales jargon.
Public, private or social?
Website module, before you plan your pages, to find out if you need a login
Help me decide what kind of website [app name] needs. It's [what it does], for [who it's for].
Ask me these one at a time:
1. Can anyone see it, or only people I let in?
2. Do people need their own account?
3. Can people post things other people see, like comments, photos or messages?
4. Will kids under 13 use it?
Then tell me which kind it is:
- Public: anyone can see it, no login
- Private: only people I let in, so it needs a login
- Social: people post for each other, so it needs a login, a database and rules
List what I need for my kind, in plain English, with free options first (like Supabase for logins). If kids will use it, tell me how to keep it invite-only and collect as little as possible. Tell me where I should ask an expert.
An invite-only site is not enough by itself to meet childrenβs privacy rules. Check current official guidance and tell me which decisions need qualified advice before collecting information.
Before you start, repeat back what you understand in 3 sentences or less, in simple words, and wait for me to say yes.
Double-check the words
Website module, write the words
You're my honest editor. Here are the words for my website, written by another AI: [paste].
Here's what's actually true about my app today: [paste your real facts].
Check it and give me a list:
1. Anything that isn't true, or that I can't prove yet. Quote it.
2. Anything that sounds like a robot or a commercial, with a plainer way to say it.
3. Anything a sixth grader wouldn't understand.
4. Anything missing that someone searching this would want to know.
Don't rewrite the whole thing. Just give me the list so I can decide.
Help search tools read my public pages
Website module, help Google and AI find you
Help search tools read [app name]'s website: [what it does], for [who it's for]. My domain: [address]. Do not promise a search ranking or an AI recommendation.
For each public page, check:
- A short, accurate title and description.
- One main heading, called H1, with smaller headings in a sensible order.
- Important words as real text, not only inside pictures.
- Useful picture descriptions, called alt text. Use empty alt text for purely decorative pictures. Keep image files small enough to load quickly.
- The preferred page address, called a canonical link.
- A title and picture for shared links, using Open Graph settings.
- Working links to related pages and the help and privacy pages at the bottom.
- Readable text and usable buttons on a phone and computer.
Also check:
- A sitemap.xml file listing the public pages we want search tools to find.
- A robots.txt file with instructions for automated readers. It must not be treated as protection for private information.
- Structured data, meaning labels computers can read about the app. If useful, add it as JSON-LD, with real names, prices and other facts that match the visible page. Check current search-tool support before adding optional types.
- A helpful βpage not foundβ screen, often called a 404 page, with a working link home.
Use only what this site needs. Explain technical terms as you go. Show what you checked, the results and what I should try myself. Keep private pages protected by real access rules.
Ask Polar to connect my website address
Website module, put it online
Polar, help me connect my website to the address I bought.
My domain: [address]. The place managing its settings: [provider]. My website host: [host]. My appβs GitHub project: [link].
1. Open the hostβs current instructions and explain which settings need to change. These are called DNS records.
2. Show the old and new values before saving. Keep existing email records unchanged, including MX, SPF, DKIM and DMARC. Explain what each does if it appears.
3. Check that my address opens the right website using https:// without a connection warning. Try the www address too if the plan uses it.
4. Check the main page links and any existing domain email.
5. Offer to help add the public website to Google Search Console and send its list of public pages, called a sitemap.
Explain one step at a time. Let me type passwords and sign-in codes. Ask before spending money, sending messages or deleting anything. Show me how to check the result.
When the AI gets it wrong
When an answer is wrong, a task fails, or a claimed fix needs proof
We are working on [app name]: [what it does], for [who it's for], on [website or phone choice]. Read the current instruction folder first.
What I expected: [what should happen]
What happened: [what I saw]
What I did: [the steps to make it happen again]
What I can show you: [error message, screenshot, files or source links, with private details removed]
1. Tell me what you know from these details and what you are guessing. Ask about anything important that is missing.
2. Explain the likely cause in everyday words. Show what supports that explanation. If unsure, say what we need to check.
3. Suggest the smallest fix. Say what it changes and what else could be affected. Keep saved information and working parts safe.
4. Show a check that catches the problem before the fix and passes after it. Do not say you ran it unless you did.
5. Give me short steps to try the task myself. Tell me what I should see. Also check what happens if a step fails.
6. Make a short note for my second AI to review. Say what still has not been checked.
Do not publish, spend money or delete data. For a wrong factual answer, use original sources and show which sentence they support.
Make my website work
After choosing the draft, before putting the website online
Help me turn the chosen draft for [app name] into a working website. It is [what it does], for [who it's for].
First read my page plan, checked words, design choices and current project files. Ask about missing details. Work in my website project, and reuse what already works.
Save short instruction files describing the site, its pages and how to build it. Make the real pages and connect the main action. For a form, tell me where messages go, who can see them and how unwanted repeated submissions are limited. Keep secrets in private settings. Do not add accounts or paid tools unless the plan needs them.
If there are accounts, private saved data or payments, stop and identify the app-path build and test work still needed. Do not pretend a visual draft has these features.
Use made-up information. Guide me through the main action on a phone and computer. Check actual form delivery, any promised email, downloads and links. Try wrong or missing input, larger text and keyboard use. Tell me what I should see and help fix failed checks.
Write the run steps in a README file and help me follow them. Save a version to my GitHub project after checking for secrets. Give me the link so I can check the files arrived. Do not publish or enable real payments yet.
Before you start, repeat back what you understand in 3 sentences or less, in simple words, and wait for me to say yes.
Check whether this version is ready to share
Before a public release, and again after an important update
Review [app name]: [what it does], for [who it's for]. We plan to release on [website or phone choice].
Exact website address or store version: [paste it].
Main task: [what a new person should finish].
Our ready-to-share checklist and results: [paste them].
Read the actual files and results available to you. Say what you inspected, what you tested and what remains unverified. Do not treat two AI opinions or a checked box as evidence that a task works.
Guide me through a new person's visit, the main task, saving and reopening if needed, account recovery and privacy rules if there are accounts, and the actual delivery of forms, downloads and promised emails. Check supported devices and readable controls.
If we charge money, use the provider's test setup with pretend money. Check success, decline, abandoning checkout, returning to paid access, a second device when promised, refund and subscription cancellation when relevant. A success page alone does not prove payment. Leave real payments off until these checks pass and the real service settings are reviewed.
Help me practice restoring a working code version on a test copy. If the app saves information, test restoring its backup separately without touching real customer data. Write short instructions for pausing sales, getting help and returning to a working version.
List what passed, what failed and what we could not check, with the exact version and date. Separate failures that block the main task, privacy, payment or delivery from improvements that can wait. Give me one next action at a time. Do not publish, charge real money, contact people or delete real data.
Build sign-in and a safe way to leave
When your plan says people need accounts. Test accounts only.
We're adding sign-in to [app name]. First read our plan, my answers about who sees what and where things are saved, and docs/safety-rules.md. Tell me which parts below our plan needs, and skip the rest. Use made-up test accounts only.
1. Sign up, sign in, sign out and getting back in. If we use passwords, test a password reset. If we use email links, test getting a new link.
2. Delete account, inside the app, in settings. Before they confirm, tell the person what will be deleted. Then delete their account and their saved information. Apple asks for this in any app with sign-up.
3. Make two test accounts, A and B, with made-up details. We'll use them in the next step to check who can see what. Write down how to make them again.
4. If people sign in with an email link, or the app sends emails, set up a real email sender. Supabase's built-in sender is only for trying things out. It sends a couple of emails an hour, and only to people on your own team.
5. If kids or teens can make an account, stop before building it. Tell me what the rules ask for and who should check it.
Explain each part in plain words. Run the tests and show me what passed before you say it's done.
Before you start, repeat back what you understand in 3 sentences or less, in simple words, and wait for me to say yes.