Dev Vocabulary, Conquered: The 26-Card Vibe Coding Dictionary

Instead of cooking yourself, you describe the taste you want to a top chef and receive the dish.

A way of building software by asking an AI in plain language instead of typing code line by line. The clearer the picture in your head, the better the result, and the VibeCampus Studio builds websites, apps, and games exactly this way.

The order slip you hand the chef. 'Medium spicy, noodles firm' gets you the dish you wanted; 'surprise me' does not.

The request you send to the AI. The more it says about who it's for, what's needed, and what mood, the more accurate the result. Every sentence you type into the Studio's input box is a prompt, and polishing them matters enough to have its own course.

The chef in person, the one who reads the order slip and actually cooks.

The brain of the AI, the part that actually thinks and produces answers. Names like Claude, GPT, and Gemini are all model names, and which model is on duty changes the quality and speed of the result. The Studio picks the model that fits each job.

The amount of ingredients a dish consumes. A long, complicated order uses more ingredients.

The unit of text chunks an AI counts as it reads and writes. An AI's workload is measured in tokens, so for the same content, short and clear wording is more efficient. All you need is the sense that longer text means more tokens.

The order window between the dining room and the kitchen. Food comes out without customers ever walking into the kitchen.

The standard window through which programs exchange data and features. When your app borrows weather, maps, or AI from outside, it all goes through APIs. This is how the world's services shake hands.

A capable employee who says 'I'll report back when it's done' and gets moving on their own.

An AI that takes one instruction, then plans, uses tools, checks results, and carries multiple steps through by itself. While the build gauge fills, the agent is writing code to the blueprint and verifying as it goes. The decisive difference from a simple Q&A AI is exactly this 'carries it through by itself'.

The conductor who binds many players into one piece of music.

Dividing work among multiple AIs and tools, each doing what it does best, and coordinating the sequence. Text to this model, images to that one, verification to yet another tool. Split the roles and quality and stability rise together. Even a single Studio result has many players in it.

A connection standard like USB: plug anything in and it just works.

The standard spec (Model Context Protocol) for connecting external tools and data to an AI. With a unified standard, an AI can safely pick up tools like calendars, databases, and search. The most common misunderstanding is thinking it's a payment method; it's a way of connecting.

A device that fires automatically at a set moment, like a bell that rings whenever the door opens.

A link that automatically runs a predefined action the instant a certain event happens. Automation like running checks on every save or sending a notice when a deploy finishes is built from hooks. It's how the system remembers even when humans forget.

A chef's proven recipe card. Pull it out and failures drop sharply.

A package of proven techniques like 3D staging, charts, or parallax scrolling. You can search the Studio's skill library and add them to a build, and even if you don't pick any, skills matching your prompt are chosen and combined automatically.

A big refrigerator with tidy compartments. Whatever you put in is still there next time you open it.

A store that keeps information like customers, bookings, and posts in an organized structure. What's on screen vanishes when you close it, but data in the DB stays. It's the heart of any service that takes bookings or manages members.

A complete warehouse service that rents you the refrigerator with the locks and a delivery window included.

A service that bundles a DB with extras like login and file storage. On VibeCampus you can connect your own Supabase account directly to the Studio, so your service's data is under your ownership from day one.

Bringing your own wine to a favorite restaurant. It's yours, so both the contents and the bill stay under your control.

Bring Your Own: connecting with your own account and keys. Data and usage are in your name, so your service never gets locked into a platform as it grows, and you can pack up and move everything at any time.

The membership card that proves it's you at the order window. If someone else uses it, the bill lands on you.

A secret string proving an API request belongs to your account. Usage is billed against this key, so treat it like a password and never expose it on screen or in public code.

The safe backstage. Actors act on stage; valuables stay in the safe.

A settings space that keeps secrets like API keys outside your code. Share or publish the code and no secrets leak, and when your environment changes you swap the values while the code stays untouched.

A game's save points. You can always return to an earlier save.

A service that records your code's change history (version control) and stores it online. Mistakes can be rolled back to yesterday's code, and when several people build together it keeps their work from colliding and breaking. Most of the world's software lives here.

Opening day for the shop. The moment what you built opens its doors to customers.

Putting your finished work on the internet so anyone can reach it. On VibeCampus it's one click, and the moment you deploy you get a shareable address. A build before deploy is still a prototype that only exists in your workshop.

The shop sign, and the address you print on business cards.

The name people type to reach your site (like mysite.com). A memorable domain of your own is what turns a site into a brand, and VibeCampus domain search lets you find the name you want and connect it right away.

The internet's phone book, turning a sign's name into the building's actual location.

The system that translates a domain name into a server's real address (IP). Connecting a domain ultimately means writing 'guests for this name go to this server' into DNS. The record can take a little while to spread.

Sending a letter in a sealed envelope. Nobody can read it in transit.

The security layer encrypting traffic between your site and its visitors. The padlock in the address bar means SSL is on; without it, browsers warn that the site is not secure and visitors turn back. These days it's not optional, it's the baseline.

The building your shop occupies. The lights never go out, 24 hours a day.

Renting server space that keeps your site running day and night. VibeCampus handles hosting along with deploys, so there's no server to buy or babysit. You build; the building management is covered.

The shop's interior and display windows. Everything guests see and touch.

The visible part: layout, buttons, colors, type. Requests like 'more premium, bigger buttons' are polishing exactly this area, and it's also the part you can touch directly with Click to edit.

The kitchen and the storeroom. Guests never see it, but this is where the shop actually runs.

The processing behind the screen: storing data, logins, payments. Form submissions actually saving and logins actually working happen because a backend exists. It's the essential other half of any app where data stays alive.

Renting a water purifier instead of buying one. Installation, upkeep, and filter changes are all included.

Software you subscribe to over the internet with nothing to install (Software as a Service). Notion and Netflix are classic examples, and the subscription services you'll build and sell are SaaS too. Not a one-time sale but a relationship that renews monthly.

A sandpit where children play only inside the box. Nothing outside gets messy.

A safety device that runs code in a space isolated from the real service. It's why Trust & Fact-Check can actually execute your code in an E2B sandbox: whatever happens, the live service is untouched.

A finished picture frame you can rehang on any wall.

A way to drop your creation into another site or blog with a few lines of code. The Studio's embed feature produces copy-paste-ready code, so your build can go straight onto a homepage that's already running.