Sceneproof

Use whenever a change can alter rendered output — components, styles, layout, SVG, canvas, scenes, cameras, lights, materials, animation — before claiming that something looks right, is visible, or renders correctly, and when diagnosing why something is invisible, black, clipped, misframed, or mis-lit.

43 stars 4 forksFrontend & Design

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add ReyJ94/SceneProof --skill sceneproof
Manual install
git clone --depth 1 https://github.com/ReyJ94/SceneProof.git /tmp/SceneProof
mkdir -p ~/.claude/skills
cp -r /tmp/SceneProof/skills/sceneproof ~/.claude/skills/sceneproof

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# SceneProof: seeing before claiming

You have a tool that can render the real source and show you real structure.
That changes what you are allowed to claim. A passing build, a clean
typecheck, or code that "should" produce the right output is **zero visual
evidence**. If you are about to assert anything about appearance, you either
have an artifact you actually looked at, or you say plainly that the visual
result is unverified.

The CLI (`sceneproof --help`, per-command help, and mechanically grounded
`suggestions` when available) tells you what commands exist and what evidence
it can gather next.
Before a serious review, run `sceneproof --version` and `sceneproof doctor`.
Do not spend a debugging session against a stale installed binary; inspect the
doctor installation block and use its reinstall command when installed-bin
readiness fails.
Run it directly on the host: it renders from source and needs no sandboxed
desktop or browser automation. When it lacks a capability a claim needs, report
the gap for the tool's own repository instead of working around it with ad-hoc
screenshots.
This skill is about something the CLI cannot do for you: choosing what
uncertainty to resolve, in what order, and judging the result honestly.

## First: name the purpose

Before claim-directed work, state the visual claim as a falsifiable question.
"Is the price label legible at the size it ships at?", "Is the selected card
Read the full skill on GitHub

Details

Skill name
sceneproof
Path
skills/sceneproof/SKILL.md
License
MIT
Repo updated
3 November 2026

FAQ

What does the Sceneproof skill do?

Use whenever a change can alter rendered output — components, styles, layout, SVG, canvas, scenes, cameras, lights, materials, animation — before claiming that something looks right, is visible, or renders correctly, and when diagnosing why something is invisible, black, clipped, misframed, or mis-lit.

How do I install the Sceneproof skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add ReyJ94/SceneProof --skill sceneproof. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Sceneproof popular?

It lives in ReyJ94/SceneProof, which has 43 GitHub stars and 4 forks.

Related skills

Don Norman Principles Audit

74

mastepanoski/claude-skills

Evaluate UX/UI using Don Norman's 7 fundamental design principles from The Design of Everyday Things. Audit discoverability, affordances, signifiers, feedback, mapping, constraints and conceptual models.

Frontend & Design

Gradientdeck

46

VenoM9078/gradientdeck-skill

Design judgment for building and reviewing user interfaces. Use when creating or restyling a landing page, website, app screen, dashboard, component or design system; when adding a page to an existing codebase so it matches; when asked to make UI look better, less generic, more polished, bolder or quieter; or when critiquing, auditing or polishing a design. Works for any web stack.

Frontend & Design

Nielsen Heuristics Audit

74

mastepanoski/claude-skills

Evaluate UX/UI using Jakob Nielsen's 10 usability heuristics. Comprehensive audit of visibility, control, consistency, error prevention, recognition, flexibility, aesthetics, error recovery, and documentation.

Frontend & Design

Better UI

107

Dimon94/skills

Polishes and improves the UI in your project. Covers concentric border radius, optical alignment, surface depth, contextual icons, hit areas and more.

Frontend & Design21

UI Design Review

74

mastepanoski/claude-skills

Comprehensive visual design and aesthetics evaluation. Analyzes typography, color, spacing, hierarchy, consistency, branding, and current product-category conventions for polished, professional interfaces.

Frontend & Design

Better Typography

107

Dimon94/skills

Focuses on type scale, spacing, sizing, variable fonts, OpenType features, wrapping, truncation and other details that make typography feel great across your product.

Frontend & Design21

Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.