Skip to content

LumosLab-Innovation/3D-lab-skills / plugins/threejs-lab/skills/threejs-studio

threejs-studio

Verified

Create image options, get human approval on localhost, author geometry in Three.js or Blender MCP, then code Three.js motion, contraction and interaction for either model. Use for prompt-to-3D, image-to-model, animated interactive assets or resuming visual approval across coding agents. No paid image-to-3D service.

references/hard-surface.md

View on GitHub
# Hard-surface modeling rules

## Shape language and edges

1. Make the primitive carry the authored look. Use tangent corner fillets, a
   bevel band between broad faces and side walls, and shared normals across
   those bands. Keep straight runs flat.
2. Budget bevels by perceptual role. One bevel facet with smoothed normals is
   the default. Add a second segment only to hero masses whose silhouette or
   highlight needs it. Keep tiny marks and inset details flat and inexpensive.
3. Grade cuts per corner and break perfect mirrors. Accept per-corner chamfer
   values where they affect the silhouette and vary mirrored detail placement
   deliberately.
4. Choose the extrusion axis from the required facets. Decide which edges must
   affect the silhouette, orient the ring into that plane, then extrude along
   the remaining axis.

## Geometry correctness

5. Assume winding changes when a ring insets. For a suspect cap or inward rim,
   compare the first triangle's edge cross product with the intended outward
   normal.
6. Keep chamfers below roughly sixty percent of the affected half-extent. Clamp
   against the thinnest dimension and inspect for finite, non-degenerate
   triangles.
7. Size physical features in world units. Bevels, seams, wear bands, bolts, and
   clearances represent physical dimensions; do not scale them as a percentage
   of every host part.

## Layering, depth, and batching

8. Calculate clearance for every applied layer. Compare the host face with the
   detail's back and front faces. In this metre-scale kit, begin with at least
   0.015 units of clearance and verify from the actual camera.
9. Never let two visible faces share a plane facing the same way.
   Interpenetration is expected here; coincidence is not. The depth buffer
   cannot order two surfaces at one depth, so the overlap renders as a
   per-pixel speckle that crawls with the camera — and both a still frame and
   a resemblance critique miss it. It comes from authoring a part from a
   landmark it shares with its neighbour: a cap ring as [END - w, END] against
   a body that ends at END, a marking as [SURFACE, SURFACE + t] on the surface
   it marks. Separate the two — proud parts 0.02-0.03 further out, lapping
   parts 0.01-0.02 further in, markings sunk into their host. Flush is the bug,
   not the fix. Coincidence sealed inside another solid is never rasterised and
   does not matter; inspect the remaining exposed surfaces while orbiting the live model. The upstream coplanar checker is not bundled.

10. Build, bake, then merge. Derive adjacency data, surface identity, semantic
    parts, and material ownership while objects remain separate. Merge only
    afterward. Normalize vertex attributes before merging and respect the
    renderer's vertex-buffer budget.
11. Keep runtime anchors outside replaceable generated content. Configuration
    can rebuild geometry without invalidating consumer attachments.

## Reference matching

12. Measure the reference and solve the camera with the model. Compare clean
    silhouette bounds and cross-sections rather than reflections, smoke,
    shadows, or effects that extend the apparent shape.
13. Tune yaw, pitch, focal length, and target together. Incorrect perspective
    can make correct dimensions look wrong.
14. Treat critic feedback as evidence, not a numeric gradient. Prefer changes
    that recur across independent critiques. If critics disagree about the same
    dimension, spend the next iteration on a more stable mismatch.

## Vibe3D runtime contract

15. Keep the model root stable for its entire lifetime. Rebuild generated
    children inside it when topology changes.
16. Expose meaningful runtime anatomy through stable semantic part anchors,
    sockets, material slots, and typed actions. Do not make consumers depend on
    anonymous mesh order.
17. Respect ownership. Dispose model-owned resources exactly once and never
    dispose materials or textures supplied by the consumer.
18. Keep preview scenery, lights, floors, cameras, smoke, and diagnostic
    effects out of the installed model root or mark them for export exclusion.


Adapted from Vibe3D (MIT), commit d8f86a02469eb862220c2fa4b2bb1fe4d03b41a3. LumosLab replaced the upstream-only checker command. Numerical clearances above are examples for the upstream metre-scale kit; use the current model's units and intended manufacturing gaps. See [license](licenses/vibe3d.txt).
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall