← ClaudeAtlas

review-gallerylisted

Show visual work to the user as a local HTML review page - every screenshot, generated image, design option and before/after (GIF for anything that moves) in numbered sections, each with Looks good / Needs work buttons or an option pick, a note box, and a Copy feedback button whose numbered text the user pastes back for the next round. Use this by default whenever you have UI, screens, game art, icons, illustrations, VFX, animations, logos, layouts or any other visual result to show or to get feedback on - for requests like "show me the screens", "put the screenshots together", "make a few options", "mockups", "before and after", "compare these", "which one is better", "let me pick", "improve the UI", "let me mark what to fix", "review", "feedback" in any language - and whenever the user pastes back text that starts with a page header such as "UI round 2 feedback" followed by lines like "12. [Hero detail] Needs work - ...". Prefer it over describing images in chat or sending loose files.
RevStudio/review-gallery · ★ 9 · Web & Frontend · score 82
Install: claude install-skill RevStudio/review-gallery
# Review gallery Visual work is judged by looking. Describing it in chat, or handing over a folder of files, makes the user do the sorting. This skill turns a round of visual work into one local page they read top to bottom, mark, comment on and paste back as a numbered list, and turns that list into the next round of work. ## The loop 1. **Capture** the real thing at the sizes it is used (phone and desktop for UIs, in context and a 100 % crop for art). Anything that moves becomes a looping GIF, side by side BEFORE | AFTER for a change (`scripts/make_gif.py`). Details: `references/capture.md`. 2. **Write a spec** (`review.json`): title, a short intro, and one item per request / screen / asset, each with the user's number, their words quoted, plain "what I did" lines, and before / after / options media. Format and the three page shapes (inventory, fix round, options): `references/spec.md`. 3. **Build and open**: `python <skill>/scripts/build_review.py review.json --open` writes `index.html`, `img/` thumbnails and `media/` next to the spec and opens the page in the user's browser. It exits 1 and lists any missing file; fix those first. Open the page the moment the round's work is complete, without waiting to be asked, and do not just print the path. 4. **Tell them how to answer** in one or two lines ("mark each item, press Copy feedback and paste it here"), then stop and let them review. Do not keep piling on work they have not seen. When parallel age