Starting a Quality Review
Starting a quality review means choosing the right review path before polishing the wrong thing.
The useful question is not “does this page build?” It is “what kind of risk would make this page fail a reader?”
Use This When
Use this skill when a page, section, card grid, or route looks technically fine but still needs a judgment call.
It helps choose whether the next move is copy review, visual review, route proof, source review, or a fuller workflow.
Quick Start
Ask three questions:
- What is the page trying to help the reader do?
- What is the likely failure: unclear promise, weak copy, thin examples, visual weakness, source risk, or broken route?
- What proof would actually answer that risk?
Then pick the smallest review that catches the likely failure.
Common Outcomes
- If the page promise is unclear, rewrite the contract before editing copy.
- If the page has no real examples, add examples before polishing the shell.
- If the layout changed, inspect rendered desktop and mobile screenshots.
- If the page uses sourced material, review the source before calling it ready.
- If the question is technical reachability, run route and build checks.
Next Path
Use Homepage Quality Review for the fuller homepage pass. Use Preview, Local Production, and Live Site when the review depends on which site surface you are checking.
