| name | rust-skills-minecraft |
| description | Rust skill set for Minecraft-adjacent systems: voxel engines, chunk management, procedural world generation (Perlin / simplex / density functions), block state machines, entity simulation, redstone-like logic, player movement physics, NBT/SNBT parsing, biome interpolation, region file I/O, and async server tick loops. Invoke with /minecraft-rust or by mentioning any of the trigger keywords below. Built on the actionbook meta-cognition framework (Layer 3 → Layer 2 → Layer 1) and the leonardomso 179-rule taxonomy.
|
| license | MIT |
| metadata | {"version":"1.0.0","based_on":["https://github.com/actionbook/rust-skills","https://github.com/leonardomso/rust-skills","https://doc.rust-lang.org/stable/","https://rust-lang.org/learn/"]} |
| triggers | ["voxel","chunk","block state","world gen","worldgen","perlin noise","simplex noise","density function","entity tick","player movement","redstone","NBT","SNBT","minecraft protocol","azalea","valence","pumpkin","feather","schematic","biome","tick system","level.dat","region file","anvil format","chunk loading","spawn chunk","pathfinding","AABB collision","game loop","minecraft server","voxel rendering","greedy meshing"] |
Rust Skills — Minecraft Domain
Comprehensive Rust guide for Minecraft-like systems.
Covers Layer 0 (vibe) + 9 sub-domains × 3 cognitive layers × 179-rule alignment.
How to Use
This skill set follows the actionbook meta-cognition framework:
Layer 0: Plain-English / Vibe ← "I want to…" / beginner — translates to technical skills
↕
Layer 3: Domain Constraints (WHY) ← Start here for architecture questions
↕
Layer 2: Design Choices (WHAT) ← Patterns, data structures, crates
↕
Layer 1: Language Mechanics (HOW) ← Rust ownership, lifetimes, compiler errors
Routing table:
| Your problem | Entry layer | Skills to load |
|---|
| "I want to make…" / beginner / non-technical | Layer 0 | mc-00-vibe → then target skill |
| E0382 in chunk system | Layer 1 → trace UP | domain-minecraft + mc-01-ownership |
| How to design chunk loading? | Layer 2 | mc-02-chunk-storage + domain-minecraft |
| Best noise algo for terrain gen? | Layer 2/3 | mc-03-worldgen + domain-minecraft |
| Entity AI slow at 10k entities | Layer 1→2 | mc-04-entity-ecs + mc-07-performance |
| Parse NBT from .mca files | Layer 1 | mc-05-nbt-io + mc-01-ownership |
| Async packet architecture | Layer 2/3 | mc-06-networking + domain-minecraft |
| Player physics jitter | Layer 2 | mc-04-entity-ecs + mc-07-performance |
| Dark chunks / light leaks / skylight wrong | Layer 2 | mc-08-lighting |
| Plugin system / extensible server | Layer 2 | mc-10-plugins |
Skill Index
🦀 Entry / Vibe (Layer 0)
| Skill | Core Question | Triggers |
|---|
mc-00-vibe | What do you want to build? (plain English → technical skill) | I want to make, beginner, laggy, where do I start |
🌍 Domain Layer (Layer 3 — WHY)
| Skill | Core Question | Triggers |
|---|
domain-minecraft | What are Minecraft's hard constraints? | voxel, chunk, world gen, tick, protocol |
⚙️ Mechanics Layer (Layer 1 — HOW)
| Skill | Core Question | Triggers |
|---|
mc-01-ownership | Who owns chunk/entity data? | E0382, E0597, Arc, clone |
mc-05-nbt-io | How to parse NBT / region files? | NBT, SNBT, .mca, region, level.dat |
🏗️ Design Layer (Layer 2 — WHAT)
| Skill | Core Question | Triggers |
|---|
mc-02-chunk-storage | What data layout for chunk data? | chunk, section, palette, block state |
mc-03-worldgen | What noise / generation algorithm? | worldgen, perlin, simplex, biome, terrain |
mc-04-entity-ecs | ECS vs OOP for entities? | entity, player, mob, physics, pathfinding |
mc-06-networking | Async server tick architecture? | server, protocol, packet, tokio, TPS |
mc-07-performance | Where is the 50ms budget going? | performance, lag, TPS, optimization |
mc-08-lighting | How does skylight/block light propagate? | lighting, skylight, light leak, heightmap |
mc-10-plugins | How to extend the server without recompiling? | plugin, WASM, libloading, extensible |
Cargo.toml Reference
[dependencies]
bevy = { version = "0.14", default-features = false, features = [
"bevy_core_pipeline", "bevy_render", "bevy_asset"
]}
valence = { git = "https://github.com/valence-rs/valence", optional = true }
azalea = { git = "https://github.com/azalea-rs/azalea", optional = true }
simdnoise = "3"
noise = "0.9"
fastnbt = "2"
valence_nbt = "0.8"
flate2 = "1"
memmap2 = "0.9"
tokio = { version = "1", features = ["full"] }
bytes = "1"
ahash = "0.8"
=
=
=
=
=
=
=
=
=
Rule Alignment (leonardomso taxonomy)
The following leonardomso rules apply with Minecraft-specific nuance:
| Rule | Minecraft context |
|---|
own-arc-shared | Arc<RwLock<Chunk>> — chunks shared by world, renderer, entities |
own-rwlock-readers | Chunk reads dominate writes; use RwLock, not Mutex |
mem-with-capacity | Pre-size Vec<BlockState> to 4096 per section |
mem-smallvec | Palette entries per section rarely exceed 16 |
mem-boxed-slice | Box<[u8; 2048]> for light arrays — fixed-size, no realloc |
async-no-lock-await | NEVER hold a chunk RwLock across .await — server deadlock |
async-spawn-blocking | Chunk generation is CPU-bound → spawn_blocking |
async-bounded-channel | Backpressure on packet ingestion — bounded mpsc |
opt-simd-portable | simdnoise for terrain generation — mandatory |
opt-cache-friendly | SoA layout for entity components via ECS |
perf-iter-over-index | Iterate chunk sections with par_iter() (rayon) |
anti-unwrap-abuse | Chunk lookups return Option<Chunk> — never .unwrap() |
type-newtype-ids | ChunkPos(i32, i32), EntityId(u32), BlockState(u16) |
Sources
