How to use these prompts
Paste the first prompt into a brand-new, empty project folder. Once it finishes and you've looked at the result, move to the next prompt in the same folder — the agent can see everything it already built, so each prompt builds on the last rather than starting over. Test on your own phone after each step, not just at the very end.
Prompt 1 — Scaffold the app
Prompt: scaffold
I want to build a mobile app for my export business using React Native and Expo. Set up a new
Expo project called "my-export-app". Create three screens with basic navigation between them:
1. Home — a welcome screen with my company name and a short tagline
2. Products — a screen that will later show a list of products
3. Contact — a screen with our email, phone number, and a WhatsApp button
Use a clean, professional dark-navy and gold color scheme. Don't add any backend or database yet
— just the screens and navigation working, so I can see it on my own phone with Expo Go.Prompt 2 — Add a product catalogue
Prompt: product catalogue
On the Products screen, show a scrollable list of products. For now, use this sample data
hard-coded in the app (I'll replace it with real data later):
- Product name, a short description, and a price for each item
- At least 6 sample products relevant to [YOUR PRODUCT CATEGORY — e.g. "handloom textiles" or
"organic spices"]
Each product should be a card with the name, description, and price. Tapping a product opens a
detail screen showing the same information larger, plus a button that says "Enquire on
WhatsApp".Prompt 3 — Buyer enquiry via WhatsApp
Prompt: whatsapp enquiry
On the product detail screen, make the "Enquire on WhatsApp" button open WhatsApp with our
number [YOUR WHATSAPP NUMBER, e.g. +91XXXXXXXXXX] and pre-fill the message with:
"Hi, I'm interested in [Product Name]. Can you share more details and pricing for export?"
Also add a similar "Enquire on WhatsApp" button on the Contact screen with a generic message:
"Hi, I found your app and would like to know more about your products."Prompt 4 — Connect a real backend
Once the hard-coded version works and looks right, replace it with real data.
Prompt: connect a backend
Replace the hard-coded product list with data fetched from a real API. [Describe what you
actually have — for example: "I have a Google Sheet with my product list" or "I have a simple
REST API at https://your-api.com/products that returns JSON" or "Use Firebase Firestore — help
me set up a free Firebase project and a 'products' collection first."]
Show a loading indicator while data is fetching, and a friendly message if the request fails
("Couldn't load products — check your connection and try again") instead of a blank or broken
screen.Prompt 5 — A general-purpose starting prompt (not export-specific)
Use this instead of Prompt 1 if you're building something other than a catalogue/enquiry app.
Prompt: general app starter
I want to build a mobile app using React Native and Expo. The app should do the following:
[describe your app in 2-4 plain-English sentences — what problem it solves and who uses it].
Start by setting up the project and building just the first, most important screen a user would
see. Don't build every feature at once — get this one screen working and looking good first, and
I'll ask for the next screen after I've seen it.Prompt 6 — Prepare for real-device testing
Prompt: prepare for testing
Check the app for anything that would break on a real phone but not show up in a simulator:
missing error handling for no internet connection, text that could overflow on a small screen,
and any hard-coded test data I should know about before I show this to someone else. List what
you find, then fix the ones you're confident about.Rules for prompting well
- One screen or feature per prompt. A prompt trying to build five things at once produces worse results than five prompts building one thing each, reviewed in between.
- Be specific about your actual business, not generic. "handloom textiles" gets a better result than "products" — the agent has nothing to work with beyond what you tell it.
- Say what's wrong, not just "fix it." "The button text is cut off on small screens" gets fixed faster than "the button looks bad."
- Test on your own phone, not just the preview. Network delays, real screen sizes, and touch targets only show up there.
- Keep a running note of your brand details (colors, tagline, contact number) so you're not re-typing them every session — Claude Code calls this file
CLAUDE.md; other tools have an equivalent standing-instructions file.