Use this skill for character creation: "character design", "player character", "NPC design", "antagonist", "villain", "boss design", "companion", "character arc". **Load references when:** - Full character worksheet → `references/character-worksheet.md` - NPC roles and patterns → `references/npc-roles.md` - Villain/boss design → `references/antagonist-design.md`
/plugin marketplace add nethercore-systems/nethercore-ai-plugins/plugin install game-design@nethercore-ai-pluginsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
references/antagonist-design.mdreferences/character-worksheet.mdreferences/npc-roles.mdFrameworks for designing memorable characters. Every character exists to serve a purpose: design function before personality, then add personality that reinforces function.
| Type | Function |
|---|---|
| Player characters | Express player agency and skill |
| NPCs | Provide services, information, emotional connection |
| Antagonists | Create obstacles and motivation |
| Companions | Expand gameplay and relationships |
Hook formula: "The [adjective] [archetype] who [unique trait or contradiction]"
Three tests:
| Approach | Pros | Cons |
|---|---|---|
| Blank slate | Player projects themselves | Less narrative depth |
| Defined character | Stronger story potential | May not identify |
| Hybrid | Balance of both | Complex to design |
Key questions: Does PC speak? How much backstory? What abilities start/unlock?
| Role | Function | Example |
|---|---|---|
| Mentor | Teaches, guides | Tutorial giver, wise figure |
| Merchant | Trades resources | Shopkeeper |
| Quest giver | Provides objectives | Village elder |
| Ally | Assists gameplay | Combat helper |
| Gatekeeper | Controls access | Guard |
| Flavor | World texture | Townsfolk |
Key Rule: Every NPC serves at least one clear function.
See references/npc-roles.md for detailed patterns.
| Type | Relationship | Design Focus |
|---|---|---|
| Rival | Equal competitor | Mirror of player |
| Tyrant | Power imbalance | Oppressive presence |
| Monster | Inhuman threat | Primal fear |
| Fallen hero | What player could become | Tragic connection |
See references/antagonist-design.md for boss design patterns.
WANT: What they desire
NEED: What they actually need (often different)
LIE: False belief holding them back
TRUTH: Realization enabling growth
CHANGE: How they're different at end
| Arc | Pattern | Payoff |
|---|---|---|
| Positive | Flaw → Growth | Hope, satisfaction |
| Negative | Virtue → Fall | Tragedy, warning |
| Flat | Tested → Proven | Affirmation |
| Model | Description | Best For |
|---|---|---|
| Unlock | Gain new abilities | Metroidvanias |
| Upgrade | Improve existing | Roguelikes, RPGs |
| Transform | Fundamentally change | Story-driven |
| Equip | Change via items | Loot games |
| Master | Player skill grows | Skill-based |
Law of Character Economy: More characters = less development per character.
| Scope | Character Count |
|---|---|
| Game jam | 3-5 total |
| Short game | 5-10 |
| Medium game | 10-20 |
| Long game | 20-40 |
Focus resources on: PC (most screen time), main antagonist (most conflict), key NPCs (most interaction).
narrative-design — Character arcs and storyworld-building — Characters in contextgame-balance — Balancing abilitiesThis skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.