← ClaudeAtlas

wireframe-reviewerlisted

Use when reviewing or critiquing an existing website wireframe, landing page, or page structure for any niche or business — when you need structured feedback on narrative flow, visual hierarchy, clarity, and conversion path, plus concrete fixes per section. For building a new page structure from scratch, use wireframe-writer.
yaxeen/storytelling-skills · ★ 2 · Code & Development · score 73
Install: claude install-skill yaxeen/storytelling-skills
# Wireframe Reviewer - Reviewing a page = checking whether it tells a clear story that pulls one scroll toward one action. - Critique against five axes, then return structured findings + a concrete fix for each. - Built on the six levers — see **storytelling-hooks**. Recap: 1. Curiosity gap · 2. Emotional mirror · 3. Conflict engine · 4. Relatability · 5. Pattern + surprise · 6. Three-act. ## When to Use - Reviewing a wireframe, mockup, or live landing/sales/home page. - Diagnosing low conversion, confusing flow, or "it just feels off". - Giving a designer/marketer structured, actionable feedback. - Any niche or business. To build a new structure, use **wireframe-writer**. ## The Five Review Axes (Quick Reference) | Axis | Question | Common failure | |------|----------|----------------| | Narrative flow | Does each section earn the next scroll? | Sections in random order; no loop | | Visual hierarchy | Does the eye land on what matters first? | Everything equal weight; buried CTA | | Clarity | Is the message understood in 5 seconds? | Vague hero; jargon; feature dump | | Conversion path | Is there one obvious next action? | Many/competing CTAs; no CTA above fold | | Friction | What makes a visitor hesitate or leave? | Unanswered objections; cognitive load | ## Intake (Before Reviewing) - A review without context grades against guesses. Know before reviewing: the page's **one conversion goal**, the target visitor in a sentence, and the main traffic source. - If these ar