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.
07

Build A Site QA Workflow

Create reusable checks for the site's content, links, and browser behavior.

0/3
Turn Site Checks Into A SkillPackage the personal site's pre-launch content, link, mobile, and accessibility checks into one reusable skill.
10 minReady

Turn Site Checks Into A Skill

Create a repeatable pre-launch checklist instead of rewriting the same QA prompt.

skill triggersite QA stepsevidence report

Watch, then try

19｜規劃可重複 QA 流程（CLI 版・25 秒）

真實 CLI 輸出檢視器與本機網站錄影，非 Codex 原生介面；繁中字幕、無旁白，等待區段已剪接。交付 QA Skill 規格草案，未安裝 Skill。

zero2codex
MP4

Step-by-step

  1. 沿用前一課的 my-brand-site，或從下方練習檔取用本課 before 起點。
  2. 在專案目錄執行本片 CLI 指令；本課權限為 read-only。
  3. 核對實際輸出與結束碼，不把文字回報當成瀏覽器操作證據。
  4. 此課交付 Skill 規格草案，不冒充已安裝或執行 Skill。
跟著本片操作：CLI 指令與練習檔（繁體中文）

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

codex exec --ephemeral --ignore-user-config --sandbox read-only '讀 AGENTS.md 和 check_site.py，草擬一個未安裝的網站 QA Skill 規格：觸發時機、唯讀範圍、兩個實際命令、需要人操作的浏览器步驟、通過/問題/未驗證三類輸出。不建立或安裝 Skill，不更動設定，限 200 字。'

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

Plain-language explanation

You have now checked the site several times: required sections, links, narrow screens, controls, and final evidence. That repeated sequence is a good candidate for a small QA skill.

The skill should run before launch and produce a report. It should not take over unrelated design or content work.

Why it matters

A reusable checklist keeps future portfolio updates from skipping the same important checks.

Common beginner mistake

A common mistake is making a giant 'build websites' skill instead of a small, predictable pre-launch check.

Good prompt

Codex, outline a personal-site QA skill. It should trigger before launch, check required sections and in-page links, inspect wide and narrow layouts, review basic accessibility, and end with passed, failed, and human-review items.

Try this

Write one sentence that says exactly when the site QA skill should run.

Completion checklist

  • The skill has a clear pre-launch trigger and a narrow QA purpose.
  • Its output makes missing checks easy to spot.

Sources

Bring In Project Data SafelyDecide whether project cards need outside data, and use the smallest read-only connection only when it adds value.Test Contact SafelyTest the Contact section with sample data and stop before anything is sent to a real service.
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