Skip to content

arjun988/blender-skills / .claude/skills/scene-assembly

scene-assembly

Verified

Large scene layout in Blender with collections, linking, overrides, streaming-friendly organization, and set assembly via MCP.

Scene Assembly

Layouts that scale. Clear collections. Linking/overrides for big sets.

When to Use

  • Levels, dioramas, cinematic sets
  • Assembling modular kits into spaces
  • Library linking / collection instances
  • Outliner structure for team scenes

Workflow

Block layout (greybox) → Modular assemble → Set dressing
  → Lighting volumes → Cameras → QA pass → Optimize visibility

Collection Structure

COL_Layout
COL_Modular_Geo
COL_SetDressing
COL_Lights
COL_Cameras
COL_FX
COL_Collision
COL_Trash / COL_Ref

Linking Strategy

ApproachWhen
Collection instanceRepeated modular pieces
Library link + overrideShared hero assets across scenes
AppendOne-off ownership transfer

Prefer non-destructive linking for repeated kits.

Layout Rules

  1. Greybox scale and navigation first
  2. Snap to grid for modular kits
  3. Hide heavy collections while dressing
  4. Keep world origin meaningful (level zero)

Performance Hygiene

  • Instance repeated meshes
  • Cull unseen interiors
  • Separate streaming volumes if game-oriented
  • Avoid unique high materials on every duplicate

Handoff

  • Dressing → set-dressing
  • Mood → lighting + style skill
  • Gate → qa-review

Constraints

MUST DO

  • Establish collection hierarchy early
  • Greybox before final dressing
  • Name cameras and light groups

MUST NOT DO

  • Dump everything in Scene Collection
  • Apply library overrides casually without need
  • Duplicate hero meshes instead of instancing

Reference Guide

TopicReferenceLoad When
Collection Templatereferences/collection-template.mdWhen needed
Linking Overridesreferences/linking-overrides.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: 471kUpdated 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: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated 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: 322kUpdated Claude CodeCodexVerifiedInstall