threejs-deployment — Claude Code skill: what it does, how to install
Claude Code skill threejs-deployment prepares and verifies Three.js web builds, asset hosting, decoder paths, and caching.
MIT 582 installs ★ 26 updated 2026-09-10
npx skills add cesartevisual/threejs-skills --skill threejs-deployment -a claude-codeWhat threejs-deployment does
The skill inspects build tools, hosting targets, base paths, and browser requirements while maintaining compatible versions of Three.js and its addons. It resolves paths for models, textures, decoders, workers, and WASM files, configures CORS, and sets up CSP directives for worker environments. Asset responses and MIME types are verified to prevent HTML fallbacks.
Caching strategies use content hashing and update controls to prevent stale service workers from pairing new code with old decoders. A production preview runs to check representative assets, load failures, route reloads, and fallback devices. The assistant operates within existing project architecture and follows established conventions.
The agent activates during tasks involving Three.js build validation, asset delivery configuration, and deployment compatibility checks.
What it helps with
- verify decoder and WASM paths in Three.js builds
- configure CORS and CSP directives for workers
- check asset caching and content-hashed bundles
- run a production build preview locally
Example prompts for the agent
- Prepare the Three.js build and verify decoder paths
- Check asset caching and MIME types for the Three.js build
- Run a production preview and test worker configurations
How to install threejs-deployment
1Skills CLI (Vercel)
npx skills add cesartevisual/threejs-skills --skill threejs-deployment -a claude-code2Manually: put the files in place
~/.claude/skills/threejs-deployment/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/threejs-deployment/
1Skills CLI (Vercel)
npx skills add cesartevisual/threejs-skills --skill threejs-deployment -a codex2Manually: put the files in place
.agents/skills/threejs-deployment/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add cesartevisual/threejs-skills --skill threejs-deployment -a cursor2Manually: put the files in place
.cursor/skills/threejs-deployment/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install cesartevisual/threejs-skills skills/threejs-deployment2Manually: put the files in place
.github/skills/threejs-deployment/SKILL.md1Skills CLI (Vercel)
npx skills add cesartevisual/threejs-skills --skill threejs-deployment -a gemini-cli2Platform CLI
gemini skills install https://github.com/cesartevisual/threejs-skills --path skills/threejs-deploymentManually: put the files in place
.devin/skills/threejs-deployment/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add cesartevisual/threejs-skills --skill threejs-deployment -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-deployment
How to install threejs-deployment in Claude Code?
Run npx skills add cesartevisual/threejs-skills --skill threejs-deployment -a claude-code, then use the skill file at ~/.claude/skills/threejs-deployment/SKILL.md.
What does threejs-deployment do?
It prepares and verifies Three.js web builds, asset hosting, decoder paths, caching, and deployment compatibility.
Where can I check exact build signatures?
Consult the official Vite documentation at https://vite.dev/guide/assets for revision-specific behavior.
Source text
SKILL.md · MIT
--- name: threejs-deployment description: "Prepare and verify Three.js web builds, asset hosting, decoder paths, caching, and deployment compatibility." --- # Build and Delivery 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 existing build tool, hosting target, base path, browser requirements, and deployment authorization. Preserve project conventions. Prepare and validate the build even when publishing requires a later authorized step. Keep Three.js and addons on a compatible revision and deduplicate conflicting instances. Verify peer dependencies before upgrades. Include only required loaders/helpers and lazy-load heavy optional paths when useful. Inspect the output rather than assuming tree-shaking removed unused code. Resolve model, texture, decoder, worker, and WASM URLs through build-aware paths. Test the actual nested base path and direct navigation to application routes. Serve the right MIME types; verify asset responses are not HTML fallbacks. Set CORS for legitimately cross-origin assets and CSP directives needed by the chosen worker/decoder setup. Require secure contexts for features that need them. Add cross-origin isolation only when the actual threaded/runtime feature requires it; account for third-party resource implications. Use immutable caching for content-hashed assets and a coherent update strategy for HTML and manifests. Avoid stale service workers pairing new code with old decoders. Handle offline/error states according to product requirements. Run a production preview and check representative assets, cache behavior, load failures, fallback devices, and route reloads. Publish only within existing authorization and report the deployed URL only after verifying it. ## API reference Consult the [official documentation](https://vite.dev/guide/assets) 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