.cursor/skills/before-and-after/SKILL.md
Captures before/after screenshots of web pages or elements for visual comparison. Use when user says "take before and after", "screenshot comparison", "visual diff", "PR screenshots", "compare old and new", or needs to document UI changes. Accepts two URLs (file://, http://, https://) or two image paths.
npx skillsauth add jyrrahcc/verifiedphonesph before-and-afterInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Package:
@vercel/before-and-afterNever usebefore-and-after(wrong package).
DO NOT:
--full unless user explicitly asks for full page / full scroll captureDO:
--markdown when user wants PR integration or markdown output--mobile / --tablet if user mentions phone, mobile, tablet, responsive, etc.which before-and-after || npm install -g @vercel/before-and-after.vercel.app URL: curl -s -o /dev/null -w "%{http_code}" "<url>" (401/403 = protected)before-and-after "<before-url>" "<after-url>"./scripts/upload-and-copy.sh <before.png> <after.png> --markdowngh pr edit to append markdownNever skip steps 1-2.
# Basic usage
before-and-after <before-url> <after-url>
# With selector
before-and-after url1 url2 ".hero-section"
# Different selectors for each
before-and-after url1 url2 ".old-card" ".new-card"
# Viewports
before-and-after url1 url2 --mobile # 375x812
before-and-after url1 url2 --tablet # 768x1024
before-and-after url1 url2 --full # full scroll
# From existing images
before-and-after before.png after.png --markdown
# Via npx (use full package name!)
npx @vercel/before-and-after url1 url2
| Flag | Description |
|------|-------------|
| -m, --mobile | Mobile viewport (375x812) |
| -t, --tablet | Tablet viewport (768x1024) |
| --size <WxH> | Custom viewport |
| -f, --full | Full scrollable page |
| -s, --selector | CSS selector to capture |
| -o, --output | Output directory (default: ~/Downloads) |
| --markdown | Upload images & output markdown table |
| --upload-url <url> | Custom upload endpoint (default: 0x0.st) |
# Default (0x0.st - no signup needed)
./scripts/upload-and-copy.sh before.png after.png --markdown
# GitHub Gist
IMAGE_ADAPTER=gist ./scripts/upload-and-copy.sh before.png after.png --markdown
If .vercel.app URL returns 401/403:
which vercel && vercel whoamivercel inspect <url> to get bypass token# Check for gh CLI
which gh
# Get current PR
gh pr view --json number,body
# Append screenshots to PR body
gh pr edit <number> --body "<existing-body>
## Before and After
<generated-markdown>"
If no gh CLI: output markdown and tell user to paste manually.
| Error | Fix |
|-------|-----|
| command not found | npm install -g @vercel/before-and-after |
| could not determine executable | Use npx @vercel/before-and-after (full name) |
| 401/403 on .vercel.app | See Vercel protection section |
| Element not found | Verify selector exists on page |
development
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
development
Emulated Vercel REST API for local development and testing. Use when the user needs to interact with Vercel API endpoints locally, test Vercel integrations, emulate projects/deployments/domains, set up Vercel OAuth flows, manage environment variables, or test without hitting the real Vercel API. Triggers include "Vercel API", "emulate Vercel", "mock Vercel", "test Vercel OAuth", "Vercel integration", "local Vercel", or any task requiring a local Vercel API.
development
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
development
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.