Sophia A.

I build with AI-assisted tools, ship real apps and websites, and design games — and I'm the one who goes back in afterward to harden the part clients can't see but would absolutely get burned by. AI-Assisted Programming I use tools like Lovable, Bolt.new, and v0 to move fast — but speed isn't the pitch, judgment is. I know what the fast path skips and I fix it before it ships: LLM output that's schema-validated and retried instead of trusted straight into the UI, prompts hardened against injection, API keys that never touch the browser. App and Website Development Full-stack builds on Postgres/Supabase — auth, sessions, and Row Level Security enforced at the database, not just hidden by the UI. I test the boundary the way an attacker would: two accounts, the network tab open, confirming the API itself returns zero of another user's data. I also handle the deploy end to end — Git-based CI/CD, DNS, static hosting — so nothing depends on a manual upload step. Game Design My background is game programming (C++, Unity), so I default to caring whether something runs correctly under real conditions — the physics, the frame-rate independence, the collision timing most AI-generated demos get wrong. That instinct carries into everything else I build. Recent work: a vector Asteroids clone with a tamper-proof global leaderboard, an invoicing SaaS prototype with verified per-user data isolation, and an AI job-post parser that degrades gracefully instead of breaking when the model wobbles. Happy to walk through the actual code, not just the demo. If you need something built quickly that still holds up once real users touch it, that's the gap I fill.