zero2codex
OpenAI Codex workflow course

Course goal: ship your personal brand site

Build a personal brand site with Codex

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.

0/4
00｜Install And Open CodexInstall the desktop app, sign in, open the site project folder, and send a safe first message.What Codex Is ForBuild the first version of your site with a name, introduction, projects, contact details, and one working button.Choose A Codex SurfaceEdit the site's Projects button locally, then verify its text and behavior in a browser.Your First Useful PromptTurn “add an About section” into a concrete request with content, constraints, and browser checks.
04

Ship Verified Changes

Test the site, check desktop and mobile views, and review the final diff.

0/3
Test The ChangeAdd focused checks for the site's theme and navigation without breaking earlier work.Browser VerificationOpen the real site and check content, navigation, and layout at desktop and mobile widths.
11 minReady

Browser Verification

Verify UI behavior where code tests alone are not enough.

browser inspectionvisual proofinteractive checks

Watch, then try

11｜桌面與手機實際驗證（CLI 版・54 秒）

真實 CLI 輸出檢視器與本機網站錄影，非 Codex 原生介面；繁中字幕、無旁白，等待區段已剪接。

zero2codex
MP4

Step-by-step

  1. 沿用前一課的 my-brand-site，或從下方練習檔取用本課 before 起點。
  2. 在專案目錄執行本片 CLI 指令；本課權限為 read-only。
  3. 核對實際輸出與結束碼，不把文字回報當成瀏覽器操作證據。
  4. 錄製者實際按 CTA、切換主題，並檢查 390px 手機版。
跟著本片操作：CLI 指令與練習檔（繁體中文）

這是本課的 CLI 替代實作路徑；下方概念課程仍保留其他介面的說明。先安裝並登入 Codex CLI，在 my-brand-site 資料夾內執行下列 macOS／Linux 指令。影片將真實 CLI JSON 事件排版成易讀畫面，下列指令使用一般 CLI 輸出；不是 Codex 原生介面，等待區段已剪接。

codex exec --ephemeral --ignore-user-config --sandbox read-only '讀 index.html，提供四項具體瀏覽器驗證：CTA 跳轉、主題切換兩次、Email 目標但不寄信、390px 手機不溢出。只列各自的預期結果，限四點。不要假稱你已操作瀏覽器，不改檔。'

下載逐課練習檔與實際結果（ZIP）

Plain-language explanation

Some UI problems only appear in the rendered page. Browser verification lets Codex inspect the real screen, click through a flow, and report what it observed.

This does not replace code tests. It adds visual and interaction evidence for layout, copy, responsive behavior, and user flows.

Why it matters

A UI diff can pass tests and still look wrong. Browser verification catches issues that only exist in the running app.

Common beginner mistake

Beginners often assume unit tests prove a layout or interaction is correct without opening the page.

Good prompt

Codex, open the local index.html preview for my-brand-site. At desktop and 390px mobile widths, click the project CTA, toggle the theme twice, use Back to top, and check for horizontal overflow. Inspect only the mailto target; do not open mail or send anything. Report actual interactions, visible results, and incomplete checks. If this interface cannot control a browser, provide steps for me to perform instead of claiming verification.

Try this

Choose one UI route and write a browser verification request that names the route, viewport, interaction, and evidence.

Completion checklist

  • The check uses the running app, not only static code review.
  • The report mentions the screen state or interaction that was observed.

Sources

Review Before AcceptingReview the site's full diff, test evidence, and any remaining visual or behavior risks.
08

Finish And Deliver The Site

Polish independent tasks in parallel, then complete one final acceptance review.

0/3
Complete The Site GoalTurn the finished personal site into one measurable goal with content, layout, interaction, and evidence checks.Polish Copy And Accessibility In ParallelUse isolated worktrees only when copy polish and accessibility review can avoid editing the same lines.Run The Final Three ReviewsRun separate content, link, and accessibility reviews, then compare all evidence against the same launch checklist.

Practice lab

Copyable Codex prompts

Plan before coding

Codex, inspect the relevant files first, then propose a plan. Do not edit until the plan names tests and verification steps.

Verification checklist

  • Relevant files are named before edits begin.
  • The plan includes tests and verification commands.

Verify a UI change

Codex, start the dev server, open the route in the browser, check desktop and mobile layouts, then report the exact evidence.

Verification checklist

  • Desktop and mobile states are checked in the browser.
  • The final note includes exact evidence.

Review focused risk

Codex, review the uncommitted diff. Focus on behavioral regressions, missing tests, and accessibility issues. Do not modify files.

Verification checklist

  • Findings lead with severity and file references.
  • Unchanged files are left untouched.
Every good Codex request says what to change, what to preserve, and how to prove it worked.

Reference

Codex concepts to keep nearby