create-map
Skill4 starsChanged 4 months agoMITView on GitHub
Create a new playable Workmelt map from user-supplied assets (reference images, floor plans, screenshots, sketches, blueprints) and/or a written description. Use this skill whenever the user asks to add a map, level, arena or area to the game, drops in image/plan files meant to become a map, wants to recreate a real place or a map from another game, or asks to extend or rework an existing map's layout. Also use it for questions about how maps are structured if the intent is to build one.
In this repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- elevenlabs-sfxSkill
- glb-weaponSkill
- visual-checkSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
15 rules. About 0 are common, 4 are distinctive, and 11 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
11
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 27
Accurate but playable: Follow the asset's layout as closely as you can, then bend it wherever a faithful copy would make a bad FFA …
- Very specific: line 39
Read it before writing the build() function or a props file.
- Distinctive: line 63
If there are no assets, work from the description alone.
- Very specific: line 85
the palette: Every colour you map onto a palette.js key comes from looking, and step 5 of the playbook depends on it.
- Very specific: line 89
whether the source has interiors at all: Add --cut=<m> for a roofs-off plan.
- Very specific: line 112
Create src/world/<id>.js following the rust.js shape:
- Very specific: line 129
If the map needs props the shared libraries lack, add src/world/<id>props.js built with PB — but reuse the ~70 existing prototypes first …
- Very specific: line 137
Do not touch DEFAULT_MAP_ID — captures baseline on the market.
- Very specific: line 141
Update the map-id union in ARCHITECTURE.md (search for world.mapId).
- Very specific: line 145
Add a map-specific section to src/world/maps.selftest.mjs following the existing per-map sections: solids don't overlap, everything sits …
- Very specific: line 155
Run, in order (details and more options in references/map-contract.md):
- Distinctive: line 171
Never load an asset at runtime.
- Very specific: line 172
Never call Math.random() in world code.
- Very specific: line 173
Never hard-code a hex colour.
- Distinctive: line 178
Avoid per-frame allocations.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
Files
Create a Workmelt map
This skill turns reference assets and a description into a new map module in
src/world/, registered in the map list and passing the headless map
self-test. A Workmelt map is not loaded from disk: it is a few layout
tables plus a build function that generates every mesh in code. The assets
the user gives you are reference material for layout, proportions, mood and
palette — they are never shipped, imported or sampled at runtime.
Two standing priorities, straight from the project's brief:
- Performance over realism. Low-poly blocked-out forms; surface detail comes from the shared procedural materials, not geometry or textures. The self-test enforces < 320 draw calls for the whole map.
- Accurate but playable. Follow the asset's layout as closely as you can, then bend it wherever a faithful copy would make a bad FFA deathmatch space (dead ends, unwatchable sightlines, unreachable floors, leaky perimeter).
Reference files — read before writing code
references/map-contract.md— the map descriptor contract, exactly whatmaps.selftest.mjsenforces (with numbers), the registration checklist and every verification command. Read it in full before authoring the module.references/engine-api.md— the Assembler, thePBprop builder,kit.jshelpers, palette keys and the existing prop vocabulary you should reuse. Read it before writing thebuild()function or a props file.references/layout-playbook.md— how to turn assets into a layout: scale calibration, lanes/cover/landmark rules, spawn-zone authoring, sealing the perimeter, walkability targets. Read it during the design stage.
Also read src/world/rust.js end to end — it is the canonical self-contained
map module and the template every new map should follow. src/world/maps.js
documents the descriptor. ARCHITECTURE.md covers the engine contract if you
need to touch anything outside src/world/.
Workflow
1. Inventory and read the assets
List everything the user supplied. View every image with the Read tool — actually look at them; the layout you author must be traceable back to what is in the pictures. For each asset note:
- what it shows (plan view, elevation, screenshot, mood/reference photo)
- the major masses: buildings, walls, roads/lanes, open ground, water
- the landmark — the one tall or unmistakable thing the map reads by
- vertical opportunities: roofs, decks, platforms, terraces
- materials and palette (map these to existing palette keys later)
If there are no assets, work from the description alone; ask nothing the description or genre conventions can answer.
If an asset is a 3D model (.glb/.gltf), run both readers over it. They
answer different questions and you need both before step 2:
node tools/glb-plan.mjs <file.glb> --scale=<s> --depth=3 # measurements
node tools/glb-render.mjs <file.glb> --scale=<s> --out=.shots/<id>-refglb-plan gives extent, the named part table and a top-down ASCII height
field — the numbers the layout tables are transcribed from. glb-render
writes an aspect-corrected orthographic plan, three iso angles and an
eye-level view into .shots/. Read every PNG back with the Read tool and
say what you saw; a .png nobody looked at is not a reference render.
The renders are not a nicety — the height field genuinely cannot tell you:
- what a mass is. A block of tall cells reads identically whether it is a tower block, a container stack or a stand of trees. The plan module needs to know which.
- the palette. Every colour you map onto a
palette.jskey comes from looking, and step 5 of the playbook depends on it. - building vs. prop. Which masses become
STRUCTURESentries and which are dressing is a judgement made by eye. - whether the source has interiors at all. Add
--cut=<m>for a roofs-off plan. It reports how many meshes it hid: if that is 0, or the image is unchanged, the model's buildings are single floor-to-roof masses and every interior is yours to invent — do not report the rooftop plan as the interior.
2. Establish scale and draft the plan
Calibrate metres from known objects in the assets (a door ≈ 1 m, a car ≈ 4.5 m, a shipping container is 6.06 × 2.44 m, a floor ≈ 3 m). Existing maps run 55 × 55 m (Rust) to 120 × 120 m (Market); land inside that band — smaller plays frantic, larger starves an 8-player FFA of contact.
Draft the plan before writing any code: a coordinate sketch (ASCII art or
a commented table) in LEVEL space — origin at the centre, north at −Z,
structures as axis-aligned rectangles. This is where layout accuracy is won:
place each mass where the asset puts it, then apply the playability passes
from references/layout-playbook.md (lane widths, cover rhythm, sealed
perimeter, stair-only verticality). Present the plan and the deviations you
made for playability in your summary — the user asked for their space, so
say where and why you bent it.
3. Author the map module
Create src/world/<id>.js following the rust.js shape:
- Constants + layout tables first, exported (the self-test reads them):
the extent object,
STRUCTURES, and tables for whatever else is solid. Tables of numbers, one entry per placed thing, comments explaining any placement that matters. - Spawn table —
[x, z, yaw, zone], ≥ 8 points in ≥ 4 named zones, authored per the playbook. Index 0 is the frozen boot spawn. - Occupancy — build a
BLOCKERSrect list once from the tables, theninSolid,standableAt<Name>,isOpen<Name>,groundY<Name>. These must agree with the geometry because spawns, AI and the minimap trust them. build<Name>(A, rng)— register prop prototypes, then ground, perimeter, structures, set pieces, dressing. Draw randomness only from therngargument, neverMath.random()— capture runs must reproduce.- The
<ID>_MAPdescriptor at the bottom.
If the map needs props the shared libraries lack, add
src/world/<id>props.js built with PB — but reuse the ~70 existing
prototypes first (see references/engine-api.md); every new prototype is
GPU memory and bake time.
4. Register and document
src/world/maps.js: import the descriptor, append toMAPS, re-export. Do not touchDEFAULT_MAP_ID— captures baseline on the market.- The lobby menu, minimap, relay and
?map=<id>all pick the map up from the list automatically; the relay validates slugs generically, so no server change. - Update the map-id union in
ARCHITECTURE.md(search forworld.mapId).
5. Extend the self-test
Add a map-specific section to src/world/maps.selftest.mjs following the
existing per-map sections: solids don't overlap, everything sits inside the
perimeter, every gate/mouth is sealed (probe the first 2–3 m of each
opening), the landmark invariants, and a sampled walkable fraction with a
band that matches the map's density. These checks exist because each of them
found a real bug a screenshot would not show — give the new map the same
protection.
6. Verify
Run, in order (details and more options in references/map-contract.md):
node src/world/maps.selftest.mjs
node src/world/spawns.selftest.mjs
npm run buildThen, where a browser/GPU is available: node tools/capture.mjs with
?map=<id> for the visual smoke test and node src/world/spawns.probe.mjs
for collision-validated spawns. Report which checks ran and which the
environment could not support. Iterate until the self-test is green — its
failures name the exact table entry to fix.
Hard rules (the ones that are easy to break silently)
- Never load an asset at runtime. Geometry, materials, masks: all generated.
- Never call
Math.random()in world code; use the handedrngfork. - Never hard-code a hex colour; surfaces come from
palette.jskeys. - Stairs are the only way up — the controller mantles ~0.5 m ledges but cannot climb ladders. A roof without a stair is scenery, not a position.
- The perimeter must be sealed: every opening blocked solid within its first 2–3 m, or players walk out into empty backdrop.
- Avoid per-frame allocations; register collision as cheap proxy boxes, not the visual mesh.
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
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.

