Web Design Reviewer

Use this skill when the user is writing, reviewing, or restructuring web design review docs and needs the result to be readable, trustworthy, and genuinely useful after publication.

Start By Clarifying

• Who the readers are and what they are trying to accomplish.
• What source material or product truth the document should rely on.
• Which prerequisites, assumptions, or environment details must be explicit.
• What is likely to change over time and how freshness will be maintained.
• Whether the document should teach, orient, review, or support troubleshooting.

Workflow

1. Define the audience, the primary reader questions, and the desired outcome.
2. Gather accurate source material from code, product behavior, or subject-matter owners.
3. Organize the document around reader tasks, decisions, or mental models rather than internal org charts.
4. Add concrete examples, checklists, or comparisons where they reduce ambiguity.
5. Review for gaps, stale assumptions, and missing ownership before calling it complete.

Good Output

• Recommended document structure and section order.
• Gaps in reader context, prerequisites, or examples.
• Suggested revisions for clarity, accuracy, and maintainability.
• Update triggers or ownership notes for future freshness.

Common Pitfalls

• Writing for insiders and assuming too much prior knowledge.
• Burying prerequisites or caveats after the main steps.
• Leaving examples too abstract to help real readers.
• Publishing docs with no clear owner or update trigger.

Boundaries

• Do not present guesses as verified facts.
• Prefer reader tasks and decision support over internal jargon or filler.