A practical eight-session workshop

Build with Codex.
Keep your hands on the wheel.

Learn how to turn a useful idea into a bounded mission, inspect before editing, debug from evidence and hand off work another human can trust.

Independent publication. Not affiliated with, endorsed by, or published by OpenAI.

Eight focused sessionsReal companion projectReusable workflow
01Brief the work
02Protect the workspace
03Verify the real flow
04Hand off honestly
Inside the book

From first prompt
to defensible handoff.

The workshop follows one intentionally modest project: a local-first Community Help Finder. Small enough to finish, serious enough to teach privacy, accessibility, stale-data handling and release judgment.

00–02

Start under control

Choose a Codex surface, protect the workspace, write an executable mission and map the actual project before changing it.

03–04

Build and debug narrowly

Create one complete user-facing slice, then move from symptom to evidence instead of guessing or rewriting broadly.

05–06

Review and verify

Run findings-first review, test the actual browser path and separate observed facts from unproved assumptions.

07–08

Make it last

Use durable project instructions, freeze scope and prepare work another person can run, understand and maintain.

Companion project included

Meet the Community
Help Finder.

Download the complete local-first case-study app used throughout the guide. Search sample community resources, test filters and empty states, then practise reviewing privacy, trust and handoff risks.

Download companion files ↓ZIP · HTML, CSS, JavaScript and README
community-help-finder/
  • index.htmlOpen the app
  • styles.cssResponsive interface
  • app.jsSample data and filtering
  • README.mdSetup, golden path and limits

Sample data only. Verify every real listing before public use.

The builder loop

Six habits that
outlast the interface.

Codex changes quickly. The operating discipline does not. Each stage turns speed into work you can inspect, reverse and explain.

  1. Brief

    Define the goal, context, scope, constraints, proof and fallback.

  2. Inspect

    Learn the project’s real entry points, commands and fragile boundaries.

  3. Build

    Create the smallest complete slice of the intended experience.

  4. Verify

    Run checks and exercise the actual user flow.

  5. Review

    Search for prioritized findings instead of reassurance.

  6. Handoff

    Explain operation, limits, ownership and the next safe move.

Who it is for

For beginners
with real standards.

You do not need to imitate a senior engineer. You need a reliable way to guide a powerful tool toward useful work—and to know what evidence deserves your trust.

START

First-time builders

Learn the operating vocabulary without being buried in framework theory.

TEACH

Workshop leaders

Use a structured eight-block curriculum, exercises and review templates.

HAND OFF

Community teams

Practise making small software understandable, maintainable and honest about its limits.

Independent practical guide

Small changes.
Clear proof.

The guide was built, tested and documented with Codex. Product interfaces change, so it separates durable operating habits from interface details and points readers to current official documentation.

Ask about availability →
Plain answers

Questions

What to know before you begin.

Do I need to be a programmer?

No. The guide explains the operating habits and technical vocabulary as they become useful. Basic comfort opening folders and following commands helps.

Is this an official OpenAI book?

No. It is an independent practical guide from The Giant Tiny App Factory Tech Team and is not affiliated with, endorsed by, or published by OpenAI.

Is the companion project included?

Yes. The complete Community Help Finder starter is available above as a ZIP containing HTML, CSS, JavaScript and setup instructions.

What do I need?

Access to Codex, the companion project files, Node.js 20 or newer for automated checks, Python 3 for the local server, and a willingness to review commands before running them.

Does “eight hours” mean exactly eight hours?

No. The book is designed as eight guided workshop sessions. Installation, careful review or unfamiliar tools may take longer.

Will the Codex interface change?

Almost certainly. The guide separates durable working habits from changeable interface details and tells readers to consult current official documentation when they differ.

What will I practise?

You will practise briefing, inspecting, building, debugging, reviewing, verifying and handing off one small Codex-assisted project with explicit evidence and limits.

Start with control

Make the next build
small enough to prove.

Ask about CODEX 2026 →