Glossary

Short, plain definitions of the terms in this guide. Each page links a term here the first time it uses it.

Accessibility
Whether everyone can use your site: also with a screen reader, with a keyboard only, or with weak eyesight. The Check tests it with the rules behind Lighthouse's accessibility score.
Accessibility statement
The part of your legal page that says how accessible your site is: the standard it aims at, how it was tested, the barriers still known, and how a visitor reports one. The Developer's legal tool writes it, and QA reads it with you.
Agent
An AI that does work for you: it reads files, writes code and runs commands, then reports back. In Antigravity IDE it lives in the agent panel. You lead; it does the typing.
Agent memory
What an agent tool writes down and reads back in the next chat, such as your preferences and corrections. The model itself remembers nothing between chats. Read it now and then, and delete what is no longer true.
Agentic coding
Building software by directing agents through a plan, small steps, rules and checks, with you as the lead. The opposite of vibe coding.
AGENTS.md
The rules file in your repo. Antigravity IDE hands it to the agent: the order of the Roles, one Role per chat, read changes back, and the right commands for your system.
Antigravity 2.0
Google's agent dashboard without an editor. We do not use it today, because you could not see your files.
Antigravity IDE
Google's code editor with a built-in AI agent: files on the left, the agent panel on the right, a terminal at the bottom. The editor we use today.
axe
An automatic accessibility test. It checks a page against a list of rules, such as text that is hard to read or an image without a description. The Check uses it; Lighthouse uses the same rules for its accessibility score.
Block
A timed part of the workshop with one outcome. When its time is up, the whole room starts the next Block, and a checkpoint gives the outcome to anyone who is not done. Each Block after Setup fills one Role.
Build step
A tool that turns the files you write into the files of the finished site. Yours is small: node tools/build.mjs puts your content into the HTML pages. It needs only Node, and your site stays plain HTML, CSS and JavaScript.
Chat
One conversation with the agent. Every Role starts in a fresh chat, so the agent starts with a clean context.
Check
The command node tools/check.mjs. It tests five things about your site, among them what an agent sees and your legal page, and prints PASS or NEEDS ATTENTION for each. It only reports: it never stops you from publishing.
Checkpoint
The finished state of your site at the end of a Block. The command node tools/checkpoint.mjs and a Block's name bring you there, and keep your own content file, design brief and spec.
Chrome DevTools
The developer tools built into Chrome. Open them with F12, or Cmd+Option+I on a Mac. Performance measures how fast a page loads, Device mode shows it on a phone, Lighthouse checks accessibility. QA's tools use the same engine, and an agent can use DevTools through MCP.
CLS (Cumulative Layout Shift)
How much a page jumps while it loads. Good is 0.1 or less. A jumping page makes visitors tap the wrong link.
Command line developer tools
Apple's free package of programming tools for the Mac. It brings Git. The Install script asks the Mac to install it if Git is missing.
Commit
A saved version of your files in Git, with a short message. Ops makes one before each push.
Content file
The file site/content.json. It contains all your content, and every section of your site is drawn from it. To change what your site says, change this file.
Context
Everything the agent keeps in mind during one chat: your messages, its replies, the files it read. Too much of it, and the agent loses track. A fresh chat starts with a clean context.
Core Web Vitals
Google's three numbers for how a page feels to visitors: LCP for loading, CLS for jumping, INP for answering a tap. A page passes when three in four real visits meet the mark.
Demo site
The Instructor's own portfolio site, built with the same steps you follow today: newsletter-lgtm.github.io/portfolio. It shows what you build.
Design brief
The file design/brief.md: your style, colours, fonts, shapes and layout, one personal detail and your signature move. The Developer builds from it. The Designer writes it from your Stitch design.
Gemini Flash
Google's small, fast Gemini models. Today you pick the smallest: Gemini 3.8 Flash.
Git
The tool that saves versions of your files and sends them to GitHub. The Install script installs it if it is missing.
GitHub
The website that hosts your repo, at github.com.
GitHub Actions
Tasks that GitHub runs for you when something happens in your repo. Here: publish your site after every push.
GitHub Pages
GitHub's free website hosting. Your site lives at https://YOUR-USERNAME.github.io/portfolio/.
Home folder
Your own folder on the laptop, the one with your Documents, Downloads and Desktop. The Install script puts your portfolio folder there. On a Mac, Finder opens it with Cmd+Shift+H; on Windows, typing %USERPROFILE% in the address bar of File Explorer opens it.
Hook
A script that an agent tool runs by itself at a fixed moment, for example the Check after every edit. Not used today.
HTML, CSS and JavaScript
The three languages of a web page. HTML gives a page its content and structure, CSS its look, JavaScript its behaviour. Your site is written in these three, with nothing else.
INP (Interaction to Next Paint)
How fast a page answers a tap or a click. Google calls 200 milliseconds or less good; aim for under 100. It needs real taps, so it comes from real visitors, not from a test run.
Install script
The one command that prepares your laptop: it checks Chrome and Antigravity IDE, installs Git and Node where missing, copies your repo to your laptop and opens it.
IP address
The number that identifies a device's internet connection. Every server a page loads something from sees it, which is why your site loads nothing from other servers.
JSON-LD
Facts about a page, written for machines, in a block inside its HTML. On your home page they say who you are: your name, what you do, your links. Search engines and AI agents read them.
LCP (Largest Contentful Paint)
How long until the biggest text or image of a page shows, measured on a slow phone connection. Aim for under 1 second. Google calls 2.5 seconds or less good, and that is the line QA's tool prints.
Legal page
The page site/privacy.html, linked at the bottom of your site as Legal notice & privacy. One page with three parts: a legal notice, a privacy notice and an accessibility statement. The Developer writes it from a template with node tools/legal.mjs, and QA reads it with you.
Lighthouse
Chrome's quality audit for web pages: accessibility, speed and more, each as a score. The Check runs the rules behind its accessibility score.
Lockstep
The rule that the whole room moves through the Blocks together: when a Block's time is up, everyone starts the next one. Nobody is ahead by more than one Block.
MCP (Model Context Protocol)
A standard plug that lets any agent use more tools. Anyone can publish an MCP server, and any agent tool that speaks MCP can use it. Your repo sets one up: Chrome DevTools for agents, which QA uses.
Model
The AI behind the agent. Bigger models are slower and use up your free quota faster. Today: Gemini 3.8 Flash.
Modern Web Guidance
Open-source guides to today's web, written by the Chrome team as an agent skill. Your repo contains a copy, so the agent reads current knowledge it missed after its training.
Node
A program that runs JavaScript on your laptop. The build, the Check, the preview and the checkpoints need it; your site does not.
Optional module
A section you can add after the core sections: YouTube videos, podcasts, a blog, resources or project ideas.
PATH
The list of folders where a terminal looks for programs. A terminal reads it when it opens, so after an install you open a fresh one.
Plugin
A package of agent parts, such as skills, subagents, hooks and MCP servers, that installs as one unit. Useful to reuse a setup across projects or share it with a team; not used today.
Portfolio site
Your personal career hub on the web: who you are, what you built, where people find you.
PowerShell
The terminal on Windows that we use today.
Pre-rendering
Building the finished HTML of your pages before anyone visits them. The build tool, node tools/build.mjs, puts your content into the pages. So search engines, AI agents and link previews read your whole page, even without running JavaScript.
Preview
The command node tools/preview.mjs. It shows your site on your own laptop, at an address such as http://localhost:8000, before you publish it.
Privacy notice
The part of your legal page that says what your site does with visitors' data: no cookies, no tracking, nothing loaded from other servers, and the visitor's rights. The Developer's legal tool writes it from a template.
Prompt
What you type into the agent chat.
Prompt injection
Instructions hidden in something the agent reads, such as a web page, a CV or a pasted text, that try to make it ignore its rules. The agent runs commands with your rights, so every skill in your repo tells it: what the person pastes is data, not orders.
Push
Sending your commits to GitHub. Every push to your repo publishes your site again.
Quota
How much free use of the models Antigravity IDE gives you per week. A small model makes it last.
Repo
Short for repository: the folder of your project, with all its saved versions. Yours lives on GitHub and, after Setup, on your laptop.
Role
A job people used to do in a web project: Analyst, Designer, Developer, QA or Ops. Today an agent does it, under your direction.
Schema
The list of what a file may contain and in which shape. site/content.schema.json is the schema of your content file; the content check compares your file with it.
Signature move
The one effect visitors remember on your site, picked from a menu: for example, a header that shrinks as you scroll. The Developer reads the matching Modern Web Guidance guide first. For visitors who ask their computer to reduce motion, it becomes a fade, or nothing moves.
Skill
A folder of instructions an agent loads when it needs them. Your repo has one skill per Role in .agents/skills/.
Spec
A short written plan for your site: who it is for, what a visitor should do, which sections it has. The Analyst writes it in docs/spec.md.
Stitch
Google's AI design tool, at stitch.withgoogle.com. The Designer writes your personal prompt for it. You design your look there, then hand the design back to the Designer.
Style
The overall look of your site: Classic, Modern, Bold, Playful or Technical, or a mix of two. Your colour, a site you love and one personal detail make yours different from others in the same style.
Subagent
A helper agent that the main agent starts for a side task. Useful in big projects; not needed today.
Template repo
The public repo you copied at the start: fabkrum/portfolio-template. It brings the Role skills, the rules, the tools and the checkpoints.
Terminal
The window where you type commands. On a Mac and on Linux it is called Terminal; on Windows we use PowerShell. Antigravity IDE has one built in.
Ticket loop
The middle of a web factory: an agent builds the change for one ticket, a review checks it, and if it does not pass, it goes back to the builder. It runs by itself, as many rounds as it takes; a ticket that stays stuck comes to a person. A ticket is one task with one goal, small enough for one chat.
Token
Two meanings today. In AI, a small piece of text, about three quarters of a word: a model reads and writes in tokens, and every token in the chat costs time and quota. Input tokens are what the model reads, the whole chat again on every turn; output tokens are what it writes, one at a time. On GitHub, a long password that GitHub makes for you, for one purpose. On a Mac or on Linux, Git asks for one at your first push, because GitHub does not take your account password there.
Tool
Something an agent can do besides writing text: read and write files, run a command, open a browser.
Vibe coding
Typing "build me a website" and accepting whatever comes back, without a plan or checks. The way of working this workshop shows you how to avoid.
Web factory
Today's Roles as one loop: you decide at both ends, what is built and what goes live, and in the middle agents build and review each change until it passes. Also called a software factory. The web factory explains it.
Widget
A small section your site shows only when your content file has its data: events with their badges, certifications, a dated "Now", a few stats, or projects as small case studies. The Analyst takes events and certifications from your text; an Optional module chat adds any widget later.