Part 5 — Developer-oriented scene organization

A scene that grows past a handful of objects becomes a maintenance problem — exactly like an unstructured codebase. When you drive Blender entirely through Claude Code, the names and structure are doubly important, because they are how you and Claude refer to things in plain language. A prompt like “move the front-left wheel up” only works if the front-left wheel is actually called car_wheel_fl and not Cylinder.004.

This part covers two habits that pay off immediately: enforcing clear, conventional object names, and using collections as the folder structure of your scene. You will never touch Python — you simply prompt Claude, and it applies the conventions across the whole scene for you.

Lesson 13: Naming Rules

Blender hands every primitive a generic, auto-incrementing name: Cube, then Cube.001, then Cube.002, and so on. Those names tell you nothing about what the object is, and they make natural-language prompts ambiguous. Teach Claude your naming convention early — before the scene fills up — and every object will arrive correctly labeled.

Use lowercase_snake_case with a category prefix and, where it helps, a position or index suffix. Good object names read like self-documenting identifiers:

car_body
car_cabin
car_wheel_fl
car_wheel_fr
car_wheel_rl
car_wheel_rr
garage_wall_front
garage_roof
crate_wood_01
barrel_red_01

Notice the patterns: a shared prefix groups related parts (car_, garage_), position codes disambiguate repeated parts (fl, fr, rl, rr for front/rear left/right), and a zero-padded index (_01) leaves room to add more of the same kind. Avoid names that are generic, vague, or one-off:

Cube.001
Cylinder.004
Thing
Object
FinalCar

Collections deserve the same discipline. Give them a consistent prefix so they sort together and read as structure rather than as random groups:

collection_environment
collection_vehicle
collection_props
collection_lighting
collection_camera

The most reliable way to keep names clean is to make the rule part of how you ask. Hand Claude this instruction up front, and it will name objects correctly as it builds — instead of leaving you a pile of Cube.001s to clean up later:

Name every object clearly using lowercase_snake_case. Do not leave objects named Cube, Cylinder, Sphere, or Plane.

Lesson 14: Collections as Project Structure

Collections are Blender’s folders. They let you group objects, show and hide whole groups at once, and keep the Outliner readable as a scene grows. For a developer, the mental model is simple: a collection is a directory, and your objects are the files inside it. A well-organized scene has a shallow, predictable tree where every object lives in exactly one obvious place.

Here is what a tidy scene looks like — a top-level scene grouping with one collection per concern, and clearly named objects inside each:

garage_scene
├── collection_environment
│   ├── ground_plane
│   ├── road_main
│   └── sidewalk_left
├── collection_building
│   ├── garage_wall_front
│   ├── garage_roof
│   └── garage_door
├── collection_vehicle
│   ├── car_body
│   └── car_wheel_fl
├── collection_props
│   ├── crate_wood_01
│   └── barrel_red_01
├── collection_lighting
│   └── area_light_main
└── collection_camera
    └── camera_main

Separating concerns this way makes the scene easy to work with: hide collection_building to see inside the garage, toggle collection_lighting while tuning a look, or export only collection_vehicle when you need the car on its own. Claude can build and maintain this structure for you — you just describe the layout you want and let it sort the objects in:

Organize the scene into collections:
- collection_environment
- collection_building
- collection_vehicle
- collection_props
- collection_lighting
- collection_camera

Move any misplaced objects into the correct collection.

Run this on a flat scene and Claude inspects what exists, creates any missing collections, and moves each object into the right one — turning a single undifferentiated list into the structured tree above, with no manual drag-and-drop in the Outliner and no Python on your part.