GlossaryVibe coding glossary
Every word you’ll meet, in plain English.
Plain definitions of the words you meet while vibe coding, from frontend and backend to API keys, DNS records and Next.js, each linked to the lesson that teaches it.
On this page
How to use this glossary.
Each word has a short, plain definition and a link to the lesson that teaches it properly. Every lesson also lists the glossary words it uses, under “Words in this lesson”, so you can look one up whenever you need to.

The basics
- Vibe coding
- Building websites and web apps by describing what you want in plain words, while an AI coding agent writes the code. You review the result and ask for changes. Lesson 1: What is vibe coding?
- AI coding agent
- The AI that reads your request, plans the change and writes the code. In 3Edit you can choose which one builds your project. Lesson 1: What is vibe coding?
- Prompt
- A message you send the AI, describing what you want built or changed. Clear, specific prompts get better results. Lesson 3: Writing prompts that build what you mean
- Brief
- A short description of a whole website for your first prompt: who it’s for, what it offers, the main action, the sections and how it should feel. Lesson 2: How to vibe code your first website
- Live preview
- Your website shown inside 3Edit while it builds and as you make changes, before anyone else can see it. Lesson 2: How to vibe code your first website
- Engine
- The AI coding agent powering your project at the moment. In 3Edit you can switch between Claude Code, Codex, the 3Edit Agent and 3Edit Node from the agent menu and carry on in the same project. Lesson 5: Choose how the AI works for you
- 3Edit Agent
- 3Edit’s own built-in AI agent. New projects start on it, it works straight away, and it uses your plan’s AI credits. Lesson 5: Choose how the AI works for you
- Codex
- OpenAI’s coding agent. In 3Edit you can build with it on your own ChatGPT plan, signed in with your own account, with no API keys. Lesson 5: Choose how the AI works for you
- Claude Code
- Anthropic’s coding agent. In 3Edit you can build with it on your own paid Claude plan, signed in with your own account, with no API keys. Lesson 5: Choose how the AI works for you
- 3Edit Node
- AI that runs on your own computer, so building has no per-prompt fees. It is optional: everything in 3Edit works without it. Lesson 5: Choose how the AI works for you
- Starter kit
- A complete website with its backend already built, ready to make your own by chatting. 3Edit’s kits are Ecommerce Store, Aurelle and Restaurant & Takeaway. See the starter kits
How web apps work
- Frontend
- Everything a visitor sees and clicks in their browser: pages, layout, buttons, forms, text and pictures. Lesson 6: Frontend and backend, explained
- Backend
- The part of an app that works behind the scenes on a server: keeping information in a database, signing people in, sending emails, taking payments and keeping data safe. Lesson 6: Frontend and backend, explained
- Server
- A computer that is always on and connected to the internet. It runs your app’s backend and hosts your published site. Lesson 6: Frontend and backend, explained
- Database
- Your app’s memory: information kept in tidy tables, such as accounts, bookings, orders and messages, so it is still there tomorrow. Lesson 7: Does my website need a database?
- Table
- One kind of record in a database, like a spreadsheet with strict rules: a Bookings table has one row per booking and one column per field. Lesson 7: Does my website need a database?
- Supabase
- The backend 3Edit connects to: a full Postgres database with logins and access rules, in your own Supabase account. Lesson 8: What is Supabase, and why connect it?
- Postgres
- A widely used, standard database. Supabase is built on it, so your data is kept in a form any developer recognises. Lesson 8: What is Supabase, and why connect it?
- Login
- Signing in to an account, so the app knows who you are and can show you what belongs to you. The accounts are lasting records, kept in a database such as your own Supabase. Lesson 9: User login and accounts
- Role
- A label on an account, such as member or admin, that says what kind of user someone is and what they may do. Lesson 9: User login and accounts
- Access rules (row level security)
- Rules kept next to the data that decide who may read or change each row of a table, so each person sees only what belongs to them. Lesson 9: User login and accounts
- API
- The doorway a service offers to other software. Your app uses APIs to work with services such as payments, email and the database. Lesson 10: Keys, server routes and keeping secrets safe
- API key
- A password your app shows a service’s API, so the service knows which account a request belongs to. Lesson 10: Keys, server routes and keeping secrets safe
- Publishable key
- A key built to be seen, so it may sit in the browser. Supabase’s publishable key only reaches what your access rules allow. Lesson 10: Keys, server routes and keeping secrets safe
- Secret key
- A key that must stay on the server, never in a page, an app you ship or your code on GitHub. Rotate it at once if it ever leaks. Lesson 10: Keys, server routes and keeping secrets safe
- Server route
- A small piece of your backend that runs on the server. The browser asks it to do a job, and it uses secret keys to do it, then sends back only the answer. Lesson 10: Keys, server routes and keeping secrets safe
- Test keys and live keys
- Two sets of keys some services give you. Test keys let you try payments without real money; live keys take real payments. Lesson 10: Keys, server routes and keeping secrets safe
- Webhook
- A message a service sends your app when something happens, such as a payment succeeding. In a 3Edit store, the payment webhook is set up for you when you publish. Read the guide
Saving and publishing
- Version
- A saved snapshot of your project. In 3Edit you can restore an earlier version from Project History, and your current version is saved first. Lesson 11: Versions, backups and GitHub
- GitHub
- A website where code is kept, with a full history of every change. 3Edit can keep your project in a private repository in your own GitHub account, updated each time you save. Lesson 11: Versions, backups and GitHub
- Repository
- A project’s home on GitHub: its code and its whole history. A private repository is one only you, and people you invite, can see. Lesson 11: Versions, backups and GitHub
- Git
- The program developers use to send changes to GitHub. In 3Edit you don’t need it: 3Edit sends your code to GitHub directly. Lesson 11: Versions, backups and GitHub
- Publish
- Copying a finished version of your site to a host, so anyone can visit it. Each time you publish again, the live site updates. Lesson 12: Publish your website: hosting and domains
- Hosting
- Keeping your website on a server that is always on, so anyone can visit it. In 3Edit you publish on 3Edit hosting (3Edit Cloud) or your own Vercel. Lesson 12: Publish your website: hosting and domains
- Vercel
- A hosting company. In 3Edit you can publish to your own Vercel account; Vercel’s own plans and terms apply to it. Lesson 12: Publish your website: hosting and domains
- Domain
- Your website’s address, such as www.yourbusiness.com. You buy it from a domain provider, and it stays there. Lesson 12: Publish your website: hosting and domains
- DNS records
- Small lines of settings at your domain provider that tell the internet where your site lives. 3Edit shows the exact records to add. Lesson 12: Publish your website: hosting and domains
Building bigger
- Next.js
- A widely used framework for websites and web apps that holds the frontend and the backend in one project. Every 3Edit project is standard Next.js code you own. Lesson 22: Own your code: Next.js and handing over to a developer
- Framework
- A ready-made structure for building software, so nobody starts from a blank page. Next.js is one. Lesson 22: Own your code: Next.js and handing over to a developer
- Env file
- The file where a project’s keys live. 3Edit leaves env files out of project downloads and GitHub uploads, so you add your keys again wherever you host the project. Lesson 10: Keys, server routes and keeping secrets safe
- MVP
- Minimum viable product: the smallest version of an idea that real people can use, built to learn whether it is worth growing. Lesson 21: Build a SaaS MVP or internal tool
- SaaS
- Software as a service: an app people use in their browser, usually by signing in and often paying a subscription. Lesson 21: Build a SaaS MVP or internal tool
- Internal tool
- An app built for your own team, such as a booking board, a CRM, a stock list or a dashboard. Lesson 21: Build a SaaS MVP or internal tool
- README
- A short file that explains a project to a person reading its code: what it does, its main parts and how to run it. It is the first page people see in a repository. Lesson 22: Own your code: Next.js and handing over to a developer
- Project notes file
- A short document in your project that describes what the app does, its roles, records, rules and services, so every chat and every engine stays on the same page. Lesson 23: Large projects and good AI habits
Keep learning.
Start vibe coding today.
Download 3Edit for Mac or Windows and build your first professional website in minutes.
Download now
macOSWindows