Skip to content
Back to search

design-review-page

SkillWorks with Claude CodeGitHub

A Claude Code skill that turns a frontend change into a review page stakeholders can comment on: captioned screenshots of every screen and state, pins, notes, and a resolve and reopen flow, without running the app.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/suiyangqiu--design-review-page/badge.svg)](/listings/suiyangqiu--design-review-page)

HTML

<a href="/listings/suiyangqiu--design-review-page"><img src="/api/listings/suiyangqiu--design-review-page/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Copy the skill folder into your personal skills folder:

git clone https://github.com/suiyangqiu/design-review-page.git
cp -r design-review-page/skills/design-review-page ~/.claude/skills/

On Windows PowerShell:

git clone https://github.com/suiyangqiu/design-review-page.git
Copy-Item -Recurse design-review-page\skills\design-review-page $HOME\.claude\skills\

Or put it in a project's `.claude/skills/` folder to share it with that repo's team.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 97 lines
  1. # design-review-page
  2. A [Claude Code](https://claude.com/claude-code) skill that turns a frontend change into a review page that product owners, designers and other stakeholders can comment on, without ever running the app.
  3. Every new screen and state becomes a captioned screenshot on a Claude artifact. Reviewers click a spot on a screenshot to pin a comment, add notes per section, and mark comments resolved or reopen them. You get the feedback back grouped by section, ready to turn into fixes and tickets.
  4. ![The top of a review page: sections in the left rail, the how-to steps, the facts about the review, and a "Please verify or decide" card](docs/screenshots/page-top.png)
  5. ## What it does
  6. - **Captures the real app** with the Playwright MCP: every new or changed screen, at rest and after the interactions that matter, plus loading, empty and failure states (forced in the browser when mock data never produces them). Area-of-focus red boxes, consistent clips, one viewport size.
  7. - **Writes for people who won't run the app.** Captions say what the reader is looking at and why it matters, in the product's words, not the code's. Each section lists what was built differently from the design on purpose, and can open with a "Please verify or decide" card for the calls only the product owner can make.
  8. - **Has its own comment system.** Pins on screenshots, notes per section, replies, "mark resolved" with a note, and "reopen" with a reason. Comments live in the artifact's own database, not in Claude's native artifact comments, so nobody gets an @Claude notification and the owner reads them in their own time. Names come from the viewer's claude.ai profile.
  9. - **Reads the feedback back for you.** `/design-review-page feedback <url>` lists every comment by section (reopened first, then open), and proposes a fix, a reply or a resolution for each. Nothing is written to the page or your tracker until you say so.
  10. - **Is tested before it ships.** A build script checks the content, and a mock flow test drives the comment system end to end in a browser against a local stand-in for the artifact runtime.
  11. ![A screenshot with three pins (open, resolved and reopened) and their threads directly underneath](docs/screenshots/pins-and-thread.png)
  12. ![The All feedback view: comments grouped by section, reopened first, with a tally and a Copy as text button](docs/screenshots/all-feedback.png)
  13. ## Requirements
  14. - **Claude Code** with the Artifact and ArtifactData tools, so pages can be published as claude.ai artifacts with the `db` and `user` capabilities.
  15. - **Reviewers on claude.ai.** You share the page from its Share menu. Reviewers need **Contributor** access to comment; Viewers and Commenters can only read.
  16. - **Node 18 or later** for the build, mock server and test scripts. They have no dependencies.
  17. - **The Playwright MCP** to capture screens and run the mock test.
  18. - Optional: the **Atlassian MCP** (or your tracker's equivalent) to post the page's link on each ticket.
  19. ## Install
  20. Copy the skill folder into your personal skills folder:
  21. ```sh
  22. git clone https://github.com/suiyangqiu/design-review-page.git
  23. cp -r design-review-page/skills/design-review-page ~/.claude/skills/
  24. ```
  25. On Windows PowerShell:
  26. ```powershell
  27. git clone https://github.com/suiyangqiu/design-review-page.git
  28. Copy-Item -Recurse design-review-page\skills\design-review-page $HOME\.claude\skills\
  29. ```
  30. Or put it in a project's `.claude/skills/` folder to share it with that repo's team.
  31. ## Use
  32. | Command | What it does |
  33. |---|---|
  34. | `/design-review-page <tickets, PR or branch>` | Build a new page: scope it, capture the screens, write `review.json`, build, test on the mock, publish. |
  35. | `/design-review-page update <artifact url>` | Add or retake screens, edit the text, republish. Comments are backed up first and kept. |
  36. | `/design-review-page feedback <artifact url>` | Read the comments, summarise them by section, and act on them with you. |
  37. Claude also picks the skill up when you ask for "a review page for the PO", "screenshots the designers can comment on" and the like.
  38. ## Try the page locally
  39. The repo has a made-up example (a shop called Larkspur Goods, with invented data) you can build and click through without Claude:
  40. ```sh
  41. node skills/design-review-page/scripts/build-page.cjs examples/storefront-search/review.json --out build
  42. node skills/design-review-page/scripts/serve-mock.cjs build --port 18765
  43. ```
  44. Open http://127.0.0.1:18765/. The mock keeps comments in `sessionStorage`. To see the page as someone else, set `sessionStorage.mockme` to `u_reviewer`, `u_owner` or `u_viewer` in the browser console and reload; `sessionStorage.mockro = "1"` makes you read-only.
  45. To run the full mock flow test, point the Playwright MCP's `browser_run_code_unsafe` at a copy of `skills/design-review-page/scripts/mock-flow-test.js` (set `BASE` to your port). It returns `pass: true` with 36 named checks.
  46. ## What's in the box
  47. ```
  48. skills/design-review-page/
  49. SKILL.md the three modes, settings and hard rules
  50. assets/review-page.html the page template: layout, comment system, All feedback view
  51. references/
  52. review-json.md every review.json field, choosing sections, writing for reviewers
  53. capturing-screens.md worktrees, the Playwright MCP, red boxes, forcing loading/empty/failure
  54. comments-data.md the comment rows, reading feedback, backups and restores
  55. scripts/
  56. build-page.cjs checks review.json and builds index.html
  57. serve-mock.cjs serves a built page with a stand-in for the artifact runtime
  58. mock-claude.js that stand-in: comments in sessionStorage, three made-up people
  59. mock-flow-test.js drives the comment flows end to end
  60. examples/storefront-search/ review.json and screenshots for the made-up example
  61. ```
  62. ## Defaults you may want to change
  63. - **House style.** The build warns on en and em dashes, and the skill writes every PR as `[repo #N](link)`. Change these in `SKILL.md` (hard rule 9) and `build-page.cjs` if your team writes differently.
  64. - **Ticket links.** Set `jiraBase` in `review.json` to the URL your ticket keys are appended to (`https://your-site.atlassian.net/browse/`). Without it, keys show as plain text.
  65. - **Dates.** Comment times use each viewer's own locale, or `locale` in `review.json` (`en-US`, `en-AU`) to fix one.
  66. - **Viewport.** Screens are captured at 1440x900 unless the change is about another size.
  67. ## License
  68. [MIT](LICENSE)

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.