一键导入
game-design
Game design principles. GDD structure, balancing, player psychology, progression.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Game design principles. GDD structure, balancing, player psychology, progression.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
API contract validator that ensures API responses match documented contracts and catches breaking changes. Activate when validating API contracts, checking schema validation, detecting contract drift, comparing OpenAPI specs with implementation, finding undocumented endpoints, or auditing response shapes.
API contract validation and Zod-first design patterns. Use when designing, implementing, or validating API routes and schemas.
API design, style selection, and contract validation. REST vs GraphQL vs tRPC decision-making, Zod-first validation, response formats, versioning, pagination, API contracts. Use when designing APIs, choosing REST vs GraphQL, implementing API validation, creating Zod schemas, or defining API contracts.
API design principles and decision-making. REST vs GraphQL vs tRPC selection, response formats, versioning, pagination.
Main application building orchestrator. Creates full-stack applications from natural language requests. Determines project type, selects tech stack, coordinates agents.
Project scaffolding templates for new applications. Use when creating new projects from scratch. Contains 12 templates for various tech stacks.
| name | game-design |
| description | Game design principles. GDD structure, balancing, player psychology, progression. |
| tools | Read, Glob, Grep |
Design thinking for engaging games.
Every game needs a fun 30-second loop:
1. ACTION → Player does something
2. FEEDBACK → Game responds
3. REWARD → Player feels good
4. REPEAT
| Genre | Core Loop |
|---|---|
| Platformer | Run → Jump → Land → Collect |
| Shooter | Aim → Shoot → Kill → Loot |
| Puzzle | Observe → Think → Solve → Advance |
| RPG | Explore → Fight → Level → Gear |
| 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 |
| Type | Driven By |
|---|---|
| Achiever | Goals, completion |
| Explorer | Discovery, secrets |
| Socializer | Interaction, community |
| Killer | Competition, dominance |
| Schedule | Effect | Use |
|---|---|---|
| Fixed | Predictable | Milestone rewards |
| Variable | Addictive | Loot drops |
| Ratio | Effort-based | Grind games |
Too Hard → Frustration → Quit
Too Easy → Boredom → Quit
Just Right → Flow → Engagement
| Strategy | How |
|---|---|
| Dynamic | Adjust to player skill |
| Selection | Let player choose |
| Accessibility | Options for all |
| Type | Example |
|---|---|
| Skill | Player gets better |
| Power | Character gets stronger |
| Content | New areas unlock |
| Story | Narrative advances |
| ❌ 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.