Level 2 Practice: Make a Bounded ProjectCard Edit
About This Tutorial
This tutorial organizes the scope, deliverable, and completion checks for repository work delegated to Codex.
A small first edit makes it practical to review Codex output and detect unintended changes. This level limits work to the existing ProjectCard responsibility.
What You Will Complete
You will produce a small reviewable diff. The goal is not the amount of work; it is a reproducible Level 2 delegation boundary and completion check.
Step 1: Set the Boundary
Before handing work to Codex, state the goal, scope, exclusions, and completion criteria. Adapt this prompt to your project.
Add technology tags to ProjectCard using existing patterns. Limit changes to the component and directly related tests. Preserve routing, whole-card link behavior, and shared styles.Check: Continue only when Codex can restate the scope and unresolved questions before acting.
Step 2: Practice
- Limit the scope to
ProjectCardand directly related tests. - Add technology tags while preserving existing props, spacing, and link states.
- Review the diff for unrelated formatting or dependency changes.
Keep the scope stable and inspect the output or diff after each stage.
Step 3: Verify Completion
You are done when git diff --stat matches the requested scope and existing card interactions remain intact.
Record the actions performed, supporting evidence, and anything not verified. Also record why work stopped when a condition was not met.
Troubleshooting
Codex exceeded the requested scope
Stop the task and inspect the diff. Add explicit owned files and exclusions to the prompt, then rerun only the approved scope.
Completion is difficult to judge
Replace vague criteria such as “implement it” with observable files, commands, pages, or review results.
Next Step
Continue to Level 3 to expand the delegation boundary by one step.
See the references for the external specifications and background sources used on this page.[1][2][3]