← Cheatsheets
Tags: vibe-coding, ai, llm, agentic, prompting, cursor, cline, copilot, beginner
Last updated: 2026-06-27
Vibe Coding Cheatsheet
What Is Vibe Coding?
Vibe coding is a new way to build software where you describe what you want in plain English and an AI assistant writes the code for you. You “vibe” with the AI — you review, accept, reject, and guide its output in a conversation instead of typing every line yourself.
The term was coined by Andrej Karpathy (co-founder of OpenAI, former Tesla AI lead) in early 2025:
There’s a new kind of coding I call ‘vibe coding,’ where you fully give in to the vibes, embrace exponentials, and forget that the code even exists.
In practice, it means you prompt an AI, watch it generate entire files, iterate through conversation, and only intervene when the output isn’t what you intended. It’s like pair-programming with a tireless junior developer who types at 10,000 words per minute.
Why Vibe Code?
| Benefit | What It Means |
|---|
| Speed | Build a full prototype in hours, not weeks |
| Low barrier | No need to memorise syntax or APIs |
| Exploration | Try 5 approaches quickly, keep the best one |
| Learning | Watch the AI solve problems and learn patterns |
| Accessibility | Non-engineers can build working software |
Core Terminology
| Term | Definition |
|---|
| LLM (Large Language Model) | The AI brain (Claude, GPT-4, Gemini). Predicts the next token in a sequence. |
| Prompt | The natural-language instruction you give the AI. Good prompts = good code. |
| Context Window | How much conversation the AI can remember. Larger windows = more code per session. |
| Agent / Agentic | The AI reads files, runs commands, creates files, and loops autonomously. |
| BYOK (Bring Your Own Key) | You provide your own API key. Pay per generation, no subscription lock-in. |
| MCP (Model Context Protocol) | Open standard for AI agents to connect to external tools (databases, APIs, game engines). |
| Scaffolding | Generating the boilerplate folder structure, config files, and package setup. |
| Hallucination | The AI invents functions or APIs that don’t exist. Review everything. |
| Vibe Check | Running AI-generated code to see if it works. Pass/fail, usually a surprise. |
| Token | The unit LLMs read. ~0.75 words per token. Billed per token (input + output). |
Types of Vibe Coding
Prompt-Driven (Chat)
- Describe what you want in a chat interface.
- AI responds with code snippets; you copy-paste into your IDE.
- Tools: ChatGPT, Claude.ai, Gemini.
- Best for: Quick questions, small functions, learning.
Agentic (In-IDE)
- AI runs inside your IDE (VS Code, JetBrains).
- Reads your project, creates/edits files, runs terminal commands, debugs autonomously. You review each change.
- Tools: Cline, Cursor, Windsurf, GitHub Copilot Agent Mode.
- Best for: Full-stack apps, game dev, refactoring.
Multi-File / Project-Gen
- Describe your entire app in one prompt.
- AI generates the full project — folders, config, source, tests, README.
- Tools: Bolt.new, v0.dev, Lovable, Replit Agent.
- Best for: New projects, hackathons, MVPs.
Multi-Agent
- Multiple AI agents collaborate on different parts of a project.
- One writes backend, another frontend, a third reviews.
- Tools: Custom setups, CrewAI, AutoGen.
- Best for: Large codebases, enterprise, microservices.
The Vibe Coder’s Workflow
- DESCRIBE → “Build a to-do app with dark mode and local storage.”
- GENERATE → AI creates the project, files, and code.
- VIBE CHECK → Run it. Does it work?
- ITERATE → “Add drag-and-drop reordering.” AI updates code.
- REFINE → “Make it faster.” AI suggests optimisations.
- SHIP → Deploy. Move on to the next feature.
Choosing Your Stack
| You Are | Try |
|---|
| Total beginner, never coded | ChatGPT + Replit Agent |
| Learning to code | Cursor or Cline in VS Code |
| Indie game dev | Cline + Unity/Godot (BYOK) |
| Web dev, shipping fast | Cursor or Windsurf |
| Building a SaaS | Cline with MCP servers |
| Want everything in browser | Bolt.new or v0.dev |
| Enterprise / large teams | GitHub Copilot Agent Mode |
Essential Skills to Learn
| Skill | Why It Matters |
|---|
| Prompt writing | Vague instructions = vague code. Be specific about tech stack, patterns, and constraints. |
| Reading code | You don’t need to write it, but understanding the output is essential for debugging. |
| Reviewing & rejecting | AI makes mistakes. Learn to spot hallucinations, over-engineering, and security flaws. |
| Version control (Git) | Commit after every working iteration so you can roll back. AI changes are fast and sometimes destructive. |
| Debugging | When the vibe check fails, you need to describe the error back to the AI clearly. |
| System design | AI can build components; you need to know how they fit together. |
Common Mistakes
| Mistake | Fix |
|---|
| Prompt too vague | Specify language, framework, file structure, and style preferences. |
| Not reading generated code | Review every file before accepting. AI invents functions that don’t exist. |
| No version control | Commit before every major AI change. AI can nuke your working code. |
| Ignoring context limits | Long sessions degrade quality. Start fresh sessions for new features. |
| Blindly trusting AI | Test everything. AI doesn’t understand your project the way you do. |
| Under-specifying security | Tell AI explicitly about auth, validation, and sanitisation requirements. |
History & Milestones
| When | What Happened |
|---|
| 2020 | GitHub Copilot launches — first mainstream AI code assistant (autocomplete style). |
| Late 2022 | ChatGPT released. Developers realise they can prompt for entire functions. |
| 2023 | GPT-4 improves code generation significantly. Cursor IDE launches with AI-first UX. |
| Early 2024 | “Agentic” coding emerges — AI runs terminal commands, reads files, writes multi-file changes. |
| Late 2024 | Cline launches as open-source BYOK VS Code agent. MCP protocol standardises tool connections. |
| Early 2025 | Andrej Karpathy coins “vibe coding” — describes building apps entirely through AI conversation. |
| Mid-2025 | Multi-agent frameworks and AI project generators become mainstream. |
| Now | Vibe coding is a recognised development paradigm. You’re holding the cheatsheet. |
Philosophy
Vibe coding isn’t about replacing developers. It’s about shifting from “how do I write this?” to “what do I want to build?”
- Focus on the product, not the syntax.
- Treat AI as a superpowered junior dev you mentor.
- Ship fast, iterate faster.
- The best vibe coders are great at: describing intent, reviewing output, and knowing when to step in and write it themselves.