[{"data":1,"prerenderedAt":1618},["ShallowReactive",2],{"blog-vibe-coding-ai":3,"related-vibe-coding-ai":477},{"id":4,"title":5,"author":6,"body":7,"category":6,"date":462,"description":463,"draft":464,"extension":465,"image":6,"meta":466,"navigation":467,"path":468,"seo":469,"stem":470,"tags":471,"__hash__":476},"blog\u002Fblog\u002Fvibe-coding-ai.md","Vibe Coding AI: What It Actually Is and Where It Works",null,{"type":8,"value":9,"toc":444},"minimark",[10,15,19,24,27,30,33,37,40,43,46,50,53,64,72,75,79,82,85,94,98,106,109,148,157,161,164,167,171,174,256,259,263,266,272,278,284,290,294,297,323,331,335,338,375,378,382,385,388,392,425,434,438,441],[11,12,14],"h1",{"id":13},"vibe-coding-what-it-is-where-it-works-and-where-it-falls-apart","Vibe Coding: What It Is, Where It Works, and Where It Falls Apart",[16,17,18],"p",{},"Vibe coding is the practice of describing what you want in natural language and letting an AI agent write the code. The term went from Twitter joke to industry vocabulary in a matter of months, and it now describes everything from \"build me a to-do app\" prompts to agents that provision entire production stacks. This guide separates the marketing from the mechanics: what vibe coding actually is, where it earns its keep, and where it quietly falls apart.",[20,21,23],"h2",{"id":22},"what-is-vibe-coding-beyond-describe-your-app","What is Vibe Coding? Beyond \"Describe Your App\"",[16,25,26],{},"At its simplest, vibe coding means turning intent into working code without hand-typing every line. You describe a goal; a large language model generates the implementation. But that definition hides a spectrum.",[16,28,29],{},"At one end is prompt-based generation: you ask, the model produces a snippet, you paste it. At the other end is agent-driven development, where the model reads your codebase, follows your conventions, applies structured changes, and even provisions the services your app depends on.",[16,31,32],{},"The term exists now because the tooling finally caught up. Models like Claude can hold large contexts, follow multi-step instructions, and edit files in place. Editors like Cursor made iteration local and fast. Agents matured from autocomplete into something that can reason about architecture. \"Vibe coding\" is shorthand for that shift.",[20,34,36],{"id":35},"the-real-difference-vibe-coding-vs-no-code-builders","The Real Difference: Vibe Coding vs. No-Code Builders",[16,38,39],{},"No-code builders aim at people who don't read code. Vibe coding assumes you do. That single distinction explains most of the confusion in the market.",[16,41,42],{},"Tools like Lovable, Bolt, and Replit are excellent at generating a UI from a sentence. Where they struggle is the plumbing layer — the integration work between services that isn't clever but eats weeks. A generated login screen is easy. A signature-verified, idempotent Stripe webhook that agrees with your database is not.",[16,44,45],{},"Vibe coding wins in three places: working inside existing codebases, wiring integrations across services, and handling edge cases that a template can't anticipate. It fails, or at least needs a human, at pixel-perfect UX, complex state machines, and anything where \"looks plausible\" is not the same as \"is correct.\"",[20,47,49],{"id":48},"how-vibe-coding-actually-works-in-practice","How Vibe Coding Actually Works in Practice",[16,51,52],{},"The reliable pattern is an interview loop. The agent gathers requirements, generates code, and you iterate. Instead of one giant prompt, you have a conversation: What's your domain model? Which billing tiers? What auth scope?",[16,54,55,56,63],{},"The best results come when the agent has something to read. Folder structure, type hints, and a conventions file give it a map. Without one, an agent ",[57,58,62],"a",{"href":59,"rel":60},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fconventions-for-ai-coding-agents",[61],"nofollow","adds a fourth way to fetch data"," the moment it finds three — not because it's dumb, but because it has no reason to prefer yours.",[16,65,66,67,71],{},"There's also a meaningful difference between free-form code generation and ",[68,69,70],"strong",{},"deterministic patches"," — automated, repeatable changes applied to a known starting point. Free-form output is creative and unpredictable. Deterministic patches reshape a codebase to your answers in a way you can review and reproduce.",[16,73,74],{},"Constraints make agents reliable. Strict TypeScript catches hallucinated APIs at compile time. Documented patterns give the model a single correct choice instead of five plausible ones.",[20,76,78],{"id":77},"the-stack-that-enables-vibe-coding","The Stack That Enables Vibe Coding",[16,80,81],{},"Some stacks are simply more agent-friendly than others. Nuxt, Supabase, and Stripe happen to combine well because each one rewards consistency.",[16,83,84],{},"Supabase's row-level security is a machine-readable contract: access rules live in the database and are enforced at query time. Stripe's model treats webhooks as the source of truth for billing state, which is exactly the kind of explicit, documented behavior an agent can follow. Nuxt's folder conventions give the agent predictable places to put things.",[16,86,87,88,93],{},"What breaks agents is the opposite: undocumented side effects, magic strings, and implicit state that only lives in someone's head. If a human has to \"just know\" that changing one file requires editing four others, the agent won't know either. This is the whole argument behind ",[57,89,92],{"href":90,"rel":91},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fnuxt-saas-boilerplate-for-ai-agents",[61],"why every boilerplate ships the stack but the wiring is the real work",".",[20,95,97],{"id":96},"vibe-coding-for-saas-where-it-saves-weeks","Vibe Coding for SaaS: Where It Saves Weeks",[16,99,100,101,93],{},"SaaS is where vibe coding pays off most, because SaaS is mostly plumbing. The framework debate is over in an afternoon; the wiring between pieces is ",[57,102,105],{"href":103,"rel":104},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fhow-to-ship-saas-fast",[61],"what actually eats your launch",[16,107,108],{},"Consider what a competent agent has to handle for a real product:",[110,111,112,124,130,142],"ul",{},[113,114,115,118,119,93],"li",{},[68,116,117],{},"Billing edge cases",": idempotent refunds, subscription state transitions, and EU consent laws like the ",[57,120,123],{"href":121,"rel":122},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fstripe-checkout-consent-collection-german-withdrawal-waiver",[61],"German withdrawal waiver encoded into the pay button",[113,125,126,129],{},[68,127,128],{},"Multi-tenant auth",": row-level security expressed as policies the agent can read and extend.",[113,131,132,135,136,141],{},[68,133,134],{},"Payment as source of truth",": ",[57,137,140],{"href":138,"rel":139},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fstripe-webhooks-source-of-truth",[61],"your checkout success page should not touch billing state"," — the webhook is the record.",[113,143,144,147],{},[68,145,146],{},"Transactional email and consent tracking",": the unglamorous flows every paid product needs on day one.",[16,149,150,151,156],{},"This is the premise behind ",[57,152,155],{"href":153,"rel":154},"https:\u002F\u002Fboiledplate.ai",[61],"BoiledPlate",": the agent doesn't just write code, it provisions Stripe products and webhooks, a Supabase database with RLS, and Google sign-in in a single session.",[20,158,160],{"id":159},"vibe-coding-limitations-an-honest-take","Vibe Coding Limitations (An Honest Take)",[16,162,163],{},"Agents are not magic. They struggle with UX debugging and CSS refinement, where the feedback loop is visual and subjective. They make plausible architectural choices that are subtly wrong. And they hallucinate — confidently inventing an API method that doesn't exist.",[16,165,166],{},"Complex business logic still needs human review. The hallucination risk in architecture decisions is exactly why a conventions contract exists: it narrows the agent's choices to the ones you've already blessed. Knowing when to say \"no, I'll write this myself\" is a skill, not a failure.",[20,168,170],{"id":169},"vibe-coding-tools-tested-capabilities-vs-reality","Vibe Coding Tools Tested: Capabilities vs. Reality",[16,172,173],{},"The market is crowded, so it helps to compare tools by what they actually do rather than what they advertise.",[175,176,177,196],"table",{},[178,179,180],"thead",{},[181,182,183,187,190,193],"tr",{},[184,185,186],"th",{},"Tool",[184,188,189],{},"Interview",[184,191,192],{},"Service provisioning",[184,194,195],{},"Edge cases",[197,198,199,214,228,242],"tbody",{},[181,200,201,205,208,211],{},[202,203,204],"td",{},"Cursor",[202,206,207],{},"Limited",[202,209,210],{},"No",[202,212,213],{},"Local iteration only",[181,215,216,219,222,225],{},[202,217,218],{},"Claude (agent)",[202,220,221],{},"Strong",[202,223,224],{},"Yes, with the right scaffold",[202,226,227],{},"Handles when documented",[181,229,230,233,236,239],{},[202,231,232],{},"Lovable \u002F Bolt",[202,234,235],{},"Minimal",[202,237,238],{},"Weak on integrations",[202,240,241],{},"Fast UI, thin backend",[181,243,244,247,250,253],{},[202,245,246],{},"Replit",[202,248,249],{},"Some",[202,251,252],{},"Environment-based",[202,254,255],{},"No billing\u002Fauth defaults",[16,257,258],{},"Cursor is superb for local iteration but doesn't provision services. Lovable and Bolt produce UI fast and stall at integrations. Replit gives you an environment but no billing or auth defaults. Claude, given a codebase with a conventions contract, can run interviews, apply deterministic patches, and set up services — the difference is the scaffold, not just the model.",[20,260,262],{"id":261},"building-with-agents-patterns-that-work","Building With Agents: Patterns That Work",[16,264,265],{},"A few habits separate productive vibe coding from frustrating chaos.",[16,267,268,271],{},[68,269,270],{},"Write specific, convention-following prompts."," Vague prompts get vague code. Point the agent at your patterns.",[16,273,274,277],{},[68,275,276],{},"Keep code review discipline."," Agents produce plausible output. Plausible is not correct. Read every diff as if a fast, tireless junior wrote it.",[16,279,280,283],{},[68,281,282],{},"Iterate one loop per major feature."," One interview per billing flow beats one 2,000-word prompt trying to build everything.",[16,285,286,289],{},[68,287,288],{},"Use version control and semantic release notes"," so updates stay agent-readable and you can trace what changed and why.",[20,291,293],{"id":292},"the-anti-plumbing-stack-choosing-tools-for-agent-compatibility","The Anti-Plumbing Stack: Choosing Tools for Agent Compatibility",[16,295,296],{},"Framework choice matters less than consistency. Pick tools that expose explicit, documented contracts:",[110,298,299,305,311,317],{},[113,300,301,304],{},[68,302,303],{},"Supabase",": RLS is machine-readable security; agents respect policies they can read.",[113,306,307,310],{},[68,308,309],{},"Stripe",": webhooks as the source of truth — a model agents get right when told to.",[113,312,313,316],{},[68,314,315],{},"Resend",": transactional email without heavy vendor lock-in.",[113,318,319,322],{},[68,320,321],{},"Nuxt",": folder conventions an agent can follow without guessing.",[16,324,325,326,93],{},"The precise wiring each of these demands is covered in detail in ",[57,327,330],{"href":328,"rel":329},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fnuxt-supabase-stripe-saas-boilerplate",[61],"what it actually takes to wire up a Nuxt, Supabase and Stripe SaaS",[20,332,334],{"id":333},"vibe-coding-in-production-real-world-edge-cases","Vibe Coding in Production: Real-World Edge Cases",[16,336,337],{},"Production is where the honest work shows up. A few examples worth prompting for explicitly:",[110,339,340,346,352,364,369],{},[113,341,342,345],{},[68,343,344],{},"Webhook failure handling"," and idempotency, so a retried event doesn't double-charge or double-provision.",[113,347,348,351],{},[68,349,350],{},"Refund flows"," and billing dispute workflows.",[113,353,354,357,358,363],{},[68,355,356],{},"Multi-plan subscription logic"," — the ",[57,359,362],{"href":360,"rel":361},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fstripe-subscriptions-nuxt-supabase",[61],"five decisions behind Stripe subscriptions"," — plus usage tracking.",[113,365,366,93],{},[68,367,368],{},"Consent withdrawal and GDPR data deletion",[113,370,371,374],{},[68,372,373],{},"Rate limiting"," on agent-generated API calls.",[16,376,377],{},"These are exactly the flows a template glosses over and a real launch cannot.",[20,379,381],{"id":380},"vibe-coding-vs-traditional-development-the-real-trade-offs","Vibe Coding vs. Traditional Development: The Real Trade-Offs",[16,383,384],{},"The trade-off is speed to MVP versus review overhead. Vibe coding collapses weeks of plumbing into a session, but you pay it back in code review. Agent-driven setup gets you to a running product fast; deep, unusual customization still favors hand-coding.",[16,386,387],{},"Vibe coding is worth it for SaaS, multi-service provisioning, and integration-heavy work. Traditional coding still wins for bare-metal performance, custom DSLs, and performance-critical paths where every allocation matters.",[20,389,391],{"id":390},"getting-started-with-vibe-coding-a-practical-workflow","Getting Started With Vibe Coding: A Practical Workflow",[393,394,395,401,407,413,419],"ol",{},[113,396,397,400],{},[68,398,399],{},"Set up your environment",": an agent like Claude, a codebase it can read, and a conventions contract.",[113,402,403,406],{},[68,404,405],{},"First interview",": nail the domain model, billing tiers, and auth scope.",[113,408,409,412],{},[68,410,411],{},"Second pass",": integrations and edge cases — webhooks, RLS, email.",[113,414,415,418],{},[68,416,417],{},"Continuous",": refine prompts based on the quality of what comes back.",[113,420,421,424],{},[68,422,423],{},"Know your escape hatches",": when to hand-code and when to override the agent.",[16,426,427,428,433],{},"If you want a free place to practice the loop, ",[57,429,432],{"href":430,"rel":431},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Ffree-nuxt-supabase-saas-boilerplate",[61],"BoiledPlate Lite"," is an MIT-licensed Nuxt + Supabase starter you can clone and wire yourself.",[20,435,437],{"id":436},"the-future-of-vibe-coding","The Future of Vibe Coding",[16,439,440],{},"Deterministic patches will stop being a bespoke trick and become standard practice. Agents will increasingly act as service provisioners, not just code writers. Edge cases — billing, compliance, webhooks — will become first-class prompts rather than afterthoughts. And we'll start measuring agent-written code the way we measure human code: on readability and maintainability, not just whether it compiles.",[16,442,443],{},"Vibe coding won't replace developers. It shifts the work from typing plumbing to reviewing it — and, if you set up your conventions well, that's a much better place to spend your time.",{"title":445,"searchDepth":446,"depth":446,"links":447},"",3,[448,450,451,452,453,454,455,456,457,458,459,460,461],{"id":22,"depth":449,"text":23},2,{"id":35,"depth":449,"text":36},{"id":48,"depth":449,"text":49},{"id":77,"depth":449,"text":78},{"id":96,"depth":449,"text":97},{"id":159,"depth":449,"text":160},{"id":169,"depth":449,"text":170},{"id":261,"depth":449,"text":262},{"id":292,"depth":449,"text":293},{"id":333,"depth":449,"text":334},{"id":380,"depth":449,"text":381},{"id":390,"depth":449,"text":391},{"id":436,"depth":449,"text":437},"2026-07-26","Explore vibe coding AI: how natural language prompts generate code, the difference from no-code tools, and where AI agents actually deliver results.",false,"md",{},true,"\u002Fblog\u002Fvibe-coding-ai",{"title":5,"description":463},"blog\u002Fvibe-coding-ai",[472,473,474,475],"AI","code generation","vibe coding","development tools","1UKqjha_b2t6Ck5ww4bJQxTBxsLrxzsBBo-yTf1pbOs",[478,971,1280],{"id":479,"title":480,"author":6,"body":481,"category":6,"date":960,"description":961,"draft":464,"extension":465,"image":6,"meta":962,"navigation":467,"path":963,"seo":964,"stem":965,"tags":966,"__hash__":970},"blog\u002Fblog\u002Fvibecoding-apps-promise-vs-reality.md","Vibecoding Apps: The Promise vs. Production Reality",{"type":8,"value":482,"toc":942},[483,492,495,499,502,505,523,526,530,533,536,549,553,556,582,585,590,644,648,651,687,690,694,697,704,717,721,724,732,735,761,764,768,779,782,786,789,824,827,831,834,854,857,861,893,897,905,909,912,916,923,927,933],[16,484,485,486,491],{},"Vibe coding has a clean pitch: describe your app in plain language, and an AI writes the code. The term went mainstream after Andrej Karpathy ",[57,487,490],{"href":488,"rel":489},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FVibe_coding",[61],"described it"," as \"fully giving in to the vibes\" and forgetting the code even exists. For prototypes, it genuinely works. For production SaaS with real billing and real users, the gap between \"it runs\" and \"it ships\" is where most vibecoding apps quietly stall.",[16,493,494],{},"This is an honest map of what vibe coding actually does, where the tools break, and how agent-guided building differs from one-shot generation.",[20,496,498],{"id":497},"what-vibe-coding-actually-is","What Vibe Coding Actually Is",[16,500,501],{},"Vibe coding is AI-assisted development where natural language drives code generation instead of traditional syntax. You describe intent; a model produces implementation.",[16,503,504],{},"But \"vibe coding\" is a spectrum, not one thing:",[110,506,507,513],{},[113,508,509,512],{},[68,510,511],{},"Pure description"," (Google AI Studio, Lovable): you type a goal, you get output.",[113,514,515,518,519,522],{},[68,516,517],{},"Agent-guided structured building"," (Cursor with conventions, ",[57,520,155],{"href":153,"rel":521},[61],"): an agent interviews you, then applies structured changes to a known codebase shape.",[16,524,525],{},"Both use natural language. Only one keeps producing coherent code past the first afternoon.",[20,527,529],{"id":528},"the-promise-vs-the-reality-gap","The Promise vs. the Reality Gap",[16,531,532],{},"Marketing says: describe your app, get a working product. What actually happens is: description → generated code → integration hell.",[16,534,535],{},"The generated code is usually the easy 10%. The other 90% is plumbing — the wiring between services that no demo ever shows. Stripe webhooks that agree with your database. Row-level security policies. Refund state. EU consent flows. i18n strings that have to land in five places before the build stops complaining.",[16,537,538,539,543,544,548],{},"Vibe coding fails silently here because a one-shot generator can produce a Stripe checkout button that ",[540,541,542],"em",{},"looks"," done and has no working webhook behind it. It compiles. It even redirects. It just doesn't record the payment when the user closes the tab. As we've argued before, ",[57,545,547],{"href":103,"rel":546},[61],"the stack is easy and the plumbing is the project"," — and plumbing is exactly what one-shot tools skip.",[20,550,552],{"id":551},"vibe-coding-tools-an-honest-taxonomy","Vibe Coding Tools: An Honest Taxonomy",[16,554,555],{},"Four broad categories, each solving a different slice:",[110,557,558,564,570,576],{},[113,559,560,563],{},[68,561,562],{},"No-code visual builders"," (FlutterFlow, Canva Code): UI-first, limited backend logic. Fine for MVPs, high lock-in.",[113,565,566,569],{},[68,567,568],{},"Pure language-to-code"," (Google AI Studio, Lovable): fast initial output, weak at multi-service integration.",[113,571,572,575],{},[68,573,574],{},"Agent-guided structured builders"," (BoiledPlate, Cursor + strong conventions): interviews shape the infrastructure, deterministic patches keep the codebase coherent.",[113,577,578,581],{},[68,579,580],{},"Full-stack IDE environments"," (Replit, Bolt.new, Base44): sandboxed and impressive, but you still wire the real services yourself.",[16,583,584],{},"None of these is strictly better. They're built for different points in the lifecycle. The mistake is using an exploration tool for a production launch.",[586,587,589],"h3",{"id":588},"what-each-actually-solves","What each actually solves",[175,591,592,602],{},[178,593,594],{},[181,595,596,599],{},[184,597,598],{},"Need",[184,600,601],{},"Who handles it well",[197,603,604,612,620,628,636],{},[181,605,606,609],{},[202,607,608],{},"Rapid prototyping",[202,610,611],{},"All of them, inconsistently",[181,613,614,617],{},[202,615,616],{},"Production auth with RLS",[202,618,619],{},"Only tools with deterministic secrets + database-level permissions",[181,621,622,625],{},[202,623,624],{},"Real billing (idempotent webhooks)",[202,626,627],{},"Almost none in one-shot mode",[181,629,630,633],{},[202,631,632],{},"Multi-language i18n",[202,634,635],{},"Almost none automatically",[181,637,638,641],{},[202,639,640],{},"SEO (JSON-LD, canonicals, prerendering)",[202,642,643],{},"Only purpose-built frameworks",[20,645,647],{"id":646},"the-workflow-where-the-time-actually-goes","The Workflow: Where the Time Actually Goes",[16,649,650],{},"People imagine vibecoding apps is 90% prompting. In practice, for anything real:",[110,652,653,659,665,670,676,681],{},[113,654,655,658],{},[68,656,657],{},"Prompt clarity and iteration"," — 5–15% of time, but decisive.",[113,660,661,664],{},[68,662,663],{},"Reviewing generated code quality"," — 20–30%.",[113,666,667,669],{},[68,668,192],{}," (Stripe, Supabase, Google OAuth) — manual in most tools.",[113,671,672,675],{},[68,673,674],{},"Webhook architecture and idempotency"," — 30–40%. This is the real work.",[113,677,678,680],{},[68,679,195],{}," — refunds, subscription transitions, EU withdrawal periods.",[113,682,683,686],{},[68,684,685],{},"Deployment and monitoring"," — always an afterthought.",[16,688,689],{},"The prompt is the smallest slice. The webhook is the biggest. That ratio is why \"describe your app\" undersells the job.",[20,691,693],{"id":692},"ai-agents-vs-vibe-coding-tools","AI Agents vs. Vibe Coding Tools",[16,695,696],{},"The core difference is memory and structure.",[16,698,699,700,703],{},"A vibe coding tool does one-shot generation with a limited context window and no persistent conventions. An agent working against a starter kit does iterative interviews, applies deterministic patches, and reads a contract that tells it how ",[540,701,702],{},"this"," codebase does things.",[16,705,706,707,711,712,716],{},"That contract matters more than it sounds. As we've written, ",[57,708,710],{"href":59,"rel":709},[61],"an agent cannot smell a codebase"," — give it three ways to fetch data and it cheerfully adds a fourth, because it has no reason to prefer yours. Without written conventions, every suggestion drifts a little further from the shape of your code. BoiledPlate ships an ",[713,714,715],"code",{},"AGENTS.md"," contract precisely so the agent reads one documented way to do data access and secrets, then respects your customizations instead of reinventing them.",[20,718,720],{"id":719},"the-billing-problem-nobody-solves","The Billing Problem Nobody Solves",[16,722,723],{},"This is where vibecoding apps break most predictably.",[16,725,726,727,731],{},"Client-side success pages lie. The user pays, the browser redirects, and then they close the tab before your success page finishes running. If your billing state depends on that page, you just lost a payment record. The only reliable source of truth is the Stripe webhook — ",[57,728,730],{"href":138,"rel":729},[61],"your checkout success page should not touch your billing state"," at all.",[16,733,734],{},"Doing this right requires:",[110,736,737,749,755],{},[113,738,739,742,743,748],{},[68,740,741],{},"Idempotent webhooks"," so a redelivered event doesn't double-charge or double-provision. Stripe ",[57,744,747],{"href":745,"rel":746},"https:\u002F\u002Fdocs.stripe.com\u002Fwebhooks#handle-duplicate-events",[61],"explicitly recommends"," handling duplicate events.",[113,750,751,754],{},[68,752,753],{},"Refund and downgrade state machines"," — partial refunds, subscription changes, EU withdrawal windows.",[113,756,757,760],{},[68,758,759],{},"Stripe as the single source of truth",", with everything else a view of Stripe state.",[16,762,763],{},"Almost no one-shot tool encodes this. It requires ongoing architecture, not a single generation.",[20,765,767],{"id":766},"auth-and-security-where-it-breaks-quietly","Auth and Security: Where It Breaks Quietly",[16,769,770,771,774,775,778],{},"Row-level security is invisible in generated code and critical in production. A generator can wire Google sign-in flawlessly and still leave your database wide open, because sign-in only proves ",[540,772,773],{},"who"," the user is — RLS decides ",[540,776,777],{},"what rows"," they can touch.",[16,780,781],{},"Supabase RLS policies are auto-generated wrong more often than right. This is the classic \"a user saw someone else's data\" bug, and it never shows up in a demo because demos have one user. Agent-driven builders solve this by encoding RLS templates as part of the starter, not leaving each policy to a fresh guess.",[20,783,785],{"id":784},"real-world-bugs-in-generated-code","Real-World Bugs in Generated Code",[16,787,788],{},"Generated code fails in specific, repeatable ways:",[110,790,791,803,812,818],{},[113,792,793,796,797,802],{},[68,794,795],{},"JSON-LD hydration crashes"," in Nuxt SSR — a page that returns ",[57,798,801],{"href":799,"rel":800},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fthe-page-that-returned-200-on-the-server-and-500-in-the-browser-a-json-ld-tempor",[61],"200 from curl and 500 in the browser"," because of source order. A generator won't catch this; it's an integration bug, not a syntax bug.",[113,804,805,808,809,93],{},[68,806,807],{},"Canonical URL edge cases"," — trailing slashes, query params, and the memorable case of a blog telling Google its canonical URL was ",[713,810,811],{},"localhost:3000",[113,813,814,817],{},[68,815,816],{},"TypeScript strict mode"," — most generators skip it and hand you union-type nightmares.",[113,819,820,823],{},[68,821,822],{},"Peer dependency conflicts"," — Stripe SDK versions, Supabase auth breaking changes.",[16,825,826],{},"None of these are clever problems. They're endless, slightly different, and exactly the kind of thing that eats a launch weekend.",[20,828,830],{"id":829},"the-cost-equation","The Cost Equation",[16,832,833],{},"Realistic numbers matter more than hype:",[110,835,836,842,848],{},[113,837,838,841],{},[68,839,840],{},"Time to working prototype",": a couple of hours in Lovable; roughly an hour with a structured starter if the interview is clear.",[113,843,844,847],{},[68,845,846],{},"Time to production-ready",": add 2–4 weeks of plumbing regardless of tool.",[113,849,850,853],{},[68,851,852],{},"Cost of lock-in",": high with FlutterFlow and Canva Code, medium with Replit and Bolt, low with GitHub-native delivery where the code lives next to your CI\u002FCD.",[16,855,856],{},"The prototype gap between tools is small. The production gap is enormous, and it's decided by architecture, not by prompt quality.",[20,858,860],{"id":859},"choosing-a-tool-a-quick-matrix","Choosing a Tool: A Quick Matrix",[110,862,863,869,875,881,887],{},[113,864,865,868],{},[68,866,867],{},"MVP under a week",": Google AI Studio, Lovable, Canva Code.",[113,870,871,874],{},[68,872,873],{},"Production SaaS with billing",": an agent plus a strong starter kit, or manual work with agent oversight.",[113,876,877,880],{},[68,878,879],{},"Mobile-first",": FlutterFlow.",[113,882,883,886],{},[68,884,885],{},"Maximum flexibility",": Replit, Bolt.new — sandboxed, but you wire everything.",[113,888,889,892],{},[68,890,891],{},"Zero lock-in",": GitHub + Claude agent + a Nuxt\u002FSupabase\u002FStripe starter.",[20,894,896],{"id":895},"why-nuxt-supabase-stripe-works-for-agents","Why Nuxt + Supabase + Stripe Works for Agents",[16,898,899,900,904],{},"This combination isn't fashion; it's about predictable integration points. Nuxt's universal rendering forces deterministic patterns an agent can read and extend. Supabase RLS policies are template-able. Stripe webhooks give one unambiguous source of truth. Every SaaS starter ships this stack — but as we've noted, ",[57,901,903],{"href":90,"rel":902},[61],"that was never the hard part",". The parts are cheap; bolting them together is the project.",[20,906,908],{"id":907},"what-vibe-coding-wont-do-yet","What Vibe Coding Won't Do Yet",[16,910,911],{},"Be honest about the ceiling. Generated schemas are brittle, so migrations are risky. Updating generated code tends to break old queries. Vibe-coded apps are hard to inherit because no one wrote down the conventions, which means no one owns the plumbing. And AI-generated code against regulatory requirements is still a gray area.",[20,913,915],{"id":914},"where-vibe-coding-genuinely-shines","Where Vibe Coding Genuinely Shines",[16,917,918,919,922],{},"None of this means vibe coding is a fad. It is genuinely faster for exploration, for the prototype-to-feedback loop, and for grinding down repetitive boilerplate. The best use of an agent isn't \"build me a startup\" — it's \"given this codebase shape, what's the right next step?\" That question only has a good answer when the codebase ",[540,920,921],{},"has"," a documented shape.",[20,924,926],{"id":925},"conclusion-a-layer-not-a-replacement","Conclusion: A Layer, Not a Replacement",[16,928,929,930,932],{},"The real speedup in vibecoding apps isn't the initial generation — it's structured integration. The framework was never what slowed you down; the plumbing was. Use vibe coding tools for exploration, and use agent-guided starter kits for production, where deterministic patches and an ",[713,931,715],{}," contract keep output coherent past month three.",[16,934,935,936,941],{},"That's the model BoiledPlate is built around: an agent that interviews you, provisions Stripe, Supabase, and Google sign-in, and then respects your customizations instead of drifting away from them. You can read ",[57,937,940],{"href":938,"rel":939},"https:\u002F\u002Fboiledplate.ai\u002Fblog",[61],"more of the engineering log on the blog"," — every edge case it took to make the plumbing trustworthy is written down, because that's the part vibe coding still can't hand you for free.",{"title":445,"searchDepth":446,"depth":446,"links":943},[944,945,946,949,950,951,952,953,954,955,956,957,958,959],{"id":497,"depth":449,"text":498},{"id":528,"depth":449,"text":529},{"id":551,"depth":449,"text":552,"children":947},[948],{"id":588,"depth":446,"text":589},{"id":646,"depth":449,"text":647},{"id":692,"depth":449,"text":693},{"id":719,"depth":449,"text":720},{"id":766,"depth":449,"text":767},{"id":784,"depth":449,"text":785},{"id":829,"depth":449,"text":830},{"id":859,"depth":449,"text":860},{"id":895,"depth":449,"text":896},{"id":907,"depth":449,"text":908},{"id":914,"depth":449,"text":915},{"id":925,"depth":449,"text":926},"2026-07-19","Explore how vibecoding apps work, where they break down, and the gap between prototypes and production SaaS that actually ships with real users.",{},"\u002Fblog\u002Fvibecoding-apps-promise-vs-reality",{"title":480,"description":961},"blog\u002Fvibecoding-apps-promise-vs-reality",[967,968,473,969],"vibecoding","AI development","SaaS development","6xVs1JNK5DqaC2I5I7p7VIrAUYF6PkCHDYjGNHtBzOs",{"id":972,"title":973,"author":6,"body":974,"category":6,"date":1268,"description":1269,"draft":464,"extension":465,"image":6,"meta":1270,"navigation":467,"path":1271,"seo":1272,"stem":1273,"tags":1274,"__hash__":1279},"blog\u002Fblog\u002Fvibe-coding-gemini-production.md","Vibe Coding with Gemini: From Demo to Production Reality",{"type":8,"value":975,"toc":1252},[976,979,983,986,989,993,996,999,1002,1006,1009,1012,1026,1034,1038,1041,1048,1051,1059,1063,1066,1074,1080,1084,1092,1105,1117,1121,1124,1135,1139,1147,1171,1175,1183,1187,1190,1194,1197,1209,1215,1218,1222,1230,1234,1240,1244],[16,977,978],{},"Vibe coding is having a moment. Type a sentence, get an app. Google's pitch with Gemini in AI Studio is that anyone can describe a \"vibe\" and watch a working React app appear, then ship it to Cloud Run in minutes. It's genuinely impressive. It's also where most of the honest conversation stops. Because the distance between \"it runs on my screen\" and \"it survives paying customers\" is exactly the distance this article is about.",[20,980,982],{"id":981},"what-vibe-coding-actually-means","What \"Vibe Coding\" Actually Means",[16,984,985],{},"Vibe coding means turning natural-language prompts into functional code — not sketches, not pseudocode, but something that compiles and deploys. You describe the goal (\"a neon-themed pomodoro timer for my kid\") and Gemini writes it. People have built personalized apps in under 30 minutes this way, and the demos are real.",[16,987,988],{},"The gap is between \"describe your vibe\" and \"ships to production.\" Gemini positions this as democratized development: anyone can code now. What that actually requires, once you leave the single-file demo, is everything vibe coding quietly skips — billing state, data isolation, webhook retries, compliance. The framework was never the hard part.",[20,990,992],{"id":991},"gemini-vs-claude-the-agent-architecture-choice","Gemini vs. Claude: The Agent Architecture Choice",[16,994,995],{},"The two dominant coding-agent styles behave very differently, and it matters more than benchmarks suggest.",[16,997,998],{},"Gemini sprints. As one developer put it comparing it to Claude Code, \"Gemini doesn't make a plan and ask you if you want to proceed. It sprints ahead.\" That's fast and satisfying for a prototype. Gemini 2.5 Flash is faster still than Gemini 3 Pro, but developers who ran the same project through both found Flash more manual and more error-prone — speed traded against correctness.",[16,1000,1001],{},"Claude's agentic workflow leans the other way: plan first, then execute deliberate, repeatable changes. For a throwaway timer, planning is overhead. For a multi-tenant SaaS with billing, planning is the whole game. Consistency beats velocity the moment your codebase outlives the first session.",[20,1003,1005],{"id":1004},"the-real-cost-of-fast-single-file-apps-vs-plumbing","The Real Cost of \"Fast\": Single-File Apps vs. Plumbing",[16,1007,1008],{},"A neon React timer in half an hour is a fair benchmark for what vibe coding covers well: UI components, basic logic, deployment scaffolding.",[16,1010,1011],{},"Here's what it doesn't touch:",[110,1013,1014,1017,1020,1023],{},[113,1015,1016],{},"Signature-verified, idempotent Stripe webhooks",[113,1018,1019],{},"Row-level security so users can't read each other's rows",[113,1021,1022],{},"Refund flows that don't double-cancel on a retry",[113,1024,1025],{},"EU consent compliance baked into the pay button",[16,1027,1028,1029,1033],{},"None of that is clever work. It's endless, slightly-different-every-time work — the kind we call ",[57,1030,1032],{"href":103,"rel":1031},[61],"plumbing",". And it's where launches actually stall. Vibe coding a UI is a solved problem. Wiring the services beneath it is the project.",[20,1035,1037],{"id":1036},"building-real-apps-where-google-ai-studio-hits-a-wall","Building Real Apps: Where Google AI Studio Hits a Wall",[16,1039,1040],{},"Google AI Studio's newer vibe-coding experience can add databases and even multiplayer. That's progress, but \"add a database\" is where the real work starts, not where it ends.",[16,1042,1043,1044,1047],{},"Multiplayer requires state synchronization and, critically, ",[68,1045,1046],{},"row-level security"," so one user's writes never leak into another's session. A database alone gives you none of that — you still need a migration strategy, schema validation, and a policy layer enforced at query time.",[16,1049,1050],{},"Billing is worse. Provisioning Stripe products, verifying webhook signatures, and making handlers idempotent is not something a prompt reliably produces. And auth? Adding Google sign-in is trivial. Managing the user session, the RLS policies tied to it, and the secrets that must never reach the client is not.",[16,1052,1053,1054,1058],{},"This is exactly the box-of-parts problem we've written about before: ",[57,1055,1057],{"href":90,"rel":1056},[61],"every boilerplate ships the stack",", then leaves you alone in a room with the wiring.",[20,1060,1062],{"id":1061},"the-vibe-coding-workflow-that-actually-works-for-saas","The Vibe Coding Workflow That Actually Works for SaaS",[16,1064,1065],{},"The missing step in the \"describe it and deploy\" pitch is the interview.",[16,1067,1068,1069,1073],{},"Before an agent should touch a SaaS codebase, it needs answers: What's the billing model — one-time or subscription, how many plans? What user roles exist? What data must be isolated per tenant? BoiledPlate's setup runs exactly this way — ",[57,1070,1072],{"href":153,"rel":1071},[61],"your coding agent interviews you",", then provisions Stripe, Supabase, and Google sign-in based on your answers.",[16,1075,1076,1077,1079],{},"Those answers drive ",[68,1078,70],{},": automated, repeatable code changes that reshape the starter to your specific setup rather than hallucinating a fresh architecture each run. And validation matters — \"the code compiles\" is not \"the billing survives production.\" Those are two entirely different claims.",[20,1081,1083],{"id":1082},"webhook-architecture-the-plumbing-nobody-teaches","Webhook Architecture: The Plumbing Nobody Teaches",[16,1085,1086,1087,1091],{},"Here is the single lesson most vibe-coded billing systems get wrong: your checkout success page is not your source of truth. ",[57,1088,1090],{"href":138,"rel":1089},[61],"Stripe webhooks are",". The user can close the tab, lose signal, or refresh — the webhook is what tells you money moved.",[16,1093,1094,1095,1098,1099,1104],{},"That means handlers must be ",[68,1096,1097],{},"idempotent",". Stripe retries deliveries. If your handler grants access or cancels a subscription twice because it got called twice, you have a bug that only shows up under load. We've written in detail about ",[57,1100,1103],{"href":1101,"rel":1102},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fthe-github-invite-is-the-product-building-a-stripe-webhook-where-delivery-throws",[61],"a webhook where some failures must throw and some must never do"," — the distinction is the difference between a self-healing system and a support ticket.",[16,1106,1107,1108,1112,1113,1116],{},"Compliance lives here too. Encoding a ",[57,1109,1111],{"href":121,"rel":1110},[61],"German withdrawal-right waiver into the pay button"," via Stripe's ",[713,1114,1115],{},"consent_collection"," is not something a vibe prompt knows to do. It's compliance as code, and it's mandatory in the EU.",[20,1118,1120],{"id":1119},"agent-consistency-writing-conventions-that-survive-updates","Agent Consistency: Writing Conventions That Survive Updates",[16,1122,1123],{},"An agent cannot smell a codebase. Give it three ways to fetch data and it adds a fourth — not because it's dumb, but because it has no reason to prefer yours. This is the failure mode behind \"anyone can code\": the agent drifts, and by month three you have five patterns for one job.",[16,1125,1126,1127,1129,1130,1134],{},"The fix is a contract. An ",[713,1128,715],{}," file documents one way to access data, handle secrets, and apply patches, so ",[57,1131,1133],{"href":59,"rel":1132},[61],"agent output stays consistent"," past the first session. Gemini's sprint-ahead style has no equivalent plan-and-confirm gate, which is fine for a demo and dangerous for a codebase you'll maintain for a year.",[20,1136,1138],{"id":1137},"vibe-coding-languages-frameworks-and-real-bugs","Vibe Coding Languages, Frameworks, and Real Bugs",[16,1140,1141,1142,1146],{},"Most vibe coding assumes one language — JavaScript or TypeScript — and one happy path. Production is messier. A serious SaaS often needs ",[57,1143,1145],{"href":153,"rel":1144},[61],"four languages from day one"," via i18n, where a single new locale string has to land in five places before the build stops complaining.",[16,1148,1149,1150,1154,1155,1160,1161,1164,1165,1170],{},"Real debugging stories make the point. We shipped a page that ",[57,1151,1153],{"href":799,"rel":1152},[61],"returned 200 from curl and 500 in Chrome"," — a JSON-LD hydration bug hiding in source order. Our blog once ",[57,1156,1159],{"href":1157,"rel":1158},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Four-blog-canonically-pointed-at-localhost",[61],"told Google its canonical URL was localhost:3000",". A ",[713,1162,1163],{},"@vercel\u002Fanalytics"," install ",[57,1166,1169],{"href":1167,"rel":1168},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fvercel-web-analytics-nuxt-4-analytics-package-breaks-typecheck",[61],"broke Nuxt typecheck"," through a peer-dependency conflict. None of these appear in a vibe-coding demo. All of them appear in a real project.",[20,1172,1174],{"id":1173},"typed-end-to-end-why-vibe-coding-needs-typescript-discipline","Typed End to End: Why Vibe Coding Needs TypeScript Discipline",[16,1176,1177,1178,1182],{},"Natural-language-to-code loves shortcuts, and the first shortcut is usually type safety. That's a false economy. TypeScript in ",[57,1179,1181],{"href":153,"rel":1180},[61],"strict mode"," catches bugs at compile time instead of in a customer's checkout. Pair it with Zod validation and a database schema treated as a single source of truth, and refactors stop being terrifying. Vibe code without types and you're signing up for refactoring hell the first time requirements change.",[20,1184,1186],{"id":1185},"deployment-speed-is-not-shipping-speed","Deployment Speed Is Not Shipping Speed",[16,1188,1189],{},"\"Deploy to Cloud Run in minutes\" is a genuine feature. But fast-to-first-deploy and safe-in-production pull in opposite directions. A template you clone hands you parts. A kit that adapts to your interview answers hands you a wired product — and, in BoiledPlate's case, delivers it through a GitHub invite with lifetime updates. The delivery mechanism is instant; the value is that the plumbing already agrees with itself.",[20,1191,1193],{"id":1192},"when-vibe-coding-makes-sense-and-when-it-doesnt","When Vibe Coding Makes Sense (And When It Doesn't)",[16,1195,1196],{},"Be honest about fit.",[16,1198,1199,1202,1203,1208],{},[68,1200,1201],{},"Reach for Gemini AI Studio"," for prototypes, internal tools, learning projects, and quick wins. It genuinely shines here, and Google's own ",[57,1204,1207],{"href":1205,"rel":1206},"https:\u002F\u002Fai.google.dev\u002F",[61],"vibe-coding documentation"," is a good starting point.",[16,1210,1211,1214],{},[68,1212,1213],{},"Reach for agent-driven plumbing"," the moment you have billing-critical, multi-tenant, or compliance-heavy requirements. The checklist is simple: does your app need webhooks, RLS, or signature verification? If yes, you've left vibe-coding territory.",[16,1216,1217],{},"The pragmatic middle is a hybrid — vibe code the UI, then apply deterministic patches to the dangerous parts.",[20,1219,1221],{"id":1220},"the-one-time-cost-vs-subscription-trap","The One-Time Cost vs. Subscription Trap",[16,1223,1224,1225,1229],{},"\"Free and fast\" often means \"expensive to maintain.\" Free vibe-coding access still leaves you owning recurring infrastructure and — worse — the ongoing cost of code nobody wrote a contract for. BoiledPlate Pro is €159 one-time with lifetime updates and no lock-in, and if you want to start free, ",[57,1226,1228],{"href":430,"rel":1227},[61],"BoiledPlate Lite is MIT-licensed",". What you actually pay for isn't the stack — it's the agent-readable contracts, deterministic patches, and compliance encoded as code.",[20,1231,1233],{"id":1232},"the-future-of-vibe-coding-maturity-not-speed","The Future of Vibe Coding: Maturity, Not Speed",[16,1235,1236,1237,1239],{},"The trajectory is clear: from \"write code fast\" to \"write code safely.\" ",[713,1238,715],{},"-style contracts are becoming the norm, and deterministic patches are the bridge between a natural-language prompt and code you'd put in front of a paying customer. Speed got us the demo. Consistency gets us production.",[20,1241,1243],{"id":1242},"getting-started","Getting Started",[16,1245,1246,1247,1251],{},"Use Gemini when you're learning or experimenting. Use an agent-driven kit when you're shipping something with money, tenants, or regulators involved. If your vibe-coded app touches billing state, isolates user data, or verifies a webhook signature, the plumbing is your project — and it's worth reading ",[57,1248,1250],{"href":328,"rel":1249},[61],"what wiring a Nuxt, Supabase and Stripe SaaS actually demands"," before you promise a launch date.",{"title":445,"searchDepth":446,"depth":446,"links":1253},[1254,1255,1256,1257,1258,1259,1260,1261,1262,1263,1264,1265,1266,1267],{"id":981,"depth":449,"text":982},{"id":991,"depth":449,"text":992},{"id":1004,"depth":449,"text":1005},{"id":1036,"depth":449,"text":1037},{"id":1061,"depth":449,"text":1062},{"id":1082,"depth":449,"text":1083},{"id":1119,"depth":449,"text":1120},{"id":1137,"depth":449,"text":1138},{"id":1173,"depth":449,"text":1174},{"id":1185,"depth":449,"text":1186},{"id":1192,"depth":449,"text":1193},{"id":1220,"depth":449,"text":1221},{"id":1232,"depth":449,"text":1233},{"id":1242,"depth":449,"text":1243},"2026-07-17","Explore vibe coding with Google's Gemini: how natural language turns into working apps. Learn what's missing between impressive demos and production-ready systems.",{},"\u002Fblog\u002Fvibe-coding-gemini-production",{"title":973,"description":1269},"blog\u002Fvibe-coding-gemini-production",[1275,1276,1277,1278],"vibe-coding","gemini","ai-development","cloud-run","9t7yKExFOOtTP4gAd2PO34EvsBA731bM-sFnHMUa4E0",{"id":1281,"title":1282,"author":6,"body":1283,"category":6,"date":1607,"description":1608,"draft":464,"extension":465,"image":6,"meta":1609,"navigation":467,"path":1610,"seo":1611,"stem":1612,"tags":1613,"__hash__":1617},"blog\u002Fblog\u002Fandrej-karpathy-vibe-coding.md","Andrej Karpathy's Vibe Coding: The Rise and Fall",{"type":8,"value":1284,"toc":1591},[1285,1288,1292,1295,1298,1301,1304,1308,1322,1325,1328,1331,1333,1336,1339,1342,1346,1349,1361,1364,1371,1375,1378,1381,1384,1388,1394,1400,1406,1412,1418,1422,1430,1433,1436,1439,1443,1446,1449,1452,1456,1459,1462,1465,1469,1472,1479,1482,1486,1489,1535,1539,1542,1545,1549,1552,1555,1558,1562,1568,1574,1580],[16,1286,1287],{},"Andrej Karpathy dropped a tweet in February 2025 that renamed how a generation of developers talked about their work. \"Vibe coding,\" he called it — fully giving in to the vibes, embracing exponentials, forgetting the code even exists. Within a year the phrase was everywhere, then it curdled into a buzzword, and by February 2026 Karpathy himself had quietly moved on. This guide traces the whole arc: what vibe coding actually meant, where it breaks, and what serious builders do instead.",[586,1289,1291],{"id":1290},"what-is-vibe-coding","What is Vibe Coding?",[16,1293,1294],{},"Vibe coding is software development where you lean on a large language model to generate code and trust its output rather than reading every line. Karpathy's framing was deliberately loose: describe what you want, accept the diff, run it, and if it works, keep going.",[16,1296,1297],{},"The core philosophy is about embracing exponential capability. Models improve fast, so why fight them with perfectionism? You prompt, you iterate, you ship.",[16,1299,1300],{},"This is a genuine break from structured, methodical coding, where every function is reasoned about and every architectural decision is deliberate. Vibe coding says: let the model hold the details, you hold the intent.",[16,1302,1303],{},"The mindset shift is real. You stop being the author and start being the director. That works beautifully — right up until it doesn't.",[586,1305,1307],{"id":1306},"the-origins-karpathys-vision","The Origins: Karpathy's Vision",[16,1309,1310,1311,1316,1317,1321],{},"The ",[57,1312,1315],{"href":1313,"rel":1314},"https:\u002F\u002Fx.com\u002Fkarpathy\u002Fstatus\u002F1886192184808149383",[61],"original post"," landed in early 2025 and spread within days. ",[57,1318,1320],{"href":488,"rel":1319},[61],"Wikipedia"," now credits Karpathy with coining the term.",[16,1323,1324],{},"What he actually meant was narrower than how it was received. His examples were throwaway projects — weekend apps, scripts, things where a bug just meant asking the model to fix it. The point was fun, not recklessness.",[16,1326,1327],{},"The misinterpretation came fast. \"Vibe coding\" got read as license to ship production software without understanding it. That is not what the phrase was built to carry.",[16,1329,1330],{},"Context matters. In early 2025, AI coding was good enough to feel magical and immature enough to fail silently. Vibes filled the gap between capability and reliability.",[586,1332,49],{"id":48},[16,1334,1335],{},"In practice, vibe coding is a rhythm: prompt, read the result loosely, run it, correct with another prompt. You stay in flow, and the LLM absorbs the tedium.",[16,1337,1338],{},"The skill is knowing when to override the vibe. If the output touches money, auth, or user data, you stop vibing and start reading. If it's UI scaffolding or a data transform, you let it ride.",[16,1340,1341],{},"Tools like Cursor and Claude made this possible, but the real enabler was architectural: choosing a stack and conventions the model already understands well. A model vibes better inside familiar terrain.",[586,1343,1345],{"id":1344},"vibe-coding-meets-production-reality","Vibe Coding Meets Production Reality",[16,1347,1348],{},"Vibes carry you through scaffolding. They collapse at the plumbing.",[16,1350,1351,1352,1355,1356,1360],{},"We learned this building ",[57,1353,155],{"href":153,"rel":1354},[61],", where the stack was the easy part and the wiring ate the weeks. As we argued in ",[57,1357,1359],{"href":103,"rel":1358},[61],"how to ship SaaS fast",", the framework picks itself — Stripe verification, row-level security, and idempotency are where launches actually stall.",[16,1362,1363],{},"You cannot vibe your way to a signature-verified webhook. Cryptographic correctness is binary. Full vibe coding fails at scale because the failures are silent: a user sees someone else's data, a subscription state drifts, a webhook fires twice.",[16,1365,1366,1367,1370],{},"What helps is structure. Building SaaS with agents requires contracts — an ",[57,1368,715],{"href":59,"rel":1369},[61]," file that documents one way to do data access and secrets, so the agent stays consistent instead of inventing a fourth pattern.",[586,1372,1374],{"id":1373},"the-karpathy-pivot-why-he-moved-on-february-2026","The Karpathy Pivot: Why He Moved On (February 2026)",[16,1376,1377],{},"By February 2026, Karpathy had publicly declared vibe coding outdated. His reasoning: LLMs got smart enough that \"vibes\" was no longer the right word for what good AI-assisted development looked like.",[16,1379,1380],{},"The landscape had matured. Models could follow explicit conventions, apply structured edits, and reason about architecture. The loose, forget-the-code-exists ethos felt incomplete against that.",[16,1382,1383],{},"His pivot signals something bigger: AI development grew up. The frontier moved from \"trust the model\" to \"constrain the model well.\" The industry got stuck arguing about the word \"vibe\" while the actual evolution was happening in tooling and contracts.",[586,1385,1387],{"id":1386},"five-different-approaches-to-vibe-coding","Five Different Approaches to Vibe Coding",[16,1389,1390,1393],{},[68,1391,1392],{},"Pure vibes."," Full trust, minimal oversight. Great for scripts and prototypes. Fails predictably for anything with real users.",[16,1395,1396,1399],{},[68,1397,1398],{},"Vibes with guardrails."," Prompting combined with deterministic patches and schema validation, so the model's output gets checked before it lands.",[16,1401,1402,1405],{},[68,1403,1404],{},"Vibe coding for architecture."," Use agents to design systems and explore options, then let humans wire the sensitive plumbing by hand.",[16,1407,1408,1411],{},[68,1409,1410],{},"Agent-native development."," Build around an AGENTS.md contract so agents produce consistent output across months, not just across a single session.",[16,1413,1414,1417],{},[68,1415,1416],{},"Post-vibe coding."," Structured prompting, explicit contracts, deterministic outputs. This is the direction Karpathy's pivot points toward.",[586,1419,1421],{"id":1420},"vibe-coding-vs-deterministic-coding","Vibe Coding vs. Deterministic Coding",[16,1423,1424,1425,1429],{},"The problem with vibes alone is drift. An agent given three ways to fetch data will ",[57,1426,1428],{"href":59,"rel":1427},[61],"cheerfully add a fourth",", because it has no reason to prefer yours.",[16,1431,1432],{},"Drift costs rework. Every time LLM output diverges from your conventions, someone has to notice, refactor, and re-explain — often the agent itself, badly.",[16,1434,1435],{},"Deterministic patches and semantic contracts prevent this decay. Instead of hoping the model matches your style, you encode the style as rules it must follow.",[16,1437,1438],{},"The concrete cases make it obvious: webhook idempotency, RLS policies, and multi-language i18n are all places where \"close enough\" is a bug. There are five places a new locale string has to land before the build stops complaining, and vibes will find four of them.",[586,1440,1442],{"id":1441},"the-business-case-vibe-coding-in-startup-context","The Business Case: Vibe Coding in Startup Context",[16,1444,1445],{},"The speed gains from vibes are real and measurable — for the first mile. Scaffolding a landing page, a dashboard shell, a data model happens in minutes now.",[16,1447,1448],{},"Then the curve inverts. The weeks you saved on scaffolding get spent debugging the plumbing vibes couldn't handle. Founders who track this honestly land on the same rule: vibes for the MVP, structure for scale.",[16,1450,1451],{},"Karpathy's 2025 enthusiasm faded by 2026 partly through survivorship filtering. The demos that went viral were the ones that worked. The vibe-coded projects that quietly died in production billing bugs didn't trend.",[586,1453,1455],{"id":1454},"is-vibe-coding-dead","Is Vibe Coding Dead?",[16,1457,1458],{},"The buzzword trap killed the term more than the technique. Once every tool marketed itself as \"vibe coding,\" the phrase meant nothing.",[16,1460,1461],{},"What survived is the useful core: describe intent, let the model do the mechanical work, iterate fast.",[16,1463,1464],{},"What changed is the emphasis. LLMs are smarter, so the need for \"vibes\" shifted to \"conventions.\" The real skill now is judgment — knowing when to trust the agent and when to enforce determinism.",[586,1466,1468],{"id":1467},"the-anti-hype-take-what-developers-actually-need","The Anti-Hype Take: What Developers Actually Need",[16,1470,1471],{},"Here's the uncomfortable read: vibe coding solved the wrong problem. It framed the challenge as attitude — loosen up, trust the model — when the challenge was actually tooling.",[16,1473,1474,1475,93],{},"The real innovation was never vibes. It was agent-readable contracts: AGENTS.md, structured prompts, deterministic provisioning. Every starter that ships the stack misses the point; ",[57,1476,1478],{"href":90,"rel":1477},[61],"the stack was never the hard part",[16,1480,1481],{},"Starter kits with strong conventions beat pure vibes because they give the agent a floor. Building SaaS the way Karpathy now implies means structure plus AI, not vibes plus hope.",[586,1483,1485],{"id":1484},"technical-specifics-where-vibes-fail","Technical Specifics: Where Vibes Fail",[16,1487,1488],{},"Some things simply do not bend to attitude:",[110,1490,1491,1502,1508,1514,1525],{},[113,1492,1493,1496,1497,1501],{},[68,1494,1495],{},"Webhook signature verification."," You cannot vibe cryptographic correctness. See our writeup on treating ",[57,1498,1500],{"href":1101,"rel":1499},[61],"the GitHub invite as the product",", where some failures must throw and some must never.",[113,1503,1504,1507],{},[68,1505,1506],{},"Row-level security."," RLS is explicit, not emergent. A missing policy is a data breach, not a rough edge.",[113,1509,1510,1513],{},[68,1511,1512],{},"Idempotent transactions."," The two-generals problem doesn't care how confident your prompt sounded.",[113,1515,1516,1519,1520,1524],{},[68,1517,1518],{},"Consent flows."," ",[57,1521,1523],{"href":121,"rel":1522},[61],"German withdrawal law"," has specific requirements you encode into the pay button, or you don't sell legally.",[113,1526,1527,1519,1530,1534],{},[68,1528,1529],{},"Billing state.",[57,1531,1533],{"href":138,"rel":1532},[61],"Stripe webhooks are the source of truth",", not the optimistic client-side success page.",[586,1536,1538],{"id":1537},"tools-and-patterns-for-post-vibe-coding","Tools and Patterns for Post-Vibe Coding",[16,1540,1541],{},"This is exactly what BoiledPlate encodes: the lessons of vibe coding turned into structure. Instead of vibing through setup, an agent-driven interview provisions Stripe products and webhooks, a Supabase database with RLS, and Google sign-in in one session — deterministically.",[16,1543,1544],{},"The AGENTS.md contract is the evolution of vibes into something a machine can read and honor. And semantic, agent-readable release notes let agents apply updates consistently instead of guessing.",[586,1546,1548],{"id":1547},"lessons-for-the-next-wave-of-ai-coding","Lessons for the Next Wave of AI Coding",[16,1550,1551],{},"Vibe coding was a necessary phase, not the destination. It taught developers that intent-first workflows are faster — and that unstructured trust doesn't survive production.",[16,1553,1554],{},"Karpathy's pivot tells us where things head: verification over trust, contracts over vibes. The skills that will matter are prompt engineering, contract design, and knowing what to check.",[16,1556,1557],{},"The best AI-native code, it turns out, looks less like vibes and more like highly structured conventions a model can follow without drifting.",[586,1559,1561],{"id":1560},"faq-common-misconceptions-about-vibe-coding","FAQ: Common Misconceptions About Vibe Coding",[16,1563,1564,1567],{},[68,1565,1566],{},"Does vibe coding mean no testing?"," No. The durable version is vibes plus verification — generate loosely, validate strictly.",[16,1569,1570,1573],{},[68,1571,1572],{},"Is Karpathy saying not to use LLMs?"," The opposite. Use them heavily, but with determinism and explicit constraints.",[16,1575,1576,1579],{},[68,1577,1578],{},"Can I ship production SaaS on vibes alone?"," Not sustainably. The plumbing — billing, security, compliance — demands structure.",[16,1581,1582,1585,1586,1590],{},[68,1583,1584],{},"What's the successor to vibe coding?"," Agent-native development built on contracts. Start from ",[57,1587,1589],{"href":430,"rel":1588},[61],"a boilerplate designed for agents"," rather than vibing the wiring yourself.",{"title":445,"searchDepth":446,"depth":446,"links":1592},[1593,1594,1595,1596,1597,1598,1599,1600,1601,1602,1603,1604,1605,1606],{"id":1290,"depth":446,"text":1291},{"id":1306,"depth":446,"text":1307},{"id":48,"depth":446,"text":49},{"id":1344,"depth":446,"text":1345},{"id":1373,"depth":446,"text":1374},{"id":1386,"depth":446,"text":1387},{"id":1420,"depth":446,"text":1421},{"id":1441,"depth":446,"text":1442},{"id":1454,"depth":446,"text":1455},{"id":1467,"depth":446,"text":1468},{"id":1484,"depth":446,"text":1485},{"id":1537,"depth":446,"text":1538},{"id":1547,"depth":446,"text":1548},{"id":1560,"depth":446,"text":1561},"2026-07-16","Explore vibe coding, Andrej Karpathy's controversial approach to AI-assisted development. Understand what it means, where it breaks, and serious alternatives.",{},"\u002Fblog\u002Fandrej-karpathy-vibe-coding",{"title":1282,"description":1608},"blog\u002Fandrej-karpathy-vibe-coding",[474,1614,1615,1616],"andrej karpathy","ai development","software engineering","SACUbmvSS-AaQ5e5rFj_7Tzsc3NC1Ldhz-Gf4C2uvSs",1785027127953]