CongDon1207/game-design
.agent/skills/game-development/game-design/SKILL.md
Game design principles. GDD structure, balancing, player psychology, progression.
$ install --global
skillsauthnpx skillsauth add CongDon1207/AGENTS.md game-designInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 29, 2026, 6:14 PM8.5s1 file scanned
SKILL.md
- name:
- game-design
- description:
- Game design principles. GDD structure, balancing, player psychology, progression.
- allowed-tools:
- Read, Glob, Grep
Game Design Principles
Design thinking for engaging games.
1. Core Loop Design
The 30-Second Test
Every game needs a fun 30-second loop:
1. ACTION → Player does something
2. FEEDBACK → Game responds
3. REWARD → Player feels good
4. REPEAT
Loop Examples
| Genre | Core Loop | |-------|-----------| | Platformer | Run → Jump → Land → Collect | | Shooter | Aim → Shoot → Kill → Loot | | Puzzle | Observe → Think → Solve → Advance | | RPG | Explore → Fight → Level → Gear |
2. Game Design Document (GDD)
Essential Sections
| Section | Content | |---------|---------| | Pitch | One-sentence description | | Core Loop | 30-second gameplay | | Mechanics | How systems work | | Progression | How player advances | | Art Style | Visual direction | | Audio | Sound direction |
Principles
- Keep it living (update regularly)
- Visuals help communicate
- Less is more (start small)
3. Player Psychology
Motivation Types
| Type | Driven By | |------|-----------| | Achiever | Goals, completion | | Explorer | Discovery, secrets | | Socializer | Interaction, community | | Killer | Competition, dominance |
Reward Schedules
| Schedule | Effect | Use | |----------|--------|-----| | Fixed | Predictable | Milestone rewards | | Variable | Addictive | Loot drops | | Ratio | Effort-based | Grind games |
4. Difficulty Balancing
Flow State
Too Hard → Frustration → Quit
Too Easy → Boredom → Quit
Just Right → Flow → Engagement
Balancing Strategies
| Strategy | How | |----------|-----| | Dynamic | Adjust to player skill | | Selection | Let player choose | | Accessibility | Options for all |
5. Progression Design
Progression Types
| Type | Example | |------|---------| | Skill | Player gets better | | Power | Character gets stronger | | Content | New areas unlock | | Story | Narrative advances |
Pacing Principles
- Early wins (hook quickly)
- Gradually increase challenge
- Rest beats between intensity
- Meaningful choices
6. Anti-Patterns
| ❌ Don't | ✅ Do | |----------|-------| | Design in isolation | Playtest constantly | | Polish before fun | Prototype first | | Force one way to play | Allow player expression | | Punish excessively | Reward progress |
Remember: Fun is discovered through iteration, not designed on paper.
Related Skills
CongDon1207/frontend-design
development
VerifiedTrustedCommunity
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications, OR when they provide screenshots/images/designs to replicate or draw inspiration from. For screenshot inputs, extracts design guidelines first using ai-multimodal analysis, then implements code following those guidelines. Generates creative, polished code that avoids generic AI aesthetics.
11SKILL.mdUpdated Apr 17, 2026
CongDon1207/feature-investigation
development
VerifiedTrustedCommunity
Use when the user asks to investigate, understand, explore, or explain how a feature works, asks about existing logic, or wants to understand code flow. Triggers on keywords like "how does", "explain", "investigate", "understand", "what does", "where is", "how works", "logic flow", "trace", "explore feature".
11SKILL.mdUpdated Apr 17, 2026
CongDon1207/feature-implementation
development
VerifiedTrustedCommunity
Use when the user asks to implement a new feature, enhancement, add functionality, build something new, or create new capabilities. Triggers on keywords like "implement", "add feature", "build", "create new", "develop", "enhancement".
11SKILL.mdUpdated Apr 17, 2026
CongDon1207/feature-docs
development
VerifiedTrustedCommunity
Use when the user asks to generate comprehensive feature documentation with verified test cases, create feature README with code evidence, or document a complete feature with test verification. Triggers on keywords like "feature documentation", "document feature", "comprehensive docs", "feature README", "test verification", "verified documentation".
11SKILL.mdUpdated Apr 17, 2026