Hey SI Ship It: take your first app live
$9 one-time. 15 prompts + security checklist, instant download.
A $9 add-on that picks up where the Starter Pack leaves off. You'll need an app that runs and is saved in Git.
What's inside: 15 prompts in 6 sections
Before you ship
01 Am I ready to ship? · 02 Get my secrets out of the code
Deploying to the web
03 First deploy · 04 Environment variables online · 05 Read my deploy log · 06 Undo a bad deploy
Custom domain
07 Connect my custom domain · 08 My domain isn't working
Database and login
09 A basic database (safely) · 10 Login that locks down data · 11 Prove users can't see each other's data
Taking payments
12 Stripe or Lemon Squeezy · 13 Checkout in test mode · 14 Unlock access after payment (webhooks)
Keeping secrets safe
15 I think I leaked a key, plus the Ship It security checklist
You get a PDF, PROMPTS.md, CHECKLIST.md, a license and a README. It works with Cursor, Claude Code, Replit, Lovable and Bolt. It's educational: AI tools make mistakes, so review and test before real people or real money touch your app.
Example prompts
Three of the 15 prompts, word for word from Ship It. Copy one, paste it into your AI coding tool, and fill in the [PLACEHOLDERS]. Never paste a real key into a prompt.
02. Get My Secrets Out of the Code
Find every secret in my project and move it into environment variables. I'm a beginner, so explain as you go.
Services my app talks to: [LIST - e.g. "Supabase, Stripe, OpenAI"]
Framework: [e.g. NEXT.JS / VITE + REACT / OTHER]
Please:
1. Search the whole project (including config files) for API keys, passwords, tokens, and connection strings. List what you find by FILE and LINE. Do NOT print the actual secret values back to me.
2. Move each one into .env, and add only the NAME to .env.example.
3. Sort every variable into two groups and explain why:
- "Safe for the browser" (public/publishable keys, which need my framework's prefix like NEXT_PUBLIC_ or VITE_)
- "Server only" (secret keys that must NEVER have that prefix or reach the browser)
4. Check that .env is in .gitignore.
5. Check my Git history for any secret that was committed before. If one was, tell me which service it belongs to so I can replace it (see Prompt 15).
6. Show me the final list of variable NAMES I'll need to add to my hosting dashboard.03. Ship It Live (First Deploy)
Help me deploy my app for the first time with [VERCEL / NETLIFY]. I'm a beginner. Give me click-by-click steps.
Stack: [YOUR STACK]
Code is on GitHub: [YES - repo name: ___ / NO]
Environment variable NAMES I need: [PASTE THE LIST FROM PROMPT 02]
Services that need to know my live address: [e.g. "Supabase auth", "Stripe redirect URLs", "none"]
Please:
1. If my code isn't on GitHub yet, help me push it (private repo is fine).
2. Walk me through importing the repo into [VERCEL / NETLIFY], and tell me whether the detected build settings (build command, output folder) are right for my stack.
3. Tell me where to add each environment variable in the dashboard, and which ones go in Production vs. Preview.
4. Explain what happens next time I push to GitHub (automatic redeploys, preview links for branches).
5. List every setting in other services I need to update to my new live address.
6. Give me a 5-minute test plan for the live site.15. I Think I Leaked a Key
I think I leaked a secret key. Help me contain it, step by step, in order of urgency. Don't ask me to paste the key.
Which service: [e.g. "Stripe secret key" / "Supabase secret key" / "OpenAI API key"]
How it leaked: [e.g. "committed to a public GitHub repo" / "had a NEXT_PUBLIC_ prefix" / "pasted in a forum post"]
When: [e.g. "about 2 days ago"]
Is the repo public or private? [PUBLIC / PRIVATE]
Please:
1. Tell me how to create a new key and turn off (revoke/roll) the old one in that service's dashboard. Do this first.
2. Tell me where to update the new key: .env locally, my hosting dashboard, and anywhere else it's used. Then remind me to redeploy.
3. Show me how to check the service's logs or usage for anything I didn't do (unexpected charges, API calls, data changes).
4. Explain why deleting the file or commit is NOT enough, and whether I should also clean the Git history.
5. Fix the code so this can't happen again (environment variables, .gitignore, no browser prefix on secrets).
6. Suggest spending limits or alerts I can turn on for this service.$9 one-time. 15 prompts + security checklist, instant download.
Secure checkout by Lemon Squeezy, our merchant of record. 14-day refund: Refund Policy · Terms & License
The first 10 orders get 30% off every future Hey SI pack. We'll email you a code when a new pack comes out.
New here? Start with the $12 Starter Pack.