Gsp screenshot critic
Skill mike007jd/game-superpowers/publish/clawhub/gsp-screenshot-critic
Use when critiquing screenshots or visual captures for readability, hierarchy, and target-quality fit.From its SKILL.md
npx -y skills add mike007jd/game-superpowers --skill gsp-screenshot-criticAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
1.3 KB, 256 tokens by cl100k_base, as published. Nobody here has run it
Game Screenshot Critic
Goal
Use visual evidence to judge whether the build actually looks understandable and good enough for the target.
Use
./shared/checklists/screenshot-critic-output-checklist.md./shared/checklists/ui-ux-hard-rules.md
Focus
- information hierarchy
- clutter
- readability
- playfield protection
- visual coherence
- perceived completeness
- whether feedback cues are visible
- whether persistent HUD feels disciplined or bloated
By target
- first-playable: look for basic readability and affordance
- polished-prototype: hold a higher bar for coherence and perceived finish
- production-feature / live-patch: check consistency with the rest of the product
Outputs
Follow the gsp-orchestrator output strategy:
- inline (default): present critique findings and repair priorities in conversation.
- minimal or full: append to
docs/game-studio/quality-report.md.
Reporting rules
Separate:
- confirmed strengths
- confirmed issues
- inferred risks
- repair priorities
Important
Do not overstate what a screenshot proves. Use screenshots to strengthen evidence, not to hallucinate certainty.
What ships with it: 7 files
6.9 KB alongside SKILL.md
examples/
- usage.md621 B
tests/
- smoke.md453 B
- CHANGELOG.md210 B
- MANIFEST.yaml2.2 KB
- README.md1006 B