Use it when
When pages share a generic or inaccurate title.
Before moving on
Check served or rendered metadata and avoid duplicate title tags.
Verify real user journeys, metadata, build output, and the changes you are about to publish.
Name the main visitor journey and target environment. Verify links, forms, narrow layouts, direct route loading, and the production build before deploying.
Name the main visitor journey and target environment. Verify links, forms, narrow layouts, direct route loading, and the production build before deploying.
Open one task, customize it for your project, and check the result before moving on. Skip any step that does not apply.
Use it when
When pages share a generic or inaccurate title.
Before moving on
Check served or rendered metadata and avoid duplicate title tags.
Use it when
When a page is missing a useful description.
Before moving on
Check the final metadata; explain that search engines can choose a different snippet.
Make meaningful images understandable beyond their pixels.
Open this task ↗Use it when
When useful images have missing or unhelpful alt text.
Before moving on
Avoid keyword stuffing and do not invent details absent from the image.
Use it when
When a page looks finished but the flow has not been checked.
Before moving on
Report each verified step, failures, and steps that could not be tested.
Use it when
When the project works in development but will not build.
Before moving on
Rerun the relevant build and summarize what changed without hiding errors.
Use it when
When you are preparing the first public release.
Before moving on
Return a concise prioritized list of blockers, verified checks, and limitations.
Save your work or review a Git commit between meaningful stages. A clean checkpoint makes the next experiment easier to understand and reverse.
Learn the terminal basics →