Building Mechanics Router
Routes to 9 specialized skills based on game requirements.
Routing Protocol
- Classify — Single/multiplayer + scale + core features
- Match — Apply signal matching rules below
- Combine — Most games need 3-5 skills together
- Load — Read matched SKILL.md files before implementation
Quick Route
Tier 1: Core Mechanics
| Need |
Skill |
Signals |
| Spatial queries, collision |
performance-at-scale |
slow, lag, optimize, spatial, collision, thousands |
| Stability, damage, collapse |
structural-physics |
stability, collapse, support, damage, Fortnite, Rust, Valheim |
| Network sync, prediction |
multiplayer-building |
network, multiplayer, sync, server, latency, authoritative |
Tier 2: Enhanced Features
| Need |
Skill |
Signals |
| Slopes, foundations, anchoring |
terrain-integration |
slope, terrain, foundation, ground, pillar, heightmap |
| Timer decay, Tool Cupboard |
decay-upkeep |
decay, upkeep, maintenance, tool cupboard, abandoned |
| Blueprints, undo/redo, preview |
builder-ux |
blueprint, prefab, undo, redo, ghost, preview, selection |
Tier 3: Platform & Reference
| Need |
Skill |
Signals |
| Touch, VR, accessibility |
platform-building |
mobile, touch, VR, hand tracking, colorblind |
| Design analysis, trade-offs |
case-studies-reference |
how does Fortnite/Rust do, compare games, trade-offs |
Signal Priority
When multiple signals present:
- Multiplayer explicit →
multiplayer-building required
- Scale indicator → >1000 pieces triggers
performance-at-scale
- Persistence → Long-running servers trigger
decay-upkeep
- Platform constraint → Mobile/VR triggers
platform-building
- Default →
structural-physics always relevant for building games
Common Combinations
Full Survival (Rust-style, 6 skills)
performance-at-scale → spatial indexing
structural-physics → stability + damage
multiplayer-building → networking
terrain-integration → foundations on slopes
decay-upkeep → Tool Cupboard + upkeep
builder-ux → blueprints + undo
Battle Royale Building (2 skills)
performance-at-scale → fast collision
multiplayer-building → low-latency sync
Single-Player Builder (3-4 skills)
structural-physics → stability + damage
terrain-integration → natural terrain
builder-ux → blueprints + undo
performance-at-scale → if >1000 pieces
Persistent Server (4 skills)
multiplayer-building → networking
structural-physics → stability
decay-upkeep → automatic cleanup
performance-at-scale → entity management
Decision Table
| Mode |
Scale |
Terrain |
Skills |
| Single |
<1K |
Grid |
physics + ux |
| Single |
<1K |
Natural |
physics + terrain + ux |
| Single |
>1K |
Any |
performance + physics + ux |
| Multi |
Fast |
Any |
performance + multiplayer |
| Multi |
Survival |
Any |
performance + physics + multiplayer + decay |
| Multi |
Persistent |
Any |
performance + physics + multiplayer + decay + ux |
Integration Order
When combining skills, wire in this sequence:
- Spatial index → Query foundation for all other systems
- Validator → Uses spatial for neighbor/support detection
- Damage → Uses spatial for cascade radius
- Network → Broadcasts all state changes
- Client prediction → Uses local spatial + validator
Fallback
- No scale stated → Ask: "How many pieces expected?"
- Unclear mode → Ask: "Single-player or multiplayer?"
- Generic "building game" → Start with
structural-physics + builder-ux
Reference
See references/integration-guide.md for complete wiring patterns and code examples.
Converted and distributed by TomeVault — claim your Tome and manage your conversions.
1---2name: building-router3description: Router for 3D building game mechanics in Three.js. Use when creating survival games, sandbox builders, base builders, or any game with player-constructed structures. Routes to 9 specialized skills for performance, physics, multiplayer, terrain, decay, UX, platform support, and design reference. Start here for building mechanics projects. Use when this capability is needed.4---56# Building Mechanics Router78Routes to 9 specialized skills based on game requirements.910## Routing Protocol11121. **Classify** — Single/multiplayer + scale + core features132. **Match** — Apply signal matching rules below143. **Combine** — Most games need 3-5 skills together154. **Load** — Read matched SKILL.md files before implementation1617## Quick Route1819### Tier 1: Core Mechanics20| Need | Skill | Signals |21|------|-------|---------|22| Spatial queries, collision | `performance-at-scale` | slow, lag, optimize, spatial, collision, thousands |23| Stability, damage, collapse | `structural-physics` | stability, collapse, support, damage, Fortnite, Rust, Valheim |24| Network sync, prediction | `multiplayer-building` | network, multiplayer, sync, server, latency, authoritative |2526### Tier 2: Enhanced Features27| Need | Skill | Signals |28|------|-------|---------|29| Slopes, foundations, anchoring | `terrain-integration` | slope, terrain, foundation, ground, pillar, heightmap |30| Timer decay, Tool Cupboard | `decay-upkeep` | decay, upkeep, maintenance, tool cupboard, abandoned |31| Blueprints, undo/redo, preview | `builder-ux` | blueprint, prefab, undo, redo, ghost, preview, selection |3233### Tier 3: Platform & Reference34| Need | Skill | Signals |35|------|-------|---------|36| Touch, VR, accessibility | `platform-building` | mobile, touch, VR, hand tracking, colorblind |37| Design analysis, trade-offs | `case-studies-reference` | how does Fortnite/Rust do, compare games, trade-offs |3839## Signal Priority4041When multiple signals present:421. **Multiplayer explicit** → `multiplayer-building` required432. **Scale indicator** → >1000 pieces triggers `performance-at-scale`443. **Persistence** → Long-running servers trigger `decay-upkeep`454. **Platform constraint** → Mobile/VR triggers `platform-building`465. **Default** → `structural-physics` always relevant for building games4748## Common Combinations4950### Full Survival (Rust-style, 6 skills)51```52performance-at-scale → spatial indexing53structural-physics → stability + damage54multiplayer-building → networking55terrain-integration → foundations on slopes56decay-upkeep → Tool Cupboard + upkeep57builder-ux → blueprints + undo58```5960### Battle Royale Building (2 skills)61```62performance-at-scale → fast collision63multiplayer-building → low-latency sync64```6566### Single-Player Builder (3-4 skills)67```68structural-physics → stability + damage69terrain-integration → natural terrain70builder-ux → blueprints + undo71performance-at-scale → if >1000 pieces72```7374### Persistent Server (4 skills)75```76multiplayer-building → networking77structural-physics → stability78decay-upkeep → automatic cleanup79performance-at-scale → entity management80```8182## Decision Table8384| Mode | Scale | Terrain | Skills |85|------|-------|---------|--------|86| Single | <1K | Grid | physics + ux |87| Single | <1K | Natural | physics + terrain + ux |88| Single | >1K | Any | performance + physics + ux |89| Multi | Fast | Any | performance + multiplayer |90| Multi | Survival | Any | performance + physics + multiplayer + decay |91| Multi | Persistent | Any | performance + physics + multiplayer + decay + ux |9293## Integration Order9495When combining skills, wire in this sequence:961. **Spatial index** → Query foundation for all other systems972. **Validator** → Uses spatial for neighbor/support detection983. **Damage** → Uses spatial for cascade radius994. **Network** → Broadcasts all state changes1005. **Client prediction** → Uses local spatial + validator101102## Fallback103104- **No scale stated** → Ask: "How many pieces expected?"105- **Unclear mode** → Ask: "Single-player or multiplayer?"106- **Generic "building game"** → Start with `structural-physics` + `builder-ux`107108## Reference109110See `references/integration-guide.md` for complete wiring patterns and code examples.111112---113> Converted and distributed by [TomeVault](https://tomevault.io/claim/bbeierle12) — claim your Tome and manage your conversions.114<!-- tomevault:4.0:skill_md:2026-04-11 -->
tomevault-io