Guides for people who build with AI
Plain-English answers to the questions that come up after your AI builds something: keeping it safe, putting it online, and fixing it when it breaks. Every guide contains something you can use on its own — a checklist, a prompt, or a translation.
Fix-prompt library
Copy-paste prompts for when an AI-built project breaks, leaks a key, or needs a pre-launch check.
Key-leak scanner
Paste your site's link; we check the page and its scripts for exposed secret keys in seconds.
How to undo in Cursor
What each Cursor undo covers, its limits, and a project-wide undo that survives any session.
How to add a login to your AI-built app
Your options for adding accounts to an AI-built app in plain English, why letting your AI invent its own login is the one bad answer, and the checks to run before real people sign up.
My AI put an API key in my app: what do I do?
Emergency steps when an API key is exposed in an AI-built app: rotate first, then remove, then check the damage. With the exact places to click for Stripe, Supabase and OpenAI.
My AI-built site worked yesterday and broke today
AI-built sites break silently weeks after launch: expired keys, hit quotas, unpaid domains. A diagnosis checklist in the order of what actually breaks, plus the fix prompt.
Backing up an AI-built app: your code is not your data
The worst AI-building losses are databases, not code. What the code/data split means, how to back up a Supabase database by hand today, and how to automate it.
Can your users see each other's data?
The most common serious flaw in AI-built apps with logins: every account can read every other account's rows. How to test it in ten minutes with two browser windows, and what to ask for to fix it.
ChatGPT wrote me a website: how do I get it online?
ChatGPT gives you code, not a website. The shortest honest path from copied files (or a downloaded zip) to a live link you can send people.
Version control for Claude Code, without learning git
What Claude Code saves on its own, what it doesn't, and a two-minute setup that keeps every version of your project recoverable from anywhere.
Cursor deleted or broke my code: recovery steps
What to do in the first ten minutes after a Cursor agent deletes or ruins your work: checkpoints, local file history, and the mistakes that make it unrecoverable.
Connecting your own web address, in plain English
What actually happens when you connect a custom domain: the two records, why it takes an hour, the classic mistakes, and what to paste to your AI when it fails.
The easiest ways to put an AI-built site online, compared
Netlify Drop, Tiiny.host, Cloudflare Pages, your builder's own button, asking the AI to deploy, and Plyo: honest comparison for people who don't code.
Every time the AI fixes one thing it breaks another
Why AI coding tools break working features while fixing others, and a routine for non-coders that stops it: scoped changes, a known-good version, and a five-minute click-through.
Git, translated for people who don't code
Repo, commit, push, branch, pull request, merge: the whole git vocabulary in one honest table, for people who build with AI and just want their project safe.
Where should I host my Bolt project?
Bolt's own hosting, Netlify via GitHub, or a tool-agnostic home: an honest comparison for Bolt builders, plus the escape route if you're already stuck.
Is my Lovable app secure? A 20-minute checklist
Three security checks anyone can run on a Lovable (or any AI-built) app before launch: data isolation, leaked keys, unlocked admin pages. No code reading required.
I connected Lovable to GitHub and now nothing makes sense
What the Lovable-GitHub connection actually does, why edits start disappearing once a second tool touches the same project, and how to work out which copy of your app is the real one.
Lovable lost my work: now what?
Recovery steps when a Lovable prompt breaks or wipes your app: revert, GitHub sync, chat history, and how to make sure it never costs you a project again.
Plyo vs GitButler for AI-agent workflows
Both exist because AI agents break projects. GitButler is a smarter desktop git client for developers; Plyo is a hosted home for people who don't want git at all.
Plyo vs GitHub Desktop for AI-built projects
Both protect AI-built projects from lost work. GitHub Desktop is a free manual snapshot app; Plyo saves automatically and adds publishing. Which fits you.
Plyo vs Netlify Drop for AI-built sites
Netlify Drop is the fastest way to get a folder online. Plyo is slower to first link but keeps versions, updates one stable URL, and scans for leaked keys. Which fits when.
Plyo vs Vercel for AI-built projects
Vercel is built for developers and is very good at that. Plyo is built for people whose AI wrote the code. What each one assumes you already know, and which fits your project.
It works in the preview but the published site is broken
Why an AI-built app runs fine in Lovable, Bolt or v0's preview and breaks once published: missing environment variables, wrong paths, and the client-side exception. How to fix each.
Do I need a privacy policy for my AI-built app?
When a small AI-built app genuinely needs a privacy policy, what it has to say, and how to find out what your app is really collecting before you write one.
How do I put my AI-built project online?
The plain-English answer to getting an AI-built app onto the internet with a real link: what hosting means, your options by tool, and the one-click path.
Error 400: redirect_uri_mismatch — fixing Google sign-in
Google sign-in worked in the preview and breaks on your real domain. What the error means in plain English and the three settings screens that fix it.
How to share what Claude Code built with you
Ways to hand someone the site or app Claude Code just built, rendered at a stable URL with private links and version history, compared honestly.
Nobody can sign up: confirmation emails never arrive
Email rate limit exceeded, confirmation emails vanishing, signups landing in spam. Why AI-built apps hit this on launch day and how to fix it before real users do.
Am I still in Stripe test mode? Check before you launch
AI builders default to Stripe test keys and preview webhooks. How to tell which mode you're in, switch to live safely, and confirm real money can actually reach your bank.
Supabase keys: which ones are safe to be public?
The anon key is designed to be public; the service_role key must never reach the browser. How to tell them apart, check which one your app shipped, and fix it.
Supabase paused my project and my app is down
Supabase pauses inactive free projects and the app goes down. What paused actually means, how to restore it, and how to stop it happening again.
Switching AI tools without losing your project
The Lovable-to-Cursor/Claude-Code move is the most common growth path in AI building, and the most common place projects get lost. How to switch safely.
How to test your app before real people use it
A manual test script for non-coders: the fifteen checks that catch nearly every embarrassing launch-day failure in an AI-built app, in about half an hour.
How to undo in Claude Code
Claude Code's rewind and checkpoints, what they cover and where they stop, plus a project-wide undo that survives sessions, machines and tool switches.
Every way to get undo for an AI-built project, compared
Claude Code rewind, Cursor checkpoints, GitHub Desktop, GitButler, Time Machine and Plyo compared honestly: what each undo covers, and where each one stops.
What is a merge conflict? Plain English, no git required
What a merge conflict actually is, why AI builders suddenly show you one, what the <<<<<<< markers mean, and the prompt that resolves it safely.
Can I put my Lovable or Bolt app on the App Store?
Lovable, Bolt and v0 build web apps, not iPhone apps. What the difference actually is, your four real options, and Apple's rule that rejects the easy one.
Claude Code forgets my project every session
Why Claude Code starts from zero each session and the plain-English fix: one file it reads every time, holding the decisions you keep repeating.
Hundreds of fake signups appeared overnight
Bot signups and abuse on AI-built apps: how to stop it today without a developer, clean up the junk, and cap the bill it was about to create.
How to hand your AI-built project to a real developer
The checklist for hiring a developer for an AI-built project: what to give them, what to say about the code, and the credentials to rotate afterwards.
Locked out of your hosting account with the site down
Account suspended or 2FA you never set up, on a free plan with no support line. The recovery routes that work, and the copy of your project nobody can lock you out of.
What will my AI-built app actually cost per month?
The real monthly line items for an AI-built app: hosting, database, domain, email, AI tokens. What triggers each jump from free, and where the spend caps live.
Plyo is the home for AI-built projects — every version saved, one click to undo, one click to publish, plus a safety check, visitor counts and backups. Free to start: 3 projects, no card needed.
Give your project a home