[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-573255-105":53,"doc-detail-573255-en":126},{"code":4,"msg":5,"data":6},0,"success",[7,14,19,24,29,34,39,44,49],{"id":8,"doc_module":9,"doc_module_name":10,"category_name":11,"show_sort_weight":12,"slug":13},11,1,"Template","Presentations",90,"presentations",{"id":15,"doc_module":9,"doc_module_name":10,"category_name":16,"show_sort_weight":17,"slug":18},12,"Resumes",80,"resumes",{"id":20,"doc_module":9,"doc_module_name":10,"category_name":21,"show_sort_weight":22,"slug":23},14,"Invoices",70,"invoices",{"id":25,"doc_module":9,"doc_module_name":10,"category_name":26,"show_sort_weight":27,"slug":28},15,"Posters",60,"posters",{"id":30,"doc_module":9,"doc_module_name":10,"category_name":31,"show_sort_weight":32,"slug":33},16,"Social Media",50,"social-media",{"id":35,"doc_module":9,"doc_module_name":10,"category_name":36,"show_sort_weight":37,"slug":38},17,"Forms",40,"forms",{"id":40,"doc_module":9,"doc_module_name":10,"category_name":41,"show_sort_weight":42,"slug":43},18,"Letters",30,"letters",{"id":45,"doc_module":9,"doc_module_name":10,"category_name":46,"show_sort_weight":47,"slug":48},21,"Paper Templates",5,"papers-templates",{"id":50,"doc_module":9,"doc_module_name":10,"category_name":51,"show_sort_weight":4,"slug":52},158,"General","general-158",{"code":4,"msg":54,"data":55},"ok",{"site_id":56,"language":57,"slug":58,"title":59,"keywords":60,"description":61,"schema_data":62,"social_meta":119,"head_meta":121,"extra_data":123,"updated_unix":125},105,"en","vibe-coding-cheatsheet-quick-reference","vibe-coding-cheatsheet - quick reference","","vibe-coding-cheatsheet provides a compact operational guide for generating code changes safely and efficiently. It defines a Vibe Loop workflow: set frame outcomes, control scope changes, generate with minimal output, review diffs against intent, and verify using tests, UX checks, and edge-case probing before committing. It includes prompt DNA and reusable templates, quality gates, drift and anti-pattern signals, team roles and safety guardrails, plus a release checklist. It also advises when to use vibe coding versus classic approaches.",{"@graph":63,"@context":118},[64,80,101],{"@type":65,"itemListElement":66},"BreadcrumbList",[67,71,74,77],{"item":68,"name":69,"@type":70,"position":9},"https://docshare.wps.com","Home","ListItem",{"item":72,"name":10,"@type":70,"position":73},"https://docshare.wps.com/template/",2,{"item":75,"name":51,"@type":70,"position":76},"https://docshare.wps.com/template/general/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/vibe-coding-cheatsheet-quick-reference/573255/",4,{"url":78,"name":59,"@type":81,"image":82,"author":87,"headline":59,"publisher":90,"fileFormat":93,"inLanguage":57,"description":61,"dateModified":94,"datePublished":95,"encodingFormat":93,"isAccessibleForFree":96,"interactionStatistic":97},"DigitalDocument",{"url":83,"@type":84,"width":85,"height":86},"https://docshare.wps.com/thumbnails/vibe-coding-cheatsheet-quick-reference/573255.png","ImageObject",442,249,{"name":88,"@type":89},"Rizky","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-10-17","2026-10-13",true,{"@type":98,"interactionType":99,"userInteractionCount":76},"InteractionCounter",{"@type":100},"ViewAction",{"@type":102,"mainEntity":103},"FAQPage",[104,110,114],{"name":105,"@type":106,"acceptedAnswer":107},"What is the Vibe Loop workflow in this cheatsheet?","Question",{"text":108,"@type":109},"It starts by defining a frame outcome and acceptance checks, then identifies scope changes and boundaries, generates changes in a single pass, reviews the diff to align with intent and reject drift, and finally verifies with tests, UX/edge-case checks before committing.","Answer",{"name":111,"@type":106,"acceptedAnswer":112},"What should be included in the Prompt DNA section?",{"text":113,"@type":109},"Prompt DNA calls for an explicit goal/outcome tied to user impact, clear context such as key files, naming, constraints, and non-goals, plus checks that specify tests, UI steps, and edge cases.",{"name":115,"@type":106,"acceptedAnswer":116},"When should you switch from vibe coding to classic coding?",{"text":117,"@type":109},"Switch to classic when you face security-heavy flows, performance-critical logic, ambiguous scope, lack of tests or owners, regulated systems, or large architecture where blast radius demands more design before generation.","https://schema.org",{"og:url":78,"og:type":120,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":122,"canonical":78},"index,follow",{"doc_id":124,"site_id":56},573255,1792090593,{"code":4,"msg":5,"data":127},{"doc_id":124,"user_id":128,"nickname":88,"user_avatar":129,"doc_module":9,"category_id":50,"category_name":51,"doc_title":59,"doc_description":61,"doc_content":130,"file_id":131,"file_url":132,"file_type":133,"file_size":134,"view_count":76,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":9,"language":135,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":136,"faqs":137,"seo_title":138,"seo_description":61,"update_tm":139,"read_time":4},962085564807,"https://ap-avatar.wpscdn.com/davatar_6f874abed73319feea01a86fa6f0fab8","| 􀂟 THE VIBE LOOP |\n| --- |\n| 1 Frame outcome\u003Cbr>Define user result and acceptance checks\u003Cbr>2 Scope change\u003Cbr>Identify files, boundaries, non-goals\u003Cbr>3 Generate\u003Cbr>Single pass, minimal output\u003Cbr>4 Review diff\u003Cbr>Align with intent, reject drift\u003Cbr>5 Verify\u003Cbr>Tests, UX, edge cases, then commit\u003Cbr>\u003Cbr>\u003Cbr>\u003Cbr>\u003Cbr>|\n\n\n| 􀂹 PROMPT DNA |\n| --- |\n| Goal Outcome + user impact\u003Cbr>Context Key files, naming, constraints Non-goals What must not change\u003Cbr>Checks Tests, UI steps, edge cases |\n\n\n| 􀂩 PROMPT TEMPLATE |\n| --- |\n| \u003Cbr>Goal: \u003Cwhat the user should be able to do> Context: \u003Cfiles , constraints , stack> Non-goals: \u003Cwhat to avoid , scope limits> Checks: \u003Ctests , UI verification steps> |\n| Ask for a plan first when risk is high. |\n\n\n| ✅ QUALITY GATES |\n| --- |\n| Diff review Verify files, scope, and intent\u003Cbr>Run it Local test or manual UX pass Edge checks Hit a non-happy path\u003Cbr>Stop if Failing tests, unclear ownership, hidden scope |\n\n\n| ⚖ WHEN TO VIBE VS CODE |  |\n| --- | --- |\n| Great Fits\u003Cbr>MVPs and demos UI/content iteration Internal tools\u003Cbr>Docs scaffolding Data cleanup scripts Refactors with tests | Switch to Classic\u003Cbr>Security-heavy flows Perf-critical logic Ambiguous scope No tests or owners Regulated systems Large architecture |\n| Higher blast radius = more design before generation. |  |\n\n\n| ⚡ CORE PRINCIPLES |\n| --- |\n| Director mindset You define outcomes and approve diffs\u003Cbr>Small scopes Short prompts, tight diffs, faster review Verify by default Tests + behavior checks beat vibes\u003Cbr>State discipline Commit often, log prompts, keep rollback |\n\n\n| 􀀜 THE VIBE STACK |\n| --- |\n| Explore Editor + browser agent\u003Cbr>Build Repo-aware CLI agent Verify Tests, lint, runtime checks\u003Cbr>Anchor Real files, real constraints |\n\n\n| 􀀝 PROMPT PATTERNS |\n| --- |\n| Plan first Outline approach before code\u003Cbr>One feature Keep scope tight per prompt Diff-first Ask for patches, not rewrites Sample data Realistic inputs = accurate output\u003Cbr>Force checks Require explicit success criteria |\n\n\n| ⚠ DRIFT SIGNALS |\n| --- |\n| ✗ Spec expands mid-prompt or adds new features ✗ Renames or rewires files you did not touch ✗ Introduces new dependencies without approval ✗ Deletes tests or bypasses verification |\n\n\n| 􀃱 ANTI ] PATTERNS |\n| --- |\n| ✗ Letting the model redefine goals ✗ Stacking changes before verification ✗ Accepting diffs without a local run ✗ Shipping without ownership or rollback |\n\n\n| 􀁓 TEAM & SAFETY |\n| --- |\n| Roles\u003Cbr>Owner sets scope • Builder runs loop • Reviewer verifies risk\u003Cbr>Guardrails\u003Cbr>No secrets in prompts • Pin dependencies • Audit changes • Keep rollback |\n\n\n| 􀃋 RELEASE CHECKLIST |  |  |  | Use every iteration |\n| --- | --- | --- | --- | --- |\n|  Scope locked, acceptance defined |  |  |  | Diff reviewed for drift |\n|  |  |  |  |  |\n|  |  |  |  |  |\n| | Tests run or UX verified |  |  | Edge case probed |\n|  Prompt log updated |  |  |  | Rollback plan confirmed |\n\nGet the full interactive guide at  [awesomeclaude.ai/vibe-coding-guide](awesomeclaude.ai/vibe-coding-guide)  Vibe Coding Cheatsheet • This cheatsheet is maintained [by awesomeclaude.ai](by awesomeclaude.ai)","cbCaif0fjQOn9pyI","https://ap.wps.com/l/cbCaif0fjQOn9pyI","pdf",310246,"English","# Vibe Loop\n## Prompt DNA\n## Prompt Template\n## Quality Gates\n## When to Vibe vs Code\n## Core Principles\n## Vibe Stack\n## Prompt Patterns\n## Drift Signals\n## Anti-Patterns\n## Team & Safety\n## Release Checklist","[{\"question\":\"What is the Vibe Loop workflow in this cheatsheet?\",\"answer\":\"It starts by defining a frame outcome and acceptance checks, then identifies scope changes and boundaries, generates changes in a single pass, reviews the diff to align with intent and reject drift, and finally verifies with tests, UX/edge-case checks before committing.\"},{\"question\":\"What should be included in the Prompt DNA section?\",\"answer\":\"Prompt DNA calls for an explicit goal/outcome tied to user impact, clear context such as key files, naming, constraints, and non-goals, plus checks that specify tests, UI steps, and edge cases.\"},{\"question\":\"When should you switch from vibe coding to classic coding?\",\"answer\":\"Switch to classic when you face security-heavy flows, performance-critical logic, ambiguous scope, lack of tests or owners, regulated systems, or large architecture where blast radius demands more design before generation.\"}]","vibe-coding-cheatsheet - quick reference | PDF",1791935804]