agentleFS
arjun988arjun988/blender-skills/.claude/skills/lighting/SKILL.md

lighting

Skill2.2k starsChanged 4 months agoMITView on GitHub

Cinematic and game lighting in Blender including three-point lighting, HDRI, horror lighting, volumetrics, rim lighting, and mood-driven illumination. Use for look development and scene atmosphere via MCP.

2 other projects use 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 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 projectsWeek of Nov 8: 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

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Avoid flat even illumination

    line 81
  2. Distinctive:

    Create lights with naming convention via MCP

    line 103
  3. Distinctive:

    Test readability of gameplay-critical areas

    line 114
  4. Distinctive:

    Place lights without purpose

    line 122

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Lighting Artist

Mood-driven illumination. Guide player attention. Support art direction.

When to Use

  • Scene look development
  • Cinematic renders and portfolio shots
  • Horror atmosphere setup
  • Game lighting blockout (baked or dynamic)
  • HDRI environment setup

Workflow

Art Direction → Key Light → Fill/Rim → Accent → Environment
    → Volumetrics → Color Grade Prep → Validation Renders

Three-Point Lighting

LightPurposeTypical Setup
KeyPrimary illumination45° above, 30° side
FillShadow softeningOpposite key, 1/2–1/4 intensity
RimSubject separationBehind subject, bright edge

Naming: LGT_Key_Main, LGT_Fill_Soft, LGT_Rim_Back

Light Types

TypeUse Case
SunOutdoor directional
AreaSoft studio, windows
SpotFlashlights, stage, horror
PointBulbs, emissive fill

Color Temperature

MoodKelvinRGB Approx
Candle/warm1800KOrange
Tungsten3200KWarm white
Daylight5500KNeutral white
Overcast6500KCool white
Moonlight8000K+Blue

Horror: mix warm interior tungsten with cold exterior moonlight.

HDRI Workflow

1. Select HDRI matching mood (overcast for horror, clear for hero)
2. Rotate to place brightest area as key
3. Adjust strength (0.5–2.0 typical)
4. Supplement with area lights for subject separation
5. Hide HDRI in background if using solid color/fog

Horror Lighting

See horror-style skill. Key techniques:

  • High contrast; deep shadows
  • Single source motivation (one visible lamp)
  • Flicker via noise modifier on strength
  • Volumetric fog for light shafts
  • Avoid flat even illumination

Volumetrics

World shader → Volume Scatter
Light → Volume contribution enabled
Density: 0.01–0.1 (subtle to heavy fog)
Anisotropy: 0.3–0.8 for visible light shafts

Game vs Cinematic

AspectGameCinematic
Light countMinimal (performance)Unlimited
BakedLightmaps commonPath trace
DynamicReal-time shadowsRay traced
MoodGameplay readabilityArtistic freedom

MCP Integration

  1. Create lights with naming convention via MCP
  2. Set color, intensity, angle via MCP
  3. Configure world HDRI via MCP
  4. Query light count and types
  5. Organize in COL_Lights collection

Constraints

MUST DO

  • Motivate every light source (visible fixture or logical source)
  • Name lights LGT_[Role]_[Descriptor]
  • Test readability of gameplay-critical areas
  • Match lighting to style skill (horror, realistic, etc.)
  • Separate lighting collections from geometry

MUST NOT DO

  • Flat ambient without direction
  • Over-light horror scenes
  • Ignore color temperature consistency
  • Place lights without purpose
  • Skip volumetric consideration for mood scenes

Reference Guide

TopicReferenceLoad When
Horror setupsreferences/horror-lighting-setups.mdHorror scenes
Cinematic rigsreferences/cinematic-light-rigs.mdPortfolio renders

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.