building-router_skill

Overview

This skill is a router for building mechanics in Three.js games, guiding you to the right specialized capabilities for your project. It helps classify game mode, scale, persistence, and platform constraints, then routes to the appropriate combination of skills for performant, playable building systems. Start here when implementing survival, sandbox, or player-construction features.

How this skill works

It inspects high-level signals such as single vs multiplayer, expected piece count, persistence, and platform (mobile/VR). Based on those signals it matches rules to select relevant skills (performance, physics, multiplayer, terrain, decay, UX, platform, and reference). It also recommends combinations and an integration order to wire systems correctly for spatial queries, validation, damage propagation, and network sync.

When to use it

• Starting a new building mechanics project in Three.js (survival, sandbox, base-builder).
• Deciding which technical priorities to implement first (scale, network, persistence).
• Designing integration order for spatial indexing, validation, damage, and networking.
• Choosing feature sets for platform constraints like mobile or VR.
• Planning a persistent server or large-scale world with many player-built pieces.

Best practices

• Classify mode (single vs multiplayer) and expected piece count before selecting skills.
• Combine 3–5 skills commonly; don’t try to implement every feature at once.
• Wire systems in the recommended order: spatial index → validator → damage → network → client prediction.
• Prioritize multiplayer routing when network signals are explicit; prioritize performance for >1k pieces.
• Ask clarifying questions when mode or scale is unspecified (e.g., pieces expected, single or multiplayer).

Example use cases

• Rust-style persistent survival: performance, structural physics, multiplayer, terrain, decay, UX.
• Battle-royale fast-build: performance-at-scale + multiplayer-building for low-latency sync.
• Single-player sandbox with natural terrain: structural-physics + terrain-integration + builder-ux.
• Persistent server cleanup: add decay-upkeep for automatic cleanup and tool cupboard mechanics.
• Mobile/VR experience: include platform-building for touch, hand tracking, and accessibility.