---
name: page-review
description: Review a website page against its stated purpose and visual reference. Use when asked to inspect a rendered page for layout, clarity or responsive behavior.
compatibility: Requires access to the page and a browser or current screenshots.
---

# Page review

## Goal and scope

Identify concrete differences between one rendered page and its intended result.
Review the page without editing code or publishing changes.

## Inputs and rules

Use the page URL, intended visitor action and authorized visual reference.
Read the applicable project instructions before examining the page.
The reference guides appearance; the project brief supplies product facts.
Report conflicts rather than choosing an unsupported interpretation.

### Missing inputs

If the page purpose is absent, ask one focused question.
If the page cannot be rendered, state what cannot be checked.
Do not invent screenshots, browser access or test results.

## Ordered steps

1. Read the brief and identify the main visitor action.
2. Open the page and reference at the same desktop width.
3. Compare information order, type, spacing, images and controls.
4. Resize the same page to a narrow mobile viewport and repeat the review.
5. Check applicable focus, empty, loading, error and expanded states.
6. Separate observed problems from optional design preferences.
7. Check the findings against the brief before reporting them.

## Checks

Every finding names an element, an observed problem and its consequence.
Every visual claim refers to output that was actually inspected.
Any untested interaction or unavailable viewport is stated explicitly.
A successful code check alone does not establish visual quality.

## Result

Return the findings in order of their effect on the page's purpose.
Include the page, viewports examined, supporting evidence and unverified areas.
If no material problem was found, say so without inventing one.