An independent practice, deliberately kept small. Below are representative rescues — the breakages AI builders hit again and again, and exactly how each one gets fixed. Your diagnosis covers your actual app.
The app loaded but every query came back empty — Supabase row-level security rejected each read. Rewrote the policies, moved the service key server-side, verified real sessions.
Sessions weren't being restored, so users bounced between login and dashboard forever. Fixed the auth flow and middleware; the session now survives a reload.
Missing environment variables and a build-config mismatch killed every deploy. Sorted the env, fixed the build, wired a clean pipeline.
Checkout opened but nothing completed — the Stripe webhook was never verified and keys were exposed client-side. Closed the loop end to end.
A founder re-keying data between two tools every morning. Built a small scraper + sync with a scheduled report — it just runs.
A non-intrusive pass over a launching SaaS: exposed keys, open endpoints, missing HTTPS — returned as a prioritised, plain-English report.
// representative of typical fixes · your report covers your actual app, with the exact cause of each issue
Every issue ranked by what's actually stopping the app from working — with the real cause, not a guess.
Logged-in users see no data at all — row-level security rejects every read. Works in the AI preview, empty in production.
The service key ships to the browser — anyone can read it in devtools. Needs moving server-side before launch.
The session isn't restored on refresh, so users can never actually get in.
Missing environment variables — runs locally, dies on deploy. A 10-minute fix once you know where to look.
Horizontal scroll on phones; a couple of fixed widths need to go fluid.