motlab-assets — Claude Code skill: what it does, how to install
motlab-assets is a Claude Code skill that builds graphics and 3D models as code without generative AI. It stores icons, textures, and assets in a shared kit for video projects.
MIT ★ 357 updated 2026-11-17
npx skills add staryone/motlab --skill motlab-assets -a claude-codeWhat motlab-assets does
motlab-assets compiles code into vector graphics, rigged 2D characters, backgrounds, and 3D items. Instead of calling image or 3D generation models, it relies on deterministic files written in SVG, canvas, three.js, or Python. Standard renderers like Chrome and Blender produce the outputs, including transparent PNGs, SVGs, and GLB, FBX, or OBJ files.
The system arranges items inside a kit folder governed by kit.json, style.md, and tokens.json. For 3D meshes, it offers two routes: a lightweight setup via Python signed distance functions and Chrome, or a full Blender 4.2+ workflow with procedural materials, Rigify armatures, and baked PBR textures.
Prerequisites include Python 3 with numpy, scipy, Pillow, and the motlab CLI engine. Rendered files are treated purely as build outputs; modifications happen inside the source code files.
What it helps with
- generate deterministic vector graphics and icons as code
- build 3D objects with PBR textures and export to GLB, FBX, or OBJ
- maintain consistent asset styles across videos using kit tokens
- set up rigged 2D characters with distinct parts for animation
Example prompts for the agent
- Create a vector icon kit using the brand guidelines in this workspace
- Build a 3D mug model using the lightweight SDF path and export to GLB
- Add a rigged 2D mascot into the current video asset kit
How to install motlab-assets
1Skills CLI (Vercel)
npx skills add staryone/motlab --skill motlab-assets -a claude-code2Manually: put the files in place
~/.claude/skills/motlab-assets/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/motlab-assets/
1Skills CLI (Vercel)
npx skills add staryone/motlab --skill motlab-assets -a codex2Manually: put the files in place
.agents/skills/motlab-assets/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add staryone/motlab --skill motlab-assets -a cursor2Manually: put the files in place
.cursor/skills/motlab-assets/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install staryone/motlab skills/motlab-assets2Manually: put the files in place
.github/skills/motlab-assets/SKILL.md1Skills CLI (Vercel)
npx skills add staryone/motlab --skill motlab-assets -a gemini-cli2Platform CLI
gemini skills install https://github.com/staryone/motlab --path skills/motlab-assetsManually: put the files in place
.devin/skills/motlab-assets/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.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 motlab-assets
How to install motlab-assets in Claude Code?
Run npx skills add staryone/motlab --skill motlab-assets -a claude-code. You can also place the configuration directly into ~/.claude/skills/motlab-assets/SKILL.md.
What does motlab-assets do?
It builds graphic and 3D assets entirely from code instead of prompt-based image generators. Rendered assets are saved into transparent PNG, SVG, GLB, FBX, and OBJ formats.
What is required to run motlab-assets?
The skill requires Python 3 with numpy, scipy, and Pillow, plus the motlab engine. The full 3D pipeline requires Blender version 4.2 or newer.
Source text
SKILL.md · MIT
--- name: motlab-assets description: Make reusable assets as code for motlab videos, without any AI image, video or 3D generator: icons, illustrations, vector logos, rigged 2D characters, 3D objects, transitions, textures and backgrounds, kept in one kit so every video looks the same. Outputs transparent PNG plus SVG, or GLB, FBX and OBJ with PBR textures. Use whenever someone asks for assets, an asset kit, a mascot, an icon set, a 3D model or textures, even if they never say motlab. --- # motlab-assets Build assets as code and keep them in a **kit**: one folder with the style rules, the source of every asset and its rendered files. A motlab video copies the kit into its project and draws from it, so the tenth video looks like the first. Nothing here uses an AI image, video or 3D model: you write SVG, canvas, three.js and Blender code, and ordinary renderers (Chrome, Blender) draw the pixels. **The source is the asset.** Every asset has a source file you wrote (`source.svg`, `parts.svg` + `rig.json`, `build.py`, `transition.js`). PNG, GLB, FBX, OBJ and texture maps are outputs of that source. A change is made in the source and the outputs are rendered again; never edit an output by hand. That is what keeps variations consistent. **Good references in, good assets out.** Work from the user's references: brand guidelines, logos, product photos, sketches, screenshots, a 3D viewer recording, style examples. If a reference is too small or missing, ask for a better one. Don't draw a logo or a real product from memory. ## Tools - This skill's folder: `scripts/` and `templates/` below. - The motlab engine: run `motlab --help` once; it prints the engine folder. The motlab skill's scripts are in `<engine>/skills/motlab/scripts/`: `blender/kit.py` and `blender/mesh_from_sdf.py` (3D), `grid.py` (read coordinates off a reference), `get_font.py` (Google Fonts). `motlab stills` renders every PNG on the 2D and light 3D paths. - Python 3 with numpy, scipy and Pillow (the motlab skill's `requirements.txt`). Commands say `python`; on macOS and Linux it may be `python3`. - Blender, only for the main 3D path (below). ## The workflow 1. **Brief.** Ask what the assets are for (which videos, which brand or series), what is needed now, the sizes and orientation they will be used at, and which files the user wants besides PNG (SVG, GLB, FBX, OBJ, textures). Ask where the kit lives; the default is `kits/<name>/` in the user's workspace, outside any one video. 2. **Read the kit, if there is one.** Read `kit.json`, `style.md` and `tokens.json` first. New assets follow them. If a new asset needs a rule the kit does not have yet, add it to `style.md` and say so. 3. **References.** List and measure everything (size, format). Run `python scripts/palette.py <refs>` for the main colours. Write down what you can measure: line weight, corner radius, proportions, light direction, materials. 4. **Lock the style before building many assets.** For a new kit, write `tokens.json` and `style.md` (`references/kit.md`), build one hero asset, render it, and show the user a sheet with it next to the references. Wait for their OK here: a wrong style copied into twenty assets is twenty fixes. After that, build the rest without stopping. 5. **Build each asset** from its reference file: - 2D (icons, illustrations, logos, backgrounds, patterns, 2D characters, transitions): `references/2d.md`. - 3D (objects, products, simple characters, textures): `references/3d.md`. **Offer the two 3D paths first** (below). 6. **Render and export.** Each asset's folder gets its outputs (`references/kit.md` has the names). PNGs are transparent and at least 2x the largest size the asset will be shown at. 7. **Check it yourself.** `python scripts/sheet.py <sheet.jpg> <asset outputs> <refs>` and look at it: shapes against the references, edges on the checker (halos, missing alpha), sharpness at full size. `python scripts/palette.py check tokens.json <pngs>` for colour drift. For 3D, re-import every exported file (`asset3d.py check`) and look at the GLB through `templates/model.html`, which is how a motlab scene will show it. 8. **Hand over.** Update `kit.json`, rebuild the kit's `sheet.jpg`, and show the user the sheet and the list of files. Say what you could not check (an FBX opened in another program, a rig in motion, a texture at close range). 9. **Revisions.** The user names the asset and the change. Edit its source, render again, check again, and report what changed. Before a change that touches many assets, copy the kit to `backup/<n>/` inside it. ## The two 3D paths When the user wants a 3D asset, say what each path gives and let them choose: | | Light path | Main path | |---|---|---| | Needs | Python + Chrome only | Blender (4.2 or newer; tested on 5.2) | | Model from | distance functions (`mesh_from_sdf.py`) | distance functions, Blender modelling, a GLB/OBJ the user owns, MPFB humans | | Files | GLB, OBJ + MTL, PNG | GLB, FBX, OBJ + MTL, baked PBR textures (base colour, roughness, normal, AO), PNG | | Materials | one flat colour, roughness and metalness per part | any Blender material, baked into textures | | Rig | none | Rigify or MPFB armatures in FBX and GLB | | PNG | three.js turntable (`templates/model.html`) | Cycles turntable, path traced | | Time | seconds | about 30 s for the test mug: bake 7.5 s, export 2.3 s, four 1024 px views 16.5 s (RTX 3060 Laptop) | For the main path, check the machine before promising anything, and tell the user what you found: 1. **Blender.** Find it: `blender` on PATH, `C:\Program Files\Blender Foundation\Blender <version>\blender.exe`, `/Applications/Blender.app/Contents/MacOS/Blender`, `/opt/homebrew/bin/blender`. If it is missing, say so and how to get it (blender.org, or `winget install BlenderFoundation.Blender` on Windows), and offer the light path meanwhile. 2. **Add-ons.** Run `blender -b -P scripts/blender/check_blender.py`. It prints the version, the GPU Cycles will use, and whether MPFB (human characters), a Blender MCP add-on and Rigify are installed and on. MPFB is needed only for human characters; without it, build characters from shapes. 3. **Blender MCP.** Also look for Blender MCP tools in this session (tool names with `blender` in them). If they are there, use them to show the user the model live in their own Blender window while it is built. If not, say it is not installed and carry on: every export and render goes through `blender -b -P build.py` either way, because `build.py` is the asset's source, a background run gives the same result every time, and MCP export calls can time out on large files. Point the user to the MCP's install guide only if they want the live view. Through the MCP, `kit.py` and `asset3d.py` import and run in the user's Blender (bake and export of a small mug took 2.3 s), but operators that need an active object, such as `bpy.ops.mesh.primitive_cylinder_add`, fail there: build meshes with `bmesh` and the data API instead. ## Kit layout ``` kits/<name>/ kit.json what is in the kit: assets, their sources and outputs, licences style.md the style rules, in numbers where possible tokens.json colours, fonts, line weight, radii, shadow, light and lens refs/ copies of the references the kit was built from 2d/<asset>/ source.svg, asset.html, <asset>@4x.png chars/<name>/ parts.svg, rig.json, turnaround.svg, <name>@4x.png, poses.png 3d/<asset>/ build.py, mesh/, <asset>.glb, <asset>.fbx, <asset>.obj + .mtl, textures/, turntable/ transitions/<name>/ transition.js, transition.html, frames/ (PNG sequence with alpha) sheet.jpg every asset on one sheet ``` `references/kit.md` has the formats of `kit.json`, `tokens.json` and `style.md`. ## Using a kit in a motlab video Copy (never move) the kit into the video's project: `<video>/assets/kits/<name>/`, because the viewer and the renderer only serve the project folder. Read its `style.md` and `tokens.json` before building scenes, and load assets from there: PNGs and SVGs as images, a character through `svgparts.js`, a GLB in the motlab skill's `template-three.html`, a transition by importing its `transition.js`. When the kit changes later, copy it again. ## Keep it above board - Only build from references the user owns or may use, and only rebuild brands and products they own or have permission for. Record each reference's source in `kit.json`. - Downloaded CC0 material (Poly Haven HDRIs and textures) and MPFB's CC0 assets still go in `kit.json` with where they came from. - Fonts keep their licences; note them in `tokens.json`. - No real people's likenesses without their consent. ## Scripts and templates - `scripts/palette.py`: main colours of references; `check` measures assets against `tokens.json`. - `scripts/sheet.py`: labelled review sheet of any images, transparency on a checker. - `scripts/mesh_export.py`: light path, `.npz` meshes to GLB and OBJ + MTL with flat PBR colours. - `scripts/blender/asset3d.py`: main path, `bake()`, `export()`, `turntable()`, and `check` to re-import files. - `scripts/blender/check_blender.py`: Blender version, GPU and add-ons. - `templates/asset.html`: SVG files to transparent PNG at any `--scale`. - `templates/svgparts.js`: a rigged 2D character from `parts.svg` + `rig.json`, posed in a scene. - `templates/transition.js` and `transition.html`: a transition as a layer over a hard cut, and its preview. - `templates/model.html`: turntable stills of a GLB through three.js, transparent. ## Where to read more | When you are… | Read | |---|---| | starting a kit, writing tokens and style rules, naming files | `references/kit.md` | | making icons, illustrations, logos, backgrounds, 2D characters or transitions | `references/2d.md` | | making 3D objects, characters or textures | `references/3d.md` | | modelling a product from reference in Blender | the motlab skill's `references/blender.md` |
© staryone · MIT · staryone/motlab