Replit

You are my app planner. I'll build it with Replit Agent.

My business: [what you do]
What I need from a new customer: [the fields]
What happens after they submit: [for example: they see a thank you, I get an email]
Who sees the list: [just me]

1. List the fields, which are required, and why each is needed.
2. List the screens: the customer form, the thank you, and my list (behind a log in).
3. Write ONE prompt for Replit Agent: phone first, a database for answers, my list behind a log in only I can use, an email to me on each new entry, any keys in Secrets.
4. 6 tests: form saves, required fields stop a blank form, my list needs a log in, a customer can't see other customers, the email arrives, it works on a phone.

Rules:
- No payment, no customer accounts.
- Ask for only the fields I listed.
- Use only what is in my data and what I tell you. Never make up a name, number, date, price, link or promise.
- If something you need is missing, write [check: what is missing] in that spot and keep going.

Last, save these steps as a skill called 'Intake App' so you do it this way each time I build an intake form app.

Built from: The Sales Acceleration Formula, Mark Roberge, Chapter 11: Converting Inbound Interest into Revenue

You are my app planner. I'll build it with Replit Agent.

My CSV columns: [list them, for example: date, rep, calls, conversations, meetings, deals won, amount]
The numbers I want each week: [up to 5]
Who looks at it: [me, or the team]

1. Write each number's exact math in plain words, like "meetings divided by conversations".
2. Write ONE prompt for Replit Agent: upload a CSV, show the 5 numbers for the week, a small chart of the last 8 weeks, a table by rep, no log in if only I use it on my own link (say so), no outside data.
3. Make a sample CSV of 10 rows with fake names, and write the right answer for each number so I can test the app.

Rules:
- Use my math only. If a number could divide by zero, show "n/a".
- Use only what is in my data and what I tell you. Never make up a name, number, date, price, link or promise.
- If something you need is missing, write [check: what is missing] in that spot and keep going.

Last, save these steps as a skill called 'Sales Numbers Page' so you do it this way each time I build a numbers page.

Built from: Fanatical Prospecting, Jeb Blount, Chapter 6: Know Your Numbers

You are my launch checker, inside my Replit project.

What the app does: [one line]
Who will use it: [customers, staff]
Does it store personal details? [yes or no, which ones]

Check each and mark PASS or FIX, with the file and line for any FIX:
1. Keys and passwords live in Secrets, not in the code.
2. Test or fake data is removed from the live database.
3. Pages that should need a log in really do. Try the address without logging in.
4. A user can't see another user's data by changing a number in the link.
5. Forms handle blank and silly input without crashing.
6. It works on a phone screen.
7. It's on a deployment, not the test preview link.
8. Errors don't show code or keys to the user.

Then the exact fix for each FIX, smallest first, and what to watch the first week.

Rules:
- Don't change anything until I say yes to each fix.
- Use only what is in my data and what I tell you. Never make up a name, number, date, price, link or promise.
- If something you need is missing, write [check: what is missing] in that spot and keep going.

Last, save these steps as a skill called 'Launch Check' so you do it this way each time I'm about to share an app.

Built from: Extreme Ownership, Jocko Willink and Leif Babin, Chapter 9: Plan