[{"data":1,"prerenderedAt":69},["ShallowReactive",2],{"term-v\u002Fvibe-scope":3,"related-v\u002Fvibe-scope":58},{"id":4,"title":5,"acronym":6,"body":7,"category":40,"description":41,"difficulty":42,"extension":43,"letter":44,"meta":45,"navigation":46,"path":47,"related":48,"seo":52,"sitemap":53,"stem":56,"subcategory":6,"__hash__":57},"terms\u002Fterms\u002Fv\u002Fvibe-scope.md","Vibe Scope",null,{"type":8,"value":9,"toc":33},"minimark",[10,15,19,23,26,30],[11,12,14],"h2",{"id":13},"eli5-the-vibe-check","ELI5 — The Vibe Check",[16,17,18],"p",{},"Vibe scope is when the AI expands what you're building mid-session without asking. You said \"add a login button\" and somehow now you have a full auth system with password reset, email verification, and an admin panel. Feature creep, but it's technically the AI's fault. The AI interpreted your request generously and went to town. You're 4 hours in. The button works. So does everything you didn't ask for.",[11,20,22],{"id":21},"real-talk","Real Talk",[16,24,25],{},"Vibe scope occurs when an AI coding assistant infers implied requirements and implements more than explicitly requested. It's driven by the model's attempt to be helpful — if you ask for a login button, it reasons that login implies authentication, which implies session handling, etc. Managing vibe scope requires tight, explicit prompts and frequent check-ins. Left unchecked, it's the fastest path to a bloated PR that nobody can review.",[11,27,29],{"id":28},"when-youll-hear-this","When You'll Hear This",[16,31,32],{},"\"Classic vibe scope — I asked for a modal and got a design system.\" \u002F \"Watch for vibe scope in long sessions. The AI gets ambitious.\"",{"title":34,"searchDepth":35,"depth":35,"links":36},"",2,[37,38,39],{"id":13,"depth":35,"text":14},{"id":21,"depth":35,"text":22},{"id":28,"depth":35,"text":29},"vibecoding","Vibe scope is when the AI expands what you're building mid-session without asking. Feature creep, but it's technically the AI's fault.","intermediate","md","v",{},true,"\u002Fterms\u002Fv\u002Fvibe-scope",[49,50,51],"Vibe Coding","Scope Creep","Vibe Debt",{"title":5,"description":41},{"changefreq":54,"priority":55},"weekly",0.7,"terms\u002Fv\u002Fvibe-scope","v-5PyAVbl3qIVRrB9dwCeVEpc9_gBEM6Zlyzq6n36xg",[59,63,66],{"title":50,"path":60,"acronym":6,"category":40,"difficulty":61,"description":62},"\u002Fterms\u002Fs\u002Fscope-creep","beginner","Scope creep is when a simple feature request slowly grows into rebuilding the entire application.",{"title":49,"path":64,"acronym":6,"category":40,"difficulty":61,"description":65},"\u002Fterms\u002Fv\u002Fvibe-coding","Vibe coding is writing software by vibes — you describe what you want to an AI, it writes the code, and you just... vibe.",{"title":51,"path":67,"acronym":6,"category":40,"difficulty":42,"description":68},"\u002Fterms\u002Fv\u002Fvibe-debt","Vibe debt is AI-generated shortcuts that work today but will hurt later — technical debt's chaotic, fast-moving younger sibling.",1775560940223]