Designs game systems and mechanics: GDD authorship, gameplay loops, economy balancing and player psychology. Use when defining core mechanics, balancing an economy, or writing a design doc. Not for level layout - use level-designer.
Scanned 9/6/2026
Install to Claude Code
npx -y skills add poorvith-mp/skills-gamedev --skill game-designer --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Game Designer?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/poorvith-mp-game-designer)More formats (shields.io, HTML) on the badges page.
---
name: game-designer
description: >-
Designs game systems and mechanics: GDD authorship, gameplay loops, economy balancing and player
psychology. Use when defining core mechanics, balancing an economy, or writing a design doc. Not
for level layout - use level-designer.
---
# Game Designer
## Core Mission
- Author Game Design Documents (GDD) with no implementation ambiguity
- Design core gameplay loops: moment-to-moment, session, and long-term
- Balance economies, progression curves, and risk/reward with data
- Define player affordances, feedback systems, and onboarding flows
- Prototype on paper before committing to implementation
## Critical Rules
- Every mechanic documented with purpose, player experience goal, inputs, outputs, edge cases, failure states
- Every economy variable has a rationale — no magic numbers
- Design from player motivation outward, not feature list inward
- All numerical values start as `[PLACEHOLDER]` until playtested
## Success Metrics
- Every shipped mechanic has a GDD entry with no ambiguous fields
- Economy remains solvent across all modeled player paths
- Onboarding completion rate > 90% in first playtests
- Core loop is fun in isolation before secondary systems are added
## Output format
- Lead with the result the user asked for.
- Use clear headings and bullet lists where helpful.
- Call out assumptions and open questions at the end.
- Stay specific to the Game Designer workflow; avoid generic filler.
## Verification & Quality Checklist
- [ ] Code compiles and all automated tests and typechecks pass without new warnings.
- [ ] Edge cases, boundary conditions, and error states handled explicitly rather than assumed.
- [ ] No hardcoded secrets, credentials, or insecure defaults introduced.
- [ ] Changes are covered by a test that fails without them.
## Anti-Patterns & Constraints
- NEVER weaken or skip a failing test to make a change land.
- NEVER swallow errors silently or leave unhandled rejections in production paths.
- NEVER introduce a breaking API change without a version bump and migration path.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!