You’re watching a tutorial. Someone casually mentions “pushing to the backend” or “checking the logs.” You nod along, but inside you’re lost.
Here’s the thing: vibe coding has its own vocabulary. And while you don’t need to understand how the code works, knowing what these terms mean helps you communicate with AI tools, follow tutorials, and troubleshoot problems.
This isn’t a computer science textbook. It’s a practical reference — organized by when you’ll encounter each term in your vibe coding journey. Bookmark it. Come back when you hit a word you don’t recognize.
New to vibe coding entirely? Start with How to Vibe Code: A Beginner’s Step-by-Step Guide first.
Table of Contents
Getting Started: The Basics
These are the terms you’ll encounter in your first hour of vibe coding.
Prompt
The instructions you give to an AI in plain English. Your prompt is the starting point for everything — it’s how you communicate what you want built.
A good prompt is specific. Instead of “make me an app,” try “create a web app that tracks my daily water intake with a simple counter and a reset button.”
Pro tip: Ask the AI to clarify before building. End your prompt with: “Ask me any clarifying questions before we begin.” This catches misunderstandings early.
Context
The conversation history the AI remembers within a single chat session. Every message you send adds to the context, helping the AI understand what you’re building together.
Context has limits. Long conversations eventually “fill up,” and the AI starts forgetting earlier details. When this happens, you’ll need to start a fresh chat and re-explain your project.
Pro tip: When starting a new chat mid-project, write a brief handoff: “I’m continuing work on [project]. Here’s where we left off: [summary]. The key files are [list]. Let’s pick up from there.”
Front End
Everything users see and interact with — buttons, text, images, forms, colors, layouts. The front end is your app’s face.
When something looks wrong (weird spacing, ugly colors, broken buttons), that’s a front end problem. When something works wrong (data not saving, login failing), that’s usually a back end problem.
Back End
Everything happening behind the scenes that users don’t see — storing data, checking passwords, connecting to other services. The back end is your app’s brain.
You don’t need to understand back end code. But knowing the term helps you describe problems: “The button looks fine, but when I click it nothing happens” tells the AI to look at the back end.
Building Features: Making Your App Do Things
Once you have the basics, you’ll start adding real functionality. These terms come up constantly.
Database
Where your app stores information permanently. Without a database, everything disappears when users close the app.
Think of it like a spreadsheet that lives on the internet. User accounts, saved preferences, tracked habits — all stored in the database. Popular options for beginners include Supabase and Firebase.
Authentication
The system that verifies who someone is. Login screens, sign-up forms, password resets, “forgot password” emails — that’s all authentication.
Authentication answers the question: “Are you who you say you are?” It’s what prevents random people from accessing your account.
API
A way for your app to talk to other services. When your app checks the weather, processes a payment, or uses an AI model — it’s calling an API.
Think of APIs like restaurant menus. You don’t go into the kitchen; you just order from the menu. The kitchen (the other service) handles the work and sends back what you asked for.
Pro tip: APIs often require keys (passwords that identify your app). Keep these secret — never paste them directly into code that others can see.
Environment Variables
Secret values stored outside your code — API keys, passwords, database connections. They’re called “environment” variables because they change depending on where your app runs.
Why bother? If you accidentally share your code publicly (easy to do on GitHub), your secrets stay safe because they’re not in the code itself.
Agent
An AI that doesn’t just answer questions — it takes actions. Agents can browse the web, write files, run code, and use tools in a loop until a task is complete.
Regular AI: “Here’s how you would build that feature.” Agent AI: Actually builds the feature, tests it, and asks what’s next.
Claude Code is an agent. It reads your files, writes code, runs commands, and keeps going until the job is done.
Skills (Agent Skills)
Specific capabilities you can give an agent — like connecting to Slack, searching the web, or accessing a calendar. Skills extend what an agent can do beyond just writing code.
Not all vibe coding tools support skills, but when they do, they’re powerful. An agent with a Slack skill can post messages. An agent with a web search skill can research current information.
Working with Files and Assets
Your app isn’t just code — it includes images, sounds, configuration, and structure.
Assets
Files your app uses that aren’t code — images, icons, logos, sounds, fonts. When you want a custom logo or a notification sound, you’re adding assets.
Most vibe coding tools let you upload assets or generate them with AI. Just describe what you want: “Create a simple, friendly icon for a meal-planning app.”
File Upload
The ability to add files to your project. Some vibe coding platforms have built-in file management; others require you to work with files locally on your computer.
Knowing where your files live matters when troubleshooting. If the AI can’t find an image, it might be in the wrong folder.
Repository (Repo)
A folder that stores your entire project, usually on GitHub. The repo contains all your code, assets, and history of changes.
GitHub repos are how you connect your project to deployment services like Vercel. Think of it as your project’s home address on the internet.
Debugging: When Things Go Wrong
Things will break. These terms help you describe and fix problems.
Error
Something that stops your code from running entirely. Errors are usually obvious — you’ll see a red message, a crash, or a blank screen.
The good news: error messages tell you (or the AI) exactly what went wrong. Copy the entire message and paste it to your AI: “I’m getting this error: [paste]. What does it mean and how do I fix it?”
Bug
Something wrong that doesn’t crash your app — it just doesn’t work correctly. A button that does the wrong thing, a calculation that’s off, text that doesn’t display properly.
Bugs are sneakier than errors because the app still runs. Describe exactly what happens versus what should happen: “When I click Save, it shows ‘success’ but the data isn’t actually saved.”
Debugging
The process of finding and fixing errors and bugs. Professional developers spend huge amounts of time debugging — you’re in good company when things break.
Pro tip: When stuck in a “fix one thing, break another” loop, stop. Start fresh. The second build is always faster because you understand the project better.
Logs
Messages your app records as it runs — a diary of what’s happening behind the scenes. Logs help you see what the app was doing when something went wrong.
You might never look at logs directly. But if an AI asks you to “check the logs,” it’s looking for clues about what happened.
Console
A window that shows logs and error messages while your app runs. In a browser, you can open the console by pressing F12 (or right-click → Inspect → Console tab).
When the AI says “what does the console show?” — this is where to look.
Testing and Previewing
Before your app goes live, you’ll test it. These terms describe that process.
Preview
A temporary version of your app you can interact with while building. Previews let you click around, test features, and see how things look without deploying to the real internet.
Most vibe coding tools show a preview automatically. It’s your “work in progress” view.
Hot Reload
When changes appear instantly without restarting. You make an edit, and the preview updates immediately — no need to refresh or rebuild.
Hot reload makes the feedback loop fast: describe a change → see it instantly → refine → repeat.
Testing
Checking that features work correctly before calling them “done.” This might be as simple as clicking every button yourself, or as formal as writing automated tests.
Pro tip: Test existing features before adding new ones. It’s easy to accidentally break something while building something else.
Seed Data
Fake information used to see how your app looks with content. Instead of creating real users and real posts, you fill it with placeholder data: “John Doe,” “Test User,” “Lorem ipsum.”
Seed data is helpful for design work. You can see how a profile page looks with a long name or a short bio without needing actual users.
Going Live: Deployment and Hosting
The finish line: putting your app on the internet for real.
Deployment
The act of pushing your code to a server so it’s accessible on the internet. Before deployment, only you can see your app. After deployment, anyone with the link can use it.
With tools like Vercel, deployment can be a single click. Connect your GitHub repo, click deploy, and you get a real URL.
Hosting
The service that keeps your app running and available online. Think of it like renting space on a computer that’s always connected to the internet.
Popular hosting options: Vercel (great for web apps), Netlify, Replit, and many vibe coding platforms include hosting built-in.
Domain
Your app’s address on the internet. Instead of a random URL like my-app-abc123.vercel.app, a custom domain gives you something memorable: myapp.com.
You don’t need a custom domain to start — the free URLs work fine. But when you want to share something professional, buying a domain is an affordable upgrade.
Advanced Concepts
You might not need these right away, but you’ll encounter them as projects grow.
Schema
The blueprint for how your database is organized. It defines what information you store (users, posts, comments) and how pieces connect to each other.
You don’t write schemas yourself — you describe what you need, and the AI creates one. But knowing the term helps when you hear “let’s update the schema.”
Table
A single category of data in your database — like one spreadsheet within a workbook. A “users” table stores user info. A “posts” table stores posts. They can link to each other (this post belongs to this user).
Webhook
A way for one service to notify another when something happens. Instead of constantly asking “did anything change?” — webhooks send automatic messages when events occur.
Example: When someone pays on Stripe, a webhook can tell your app “payment received!” instantly.
Queue
Tasks lined up to run one after another. When you submit multiple prompts quickly, they might enter a queue and process in order rather than all at once.
SaaS
Software as a Service — an app that people pay to use. If you build something others would pay for, congratulations: you’ve built a SaaS product.
Most beginners should focus on building tools they personally need before worrying about monetization. Build something you love using first.
The Vibe Coder’s Cheat Sheet
Quick reference prompts for common situations:
| Situation | Try This Prompt |
|---|---|
| Starting a project | “Explain your approach first. Don’t write any code yet.” |
| Unsure how to proceed | “Give me 3 approaches, simplest first. Explain tradeoffs.” |
| Getting a second opinion | “Claude suggested [X]. As a second opinion, what concerns do you have?” |
| Seeing an error | “I got this error: [paste full message]. What does it mean and how do I fix it?” |
| Something’s not working | “I wanted X but got Y. Here’s exactly what should happen: [describe].” |
| It’s too complicated | “This feels too complicated. What’s the minimum version that would work?” |
| Don’t understand something | “Explain what this file does in plain English. I’m not a programmer.” |
| AI forgot context | “Before making changes, read these files: [list]. Then [describe what you want].” |
| Want to audit your work | “Review this code for security concerns and potential improvements.” |
Keep Learning
This dictionary covers the essential vocabulary. But vibe coding is a skill you build by doing, not just reading.
Ready to build something? Follow the step-by-step tutorial: How to Vibe Code: A Beginner’s Guide
Want to understand the bigger picture? Read: What is Vibe Coding? (And When You Need Something More)
Building something serious? As projects grow, pure vibe coding has tradeoffs. Learn about Specification-Driven Development for apps that need to last.
The vocabulary you just learned isn’t just for understanding tutorials — it’s for communicating clearly with AI tools. The clearer your language, the better your results.
Now go build something.
Related guides: How to Vibe Code • What is Vibe Coding? • AI Tutorials