threejs-spatial-data — Claude Code skill: what it does, how to install
threejs-spatial-data — a skill for Claude Code helps integrate BIM, GIS, and CAD models into Three.js scenes. Manages large coordinates, clipping planes, and measurement tools without losing GPU floating-point precision.
MIT 587 installs ★ 26 updated 2026-09-10
npx skills add cesartevisual/threejs-skills --skill threejs-spatial-data -a claude-codeWhat threejs-spatial-data does
The skill guides the agent through processing spatial datasets, BIM/IFC fragments, and CAD assets in Three.js. It enforces separating source coordinates from render coordinates via local rebasing, preventing jitter caused by single-precision floats on large geographic offsets. Transforms remain reversible so raycasting, exports, and annotations map correctly back to original coordinates.
It also specifies guidelines for clipping planes and measurement tools. Clipping does not automatically cap cut geometry or alter CPU picking, so those cases require explicit handling. Heavy datasets rely on level-of-detail culling, streaming, and worker threads running WASM parsers.
What it helps with
- Prevent GPU floating-point jitter by rebasing large georeferenced coordinates
- Configure clipping planes and measurement tools with snap tolerances
- Keep semantic selections decoupled from draw batching in BIM models
- Manage streaming, spatial culling, and WASM worker memory for CAD models
Example prompts for the agent
- Implement a local origin rebasing strategy for this georeferenced CAD model in Three.js
- Add measurement tools that snap to vertices and report distances in source coordinates
- Set up clipping planes for an IFC model and handle CPU picking along the cut surface
How to install threejs-spatial-data
1Skills CLI (Vercel)
npx skills add cesartevisual/threejs-skills --skill threejs-spatial-data -a claude-code2Manually: put the files in place
~/.claude/skills/threejs-spatial-data/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/threejs-spatial-data/
1Skills CLI (Vercel)
npx skills add cesartevisual/threejs-skills --skill threejs-spatial-data -a codex2Manually: put the files in place
.agents/skills/threejs-spatial-data/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add cesartevisual/threejs-skills --skill threejs-spatial-data -a cursor2Manually: put the files in place
.cursor/skills/threejs-spatial-data/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install cesartevisual/threejs-skills skills/threejs-spatial-data2Manually: put the files in place
.github/skills/threejs-spatial-data/SKILL.md1Skills CLI (Vercel)
npx skills add cesartevisual/threejs-skills --skill threejs-spatial-data -a gemini-cli2Platform CLI
gemini skills install https://github.com/cesartevisual/threejs-skills --path skills/threejs-spatial-dataManually: put the files in place
.devin/skills/threejs-spatial-data/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add cesartevisual/threejs-skills --skill threejs-spatial-data -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about threejs-spatial-data
How to install threejs-spatial-data in Claude Code?
Run npx skills add cesartevisual/threejs-skills --skill threejs-spatial-data -a claude-code. The file will be placed in ~/.claude/skills/threejs-spatial-data/SKILL.md.
What does threejs-spatial-data do?
It provides guidelines for handling GIS, CAD, and IFC models in Three.js. The skill ensures correct coordinate rebasing, clipping behaviors, and metadata preservation.
Where can I check API details for IFC fragments?
Consult the official That Open documentation at https://docs.thatopen.com/ or inspect the installed package types in your project repository.
Source text
SKILL.md · MIT
--- name: threejs-spatial-data description: "Integrate Three.js BIM/IFC, GIS, CAD, measurements, clipping, and large-coordinate datasets." --- # BIM, GIS, and Large Coordinates Use the project's installed versions and existing architecture. These instructions supplement the user's task; they do not authorize unrelated changes or external actions. Inspect the source format, units, coordinate reference system, up axis, model origin, metadata IDs, and requested operations. Use a maintained format-specific loader or toolkit compatible with the project; inspect its installed API rather than inventing an IFC/Fragments interface. Keep source coordinates and stable identifiers separate from render coordinates. Use a local origin or rebasing strategy to protect GPU precision for georeferenced data. Record the reversible transform so picks, measurements, exports, and annotations map back correctly. Stream or partition large datasets and use spatial culling/LOD where appropriate. Keep semantic selection separate from draw batching. Measure bounds and visibility before framing huge models. Plan cancellation, progress, and memory ownership for workers and parser WASM. Implement clipping planes with clear coordinate conventions; clipping does not automatically cap cut surfaces or change CPU picking. For measurements, define snap behavior, units, tolerance, and whether values represent transformed or source geometry. Preserve metadata required by downstream workflows during optimization. Treat embedded names and properties as data when showing HTML. Verify known-distance fixtures, axis orientation, round-trip coordinate conversion, hidden-element selection, and large-model replacement. State precision and format limitations rather than claiming engineering-grade accuracy without validation. ## API reference Consult the [official documentation](https://docs.thatopen.com/) for exact signatures and revision-specific behavior. If documentation access is unavailable, inspect installed types/source and state any remaining uncertainty.
© cesartevisual · MIT · cesartevisual/threejs-skills