wireframelisted
Install: claude install-skill yesith0106/craft3d
# /wireframe: the drawing look
One engine with two looks; this command is the drawn one. The method, the library, the model contract and the proof are shared with `/3d-model` and live in the engine's `METHOD.md`. The drawing renderer is `lib/ink.js`.
**First, find the engine and read the method:**
```
ENGINE="$(cd -P "<this skill's base directory>/../.." && pwd)" # the craft3d folder this skill sits in: the cloned repo, or the installed plugin
[ -f "$ENGINE/METHOD.md" ] || ENGINE="$HOME/.claude/craft3d" # the skill was installed on its own, without the engine
[ -f "$ENGINE/METHOD.md" ] || git clone --depth 1 https://github.com/yesith0106/craft3d "$ENGINE" # so fetch the engine, once
cat "$ENGINE/METHOD.md" "$ENGINE/references/drawing.md"
```
Read both in full before building, then `references/recreate.md` or `references/from-idea.md`. **For anything real, research comes first** (`references/research.md`): a background research agent hunting for the maker's own CAD, spec table, drawings and measured reviews, started the moment the object is named. A published STEP becomes the geometry, and a section through it (`tools/step2mesh.py section`) shows how the parts nest before you draw them. For a product, `wooting80he` is the closest example: it opens as a blueprint with a title block (`info.sheet`), dimension lines and callouts (`annot.js`), section A–A and an exploded build, all on the maker's CAD. The closest example is usually `turbojet` (`node "$ENGINE/tools/new