lookdev
Look development loop for Blender assets combining materials, lighting, camera, and screenshot comparison until shading reads correctly via MCP.
npx skills add arjun988/blender-skills --skill lookdev --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Lookdev Material + light + camera loop. Screenshot compare. Stop when it reads. ## When to Use - Finalizing asset shading before export/portfolio - Turntable / grey shader checks - Matching material references - Bridging `materials` and `lighting` intentionally ## Workflow ``` Clay/grey pass → Base materials → Neutral light rig → Beauty light → Screenshot → Gap list → Iterate (≤3–5) → Optional grade → QA ``` ## Standard Rigs | Rig | Use | |-----|-----| | Neutral 3-point | Evaluate materials fairly | | HDRI studio | Product / character | | In-situ scene lights | Final context | Keep a reusable `COL_Lookdev_Lights` + `CAM_Lookdev_*`. ## Checklist - [ ] Values read in grayscale - [ ] Specular roughness believable - [ ] Edges catch light (bevels/normals) - [ ] Emissive under control - [ ] No pure black / pure white traps unless stylized - [ ] Matches reference palette if provided ## Iteration Rule Each pass: change one major variable (material OR light OR camera), then screenshot. ## Constraints ### MUST DO - Grey pass before fancy textures when forms unsure - Capture screenshots each iteration - Hand off to `qa-review` before ship ### MUST NOT DO - Fix modeling problems only with ro
- When to Use
- Workflow
- Standard Rigs
- Checklist
- Iteration Rule
- Constraints
- MUST DO
- MUST NOT DO
- Reference Guide
What does the lookdev skill do?
Look development loop for Blender assets combining materials, lighting, camera, and screenshot comparison until shading reads correctly via MCP.
How do I install it?
Run `npx skills add arjun988/blender-skills --skill lookdev --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From arjun988/blender-skills, a repository with 71 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.