This skill should be used when the user asks about "creative vision", "game vision", "creative direction", "overall feel", "creative pillars", "design intent", "vision alignment", "creative drift", "game identity", "player experience", "emotional design", or discusses establishing the overall creative direction and ensuring implementation matches vision. Provides creative direction framework for holistic project coherence.
/plugin marketplace add nethercore-systems/nethercore-ai-plugins/plugin install creative-direction@nethercore-ai-pluginsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
references/emotional-design.mdreferences/pillar-design.mdEstablish and maintain creative coherence by defining core vision and ensuring all disciplines serve it.
Creative Vision (What experience do we create?)
│
┌───────────────┼───────────────┐
▼ ▼ ▼
Art Vision Sound Vision Tech Vision
│ │ │
[Assets] [Audio] [Code]
Define 3-5 non-negotiable experience principles:
PILLAR: [Short Name]
STATEMENT: [What this means for the player]
MANIFESTS AS:
- Art: [How art supports this]
- Sound: [How sound supports this]
- Code: [How mechanics support this]
Example:
PILLAR: Atmospheric Dread
STATEMENT: Players should feel isolated and vulnerable
MANIFESTS AS:
- Art: Dark palettes, obscured vision, decay
- Sound: Sparse, ambient, silence as tool
- Code: Limited resources, no map, permadeath
One-paragraph core experience:
In [GAME], players experience [CORE EMOTION] through
[PRIMARY MECHANIC]. The world evokes [ATMOSPHERE] while
players [CORE VERB]. Success feels like [SUCCESS EMOTION]
and failure teaches [FAILURE LESSON].
For any work, map to pillars:
Ask: Does this reinforce the experience promise? Evoke intended emotions? Suit the audience?
Warning signs:
Response: Acknowledge → Trace origin → Evaluate (evolution vs loss?) → Decide → Document
| Situation | Primary Director |
|---|---|
| New feature | Creative |
| Asset review | Art/Sound |
| Performance issue | Tech |
| Milestone review | Creative + All |
Store vision in .studio/creative-direction.md.
references/pillar-design.md - Crafting effective pillarsreferences/emotional-design.md - Designing emotional experiencesThis 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 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 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.