Replit lessons: workflows, costs, mistakes, prompts
Reference lessons to use after the step-by-step tutorial.
Prompt library
Before building, list the pages, data and features you plan. Wait for my OK.Add [feature]. Don’t change anything else. Tell me what files changed.Review this app for security problems: exposed keys, missing input checks, open admin pages.Mistakes and fixes
| Mistake | Fix |
|---|---|
| No plan | Ask for a plan first |
| Keys in code | Use Secrets |
| Surprise bills | Check usage weekly |
Use-case playbooks
First app
- Describe it in 3 sentences.
- Approve the plan.
- Test each page.
Add a feature
- Describe one feature.
- Let the Agent build it.
- Retest old features.
Publish
- Check Secrets.
- Test on a phone.
- Deploy and watch usage.
Troubleshooting
My credits ran out.
Core includes $20 and Pro $100 of monthly credits. Check what used them (AI vs hosting).
The Agent broke my app.
Roll back to a checkpoint and ask for smaller changes.
The answer cites a page that doesn't say that.
Treat the claim as unverified. Ask it to quote the exact sentence from that page, or say it isn't there. Then open the page yourself.
It forgot my earlier instructions.
Long sessions push early text out of context. Put standing instructions where Replit keeps them (One App per project; write a short brief at the top of the Agent chat and keep a checklist of features done.) and start fresh.
It agrees with everything I say.
Ask it to argue the other side and list the strongest evidence against your view, with sources.
Cost control
- Core: $20/month, or $18/month billed yearly; includes $20 of credits toward AI models and unlimited workspaces.
- Pro: $100/month, or $90/month billed yearly; includes $100 of credits and up to 15 collaborators.
Source: replit.com/pricing, checked Oct 30, 2026. Credits pay for AI and hosting; check usage before publishing a busy app.
Credits are monthly: Core includes $20, Pro $100. AI and hosting draw from them; usage beyond that is billed (replit.com/pricing).
- Test with the free tier (if there is one) on real tasks for a week first.
- Set a calendar reminder 2 days before any renewal.
- Keep one paid tool per job, not three, unless each earns its place.
Prompt library: bad vs good
Bad: help me
Good: Build a simple web app where my book club can list books, vote, and see the top 3. Show me your plan and the pages first. Use a simple database. No login for now.
Why: situation, task, format and limits.
Bad: research this
Good: Find the 5 most relevant official sources from the last 12 months on [topic]. For each: title, date, link, and one sentence it actually says.
Why: asks for dated, quotable, checkable sources.
Bad: make it better
Good: Rewrite this for a busy customer: max 100 words, one ask, no jargon. Then list what you cut.
Why: a reader, a length and an audit of changes.
Bad: should I do X?
Good: List the 3 strongest reasons for and against X for someone in [situation]. Mark which reasons depend on facts I should check.
Why: balanced, and separates facts from judgement.
Privacy and safety
- Don't paste passwords, ID numbers, card numbers or other people's private details.
- Assume the company can read and keep your chats unless its official policy says otherwise.
- For health, money or legal decisions, confirm with a professional or an official source.
- Store API keys in Replit Secrets, never in code.
- Published apps are public; don’t put private data in them without access control.
Failure modes to watch
- Apps that work in preview but break on mobile.
- Silent cost growth from hosting and AI. Check usage.
- Agent changes that break earlier features. Retest.
When to use it vs other bots
| Use Replit for | Consider another bot when |
|---|---|
|
See: ChatGPT · Claude · Gemini · Perplexity · Copilot · comparison |
Leveled tutorials
Where these facts come from
Checked Oct 30, 2026. Plans change, so confirm on the official page before you pay.