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

blender-modeler

Skill2.2k starsChanged 4 months agoMITView on GitHub

Core Blender modeling specialist for Edit Mode, modifiers, collections, precision modeling, and scene organization. Use for general 3D modeling, blockouts, cleanup, non-destructive workflows, and scene structure in Blender via MCP.

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.

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    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:

    Keep booleans live until export prep

    line 68
  2. Distinctive:

    Never stack multiple subsurf without supporting loops

    line 70
  3. Distinctive:

    Document modifier purpose in object custom properties if complex

    line 71
  4. Distinctive:

    Use numeric input for exact dimensions

    line 89
  5. Distinctive:

    Use orthographic views for architectural accuracy

    line 92
  6. Distinctive:

    Prefer instances over duplicate geometry for repeated elements.

    line 103
  7. Distinctive:

    Keep blockout separate from final geo

    line 139
  8. Distinctive:

    Delete blockout before silhouette approved

    line 144
  9. Distinctive:

    Leave default names (Cube.001)

    line 146

≈ “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

Blender Modeler

Foundation modeling skill for all Blender geometry work. Non-destructive by default. MCP-first execution.

When to Use

  • Blockouts and primary/secondary shape passes
  • General mesh editing not covered by discipline specialists
  • Scene organization, collections, instances
  • Modifier stack management
  • Cleanup: merge, normals, loose geometry
  • Precision modeling with snapping and numeric input

Core Workflow

1. Scene Setup     → Collections, scale reference, naming
2. Blockout        → Primitives, mirror, array
3. Shape Refinement → Edit mode or modifier-based edits
4. Modifier Stack  → Non-destructive detail
5. Cleanup         → Merge, normals, manifold check
6. Handoff         → UV/materials or discipline specialist

Scene Organization

Establish via MCP immediately:

COL_Project
├── COL_Reference      # Scale refs, ortho images
├── COL_Blockout       # Temporary blockout meshes
├── COL_Geo            # Final geometry
├── COL_Collision      # Proxy meshes
└── COL_Instances      # Empties/collections for instancing

Naming: ../references/naming-conventions.md

Modifier Stack Philosophy

Preferred order (bottom to top):

1. Mirror          # Symmetry
2. Array           # Repetition
3. Solidify        # Thickness
4. Boolean         # Cuts (prefer live booleans until export)
5. Bevel           # Edge detail
6. Weighted Normal # Hard surface shading
7. Subdivision     # Only when topology supports it

Rules:

  • Keep booleans live until export prep
  • Apply mirror only when topology is finalized
  • Never stack multiple subsurf without supporting loops
  • Document modifier purpose in object custom properties if complex

Edit Mode Essentials

OperationUse When
Extrude (E)Adding depth from faces
Inset (I)Panel lines, frames
Loop Cut (Ctrl+R)Adding resolution
Knife (K)Custom cuts
Merge by DistanceCleanup duplicates
Recalculate NormalsFix shading issues

Via MCP: execute equivalent operations; don't narrate UI.

Precision Modeling

  • Enable snapping to grid/vertex/edge as appropriate
  • Use numeric input for exact dimensions
  • Set cursor to world origin for modular alignment
  • Apply scale before boolean operations
  • Use orthographic views for architectural accuracy

Instancing Strategy

MethodUse Case
Linked Duplicate (Alt+D)Identical props with variation potential
Collection InstanceModular kit pieces
Geometry NodesProcedural scatter (see geometry-nodes)
Array ModifierLinear repetition

Prefer instances over duplicate geometry for repeated elements.

Custom Normals

  • Enable Auto Smooth with appropriate angle (30°–60° hard surface)
  • Weighted Normal modifier for hard surface without extra geo
  • Mark sharp edges explicitly for bevel control
  • Clear custom split normals before retopology handoff

Cleanup Checklist

  • Merge by distance (threshold: 0.0001m default)
  • Remove loose geometry
  • Delete interior faces
  • Recalculate outside normals
  • Apply scale if modifiers depend on it
  • Verify manifold (no holes unless intentional)
  • Check triangle count vs budget

MCP Integration

1. Create mesh objects via MCP
2. Apply modifiers via MCP
3. Query polycount after each major edit
4. Organize into collections via MCP
5. Duplicate to backup collection before destructive ops

See ../references/mcp-integration.md

Constraints

MUST DO

  • Non-destructive workflow until export phase
  • Name objects SM_ prefix immediately
  • Keep blockout separate from final geo
  • Apply transforms before boolean/export
  • Validate topology before handoff

MUST NOT DO

  • Delete blockout before silhouette approved
  • Apply all modifiers prematurely
  • Leave default names (Cube.001)
  • Model without scale reference
  • Skip cleanup pass

Reference Guide

TopicReferenceLoad When
Modifier deep divereferences/modifier-stack.mdComplex modifier chains
Scene organizationreferences/scene-organization.mdLarge scenes
Pipeline../references/asset-pipeline.mdPhase context

Handoff Points

To SkillWhen
hard-surfaceMechanical/sci-fi detail pass
environment-artistModular environment pieces
character-artistOrganic human forms
uv-workflowTopology locked, ready for UVs
asset-optimizationPre-export performance pass

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.