Keep improving one project from an empty folder to a responsive one-page site with an introduction, projects, and contact details. Every lesson adds a visible result or a check toward that finish line.
Curriculum
Personal brand site build path
01
Start With Codex
Set up Codex and build the hero section of your personal brand site.
Continue with the starter folder from lesson one. Use the local project for the file change, then use browser verification—or exact manual steps—to check the rendered result.
Before you start
Finish lesson one so my-brand-site contains index.html.
Open that folder as the current local project and start a separate task for this outcome.
Do it now
Good prompt
Codex, inspect index.html in this local project. Change the hero button label from “View my work” to “Explore my work” without changing its scroll behavior or adding packages. After editing, verify the rendered label and that it still moves to Projects; otherwise give me exact manual check steps. Report the changed files and visible result.
What success looks like
Codex changes only index.html and installs no packages.
The rendered button says “Explore my work” and still moves to the Projects section.
The final report separates the file change from the browser or manual verification evidence.
Stuck? Try this
If browser tools are unavailable, accept exact manual verification steps instead of skipping verification.
If Codex edits unrelated styles, reply: “Revert unrelated changes and keep only the button-label change.”
Plain-language explanation
You do not need to know every Codex surface before you begin. You only need to choose the surface that gives Codex the right files, tools, and review loop for the task in front of you.
A small local fix usually belongs in a local app or CLI session. A task that can be delegated safely, or one you want to run in parallel, may fit a cloud or worktree flow better.
Why it matters
Choosing the surface first prevents wasted time: Codex gets the right context, you get the right evidence, and the task stays easier to review.
Common beginner mistake
A common beginner mistake is starting every task in the same place, then wondering why Codex cannot see the files, browser state, or review context it needs.
Try this
Pick one task you might ask Codex to do. Write down whether it belongs in the app, CLI, browser, cloud, or worktree, and explain the reason in one sentence.
Completion checklist
You can name at least two Codex surfaces and the kind of task each one fits.
You can explain what context or verification the chosen surface gives Codex.