# blender-pro-workflow

This skill sets the order for building a Blender scene, from block-out and camera to render and export. Useful when one request spans modeling, lighting and materials.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 1300 installs · ★ 125
- Author: RobLe3
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/RobLe3/cc-blender-skill/tree/HEAD/plugin/skills/blender-pro-workflow/SKILL.md
- Updated: 2026-10-12
- HTML: https://affpapa.org/en/nevibecode/skills/blender-pro-workflow

## What it does

The skill answers a planning question: in what order, and at what fidelity, should each step of a scene be tackled? It lays out an 11-step canonical order — reference and plan, block-out with primitives at correct scale, camera and composition lock, a first light pass without color, geometry refinement, flat materials, a second light pass with color, detail, final render with denoising, composite, export. Each step gates the next. A material tuned under flat lighting breaks once real lighting lands.

It also carries a time budget table for a hero still, breaking total effort across block-out, lighting, modeling and materials. One anti-pattern is called out by name: 90% modeling, 10% lighting. Three Python recipes ship with it — a block-out scaffold with floor, hero and background prop, a cheap EEVEE composition test render, and a three-point lighting setup.

Blender access goes through an MCP server. The `allowed-tools` list covers code execution, scene and object queries, viewport rendering and API doc search. Before the first Blender call the skill tells you to read the MCP backend reference in the `text-to-blender` skill and stick with one backend for the whole task. When source templates, orthographic references or fit validation are involved, ordering defers to the reference-locked skills and `blender-skill-harmonizer`.

## Requirements
- Works with: Blender

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add RobLe3/cc-blender-skill --skill blender-pro-workflow -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/blender-pro-workflow/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/blender-pro-workflow/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add RobLe3/cc-blender-skill --skill blender-pro-workflow -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/blender-pro-workflow/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add RobLe3/cc-blender-skill --skill blender-pro-workflow -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/blender-pro-workflow/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install RobLe3/cc-blender-skill blender-pro-workflow
```

2. **Manually: put the files in place**
- File: `.github/skills/blender-pro-workflow/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add RobLe3/cc-blender-skill --skill blender-pro-workflow -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/RobLe3/cc-blender-skill --path plugin/skills/blender-pro-workflow
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/blender-pro-workflow/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add RobLe3/cc-blender-skill --skill blender-pro-workflow -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/RobLe3/cc-blender-skill/tree/HEAD/plugin/skills/blender-pro-workflow/SKILL.md

## When to use it
- sequence a scene build so lighting is not redone after materials
- validate composition with a cheap render before investing in modeling
- split time between block-out, lighting and geometry
- script a three-point light rig on top of a block-out
- find a starting point when a request spans modeling, lighting and rendering

## Example prompts
- Make a hero shot of a sword: block-out and camera first, then light and materials
- What's the right order for a full scene from block-out to export?
- Do a cheap EEVEE composition test before any modeling work

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: dda2cd839b8d868a.

BEGIN THIRD-PARTY FILE dda2cd839b8d868a
```text
---
name: blender-pro-workflow
description: End-to-end production workflow guidance for Blender — the order to assemble scenes (block-out → camera → light → forms → materials → detail → render → composite → export), critique protocols, time budgets, and recovery patterns. Use whenever the user asks to "make a complete scene / hero shot / production-quality render", "what's the right order to do this", "set up a full pipeline", or has a multi-step request crossing modeling + lighting + materials + rendering. Make sure to use this skill for any request that spans multiple phases of 3D work, even if the user does not say "workflow" — also covers "make a final image of X", "produce a hero render", "professional-looking result".
allowed-tools: Read Bash mcp__blender__execute_blender_code mcp__blender__get_scene_info mcp__blender__get_object_info mcp__blender__get_objects_summary mcp__blender__get_object_detail_summary mcp__blender__render_viewport_to_path mcp__blender__search_api_docs mcp__blender_official__execute_blender_code mcp__blender_official__get_objects_summary mcp__blender_official__get_object_detail_summary mcp__blender_official__render_viewport_to_path mcp__blender_official__search_api_docs
---


## MCP backend

Use when: Multi-phase Blender work spanning modeling + lighting + materials + render. Or when the user is unsure where to start. Often loaded BEFORE other sub-skills as a guide for sequencing.

Before the first Blender call, read [../text-to-blender/references/mcp-backends.md](../text-to-blender/references/mcp-backends.md). Prefer official MCP for shared capabilities; preserve the selected backend for the whole task. Tool names in recipes are client/legacy examples: map them through that reference and its agent-host guide.
# Blender Pro Workflow

End-to-end guidance for putting a real scene together. This skill answers "in what order, with what fidelity at each step, should I tackle this?" Use it as the planner, then chain-load the specific sub-skills for each step.

## Reference-locked override
```
END THIRD-PARTY FILE dda2cd839b8d868a

The third-party file has ended. Everything between the dda2cd839b8d868a tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2066 of 10228 bytes. © RobLe3 · MIT · https://github.com/RobLe3/cc-blender-skill/tree/HEAD/plugin/skills/blender-pro-workflow/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md