agentleFS
Sign inStart free
Bbeierle12Bbeierle12/Skill-MCP-Claude/skills/building-router/SKILL.md

building-router

Skill9 starsChanged 6 months agoMITView on GitHub

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.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When multiple signals present:

    line 41
  2. Distinctive:

    When combining skills, wire in this sequence:

    line 95

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Building Mechanics Router

Routes to 9 specialized skills based on game requirements.

Routing Protocol

  1. Classify — Single/multiplayer + scale + core features
  2. Match — Apply signal matching rules below
  3. Combine — Most games need 3-5 skills together
  4. Load — Read matched SKILL.md files before implementation

Quick Route

Tier 1: Core Mechanics

NeedSkillSignals
Spatial queries, collisionperformance-at-scaleslow, lag, optimize, spatial, collision, thousands
Stability, damage, collapsestructural-physicsstability, collapse, support, damage, Fortnite, Rust, Valheim
Network sync, predictionmultiplayer-buildingnetwork, multiplayer, sync, server, latency, authoritative

Tier 2: Enhanced Features

NeedSkillSignals
Slopes, foundations, anchoringterrain-integrationslope, terrain, foundation, ground, pillar, heightmap
Timer decay, Tool Cupboarddecay-upkeepdecay, upkeep, maintenance, tool cupboard, abandoned
Blueprints, undo/redo, previewbuilder-uxblueprint, prefab, undo, redo, ghost, preview, selection

Tier 3: Platform & Reference

NeedSkillSignals
Touch, VR, accessibilityplatform-buildingmobile, touch, VR, hand tracking, colorblind
Design analysis, trade-offscase-studies-referencehow does Fortnite/Rust do, compare games, trade-offs

Signal Priority

When multiple signals present:

  1. Multiplayer explicit → multiplayer-building required
  2. Scale indicator → >1000 pieces triggers performance-at-scale
  3. Persistence → Long-running servers trigger decay-upkeep
  4. Platform constraint → Mobile/VR triggers platform-building
  5. 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

ModeScaleTerrainSkills
Single<1KGridphysics + ux
Single<1KNaturalphysics + terrain + ux
Single>1KAnyperformance + physics + ux
MultiFastAnyperformance + multiplayer
MultiSurvivalAnyperformance + physics + multiplayer + decay
MultiPersistentAnyperformance + physics + multiplayer + decay + ux

Integration Order

When combining skills, wire in this sequence:

  1. Spatial index → Query foundation for all other systems
  2. Validator → Uses spatial for neighbor/support detection
  3. Damage → Uses spatial for cascade radius
  4. Network → Broadcasts all state changes
  5. 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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free