93 terms · English and Spanish

Glossary

Every term in one or two plain sentences. The same text opens when you tap a dotted word anywhere on the site.

Basics

file archivo: A named piece of content saved on your computer, like a document, an image or a piece of code.
folder carpeta: A container for files and other folders. Each project lives in its own folder.
home folder carpeta personal: Your personal folder on the computer, written ~. On Mac it has your name; on Windows it's C:\Users\<name>.
hidden file archivo oculto: A file whose name starts with a dot, like .env.local. Your computer hides it by default (Mac: Cmd + Shift + . in Finder; Windows: View → Show → Hidden items).
path ruta (path): The address of a file or folder on your computer, showing the folders you open to reach it, separated by slashes.
terminal terminal: A window where you type commands instead of clicking. Your agent mostly uses it for you.
command comando: An instruction typed in the terminal, such as git --version. Your agent explains each one before running it.

Git and GitHub

repo (repository) repositorio (repo): Your project folder plus its full history. Git records each checkpoint so you can go back to any version.
Git Git: The tool that keeps your repo's memory: it records every commit on your computer.
commit commit: A checkpoint: a snapshot of what changed, with a short note. You can return to any commit.
branch rama: A safe copy of your project where changes are drafted. main is the live one.
main main: The main branch. Whatever is in main is what your live site shows.
merge fusionar (merge): Bringing the changes from one branch into another, usually into main once approved.
pull request pull request: A proposal to merge a branch, shown on GitHub with its changes and checks, so you can review it first.
push push (subir): Sending your commits from your computer up to GitHub.
pull pull (traer): Bringing changes down from GitHub to your computer.
clone clonar (clone): Copying a repo from GitHub onto a computer for the first time, with its full history.
remote remoto: The twin of your repo that lives on GitHub. The local one lives on your computer.
.gitignore .gitignore: A file listing what Git must never save, like node_modules and your .env secret files.

The web

frontend frontend: The part of an app that runs in the visitor's browser: what people see and click.
backend backend: The part of an app that runs on a server: it keeps data, checks logins and talks to other services.
browser navegador: The program people use to open websites, such as Safari, Chrome, Edge or Firefox.
server servidor: A computer connected to the internet that runs your backend and sends pages or data when a browser asks for them.
URL URL: The full web address of a page or endpoint, such as https://my-first-app.vercel.app/recipes.
HTTPS HTTPS: The secure version of a web connection: it scrambles data between the browser and the server so nobody in between can read it.
domain dominio: A web address people can type, like agenticmakers.app.
localhost localhost: Your own computer acting as a server while you test, usually at http://localhost:3000.
port puerto: A numbered door on a computer that an app listens on, like 3000. Only one app can use a port at a time.
API API: The agreed way two programs talk to each other, like your app asking an AI provider for an answer.
endpoint endpoint: A specific address in an API or backend that performs one job, such as saving a form or answering a request.
JSON JSON: A clean text format with curly braces and key–value pairs that programs use to exchange data and store structured logs.

Building

framework framework: A ready-made foundation for building apps. Agentic Makers uses Next.js.
Next.js Next.js: The web framework used in this guide: it combines your React screens (frontend) and server logic (backend) in one project.
React React: The library Next.js uses to build screens out of reusable pieces called components, such as buttons, cards and forms.
component componente: A self-contained, reusable piece of your app's interface, like a navigation bar, a recipe card or a submit button.
package (dependency) paquete (dependencia): Ready-made code your app uses. npm installs packages into the node_modules folder.
npm npm: The package manager that comes with Node.js: it installs packages and runs your project's scripts like npm run dev.
npx npx: A companion tool to npm that runs a command-line package directly without permanently installing it on your computer.
Node.js Node.js: The program that lets your computer run JavaScript and TypeScript outside a browser, powering Next.js and your development tools.
TypeScript TypeScript: JavaScript with labels stating what kind of data each piece expects (text, number, list), so mistakes are caught before the app runs.
lint lint: An automatic check that scans your code for common slip-ups, accessibility issues and style mistakes before you publish.
type check comprobación de tipos: Running TypeScript across the whole project to verify that every function, component and database call receives the data shape it expects.
test test: A small program that checks your app does what it should, so a fix can't silently break later.

Data

database base de datos: Where your app remembers things between visits, like accounts or saved recipes.
Postgres Postgres: PostgreSQL: the trusted, open-source relational database engine that organises your app's data into tables with rows and columns.
Neon Neon: The cloud service in the default stack that hosts your Postgres database, connects to Vercel and supports isolated database branches.
table tabla: A single collection inside a database, shaped like a spreadsheet with columns for fields and one row per item.
query consulta (query): A question or instruction your backend sends to the database, such as fetching a user's saved items or inserting a new row.
migration migración: A tracked step file that creates or updates tables and columns in your database so its structure stays in sync with your code.
database branch rama de base de datos: An isolated copy of your database created by Neon for local development or a Preview deployment, so tests never touch real user data.

Accounts and security

authentication autenticación: Verifying who a user is when they sign up or sign in, handled in the default stack by Better Auth.
session sesión: The signed-in state stored in a secure browser cookie so your app remembers who is logged in as they move from page to page.
secret secreto: Anything that opens your accounts: API keys, passwords, tokens. Kept only in Vercel and .env.local.
API key clave de API: A password your app uses with another service. Whoever has it can spend your money.
environment variable variable de entorno: A named slot, like TOKENTIDE_API_KEY, that holds a setting or secret outside your code.
.env.local .env.local: The hidden file in your project folder that holds environment variables on your computer for local development, ignored by Git.
rate limit límite de uso: A cap on how often something can be done, like sign-in attempts per minute, to stop abuse.
CSRF CSRF: Cross-Site Request Forgery: a trick where another website tries to make your browser send a request to your app using your open session.
CSP (Content Security Policy) CSP (política de seguridad de contenidos): A security header your server sends to the browser listing exactly which sources of scripts, images and styles are allowed to run on your page.

AI

model modelo: The AI system that produces answers, like the one behind your coding agent.
prompt prompt: The message you give an AI model. Clear prompts get better results.
token token: A small chunk of text—roughly three-quarters of a word—that AI providers use to measure and price the prompt you send and the answer you get back.
provider proveedor: A service that runs AI models and answers your backend's API requests, such as Tokentide or Vercel AI Gateway.
fallback respaldo (fallback): A backup that answers when the main provider can't, so your app keeps working.
hallucination alucinación: When an AI states something false with confidence. It's why you check its work.
deterministic determinista: Regular code that follows exact rules: given the same input, it produces the exact same output every single time.
probabilistic probabilístico: How AI models work: they predict likely next words, so the same prompt can produce slightly different answers and occasional mistakes.

Publishing

deploy publicar (desplegar): Putting a version of your app online.
build build (compilación): The step where Next.js checks your code and packages your pages and components into a fast, ready-to-serve bundle before putting it online.
Vercel Vercel: The service that turns your code on GitHub into a live site, with a Preview for every change.
Preview vista previa (Preview): A private test link Vercel makes for each change, so you can try it before it goes live.
Production producción (Production): The live version of your app, the one everyone sees. It comes from main.
environment entorno: Where a version of your app is running: Development (on your computer), Preview (a test link on Vercel) or Production (the live site).
rollback volver a una versión anterior: Putting the previous working version back online in one click, while the problem gets fixed.

Errors

bug error (bug): A mistake in the code that makes the app behave wrongly.
error message mensaje de error: What a program says when something fails. Its first line usually says what; the rest says where.
stack trace traza de error (stack trace): The list of steps that led to an error. Useful for your agent; never shown to your users.
log log (registro): Your app's diary: one line per event. When something breaks, the logs say what happened.
console consola: The place in the browser where your app's messages and errors appear.
debugging depuración: Finding and fixing the root cause of a bug: reproduce, find, fix, prove.
error boundary límite de error (error boundary): A safety net in your app that catches unexpected errors and shows a friendly message with “Try again”.
reference id código de referencia: A short code shown in a friendly error message and written to the server log, so your agent can find the exact log entry without exposing details to the user.
monitoring supervisión: Keeping watch over your live app with tools like Sentry and structured logs so you know if real users hit an error.
alert alerta: An automatic notification—such as an email from Sentry or a billing warning from Tokentide—sent when something needs your attention.

Method

coding agent agente de programación: An AI that works in your project folder: it reads files, writes code and runs commands, with your permission.
global instructions instrucciones globales: A text file your agent reads at the start of every session, in every project. The Agentic Makers Guide is one.
skill skill: An expert playbook your agent follows for a kind of task, like writing a spec or debugging.
spec especificación: SPEC.md: what you're building, who it's for, what's in and out, and how you'll know it works.
plan plan: The spec split into small tasks, each finished and checkable on its own, in tasks/plan.md.
task tarea: One small, self-contained item in your plan and tasks/todo.md checklist that can be built on its own branch, checked in the browser and ticked off.
spec-driven development (SDD) desarrollo guiado por especificaciones (SDD): Agree on what to build (the spec) and a plan, then build one small, checked step at a time.
agentic engineering ingeniería agéntica: Building software by directing AI agents and checking their work: you lead, the agent builds.
quick experiment experimento rápido: A throwaway try-out without a spec. Fine for testing an idea, never for something you'll publish.

Was this page helpful?

Last reviewed Nov 8, 2026