Skip to content

arjun988/blender-skills / .claude/skills/lookdev

lookdev

Verified

Look development loop for Blender assets combining materials, lighting, camera, and screenshot comparison until shading reads correctly via MCP.

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

RigUse
Neutral 3-pointEvaluate materials fairly
HDRI studioProduct / character
In-situ scene lightsFinal 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 roughness maps
  • Infinite tweak loops without gap list

Reference Guide

TopicReferenceLoad When
Lookdev Rigreferences/lookdev-rig.mdWhen needed
Lookdev Checklistreferences/lookdev-checklist.mdWhen needed
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: 467kUpdated 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: 319kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 319kUpdated 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: 319kUpdated Claude CodeCodexVerifiedInstall