capture-screenshots
Skill0 starsChanged 15 days agoMITView on GitHub
Capture screenshots of each state, size and setting as evidence for a PR. Use for each UI change.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- navjyotnishant/nj-agentstheir own version, first seen Oct 15, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- navjyotnishant/nj-agents★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository25 other files it gives its agents.
- AGENTS.mdAGENTS.md
- templates/CLAUDE.mdCLAUDE.md
- a11y-auditSkill
- architecture-reviewSkill
- bootstrap-projectSkill
- customizeSkill
- deliver-featureSkill
- design-reviewSkill
- docs-upkeepSkill
- fix-bugSkill
- handoffSkill
- implementSkill
- leadSkill
- log-decisionSkill
- refine-requirementsSkill
- release-readinessSkill
- reproduce-in-worktreeSkill
- security-auditSkill
- ship-prSkill
- start-taskSkill
- sync-branchSkill
- threat-modelSkill
- verify-featureSkill
- vet-dependencySkill
- write-adrSkill
The file
Files
Capture screenshots
Playbook files named here: when the project has its own copy at
.playbook/local/<same path>, use that copy instead.
Request: $ARGUMENTS
Drivers and their traps: ${CLAUDE_PLUGIN_ROOT}/principles/08-testing-qa.md → "Drivers". Ready-made scripts: ${CLAUDE_PLUGIN_ROOT}/templates/testing/.
1. Decide the matrix (keep it to what the change touches)
| Default | Add when it matters | |
| States | the populated default | loading, error, offline, empty |
| Sizes | 375 px mobile and 1280 px desktop | 320 px (reflow), 768 px tablet, 200% zoom |
| Settings | light, normal motion | dark (colorScheme), reduced motion |
2. Capture
- Web, with Playwright: copy
templates/testing/playwright.config.tsandscreenshots.spec.ts(if the project has no equivalent), list the routes and states, and runnpx playwright test screenshots.spec.ts. To explore before scripting, use the agent's browser tools (the built-in browser, Claude in Chrome or the Playwright MCP server), then put the steps in the spec so they're repeatable. - Zoom: 200% browser zoom on a 1280 px window is a 640 CSS px viewport (add
deviceScaleFactor: 2for sharp text), and 400% is 320 px. Capture those viewports. - Name the files
<screen>-<state>-<variant>.png(settings-export-progress-zoom200.png) and put them inscreenshots/<ticket>/, which is gitignored.
3. Check every image
Open each one and look:
- Is it the right screen and state?
- Is any text clipped or overlapping?
- Is a dev overlay or a loading spinner covering it?
- Is a system dialog in the way?
A blank or half-drawn image usually means the page hadn't finished loading, a request was blocked, or the capture ran mid-animation: fix the cause and recapture. Never ship an image you haven't looked at.
4. Hand over
- List the files with one line each (what it shows) in your handoff.
ship-prpublishes them:templates/testing/push-screenshots.sh <PR> <files…>pushes to ascreenshotsbranch, never the default branch.- Reset every setting you changed (zoom, colour scheme, reduced motion), and stop what you started.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

