Review prompt

A site review for a customer: the verdict with findings, and a note per page.

Prompt

Use the klarhimmel-design skill. Build the review of {site} for its owner: {verdict}. Install: npx shadcn add @klarhimmel/review-summary @klarhimmel/review-page-note (remove what you do not use) Pick: - review-summary: the front: site, date, verdict, up to five findings, what we would build, go ahead and ask - review-page-note: one page: now beside proposed, notes marked keep, change, add or remove, an optional screenshot Props: review-summary: siteName, siteUrl, verdict, findings as { title, detail, severity high | medium | low | good, page }, buildPoints, goAhead and question as { label, href }. review-page-note: pageName, pageUrl, nowText, proposedText, notes as { type keep | change | add | remove, text }, screenshot { src, alt } and a caption. Mapping from a Canvas review: docs/review-blocks.md. Copy: Plain words for the owner. Lead with what works. A finding says what is wrong, why it matters and what we would do; severity is a word, never only a colour. Accessibility: Severity and note types are words with a shape, not colour alone. The screenshot has alt text and a visible caption. Both blocks carry h2/h3 headings only: the page that holds them supplies the h1. Never: viewport variants (md:, lg:), style=, text or images outside Text and Media, fields the schema lacks. Shorten copy to fit the limits. Done when: every severity and note type is a word; at most five findings; the actions have names; screenshots have alt text and a caption.

Variables

Variable	What to fill in	Example
`{site}`	The reviewed site	exempel.se
`{verdict}`	The verdict in a sentence	clear services page, hard to reach contact

Blocks it uses

A good result

Every severity and note type is a word. At most five findings. The actions have names.

checklist.md

- [ ] every severity and note type is a word
- [ ] at most five findings
- [ ] the actions have names
- [ ] screenshots have alt text and a caption