Verification checklists for game development tasks. Use when completing features, assets, or systems to ensure nothing is missed. Prevents "generated but not integrated" and "coded but not rendered" issues. **Load references when:** - Asset checklists → `references/asset-checklists.md` - Feature checklists → `references/feature-checklists.md` - System checklists → `references/system-checklists.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/asset-checklists.mdreferences/feature-checklists.mdreferences/system-checklists.mdSystematic verification that work is truly complete.
Before marking anything complete:
"Would a player notice this in the game?"
If no - it's not complete.
# Assets exist
ls generated/meshes/*.obj generated/textures/*.png generated/sounds/*.wav
# Assets declared
grep "\[\[assets" nether.toml
# Handles exist
grep "asset_handle!" src/assets.rs
# Assets used
grep -r "draw_mesh\|texture_bind\|sound_play" src/
# No incomplete markers
grep -r "TODO\|FIXME\|unimplemented!\|todo!" src/
# Build succeeds
nether build
# Module integrated
grep "mod " src/lib.rs
Assets:
File exists → nether.toml → src/assets.rs handle → Used in code
Features:
Module declared → init() setup → update() logic → render() display
TODO or FIXME commentsunimplemented!() or todo!() macros_ => {}For detailed checklists by asset type, feature type, and system type, load the references.
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 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.