Day 2

Read the project, then make one small change

Understand how the files relate, then keep one change as small as possible so the plan, edit, and evidence stay aligned.

Suggested time
45-60 minutes
Completion evidence
Project map and change record

Continue with yesterday's project

Open the Day 1 project and confirm it still works. Today adds no feature. You will explain the current state and change one visible sentence.

Ask Codex for a project map

You do not need to memorize code. Find the entry, each file's role, the click path, and the smallest place to edit.

Read-only analysis
Do not modify files or install dependencies.

Read the current project and create a project map for a first-time builder:
1. List only files and folders that actually exist.
2. Identify the page entry file.
3. Explain where structure, styling, and button behavior live.
4. Describe the real loading and click flow in order.
5. Identify the smallest place to change the button feedback.
6. Mark anything that cannot be confirmed.

End with a table: file / role / relationship / change needed. Do not edit.
index.htmlEntry and content

The browser opens this file. Structure and button behavior may live here.

styles.cssAppearance and mobile layout

Controls color, type, spacing, and button styles.

README.mdViewing instructions

Explains how to open and check the page. It does not run in the browser.

Make one narrow change

This exercise exposes the complete chain from plan and approval to execution and verification.

Small change
Make one small change only.

After the "View my 16th case" button is clicked, change the feedback to:
My first release goal: invite one real user to try it.

Boundary:
1. Change only the file and location required for this feedback.
2. Do not change layout, color, type, button label, or other content.
3. Do not install dependencies or create files.

Before editing, identify the file, the exact content, and the verification method. Wait for approval.
Review only three things
  • The file matches the project map.
  • The plan contains no refactor, dependency, or extra feature.
  • The test opens the page and clicks the button.

Retest the real page

Deliverable

Project map and change record

Your evidence should explain how the project ran, why this location changed, and how you proved it still works.

Go to Day 3