← All 12 lessons
LESSON 11 OF 12 · MODULE 4: BUILD AND APPLY

Build a small tool with Codex

  1. 1Define behaviour
  2. 2Build a prototype
  3. 3Test each action
Test adding, completing, deleting and saving tasks; a build passing is not a button test.

Practice tool: Download the study checklist. Open the downloaded HTML file in a browser. Tasks save in that browser where local saving is supported; they do not sync across devices.

Goal: Describe a small tool, review its behaviour and test it before relying on it.

Learn

Codex supports software development work. A beginner still needs to describe the desired behaviour and check the result. Start with a small prototype using fictional data. Ask for an explanation of what was built and any limitations. Keep a working copy before making further changes.

This activity needs an available Codex environment. If you do not have one, complete the requirements and test checklist as a planning exercise. A prototype alone is not a published website.

Demonstration

Build a simple study checklist prototype for a beginner.
Requirements: add a task, mark it complete, delete it,
and show the number of unfinished tasks.
Use large readable labels and make it usable on a phone.
Use fictional sample tasks. No accounts, payments or external AI calls.
Before implementation, explain how tasks will be stored.
After implementation, explain how to open it and test it,
and report any limitations. Do not publish it.

Practise

Test five behaviours: add a normal task; try an empty task; mark a task complete; delete a task; reload the page. Compare reload behaviour to the stated storage design. Test the interface on a narrow screen and with a keyboard.

Request one focused improvement based on a problem you observed. Repeat the affected checks after the change.

Check your result

Task counts should change correctly. Empty tasks should be handled clearly. Data persistence should match what was promised. Record remaining problems rather than claiming the tool is finished because it looks attractive.

Knowledge check: Is a successful build enough to prove every button works?

Show answer guide

No. Test the intended behaviours and inspect relevant results.

Optional feature access may differ by account and device. This lesson does not automatically run its prompts, send messages or create scheduled tasks.