preview-shots

Solid

Open image shots (screenshots, snapshot baselines, montages, renders) in ONE macOS Preview window so the user can eyeball them. Use when the user asks to open / show / pull up / review shots in Preview or Finder, or right after producing visual artifacts the user should look at before signing off.

Code & Development 43 stars 4 forks Updated 2 days ago Apache-2.0

Install

View on GitHub

Quality Score: 82/100

Stars 20%
55
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
85
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Preview Shots Put the review-worthy images in front of the user in a single Preview window they can flip through. ## Workflow 1. **Curate the set** — the images that answer "is this right?": the just-changed or just-blessed baselines, the integrated result, and the reference image when there's something to compare against. Don't dump every PNG in the folder; pick the smallest set that lets the user judge the change. If the user named specific shots, open exactly those. 2. **One window** — open them with a single `open -a Preview <path> <path> ...` call. One `open` invocation lands all the files in one window with a thumbnail sidebar; separate calls spawn separate windows. 3. **Caption them** — list one line per shot (what it is) so the user knows what they're flipping through. ## Rules - macOS only (`open`); pass absolute or repo-root-relative paths. - Order the files most-important-first; the first one is what Preview shows on open. - Review saved PNG/GIF artifacts, not live Chrome. Exact regression capture should run headless by default; only open Chrome when the user explicitly asks for a live browser or when reproducing a headful-only bug. - **One set at a time — never pile up windows.** Before opening a new set, close any open ones: `osascript -e 'tell application "Preview" to close every window'`. - **Close on unattended proceed.** When you opened shots for a non-blocking review and then move on without the user's response, close Preview afterward: `osa...

Details

Author
dzhng
Repository
dzhng/duet-agent
Created
5 months ago
Last Updated
2 days ago
Language
TypeScript
License
Apache-2.0

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Featured

preview

Stand up the project's live app and hand it to the user to try a change firsthand, then gate on their verdict before continuing. Use when the user asks to "preview the change", "let me try it", "spin up the app so I can test it", "set it up so I can poke at it", or before finalizing a UI/UX change that needs human eyes.

402 Updated 2 days ago
tobihagemann
Code & Development Listed

shotkit

Produce screenshots that look like a product shipped them — the way Shottr, CleanShot X or Screely do it: a clean deterministic capture, cropped at a real boundary, on a backdrop with padding, rounded corners, a layered shadow, optional macOS or browser window chrome, and arrows/numbered badges/blur redaction where they help. Use this whenever a screenshot is going to be *seen by someone else* — a marketing or landing page, a README or docs page, a changelog, a release post, an app store or Chrome Web Store listing, a slide, a design review — and whenever someone says their screenshots look bad, flat, cheap, amateur, inconsistent, blurry or "like a bug report", or asks to add a device frame, drop shadow, gradient background, padding or annotations to an image. Also use it to audit existing screenshots for clipped text, wrong resolution and mismatched sizes. Do NOT use it for screenshots you take to verify your own work or to debug a layout — those want the raw pixels, and framing them wastes time.

0 Updated 2 days ago
patlf
Web & Frontend Listed

preview-ui

Build and visually verify the Claude Code Tray window by launching it and capturing a screenshot. Use whenever a change touches MainWindow, any of its pages (SettingsPage / StatisticsPage / ContextPage) or any windowed UI, before claiming the layout works.

4 Updated 1 weeks ago
alegauss