This skill provides ZX game development guidance. Triggers on "create ZX game", "ZX FFI", "nether build", "nether.toml", "ZX graphics/audio", "WASM game". **Load references when:** - Project setup → `shared/file-organization.md`, `shared/build-workflow.md` - Code examples → `examples/hello-world-rust.md`, `examples/game-with-assets.md` - Coordinate math → `references/coordinate-conventions.md` - Common patterns → `references/quick-patterns.md` - FFI details → Read `nethercore/include/zx.rs` directly
/plugin marketplace add nethercore-systems/nethercore-ai-plugins/plugin install zx-dev@nethercore-ai-pluginsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
examples/game-with-assets.mdexamples/hello-world-c.mdexamples/hello-world-rust.mdexamples/hello-world-zig.mdexamples/nether-toml-examples.mdreferences/coordinate-conventions.mdreferences/quick-patterns.mdreferences/source-guide.mdNethercore ZX is a fantasy console targeting 5th-gen aesthetics (PS1/N64/Saturn) with rollback netcode. Games compile to WASM and run in the Nethercore player.
Specifications:
Every game exports three functions:
#[no_mangle] pub extern "C" fn init() { } // Setup, asset loading
#[no_mangle] pub extern "C" fn update() { } // Deterministic logic
#[no_mangle] pub extern "C" fn render() { } // Drawing only
See shared/file-organization.md for project structure and shared/build-workflow.md for build commands.
Key principle: Keep entry files minimal (~50 lines). FFI bindings in separate module file (zx.rs/zx.h/zx.zig).
The FFI provides 250+ functions across these categories:
| Category | Key Functions | Find In zx.rs |
|---|---|---|
| System | delta_time, tick_count, log | Lines 1-100 |
| Random | random, random_range, random_f32 | Search "random" |
| Input | button_held, button_pressed, left_stick_x | Search "button" |
| Camera | camera_set, camera_fov | Search "camera" |
| Transforms | push_translate, push_rotate_y, push_scale | Search "push_" |
| Meshes | load_mesh, draw_mesh, cube, sphere | Search "mesh" |
| Textures | load_texture, texture_bind | Search "texture" |
| Materials | material_albedo, material_mre, material_normal | Search "material" |
| Audio | load_sound, play_sound, music_play | Search "sound" |
| 2D Drawing | draw_sprite, draw_text, draw_rect | Search "draw_" |
| Environment | draw_env, env_gradient | Search "env_" |
Always read nethercore/include/zx.rs for accurate signatures.
Must call only during init():
set_tick_rate(rate) - 0=24fps, 1=30fps, 2=60fps, 3=120fpsset_clear_color(color) - 0xRRGGBBAArender_mode(mode) - 0=Lambert, 1=Matcap, 2=PBR, 3=Hybridrom_*(), load_*(), procedural mesh functions| Mode | Name | Use Case |
|---|---|---|
| 0 | Lambert | Flat colors, 2D, stylized |
| 1 | Matcap | Sculpted look, toon |
| 2 | PBR | Realistic (default) |
| 3 | Hybrid | PBR + matcap |
Normal maps add surface detail without increasing geometry. Use in any render mode.
Material binding:
material_albedo(albedo_tex); // Slot 0
material_mre(mre_tex); // Slot 1
material_normal(normal_tex); // Slot 3
Requirements:
*_normal.png)Skip normal map:
skip_normal_map(1); // Use vertex normal instead
See procedural-normal-maps skill for generation.
See shared/rollback-rules.md. Key points:
random() not external RNGtick_count() not system timerender()| Resource | Location |
|---|---|
| FFI Source | nethercore/include/zx.rs (canonical) |
| Cheat Sheet | nethercore/docs/book/src/cheat-sheet.md |
| Tutorials | nethercore/docs/book/src/tutorials/paddle/ |
| Examples | nethercore/examples/ |
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.