threejs-product-viewer — Claude Code skill: features and setup
This Claude Code skill guides the creation of interactive Three.js product viewers. It comes into play when a project needs material choices, camera presets, or model hotspots.
MIT 621 installs ★ 26 updated 2026-09-10
npx skills add cesartevisual/threejs-skills --skill threejs-product-viewer -a claude-codeWhat threejs-product-viewer does
The skill outlines how to build a Three.js product viewer or configurator with material variants, camera presets, hotspots, and tracked selections. For image exports, it describes capturing a frame and restoring renderer and camera state afterward.
It starts from the model structure: mesh and material names, units, variant layout, and camera targets. Product choices should map to stable identifiers rather than arbitrary mesh positions. Prices and availability belong to the application’s existing data layer; the model should not determine commercial details.
The guidance also covers URL persistence, reset behavior, mobile controls, rapid option changes, and failed assets. Cross-origin restrictions affect image capture, and the export flow must account for whether HTML overlays are included.
What it helps with
- map product options to model material changes
- add camera presets and anchored model hotspots
- persist configurator choices in a URL
- test mobile controls and image export
Example prompts for the agent
- Build a Three.js product viewer with material variants and camera presets.
- Add model hotspots and save the selected configuration in the URL.
- Set up image capture and test rapid variant changes on mobile.
How to install threejs-product-viewer
1Skills CLI (Vercel)
npx skills add cesartevisual/threejs-skills --skill threejs-product-viewer -a claude-code2Manually: put the files in place
~/.claude/skills/threejs-product-viewer/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/threejs-product-viewer/
1Skills CLI (Vercel)
npx skills add cesartevisual/threejs-skills --skill threejs-product-viewer -a codex2Manually: put the files in place
.agents/skills/threejs-product-viewer/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add cesartevisual/threejs-skills --skill threejs-product-viewer -a cursor2Manually: put the files in place
.cursor/skills/threejs-product-viewer/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install cesartevisual/threejs-skills skills/threejs-product-viewer2Manually: put the files in place
.github/skills/threejs-product-viewer/SKILL.md1Skills CLI (Vercel)
npx skills add cesartevisual/threejs-skills --skill threejs-product-viewer -a gemini-cli2Platform CLI
gemini skills install https://github.com/cesartevisual/threejs-skills --path skills/threejs-product-viewerManually: put the files in place
.devin/skills/threejs-product-viewer/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add cesartevisual/threejs-skills --skill threejs-product-viewer -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-product-viewer
How do I install threejs-product-viewer in Claude Code?
Run npx skills add cesartevisual/threejs-skills --skill threejs-product-viewer -a claude-code. The skill file is at ~/.claude/skills/threejs-product-viewer/SKILL.md.
What does threejs-product-viewer do?
It guides work on Three.js product viewers and configurators, including material choices, camera views, hotspots, selection state, and image export.
Where should product prices and availability come from?
Use the application’s existing data layer for prices and availability. The 3D model is not the authority for commercial facts.
Source text
SKILL.md · MIT
--- name: threejs-product-viewer description: "Build Three.js product viewers with material variants, camera presets, hotspots, configuration state, and image export." --- # Product Viewers and Configurators 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 model's mesh/material names, units, variant structure, camera targets, and business options. Define a stable mapping from product choices to render changes rather than coupling UI labels to arbitrary mesh array positions. Build a state model for selected options, availability, reset, and any URL persistence. Keep price/availability authority in the existing application data layer. Do not infer commercial facts from the model. Provide equivalent semantic HTML controls and selected-value summaries. Apply variants to instance-owned material state while sharing immutable textures safely. Guard async texture/model switches against stale completion. Frame each preset for both wide and narrow layouts; constrain orbit/zoom only enough to keep the subject useful. Place hotspots using stable anchors and handle occlusion/behind-camera states. Give users a reset view and a clear escape from dragging. Match materials under controlled lighting before adding dramatic effects that obscure product details. For screenshots, render explicitly at the capture size and restore renderer/camera state afterward. Capture immediately after rendering or use a suitable target/readback pipeline; preserveDrawingBuffer is not universally required. Handle cross-origin restrictions and decide whether HTML overlays belong in the export. Verify all valid option combinations or representative boundary combinations, rapid switching, reset, deep links, export framing, mobile controls, and failed assets. ## API reference Consult the [official documentation](https://threejs.org/docs/pages/WebGLRenderer.html) 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