Gsp procedural art direction
Skill mike007jd/game-superpowers/publish/clawhub/gsp-procedural-art-direction
Use when procedural visual identity, shaders, particles, SVG systems, or UI recipes are part of the game deliverable.From its SKILL.md
npx -y skills add mike007jd/game-superpowers --skill gsp-procedural-art-directionAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
1.0 KB, 181 tokens by cl100k_base, as published. Nobody here has run it
Game Procedural Art Direction
Goal
Make the build visually intentional through programmable systems.
Use when
- the user explicitly wants procedural art
- the game needs a stronger visual identity to meet the quality target
- the result currently works but looks generic or underdesigned
Rules
- Treat requested visual style as part of the product, not optional fluff.
- Prefer reusable visual recipes over one-off hacks.
- Protect readability while adding style.
- For polished prototypes, visual direction belongs in scope now, not “later someday.”
Outputs
Follow the gsp-orchestrator output strategy:
- inline (default): present visual direction decisions in conversation.
- minimal or full: update
docs/game-studio/spec.mdordocs/game-studio/ux-flow.mdif visual rules or UI behavior change materially.
What ships with it: 5 files
4.1 KB alongside SKILL.md
examples/
- usage.md649 B
tests/
- smoke.md467 B
- CHANGELOG.md217 B
- MANIFEST.yaml1.7 KB
- README.md1.0 KB