Dependency chains in game development - what must complete before other tasks can begin. Use when planning task order, identifying blockers, or ensuring proper sequencing. **Load references when:** - Phase dependencies → `references/phase-dependencies.md` - Feature chains → `references/feature-chains.md`
/plugin marketplace add nethercore-systems/nethercore-ai-plugins/plugin install ai-game-studio@nethercore-ai-pluginsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
references/feature-chains.mdreferences/phase-dependencies.mdUnderstanding dependencies ensures tasks complete in the correct order.
Creative Vision → Game Design → Asset Specs → Assets → Integration → Implementation → Testing → Publishing
Each phase depends on the previous. Skipping phases causes problems.
| Blocker | Blocked Tasks | Resolution |
|---|---|---|
| No GDD | All implementation | Create with /design-game |
| No assets | Visual features | Generate with asset-generator |
| Assets not integrated | Rendering | Run integration-assistant |
| No handles | Asset usage in code | Create src/assets.rs |
| Build fails | All testing | Fix compilation errors |
| Module not in lib.rs | Feature doesn't run | Add mod declaration |
| Not in update() | Feature doesn't update | Add update call |
| Not in render() | Feature doesn't display | Add render call |
Can run simultaneously (no dependencies):
Must run in order:
Before starting a task, verify dependencies:
# Before feature using assets:
ls generated/meshes/feature*.obj
grep "feature" nether.toml
grep "FEATURE" src/assets.rs
# Before testing:
nether build
# Before rendering:
grep "mod feature" src/lib.rs
For detailed phase and feature chains, load the references.
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 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.