rjv-replica-screenshotlisted
Install: claude install-skill rjvim/ai-skills
# Replica screenshot from real payload
Sometimes you fix a UI-visible bug but **can't screenshot the real screen**:
the dev build is broken by an unrelated import, the state is impractical to
stage, the route is feature-flagged, or the change is backend-only and the page
won't render locally. You still want a credible screenshot in the PR.
The move: render a **faithful HTML replica of the actual component**, populated
with the **real server payload strings**, and screenshot that. Done honestly it
is real evidence: the exact bytes the component renders, in the component's own
layout.
## When to use
Use it only when both hold:
- The real UI won't render locally, and the change is visible in the UI.
- You can obtain the exact strings the component receives (see Step 1).
Otherwise:
- The real page renders: screenshot the real page. A replica is a fallback
for a screen you cannot reach.
- Any value would have to be invented: report the payload as text instead,
and say the screen couldn't render.
## The honesty contract (non-negotiable)
1. **Real data only.** Every value in the replica is the exact string the real
code path emits, dumped from it. A value you typed makes the image a mockup.
2. **Faithful markup.** Mirror the real component's DOM structure and Tailwind
classes so the replica looks like the product's own row or card. Read the
component first.
3. **Label it.** A caption in the image and a line in the PR body state it is
rendered from the live p