Course glossary
Codex Glossary
200+ beginner-friendly definitions for Codex, coding, GitHub, Vercel, WordPress, web development, safety, and expert agent workflows.
Codex
Plain-English definition: OpenAI’s coding agent for software development.
Why it matters: It is the main tool learners are steering throughout the course.
Beginner example: Ask Codex to inspect a project and explain what it can safely help with before editing.
Related module: Module 00 – Course Orientation and Setup
coding agent
Plain-English definition: An AI system that can reason about software tasks and use tools such as file reading, editing, terminal commands, and browser checks.
Why it matters: It can act inside a project, so clear constraints and review matter.
Beginner example: Tell the coding agent: inspect first, propose a plan, and wait before destructive actions.
Related module: Module 01 – What Codex Is and Why It Matters
repo
Plain-English definition: A project folder tracked by Git, usually containing code, configuration, docs, tests, and history.
Why it matters: Codex needs repo context to make changes that fit the existing project.
Beginner example: Ask Codex to summarize the repo before asking it to build a feature.
Related module: Module 02 – Absolute Beginner Coding Concepts
repository
Plain-English definition: repository is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding repository helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "repository", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 03 – Developer Environment Setup
file tree
Plain-English definition: The folder and file map of a project.
Why it matters: It helps beginners understand where pages, styles, components, tests, and config live.
Beginner example: Ask Codex: show me the likely files involved in this button behavior.
Related module: Module 04 – Git and GitHub for Codex Users
terminal
Plain-English definition: A text interface for running commands on your computer.
Why it matters: Commands can start projects, run tests, install packages, or change files.
Beginner example: Run a harmless command like `pwd` before trying install or deploy commands.
Related module: Module 05 – How to Think Like a Builder
CLI
Plain-English definition: Command-line interface, a tool used from the terminal.
Why it matters: The Codex CLI is useful for local repo work and scripted workflows.
Beginner example: Use CLI commands in a test project before using them on production code.
Related module: Module 06 – Codex Prompting Foundations
IDE
Plain-English definition: An integrated development environment such as VS Code.
Why it matters: The IDE can provide Codex with editor context like open files and selected code.
Beginner example: Open the relevant file before asking for an explanation.
Related module: Module 07 – The /goal Method
VS Code
Plain-English definition: VS Code is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding VS Code helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "VS Code", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 08 – Codex for Reading and Understanding Codebases
branch
Plain-English definition: A separate line of Git work.
Why it matters: Branches let Codex experiments stay isolated from production-ready code.
Beginner example: Create a feature branch before asking for a site change.
Related module: Module 09 – Codex for Editing Existing Websites
commit
Plain-English definition: A saved snapshot of changes in Git.
Why it matters: Good commits make review and rollback easier.
Beginner example: Commit after tests pass and the diff is understood.
Related module: Module 10 – Codex for Building Landing Pages and WordPress Assets
pull request
Plain-English definition: A GitHub review page for proposing changes before merge.
Why it matters: PRs create a safe review loop for Codex-generated work.
Beginner example: Ask Codex to draft a PR description with tests and risk notes.
Related module: Module 11 – Codex for Building Web Apps
merge
Plain-English definition: merge is a version control term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding merge helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "merge", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 12 – Codex for JavaScript, TypeScript, React, and Next.js
merge conflict
Plain-English definition: merge conflict is a version control term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding merge conflict helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "merge conflict", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 13 – Codex for Debugging and Fixing Bugs
diff
Plain-English definition: diff is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding diff helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "diff", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 14 – Codex for Testing, QA, and Refactoring
staging
Plain-English definition: staging is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding staging helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "staging", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 15 – Codex for GitHub Issues, Branches, Pull Requests, and Reviews
production
Plain-English definition: production is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding production helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "production", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 16 – Codex for Deployments, Vercel, Hosting, and Rollbacks
deployment
Plain-English definition: The process of making a project available outside your local computer.
Why it matters: Deployment affects real users, so testing and rollback matter.
Beginner example: Use a preview deployment before production.
Related module: Module 17 – Codex for Data Projects, Reports, Dashboards, and Automation
rollback
Plain-English definition: A planned way to undo or revert a change.
Why it matters: It protects the site if a release breaks something.
Beginner example: Keep the previous version or revert command documented.
Related module: Module 18 – Codex for APIs, Integrations, and Environment Variables
build
Plain-English definition: build is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding build helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "build", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 19 – Codex for WordPress, SEO Tools, Calculators, and Interactive Pages
dependency
Plain-English definition: dependency is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding dependency helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "dependency", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 20 – Advanced Codex CLI, Config, Models, and Local Workflows
package manager
Plain-English definition: package manager is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding package manager helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "package manager", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 21 – Codex Cloud/Web, Parallel Tasks, and Long-Running Work
npm
Plain-English definition: npm is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding npm helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "npm", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 22 – Skills, MCP, Subagents, and Expert Agent Workflows
Node.js
Plain-English definition: Node.js is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding Node.js helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "Node.js", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 23 – Security, Privacy, Secrets, Safe Automation, and Production Readiness
React
Plain-English definition: React is a frontend implementation term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding React helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "React", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 24 – Expert Capstones, Portfolio Projects, and Certification
Next.js
Plain-English definition: Next.js is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding Next.js helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "Next.js", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 00 – Course Orientation and Setup
HTML
Plain-English definition: HTML is a frontend implementation term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding HTML helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "HTML", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 01 – What Codex Is and Why It Matters
CSS
Plain-English definition: CSS is a frontend implementation term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding CSS helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "CSS", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 02 – Absolute Beginner Coding Concepts
JavaScript
Plain-English definition: JavaScript is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding JavaScript helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "JavaScript", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 03 – Developer Environment Setup
TypeScript
Plain-English definition: TypeScript is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding TypeScript helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "TypeScript", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 04 – Git and GitHub for Codex Users
API
Plain-English definition: API is a integration security term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding API helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "API", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 05 – How to Think Like a Builder
endpoint
Plain-English definition: endpoint is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding endpoint helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "endpoint", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 06 – Codex Prompting Foundations
request
Plain-English definition: request is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding request helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "request", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 07 – The /goal Method
response
Plain-English definition: response is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding response helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "response", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 08 – Codex for Reading and Understanding Codebases
environment variable
Plain-English definition: A named value provided outside the code, often used for settings and credentials.
Why it matters: It keeps secrets and environment-specific settings out of source files.
Beginner example: Use `API_URL` or `OPENAI_API_KEY` references without pasting real values.
Related module: Module 09 – Codex for Editing Existing Websites
secret
Plain-English definition: A sensitive value such as an API key, token, cookie, or password.
Why it matters: Secrets must not be pasted into prompts, screenshots, logs, or commits.
Beginner example: If a secret appears in a file, stop and rotate it before continuing.
Related module: Module 10 – Codex for Building Landing Pages and WordPress Assets
.env
Plain-English definition: A local file commonly used to store environment variables.
Why it matters: It often contains secrets and should usually be ignored by Git.
Beginner example: Use `.env.example` for placeholder names and `.env` for local values.
Related module: Module 11 – Codex for Building Web Apps
.gitignore
Plain-English definition: A Git file that tells Git which files not to track.
Why it matters: It helps prevent secrets, build output, and local clutter from being committed.
Beginner example: Add `.env` and generated folders when appropriate.
Related module: Module 12 – Codex for JavaScript, TypeScript, React, and Next.js
Vercel
Plain-English definition: A hosting and deployment platform commonly used for frontend and full-stack web apps.
Why it matters: It provides previews, production deployments, logs, domains, and environment variables.
Beginner example: Connect GitHub and inspect the preview before promoting changes.
Related module: Module 13 – Codex for Debugging and Fixing Bugs
WordPress
Plain-English definition: A popular content management system for publishing websites.
Why it matters: Kingy AI uses WordPress, so course assets must be safe for Custom HTML workflows.
Beginner example: Paste scoped HTML/CSS into a draft page and preview before publishing.
Related module: Module 14 – Codex for Testing, QA, and Refactoring
Custom HTML block
Plain-English definition: A WordPress editor block that lets you paste HTML, CSS, and sometimes JavaScript.
Why it matters: It is useful for course pages and tools without a paid LMS plugin.
Beginner example: Wrap everything in `.kingy-codex-course` to avoid theme conflicts.
Related module: Module 15 – Codex for GitHub Issues, Branches, Pull Requests, and Reviews
schema
Plain-English definition: schema is a publishing and search visibility term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding schema helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "schema", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 16 – Codex for Deployments, Vercel, Hosting, and Rollbacks
BreadcrumbList
Plain-English definition: A schema.org structure that represents breadcrumb navigation.
Why it matters: SEO plugins may already output it, so duplicating it can create invalid schema.
Beginner example: Check Yoast output before adding any breadcrumb JSON-LD.
Related module: Module 17 – Codex for Data Projects, Reports, Dashboards, and Automation
localStorage
Plain-English definition: A browser storage feature that saves small values on one device.
Why it matters: It can store progress without user accounts, but it is not synced across devices.
Beginner example: Use it for course checkboxes, not sensitive data.
Related module: Module 18 – Codex for APIs, Integrations, and Environment Variables
accessibility
Plain-English definition: accessibility is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding accessibility helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "accessibility", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 19 – Codex for WordPress, SEO Tools, Calculators, and Interactive Pages
responsive design
Plain-English definition: responsive design is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding responsive design helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "responsive design", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 20 – Advanced Codex CLI, Config, Models, and Local Workflows
test
Plain-English definition: test is a verification term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding test helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "test", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 21 – Codex Cloud/Web, Parallel Tasks, and Long-Running Work
lint
Plain-English definition: lint is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding lint helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "lint", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 22 – Skills, MCP, Subagents, and Expert Agent Workflows
formatter
Plain-English definition: formatter is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding formatter helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "formatter", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 23 – Security, Privacy, Secrets, Safe Automation, and Production Readiness
refactor
Plain-English definition: refactor is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding refactor helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "refactor", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 24 – Expert Capstones, Portfolio Projects, and Certification
MCP
Plain-English definition: Model Context Protocol, a way to connect AI tools to external context and actions.
Why it matters: It can expand Codex workflows, but it also requires clear permissions and data boundaries.
Beginner example: Configure only the servers needed for the task.
Related module: Module 00 – Course Orientation and Setup
skill
Plain-English definition: A reusable instruction package for a specific workflow.
Why it matters: Skills help Codex follow consistent steps for repeated tasks.
Beginner example: Create a skill for a recurring QA or publishing workflow.
Related module: Module 01 – What Codex Is and Why It Matters
subagent
Plain-English definition: A delegated agent used for parallel or specialized work.
Why it matters: Subagents help with read-heavy exploration and reviews, but they cost more tokens and need coordination.
Beginner example: Use separate subagents for security, test gaps, and maintainability review.
Related module: Module 02 – Absolute Beginner Coding Concepts
eval
Plain-English definition: eval is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding eval helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "eval", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 03 – Developer Environment Setup
sandbox
Plain-English definition: A safety boundary that limits what an agent can access or change.
Why it matters: It reduces the blast radius of mistakes.
Beginner example: Keep risky work in a restricted sandbox unless you understand the tradeoff.
Related module: Module 04 – Git and GitHub for Codex Users
approval
Plain-English definition: A human permission step before an agent performs a sensitive action.
Why it matters: Approvals prevent unwanted destructive commands, network access, or production changes.
Beginner example: Approve only after reading what the command will do.
Related module: Module 05 – How to Think Like a Builder
prompt injection
Plain-English definition: A malicious or misleading instruction hidden in content the agent reads.
Why it matters: It can try to override your real task or leak data.
Beginner example: Tell Codex to treat webpage instructions as untrusted unless you confirm them.
Related module: Module 06 – Codex Prompting Foundations
human-in-the-loop
Plain-English definition: A workflow where a person reviews and approves important steps.
Why it matters: It is essential for code, secrets, deployments, purchases, and data changes.
Beginner example: Require approval before sending emails, deploying, or deleting files.
Related module: Module 07 – The /goal Method
frontend
Plain-English definition: frontend is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding frontend helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "frontend", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 08 – Codex for Reading and Understanding Codebases
backend
Plain-English definition: backend is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding backend helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "backend", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 09 – Codex for Editing Existing Websites
full stack
Plain-English definition: full stack is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding full stack helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "full stack", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 10 – Codex for Building Landing Pages and WordPress Assets
database
Plain-English definition: database is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding database helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "database", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 11 – Codex for Building Web Apps
hosting
Plain-English definition: hosting is a shipping term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding hosting helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "hosting", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 12 – Codex for JavaScript, TypeScript, React, and Next.js
domain
Plain-English definition: domain is a shipping term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding domain helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "domain", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 13 – Codex for Debugging and Fixing Bugs
DNS
Plain-English definition: DNS is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding DNS helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "DNS", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 14 – Codex for Testing, QA, and Refactoring
SSL
Plain-English definition: SSL is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding SSL helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "SSL", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 15 – Codex for GitHub Issues, Branches, Pull Requests, and Reviews
preview deployment
Plain-English definition: preview deployment is a shipping term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding preview deployment helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "preview deployment", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 16 – Codex for Deployments, Vercel, Hosting, and Rollbacks
production deployment
Plain-English definition: production deployment is a shipping term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding production deployment helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "production deployment", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 17 – Codex for Data Projects, Reports, Dashboards, and Automation
logs
Plain-English definition: logs is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding logs helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "logs", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 18 – Codex for APIs, Integrations, and Environment Variables
build logs
Plain-English definition: build logs is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding build logs helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "build logs", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 19 – Codex for WordPress, SEO Tools, Calculators, and Interactive Pages
runtime logs
Plain-English definition: runtime logs is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding runtime logs helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "runtime logs", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 20 – Advanced Codex CLI, Config, Models, and Local Workflows
CI
Plain-English definition: CI is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding CI helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "CI", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 21 – Codex Cloud/Web, Parallel Tasks, and Long-Running Work
GitHub Actions
Plain-English definition: GitHub Actions is a version control term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding GitHub Actions helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "GitHub Actions", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 22 – Skills, MCP, Subagents, and Expert Agent Workflows
issue
Plain-English definition: issue is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding issue helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "issue", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 23 – Security, Privacy, Secrets, Safe Automation, and Production Readiness
milestone
Plain-English definition: milestone is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding milestone helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "milestone", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 24 – Expert Capstones, Portfolio Projects, and Certification
label
Plain-English definition: label is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding label helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "label", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 00 – Course Orientation and Setup
review
Plain-English definition: review is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding review helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "review", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 01 – What Codex Is and Why It Matters
code review
Plain-English definition: code review is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding code review helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "code review", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 02 – Absolute Beginner Coding Concepts
review thread
Plain-English definition: review thread is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding review thread helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "review thread", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 03 – Developer Environment Setup
checkout
Plain-English definition: checkout is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding checkout helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "checkout", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 04 – Git and GitHub for Codex Users
clone
Plain-English definition: clone is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding clone helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "clone", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 05 – How to Think Like a Builder
fork
Plain-English definition: fork is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding fork helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "fork", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 06 – Codex Prompting Foundations
remote
Plain-English definition: remote is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding remote helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "remote", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 07 – The /goal Method
origin
Plain-English definition: origin is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding origin helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "origin", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 08 – Codex for Reading and Understanding Codebases
main branch
Plain-English definition: main branch is a version control term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding main branch helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "main branch", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 09 – Codex for Editing Existing Websites
feature branch
Plain-English definition: feature branch is a version control term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding feature branch helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "feature branch", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 10 – Codex for Building Landing Pages and WordPress Assets
release branch
Plain-English definition: release branch is a version control term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding release branch helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "release branch", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 11 – Codex for Building Web Apps
hotfix
Plain-English definition: hotfix is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding hotfix helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "hotfix", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 12 – Codex for JavaScript, TypeScript, React, and Next.js
revert
Plain-English definition: revert is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding revert helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "revert", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 13 – Codex for Debugging and Fixing Bugs
reset
Plain-English definition: reset is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding reset helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "reset", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 14 – Codex for Testing, QA, and Refactoring
stash
Plain-English definition: stash is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding stash helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "stash", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 15 – Codex for GitHub Issues, Branches, Pull Requests, and Reviews
cherry-pick
Plain-English definition: cherry-pick is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding cherry-pick helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "cherry-pick", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 16 – Codex for Deployments, Vercel, Hosting, and Rollbacks
tag
Plain-English definition: tag is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding tag helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "tag", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 17 – Codex for Data Projects, Reports, Dashboards, and Automation
version control
Plain-English definition: version control is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding version control helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "version control", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 18 – Codex for APIs, Integrations, and Environment Variables
semantic HTML
Plain-English definition: semantic HTML is a frontend implementation term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding semantic HTML helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "semantic HTML", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 19 – Codex for WordPress, SEO Tools, Calculators, and Interactive Pages
ARIA
Plain-English definition: ARIA is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding ARIA helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "ARIA", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 20 – Advanced Codex CLI, Config, Models, and Local Workflows
keyboard navigation
Plain-English definition: keyboard navigation is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding keyboard navigation helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "keyboard navigation", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 21 – Codex Cloud/Web, Parallel Tasks, and Long-Running Work
contrast
Plain-English definition: contrast is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding contrast helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "contrast", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 22 – Skills, MCP, Subagents, and Expert Agent Workflows
heading hierarchy
Plain-English definition: heading hierarchy is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding heading hierarchy helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "heading hierarchy", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 23 – Security, Privacy, Secrets, Safe Automation, and Production Readiness
metadata
Plain-English definition: metadata is a publishing and search visibility term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding metadata helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "metadata", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 24 – Expert Capstones, Portfolio Projects, and Certification
meta description
Plain-English definition: meta description is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding meta description helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "meta description", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 00 – Course Orientation and Setup
SEO title
Plain-English definition: SEO title is a publishing and search visibility term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding SEO title helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "SEO title", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 01 – What Codex Is and Why It Matters
canonical URL
Plain-English definition: canonical URL is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding canonical URL helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "canonical URL", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 02 – Absolute Beginner Coding Concepts
slug
Plain-English definition: slug is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding slug helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "slug", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 03 – Developer Environment Setup
internal link
Plain-English definition: internal link is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding internal link helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "internal link", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 04 – Git and GitHub for Codex Users
external link
Plain-English definition: external link is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding external link helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "external link", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 05 – How to Think Like a Builder
CTA
Plain-English definition: CTA is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding CTA helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "CTA", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 06 – Codex Prompting Foundations
landing page
Plain-English definition: landing page is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding landing page helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "landing page", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 07 – The /goal Method
calculator
Plain-English definition: calculator is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding calculator helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "calculator", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 08 – Codex for Reading and Understanding Codebases
dashboard
Plain-English definition: dashboard is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding dashboard helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "dashboard", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 09 – Codex for Editing Existing Websites
form
Plain-English definition: form is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding form helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "form", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 10 – Codex for Building Landing Pages and WordPress Assets
state
Plain-English definition: state is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding state helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "state", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 11 – Codex for Building Web Apps
event handler
Plain-English definition: event handler is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding event handler helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "event handler", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 12 – Codex for JavaScript, TypeScript, React, and Next.js
component
Plain-English definition: component is a frontend implementation term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding component helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "component", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 13 – Codex for Debugging and Fixing Bugs
prop
Plain-English definition: prop is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding prop helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "prop", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 14 – Codex for Testing, QA, and Refactoring
hook
Plain-English definition: hook is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding hook helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "hook", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 15 – Codex for GitHub Issues, Branches, Pull Requests, and Reviews
server component
Plain-English definition: server component is a frontend implementation term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding server component helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "server component", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 16 – Codex for Deployments, Vercel, Hosting, and Rollbacks
client component
Plain-English definition: client component is a frontend implementation term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding client component helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "client component", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 17 – Codex for Data Projects, Reports, Dashboards, and Automation
route
Plain-English definition: route is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding route helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "route", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 18 – Codex for APIs, Integrations, and Environment Variables
middleware
Plain-English definition: middleware is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding middleware helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "middleware", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 19 – Codex for WordPress, SEO Tools, Calculators, and Interactive Pages
server action
Plain-English definition: server action is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding server action helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "server action", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 20 – Advanced Codex CLI, Config, Models, and Local Workflows
SSR
Plain-English definition: SSR is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding SSR helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "SSR", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 21 – Codex Cloud/Web, Parallel Tasks, and Long-Running Work
SSG
Plain-English definition: SSG is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding SSG helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "SSG", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 22 – Skills, MCP, Subagents, and Expert Agent Workflows
hydration
Plain-English definition: hydration is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding hydration helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "hydration", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 23 – Security, Privacy, Secrets, Safe Automation, and Production Readiness
bundle
Plain-English definition: bundle is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding bundle helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "bundle", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 24 – Expert Capstones, Portfolio Projects, and Certification
cache
Plain-English definition: cache is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding cache helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "cache", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 00 – Course Orientation and Setup
CDN
Plain-English definition: CDN is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding CDN helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "CDN", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 01 – What Codex Is and Why It Matters
performance budget
Plain-English definition: performance budget is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding performance budget helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "performance budget", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 02 – Absolute Beginner Coding Concepts
Core Web Vitals
Plain-English definition: Core Web Vitals is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding Core Web Vitals helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "Core Web Vitals", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 03 – Developer Environment Setup
LCP
Plain-English definition: LCP is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding LCP helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "LCP", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 04 – Git and GitHub for Codex Users
CLS
Plain-English definition: CLS is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding CLS helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "CLS", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 05 – How to Think Like a Builder
INP
Plain-English definition: INP is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding INP helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "INP", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 06 – Codex Prompting Foundations
mobile-first
Plain-English definition: mobile-first is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding mobile-first helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "mobile-first", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 07 – The /goal Method
viewport
Plain-English definition: viewport is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding viewport helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "viewport", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 08 – Codex for Reading and Understanding Codebases
breakpoint
Plain-English definition: breakpoint is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding breakpoint helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "breakpoint", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 09 – Codex for Editing Existing Websites
grid
Plain-English definition: grid is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding grid helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "grid", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 10 – Codex for Building Landing Pages and WordPress Assets
flexbox
Plain-English definition: flexbox is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding flexbox helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "flexbox", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 11 – Codex for Building Web Apps
selector
Plain-English definition: selector is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding selector helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "selector", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 12 – Codex for JavaScript, TypeScript, React, and Next.js
specificity
Plain-English definition: specificity is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding specificity helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "specificity", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 13 – Codex for Debugging and Fixing Bugs
class
Plain-English definition: class is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding class helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "class", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 14 – Codex for Testing, QA, and Refactoring
ID
Plain-English definition: ID is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding ID helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "ID", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 15 – Codex for GitHub Issues, Branches, Pull Requests, and Reviews
parent class
Plain-English definition: parent class is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding parent class helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "parent class", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 16 – Codex for Deployments, Vercel, Hosting, and Rollbacks
scope
Plain-English definition: scope is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding scope helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "scope", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 17 – Codex for Data Projects, Reports, Dashboards, and Automation
CSS leakage
Plain-English definition: CSS leakage is a frontend implementation term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding CSS leakage helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "CSS leakage", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 18 – Codex for APIs, Integrations, and Environment Variables
JavaScript error
Plain-English definition: JavaScript error is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding JavaScript error helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "JavaScript error", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 19 – Codex for WordPress, SEO Tools, Calculators, and Interactive Pages
console
Plain-English definition: console is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding console helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "console", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 20 – Advanced Codex CLI, Config, Models, and Local Workflows
network tab
Plain-English definition: network tab is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding network tab helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "network tab", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 21 – Codex Cloud/Web, Parallel Tasks, and Long-Running Work
status code
Plain-English definition: status code is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding status code helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "status code", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 22 – Skills, MCP, Subagents, and Expert Agent Workflows
404
Plain-English definition: 404 is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding 404 helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "404", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 23 – Security, Privacy, Secrets, Safe Automation, and Production Readiness
500
Plain-English definition: 500 is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding 500 helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "500", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 24 – Expert Capstones, Portfolio Projects, and Certification
authentication
Plain-English definition: authentication is a integration security term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding authentication helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "authentication", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 00 – Course Orientation and Setup
authorization
Plain-English definition: authorization is a integration security term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding authorization helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "authorization", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 01 – What Codex Is and Why It Matters
OAuth
Plain-English definition: OAuth is a integration security term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding OAuth helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "OAuth", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 02 – Absolute Beginner Coding Concepts
token
Plain-English definition: token is a integration security term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding token helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "token", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 03 – Developer Environment Setup
API key
Plain-English definition: API key is a integration security term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding API key helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "API key", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 04 – Git and GitHub for Codex Users
rate limit
Plain-English definition: rate limit is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding rate limit helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "rate limit", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 05 – How to Think Like a Builder
least privilege
Plain-English definition: least privilege is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding least privilege helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "least privilege", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 06 – Codex Prompting Foundations
supply chain
Plain-English definition: supply chain is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding supply chain helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "supply chain", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 07 – The /goal Method
dependency audit
Plain-English definition: dependency audit is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding dependency audit helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "dependency audit", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 08 – Codex for Reading and Understanding Codebases
package lock
Plain-English definition: package lock is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding package lock helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "package lock", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 09 – Codex for Editing Existing Websites
lockfile
Plain-English definition: lockfile is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding lockfile helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "lockfile", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 10 – Codex for Building Landing Pages and WordPress Assets
README
Plain-English definition: README is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding README helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "README", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 11 – Codex for Building Web Apps
AGENTS.md
Plain-English definition: AGENTS.md is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding AGENTS.md helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "AGENTS.md", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 12 – Codex for JavaScript, TypeScript, React, and Next.js
config.toml
Plain-English definition: config.toml is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding config.toml helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "config.toml", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 13 – Codex for Debugging and Fixing Bugs
model
Plain-English definition: model is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding model helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "model", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 14 – Codex for Testing, QA, and Refactoring
reasoning effort
Plain-English definition: reasoning effort is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding reasoning effort helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "reasoning effort", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 15 – Codex for GitHub Issues, Branches, Pull Requests, and Reviews
context window
Plain-English definition: context window is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding context window helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "context window", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 16 – Codex for Deployments, Vercel, Hosting, and Rollbacks
compaction
Plain-English definition: compaction is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding compaction helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "compaction", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 17 – Codex for Data Projects, Reports, Dashboards, and Automation
thread
Plain-English definition: thread is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding thread helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "thread", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 18 – Codex for APIs, Integrations, and Environment Variables
local thread
Plain-English definition: local thread is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding local thread helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "local thread", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 19 – Codex for WordPress, SEO Tools, Calculators, and Interactive Pages
cloud thread
Plain-English definition: cloud thread is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding cloud thread helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "cloud thread", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 20 – Advanced Codex CLI, Config, Models, and Local Workflows
worktree
Plain-English definition: worktree is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding worktree helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "worktree", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 21 – Codex Cloud/Web, Parallel Tasks, and Long-Running Work
patch
Plain-English definition: patch is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding patch helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "patch", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 22 – Skills, MCP, Subagents, and Expert Agent Workflows
apply patch
Plain-English definition: apply patch is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding apply patch helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "apply patch", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 23 – Security, Privacy, Secrets, Safe Automation, and Production Readiness
permission
Plain-English definition: permission is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding permission helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "permission", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 24 – Expert Capstones, Portfolio Projects, and Certification
destructive command
Plain-English definition: destructive command is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding destructive command helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "destructive command", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 00 – Course Orientation and Setup
dry run
Plain-English definition: dry run is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding dry run helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "dry run", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 01 – What Codex Is and Why It Matters
backup
Plain-English definition: backup is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding backup helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "backup", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 02 – Absolute Beginner Coding Concepts
staging site
Plain-English definition: staging site is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding staging site helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "staging site", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 03 – Developer Environment Setup
plugin
Plain-English definition: plugin is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding plugin helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "plugin", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 04 – Git and GitHub for Codex Users
theme
Plain-English definition: theme is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding theme helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "theme", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 05 – How to Think Like a Builder
child theme
Plain-English definition: child theme is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding child theme helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "child theme", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 06 – Codex Prompting Foundations
shortcode
Plain-English definition: shortcode is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding shortcode helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "shortcode", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 07 – The /goal Method
block editor
Plain-English definition: block editor is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding block editor helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "block editor", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 08 – Codex for Reading and Understanding Codebases
Gutenberg
Plain-English definition: Gutenberg is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding Gutenberg helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "Gutenberg", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 09 – Codex for Editing Existing Websites
Yoast
Plain-English definition: Yoast is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding Yoast helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "Yoast", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 10 – Codex for Building Landing Pages and WordPress Assets
sitemap
Plain-English definition: sitemap is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding sitemap helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "sitemap", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 11 – Codex for Building Web Apps
robots.txt
Plain-English definition: robots.txt is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding robots.txt helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "robots.txt", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 12 – Codex for JavaScript, TypeScript, React, and Next.js
noindex
Plain-English definition: noindex is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding noindex helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "noindex", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 13 – Codex for Debugging and Fixing Bugs
schema markup
Plain-English definition: schema markup is a publishing and search visibility term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding schema markup helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "schema markup", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 14 – Codex for Testing, QA, and Refactoring
JSON-LD
Plain-English definition: JSON-LD is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding JSON-LD helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "JSON-LD", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 15 – Codex for GitHub Issues, Branches, Pull Requests, and Reviews
FAQ
Plain-English definition: FAQ is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding FAQ helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "FAQ", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 16 – Codex for Deployments, Vercel, Hosting, and Rollbacks
quiz
Plain-English definition: quiz is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding quiz helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "quiz", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 17 – Codex for Data Projects, Reports, Dashboards, and Automation
rubric
Plain-English definition: rubric is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding rubric helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "rubric", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 18 – Codex for APIs, Integrations, and Environment Variables
capstone
Plain-English definition: capstone is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding capstone helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "capstone", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 19 – Codex for WordPress, SEO Tools, Calculators, and Interactive Pages
worksheet
Plain-English definition: worksheet is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding worksheet helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "worksheet", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 20 – Advanced Codex CLI, Config, Models, and Local Workflows
checklist
Plain-English definition: checklist is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding checklist helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "checklist", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 21 – Codex Cloud/Web, Parallel Tasks, and Long-Running Work
prompt library
Plain-English definition: prompt library is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding prompt library helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "prompt library", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 22 – Skills, MCP, Subagents, and Expert Agent Workflows
bad prompt
Plain-English definition: bad prompt is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding bad prompt helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "bad prompt", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 23 – Security, Privacy, Secrets, Safe Automation, and Production Readiness
better prompt
Plain-English definition: better prompt is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding better prompt helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "better prompt", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 24 – Expert Capstones, Portfolio Projects, and Certification
expert prompt
Plain-English definition: expert prompt is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding expert prompt helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "expert prompt", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 00 – Course Orientation and Setup
done-when
Plain-English definition: done-when is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding done-when helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "done-when", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 01 – What Codex Is and Why It Matters
acceptance criteria
Plain-English definition: acceptance criteria is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding acceptance criteria helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "acceptance criteria", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 02 – Absolute Beginner Coding Concepts
user story
Plain-English definition: user story is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding user story helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "user story", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 03 – Developer Environment Setup
scope
Plain-English definition: scope is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding scope helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "scope", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 04 – Git and GitHub for Codex Users
constraint
Plain-English definition: constraint is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding constraint helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "constraint", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 05 – How to Think Like a Builder
regression
Plain-English definition: regression is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding regression helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "regression", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 06 – Codex Prompting Foundations
root cause
Plain-English definition: root cause is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding root cause helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "root cause", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 07 – The /goal Method
reproduction steps
Plain-English definition: reproduction steps is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding reproduction steps helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "reproduction steps", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 08 – Codex for Reading and Understanding Codebases
fixture
Plain-English definition: fixture is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding fixture helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "fixture", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 09 – Codex for Editing Existing Websites
unit test
Plain-English definition: unit test is a verification term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding unit test helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "unit test", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 10 – Codex for Building Landing Pages and WordPress Assets
integration test
Plain-English definition: integration test is a verification term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding integration test helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "integration test", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 11 – Codex for Building Web Apps
end-to-end test
Plain-English definition: end-to-end test is a verification term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding end-to-end test helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "end-to-end test", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 12 – Codex for JavaScript, TypeScript, React, and Next.js
mock
Plain-English definition: mock is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding mock helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "mock", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 13 – Codex for Debugging and Fixing Bugs
stub
Plain-English definition: stub is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding stub helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "stub", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 14 – Codex for Testing, QA, and Refactoring
snapshot
Plain-English definition: snapshot is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding snapshot helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "snapshot", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 15 – Codex for GitHub Issues, Branches, Pull Requests, and Reviews
coverage
Plain-English definition: coverage is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding coverage helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "coverage", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 16 – Codex for Deployments, Vercel, Hosting, and Rollbacks
smoke test
Plain-English definition: smoke test is a verification term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding smoke test helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "smoke test", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 17 – Codex for Data Projects, Reports, Dashboards, and Automation
manual QA
Plain-English definition: manual QA is a verification term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding manual QA helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "manual QA", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 18 – Codex for APIs, Integrations, and Environment Variables
release notes
Plain-English definition: release notes is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding release notes helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "release notes", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 19 – Codex for WordPress, SEO Tools, Calculators, and Interactive Pages
changelog
Plain-English definition: changelog is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding changelog helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "changelog", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 20 – Advanced Codex CLI, Config, Models, and Local Workflows
incident
Plain-English definition: incident is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding incident helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "incident", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 21 – Codex Cloud/Web, Parallel Tasks, and Long-Running Work
postmortem
Plain-English definition: postmortem is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding postmortem helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "postmortem", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 22 – Skills, MCP, Subagents, and Expert Agent Workflows
monitor
Plain-English definition: monitor is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding monitor helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "monitor", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 23 – Security, Privacy, Secrets, Safe Automation, and Production Readiness
alert
Plain-English definition: alert is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding alert helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "alert", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 24 – Expert Capstones, Portfolio Projects, and Certification
observability
Plain-English definition: observability is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding observability helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "observability", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 00 – Course Orientation and Setup
analytics
Plain-English definition: analytics is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding analytics helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "analytics", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 01 – What Codex Is and Why It Matters
privacy policy
Plain-English definition: privacy policy is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding privacy policy helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "privacy policy", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 02 – Absolute Beginner Coding Concepts
PII
Plain-English definition: PII is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding PII helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "PII", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 03 – Developer Environment Setup
data retention
Plain-English definition: data retention is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding data retention helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "data retention", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 04 – Git and GitHub for Codex Users
rollout
Plain-English definition: rollout is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding rollout helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "rollout", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 05 – How to Think Like a Builder
feature flag
Plain-English definition: feature flag is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding feature flag helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "feature flag", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 06 – Codex Prompting Foundations
migration
Plain-English definition: migration is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding migration helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "migration", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 07 – The /goal Method
seed data
Plain-English definition: seed data is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding seed data helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "seed data", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 08 – Codex for Reading and Understanding Codebases
CSV
Plain-English definition: CSV is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding CSV helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "CSV", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 09 – Codex for Editing Existing Websites
JSON
Plain-English definition: JSON is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding JSON helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "JSON", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 10 – Codex for Building Landing Pages and WordPress Assets
Markdown
Plain-English definition: Markdown is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding Markdown helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "Markdown", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 11 – Codex for Building Web Apps
YAML
Plain-English definition: YAML is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding YAML helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "YAML", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 12 – Codex for JavaScript, TypeScript, React, and Next.js
TOML
Plain-English definition: TOML is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding TOML helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "TOML", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 13 – Codex for Debugging and Fixing Bugs
shell command
Plain-English definition: shell command is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding shell command helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "shell command", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 14 – Codex for Testing, QA, and Refactoring
script
Plain-English definition: script is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding script helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "script", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 15 – Codex for GitHub Issues, Branches, Pull Requests, and Reviews
package script
Plain-English definition: package script is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding package script helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "package script", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 16 – Codex for Deployments, Vercel, Hosting, and Rollbacks
dev server
Plain-English definition: dev server is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding dev server helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "dev server", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 17 – Codex for Data Projects, Reports, Dashboards, and Automation
localhost
Plain-English definition: localhost is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding localhost helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "localhost", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 18 – Codex for APIs, Integrations, and Environment Variables
port
Plain-English definition: port is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding port helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "port", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 19 – Codex for WordPress, SEO Tools, Calculators, and Interactive Pages
browser testing
Plain-English definition: browser testing is a verification term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding browser testing helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "browser testing", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 20 – Advanced Codex CLI, Config, Models, and Local Workflows
copy button
Plain-English definition: copy button is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding copy button helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "copy button", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 21 – Codex Cloud/Web, Parallel Tasks, and Long-Running Work
filter button
Plain-English definition: filter button is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding filter button helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "filter button", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 22 – Skills, MCP, Subagents, and Expert Agent Workflows
search input
Plain-English definition: search input is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding search input helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "search input", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 23 – Security, Privacy, Secrets, Safe Automation, and Production Readiness
accordion
Plain-English definition: accordion is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding accordion helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "accordion", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 24 – Expert Capstones, Portfolio Projects, and Certification
details element
Plain-English definition: details element is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding details element helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "details element", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 00 – Course Orientation and Setup
progress tracker
Plain-English definition: progress tracker is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding progress tracker helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "progress tracker", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 01 – What Codex Is and Why It Matters
course hub
Plain-English definition: course hub is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding course hub helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "course hub", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 02 – Absolute Beginner Coding Concepts
lesson page
Plain-English definition: lesson page is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding lesson page helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "lesson page", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 03 – Developer Environment Setup
module page
Plain-English definition: module page is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding module page helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "module page", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 04 – Git and GitHub for Codex Users
source log
Plain-English definition: source log is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding source log helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "source log", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 05 – How to Think Like a Builder
QA report
Plain-English definition: QA report is a verification term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding QA report helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "QA report", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 06 – Codex Prompting Foundations
owner guide
Plain-English definition: owner guide is a Codex project work term you may see while planning, editing, reviewing, testing, or shipping AI-assisted software.
Why it matters: Understanding owner guide helps you give Codex better context and decide whether the next step is safe, testable, and reversible.
Beginner example: If Codex mentions "owner guide", ask it to explain the term, show where it appears in your project, and recommend one safe next action.
Related module: Module 07 – The /goal Method
Want your AI product explained to a large AI-native audience?
Kingy AI helps AI companies turn complex products into clear, useful YouTube videos that drive awareness, product understanding, demos, clicks, and search visibility.
