levy-street/world-of-claudecraft / .claude/skills/pr-screenshots
pr-screenshots
VerifiedCapture before/after screenshots for a World of ClaudeCraft PR (desktop and mobile), commit them under docs/screenshots, and reference them from the PR body. Use when a change is visual (render, HUD, CSS, content models, windows), when the PR template's screenshot requirement applies, or when asked to screenshot the game for a review or comparison. Covers the change-aware capture tooling, the before/after protocol, and the known puppeteer/CDP traps.
PR screenshots
The repo rule (root CLAUDE.md): a visual change ships with before/after screenshots,
desktop and mobile where relevant, committed under docs/screenshots/ and referenced from
the PR body. This skill is the capture recipe.
1. Use the change-aware tooling first
With npm run dev running (serves :5173):
git diff <base>...HEAD > /tmp/pr.diff
BROWSER_PATH=/path/to/chrome DIFF_FILE=/tmp/pr.diff SHOTS_DIR=pr-shots \
node scripts/pr_screenshots.mjs
scripts/pr_screenshots.mjs drives the OFFLINE client through the shared entry flow
(scripts/enter_offline_game.mjs, which handles the intro overlay that otherwise hides
#ui) and decides WHAT to shoot from the diff: specific windows via the target table,
the generic desktop/mobile HUD for broad visual changes, and nothing for non-visual diffs.
Adding coverage is one entry in scripts/pr_shot_targets.mjs, not a new script. Each
target maps changed-path substrings to a bring-up recipe (driving window.__game) and a
clip region. Only write a bespoke scripts/<thing>_shot.mjs when the flow genuinely cannot
be a target entry (for example an online-only or multi-client scene).
Standing capture rule (maintainer preference): every capture rig seeds the LOWEST
graphics preset before the app boots. Seed it the way the existing rigs seed presets,
via page.evaluateOnNewDocument writing localStorage woc_settings with
{ graphicsPreset: 1 } before page.goto. scripts/climb_stall_shot.mjs shows the
seeding MECHANISM, but copy only the shape: that rig deliberately seeds a high profile
(preset 5, the Advanced expert profile whose sub-dials it also seeds; the ladder in
src/ui/options_view.ts tops out at the Insane preset above Ultra) because its purpose
is a graphics shot. The default preset is not the lowest either (src/game/settings.ts
pins the range), so an unseeded rig is NOT lowest. The one
exception: shots whose PURPOSE is a graphics comparison (preset ladders, VFX quality,
shadow tiers) keep the preset the comparison needs.
2. Before/after protocol
- Capture AFTER on your branch.
git stashor check out the base commit in a scratch worktree, capture BEFORE with the same script and targets, restore.- The Vite dev client picks up source changes live, but
npm run serverbundles at START: after any branch flip, restart the server before online captures or you will shoot a stale bundle. - Move the keepers to
docs/screenshots/<slug>/before-*.png/after-*.png, commit them, and reference them from the PR body with repo-relative links. - For screenshots in a REVIEW COMMENT on someone else's PR: GitHub
user-attachmentsupload URLs only work from the web UI. Push the PNGs to a gist and embed the gist's raw URLs instead.
3. Traps that have burned sessions before
- Viewport sizing: after
page.setViewport,window.innerWidthcan be stale. Use raw CDPEmulation.setDeviceMetricsOverridefor exact metrics, and remember CDPPage.captureScreenshotshoots the WINDOW, not the viewport: clip explicitly. page.evaluateunder tsx: tsx's keepNames injects__nameand breaks nested functions inside evaluate callbacks. Pass string-form bodies toevaluateOnNewDocument/evaluatewhen a script runs under tsx.window.__gameproves reachability only to the window boundary. For a claim about real behavior, drive the actual bound key or click, not the debug hook.- Mobile is landscape-only in-game on the web client: use landscape device metrics for mobile HUD shots (the shell/guide/admin pages allow portrait).
- Dev commands: captures that teleport, level, or grant items need a server started
with
ALLOW_DEV_COMMANDS=1(dev only, never production).
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |