agentleFS
Sign inStart free
arjun988arjun988/blender-skills/.claude/skills/lookdev/SKILL.md

lookdev

Skill2.2k starsChanged 4 months agoMITView on GitHub

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

1 other project uses a version of this.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Most recently taken up by

Who's talking about arjun988/blender-skills

The biggest 5 of 12 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 12

Talked about on GitHub (12 times).

On GitHub · 12

7 more on GitHub

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Keep a reusable COL_Lookdev_Lights + CAM_Lookdev_*.

    line 41

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free