Category: MLP
-
I Leaked an API Key in My Vibe-Coded App: What to Rotate, In What Order, and How to Stop It Happening Again
A secret key in your deployed bundle or git history is the most time-sensitive problem an AI-built app can have. Rotate first, investigate second, fix the code third — the exact order, which keys matter most, and the tripwires that prevent a repeat.
-
My Vibe-Coded App Got Slow at 50 Users: The 5 Fixes (Before You Upgrade Anything)
Instant with three test users, unusable at fifty real ones. AI-built apps slow down at a predictable point for predictable reasons — N+1 queries, filtering in the browser, missing indexes, request waterfalls, refetch-on-keystroke — and almost none of them need a bigger server.
-
Vibe Coding vs Hiring a Developer: When to Stop Prompting and Bring in an Engineer
Should you keep vibe coding or hire a developer? A decision framework for founders: the four stages where AI tools are the right call, the four signals that you’ve crossed into engineer territory, and the hybrid model that keeps AI speed with human judgement — without paying for a full team.
-
Vibe-Coded App Not Showing Up on Google? The Technical SEO Fixes for AI-Built Sites (2026)
You built the site with AI, launched it, and Google can’t see it. The eight technical SEO problems almost every vibe-coded site ships with — client-only rendering, missing metadata, no sitemap, blocked crawlers, slow Core Web Vitals — and the fix for each, in the order that gets you indexed fastest.
-
From Lovable, Bolt or Replit to Production: How to Move a Vibe-Coded App Off the Prototype Platform
Your Lovable, Bolt.new, v0 or Replit app has real users and you’ve hit the platform’s ceiling. When to migrate, what to take with you, the six steps to a proper repo and deploy pipeline — and the parts that are worth having an engineer do.
-
Vibe Coding Security Checklist: 15 Things to Check Before Real Users Touch Your App (2026)
Is your vibe-coded app secure? Probably not yet. The 15-point vibe coding security checklist we run on AI-built apps — exposed API keys, missing Supabase RLS, broken authorisation, unlimited AI spend — with the one 5-minute test that finds the worst problem.
-
My Vibe-Coded App Is Broken and I Can’t Fix It: What to Do Next (and When to Hire Help)
Your AI-built app worked yesterday and now it doesn’t, and every new prompt makes it worse. The triage sequence that stops the bleeding, the three fixes you can still do yourself, and the point where hiring an engineer becomes cheaper than another day of prompting.
-
10 MCP Use Cases That Actually Ship: What Companies Connect AI to First
Past the demos, a clear pattern has emerged in what companies actually connect AI to first — and which MCP use cases quietly pay for themselves. Ten that ship, what each needs, and the one property nine of them share.
-
Remote MCP Servers: Deploying, Hosting, and Scaling Them After the Stateless Shift
Local MCP servers were fine when one developer used them. The moment a team — or your customers — need access, you’re deploying a remote server. Hosting options, auth requirements, and why the stateless spec just made this dramatically cheaper.
-
The MCP Servers We Actually Use with Claude Code (and the Ones We Turned Off)
Claude Code gets most of its leverage from what it can reach. The MCP servers that earn a place in our agency’s daily setup, how we configure them per project, and why we’ve removed more servers than we’ve added this year.