Fundamentals
Vibe Coding Glossary: Terms Every AI Builder Should Know
Building with AI drops you into a conversation full of words nobody stopped to define. Here they are in plain language — enough to follow what your AI assistant is saying and to describe what you want back. Skim it, or keep it open in a tab.
The basics
- Vibe coding — building software by describing your intent to an AI and refining what it produces, instead of writing every line yourself. See what vibe coding is.
- Prompt — the instruction you give the AI. Prompt engineering is the craft of wording it well; see prompts that generate clean code.
- Context — everything the model can see when it answers: your code, constraints, and data. Managing it on purpose is context engineering.
- Regeneration — asking the AI to rewrite something rather than editing it by hand. Cheap to do, easy to overuse.
Running and building
- Localhost — your own computer acting as a web server, reachable only by you. A port is the numbered door your app is served on (like
localhost:3000). See running AI code locally. - Dev server — the program that serves your app while you build, usually with hot reload.
- Hot reload — the page updating instantly as you save changes, without a manual refresh.
- Environment — the setup your code runs in. Dev (development) is your machine; prod (production) is where real users reach it, and the two differ in ways that cause bugs.
- Deployment / hosting — publishing your app somewhere on the internet so others can use it.
The parts of an app
- DOM — the live structure of a web page as the browser holds it, which JavaScript can read and change.
- Dependency / package — third-party code your app pulls in so it doesn't reinvent common things. Each carries its own license.
- API — a way for one program to talk to another. An API key is the secret that authorizes those requests — and must never be pasted into public code.
- localStorage — a small store in the browser for saving data on one device. Handy, but not a database — it's per-device and easily wiped.
Quality and bugs
- Happy path — the ideal run where everything goes right. Real users leave it immediately.
- Edge case — an unusual input or situation that code often forgets; see the edge cases AI code misses.
- Silent failure — an error the code swallows so you never see it; see silent failures in AI code.
- Responsive design — layout that adapts from big screens to small phones.
- Accessibility (a11y) — building so people using screen readers, keyboards, or low vision can still use your app.
- Technical debt — shortcuts and mess that make future changes harder; see dead code and duplication.
- Refactor — improving the structure of code without changing what it does.
- Audit / due diligence — a structured check of an app against a quality bar before you rely on it.
Where Vibe Coder Playground fits: a lot of these terms name things you can't see just by reading code — the DOM, live state, network calls, silent failures. The Playground makes them visible by running your app and putting them next to the page, so the vocabulary turns into something you can actually watch happen.