One fix
$12once
1 diagnosis · no subscription
One diagnosis. Add a public repo if you want a look at the project.
Stop burning credits on fix loops.
Paste the error. Get a plain-English explanation and a prompt for Lovable, Bolt, Cursor, v0, or Replit.
First diagnosis is free. No subscription. See a before and after
How it works
Three steps. You stay in the tool you already paid for.
Paste the red text
Drop in the error, the stack trace, or a sentence about what just broke. Add a public GitHub link only if you want a look at the project. We never ask for a password, a GitHub login, or a production secret.
Read it in human
You get a plain-English explanation, the likely cause, and a security heads-up when the easy fix would leave a door open. Row Level Security stays on. Keys stay off the client.
Hand the prompt back
Copy one prompt written for Lovable, Bolt, Cursor, v0, or Replit. If that prompt misses, there is a short fallback so you are not starting the loop over.
Before and after
A Supabase error that sends people into a loop of "just turn RLS off." That advice is how tables end up public.
What you paste
Error: new row violates row-level security policy for table "tasks"
at saveTask (src/lib/tasks.ts:42:11)
supabase.from("tasks").insert({ title, user_id })What you get
The lock is doing its job
Row Level Security is on, and no rule lets this visitor add a row. Ask your tool to add a policy for signed-in users, matching user_id to auth.uid(). Tell it not to disable the lock.
Security heads-up: turning RLS off would let anyone with your project URL read and edit the table.
Simple packs. No subscription.
One free diagnosis, error only, for each browser. After that, buy fixes when you need them.
Free diagnosis. Paste the error, pick your tool, and get the full explanation. A public repo read is a paid fix, because it looks at your project.
Five fixes
Start here$39once
5 diagnoses · no subscription
Enough for a messy week of building, without a subscription.
Fifteen fixes
$79once
15 diagnoses · no subscription
For a project you are actually shipping. Credits stay until you use them.
Questions
Do you edit my code?
No. ThePlainFix writes the explanation and a prompt. You paste that prompt into the tool you already use. We never open a pull request and we never write to a repository.
Do you need my GitHub password?
No. If you add a link, it has to be a public repository. We read a small set of files, including ones named in the stack trace, and that is all. Private repos are refused.
What if my log has an API key in it?
Remove secrets before you paste. We also strip obvious keys, tokens, and database passwords before anything is stored or sent to a model, and we tell you when we did. If a real secret was in the paste, rotate it.
Is this a subscription?
No. The first diagnosis is free and reads the error only. After that you buy a pack of 1, 5, or 15 fixes. Credits stay on your email until you use them.
What if the prompt does not fix it?
Use the fallback on the result. If you are still stuck, run another diagnosis and say what the tool changed. A second look uses another credit once the free one is gone.
Which tools does the prompt fit?
Lovable, Bolt, Cursor, v0, and Replit each get wording that matches how that tool expects instructions. There is also a generic prompt if you use something else.