10 words you’ll hear from the AI — and what they really mean

You start building something with Claude and suddenly you hear: “I’ll make a commit”, “we’ll push this to production”, “add an APIAPI — An agreed way for two programs to talk to each other — one asks, the other answers in a set format. Through an API your app connects to outside services (payments, maps, AI). Treat an API key like a password. key”. Sounds like a foreign language. Relax — it’s just a few words that keep coming back. Once you understand them, talking to the assistant stops being a guessing game.

Here are the ten terms you’ll hear most often at the start. In plain words.

Prompt

A prompt is simply what you write to the AI — your instruction or question. The more clearly you say what you want, the better the answer you’ll get.

It’s like ordering from a waiter: “I’ll have this, but no onion” works better than “something to eat”.

When you’ll hear it: every time the assistant asks you to clarify — it means a clearer prompt, nothing complicated.

Repository (repo)

A repository, or repo for short, is a store of your whole project along with its history — who changed what and when.

Imagine a binder in which every version of a document is labelled and you can return to it.

When you’ll hear it: when the assistant says “in this repo” — it means the folder with your project and all its history.

Commit

A commit is a saved, labelled point in the project’s history — a confirmation of a specific batch of changes. Every commit has a short description of what changed.

It’s like a save point in a game: at any moment you can return to exactly this spot.

When you’ll hear it: when the assistant says “I’ll make a commit” — it’s saving a safe point you can always come back to.

Branch

A branch is a separate working version of the project. You change something on the side, without touching what already works.

It’s like a copy of a document “to think over” — you play with it freely, and the original waits untouched.

When you’ll hear it: when the assistant suggests “let’s do this on a separate branch” — it wants to experiment safely, without risk to the version that works.

Deploy

A deploy is releasing a new version of the app “live” — where real people use it.

It’s like a play’s premiere: rehearsals done, curtain up and the audience is already watching.

When you’ll hear it: it’s the moment your work becomes public — that’s why a deploy usually requires your explicit approval.

Environment (dev / prod)

An environment is the place where the app runs. Dev is for safe testing, prod (production) is the version for real users.

It’s like a test kitchen and a dining room for guests — you experiment in the back, and serve only a proven dish.

When you’ll hear it: when “in production” comes up — it’s about what your customers see, so this is where caution is greatest.

Backup

A backup is a previously saved copy of the data, which you return to when something goes wrong.

It’s like a photo of a shelf before you rearrange the books — if you get it wrong, you put everything back.

When you’ll hear it: before the assistant does something serious, it may say “backup first” — a good sign that it cares about your safety.

Database

A database is an orderly store of your app’s information — customers, orders, texts. Everything arranged so it can be found quickly.

It’s like a large, well-labelled cabinet with drawers: every thing has its place and label.

When you’ll hear it: when “data in the database” comes up — it’s about the real information of your business, not the app’s looks.

API

An API is an agreed way for two programs to talk to each other — one asks for something, the other answers in a set format. For example, your app asks a currency-rates API “what’s today’s euro rate?”, and gets a number back — it doesn’t need to know where the bank gets it from.

It’s like a service window at an office: you file the request the right way and get an answer without going into the back room. (Definition with examples: MDN — API.)

When you’ll hear it: when the assistant asks for an API key — it’s a kind of “entry ticket” to someone else’s service (e.g. payments or maps). Treat it like a password.

Framework

A framework is a ready skeleton with the app’s basic parts. You build your own thing on it, instead of starting from scratch.

It’s like a prefab house in a shell state — the walls and utilities are there, and you fit out the interior your way.

When you’ll hear it: when the assistant says “we’ll use framework X” — it’s choosing the foundation on which it will build your app faster and more reliably.

The full glossary at hand

That was the top ten you’ll hear most often. There are more terms — rollbackRollback — Reverting a change to the previous, working state — “Ctrl+Z” for a deployment. When a new version breaks production, a rollback restores the previous one in seconds instead of fixing in a panic., migrationMigration (database) — A controlled change to the database layout — adding a column, a table or moving data — step by step. Like a renovation to plan: rebuilding data in a set order so nothing “collapses”., cacheCache — A temporarily remembered result, so the same thing isn’t computed again on every request. Speeds the app up, but can be a trap: a stale cache shows old data., GDPRGDPR — The EU’s data-protection law — how you may collect, keep and delete users’ data. It concerns every app with people’s data. Better to write in consents and retention from the start than pay fines later. and a dozen others wait in our full glossary, also explained in plain words and with an analogy.

You don’t have to know them all by heart. It’s enough to know where to look.

In short

• You don’t need to know how to code to understand what your assistant is talking about — a few words that keep recurring are enough.
• Commit and backup are your friends: a saved point and a safety copy mean you can always go back.
• When deploy or production comes up, slow down — it’s the moment your work reaches real people.