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

rendering

Skill2.2k starsChanged 4 months agoMITView on GitHub

Blender rendering with Cycles and Eevee including sampling, denoising, camera setup, render passes, color management, and render optimization. Use for final output and look validation via MCP.

4 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 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

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

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use render region for test crops

    line 91
  2. Very specific:

    When matching a photo/concept (../references/reference-image-match.md):

    line 109
  3. Very specific:

    Run ../references/visual-match-checklist.md before delivery.

    line 120
  4. Distinctive:

    Screenshot or render compare: when reference image was provided

    line 134
  5. Distinctive:

    Use denoising for Cycles production renders

    line 135
  6. Distinctive:

    Use Cycles for real-time game preview needs

    line 145

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “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

Rendering

Appropriate engine selection. Optimized settings. Production render passes.

When to Use

  • Final portfolio/cinematic renders
  • Look development validation
  • Render pass output for compositing
  • Game asset preview renders (Turntable)
  • Style validation (realistic vs stylized)

Engine Selection

EngineUse When
CyclesFinal quality, realistic, portfolio
EeveeReal-time preview, stylized, game look dev
Eevee NextImproved real-time quality (Blender 4+)

Workflow

Camera Setup → Render Settings → Sample Tests → Full Render
    → Pass Output → Color Management → Delivery

Camera Setup

Naming: CAM_[Shot]_[Number]

  • Focal length: 35mm (environment), 85mm (hero detail), 24mm (wide horror)
  • Depth of field: subject distance focused
  • Composition: rule of thirds; leading lines
  • Turntable: empty parent rotating 360° for asset preview

Cycles Settings

SettingPreviewProduction
Samples64–128512–2048
DenoiseOpenImageDenoiseOpenImageDenoise
Max bounces812
CausticsOff (default)On if glass/water hero

Eevee Settings

SettingValue
Screen Space ReflectionsOn for metals
Ambient OcclusionOn
BloomStylized/ emissive scenes
Shadow resolution2048+
Contact ShadowsGround contact

Render Passes

PassUse
CombinedFinal composite
Diffuse Direct/IndirectRelighting
GlossyReflection control
NormalCompositing effects
AOContact shadow enhancement
Z (Depth)DOF, fog in comp
CryptomatteObject masking
EmissionScreen glow effects

Color Management

View Transform: AgX (Blender 4+) or Filmic
Look: Medium Contrast (default) or High Contrast (dramatic)
Exposure: Adjust in compositor, not by blowing lights

Render Optimization

  • Use render region for test crops
  • Adaptive sampling (Cycles)
  • Disable unseen objects in render layers
  • GPU rendering default when available
  • Persistent data for animation sequences

Asset Turntable Template

1. CAM_Turntable at 3/4 height, 45° angle
2. Empty at asset origin → rotate animation 0–360° (120 frames)
3. 3-point lighting rig
4. Render 1280×1280 or project-specified resolution
5. Output PNG sequence or MP4

Reference Image Validation

When matching a photo/concept (../references/reference-image-match.md):

SettingReference match
Hero cameraMatch reference angle before grading
AgX LookBase Contrast default; High Contrast if reference is punchy
Exposure0.15–0.45 typical; hull must read, not clip white
Preview playbackEEVEE, motion blur off, taa_samples 1–8
Final stillRender at hero CAM_* — compare to reference
Compare toolget_viewport_screenshot or bpy render still

Run ../references/visual-match-checklist.md before delivery.

MCP Integration

  1. Configure render engine settings via MCP
  2. Setup camera via MCP
  3. Trigger test render via MCP if supported
  4. Query render settings validation
  5. Set output paths via MCP

Constraints

MUST DO

  • Match render engine to project style
  • Screenshot or render compare when reference image was provided
  • Use denoising for Cycles production renders
  • Setup color management before final render
  • Render validation turntable for hero assets
  • Organize cameras in COL_Cameras

MUST NOT DO

  • Production render without sample test
  • Ignore color management (sRGB vs Linear)
  • Render at excessive resolution without purpose
  • Skip render passes when compositing planned
  • Use Cycles for real-time game preview needs

Reference Guide

TopicReferenceLoad When
Pass compositingreferences/render-passes.mdMulti-pass output
NPR/stylized renderreferences/npr-rendering.mdStylized-style projects
Reference image match../references/reference-image-match.mdPhoto/concept attached
Visual match validation../references/visual-match-checklist.mdBefore delivery

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