Run a UI/UX design pass on an existing game to improve visuals, atmosphere, and game feel. No design experience needed — this command analyzes your game and applies proven visual patterns.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiondesign-gameExecute the skills CLI command in your project's root directory to begin installation:
Fetches design-game from opusgamelabs/game-creator and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate design-game. Access via /design-game in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
2
total installs
2
this week
93
GitHub stars
0
upvotes
Run in your terminal
2
installs
2
this week
93
stars
Run a UI/UX design pass on an existing game to improve visuals, atmosphere, and game feel. No design experience needed — this command analyzes your game and applies proven visual patterns.
Analyze the game at $ARGUMENTS (or the current directory if no path given).
First, load the game-designer skill to get the full design vocabulary and patterns.
package.json to identify the enginesrc/core/Constants.js for the current color palette and configsrc/core/EventBus.js for existing eventsScore each area 1-5 and present as a table:
| Area | Score | Notes |
|---|---|---|
| Background & Atmosphere | ||
| Color Palette | ||
| Animations & Tweens | ||
| Particle Effects | ||
| Screen Transitions | ||
| Typography | ||
| Game Feel / Juice | ||
| Game Over | ||
| Expression Usage | If personality characters exist, score how reactively expressions change to game events. Score 1 if expressions never change. |
Then list the top improvements ranked by visual impact, with a plain-English description of what each one does (e.g., "Add a sky gradient so the background looks like a real sky instead of a flat color").
Ask the user which improvements they want, or implement all if they say so. Follow the game-designer skill patterns:
Constants.jsnpm run build to confirm no errors/design-game examples/asteroid-dodge
Result: Audits visuals → scores Background 2/5, Particles 1/5, Typography 3/5 → adds sky gradient background, star parallax, explosion particles on asteroid destroy, screen shake on hit, smooth scene transitions. All values in Constants.js.
Cause: Too many particle emitters or gradient fills per frame. Fix: Limit active particles (pool and reuse). Use cached gradient textures instead of recreating per-frame.
Cause: Hardcoded pixel positions instead of using PX scale factor. Fix: All positions and sizes should use Constants.js PX-relative values.
Tell the user:
Your game looks much better now! Next, run
/game-creator:add-audioto add chiptune background music and retro sound effects — all procedurally generated, no audio files needed.Pipeline progress:
/make-game→/design-game→/add-audio→/qa-game→/review-game
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
omer-metin/skills-for-antigravity
anthropics/claude-code
sickn33/antigravity-awesome-skills
leonxlnx/taste-skill
erichowens/some_claude_skills
hyperb1iss/hyperskills
design-game has been reliable in day-to-day use. Documentation quality is above average for community skills.
Registry listing for design-game matched our evaluation — installs cleanly and behaves as described in the markdown.
Solid pick for teams standardizing on skills: design-game is focused, and the summary matches what you get after install.
Keeps context tight: design-game is the kind of skill you can hand to a new teammate without a long onboarding doc.
Useful defaults in design-game — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
design-game reduced setup friction for our internal harness; good balance of opinion and flexibility.
Keeps context tight: design-game is the kind of skill you can hand to a new teammate without a long onboarding doc.
Solid pick for teams standardizing on skills: design-game is focused, and the summary matches what you get after install.
design-game is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Registry listing for design-game matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 60