agentleFS
arjun988arjun988/blender-skills/.claude/skills/geometry-nodes/SKILL.md

geometry-nodes

Skill2.2k starsChanged 4 months agoMITView on GitHub

Blender Geometry Nodes for procedural modeling, scatter systems, vegetation, buildings, pipes, cables, and reusable node groups. Use for procedural asset generation and instancing pipelines 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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    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:

    Document input ranges in group name or custom properties

    line 37
  2. Distinctive:

    Always expose seed as group input for art direction iteration.

    line 74
  3. Distinctive:

    Create geometry nodes modifier via MCP

    line 97
  4. Distinctive:

    Document which approach per target engine.

    line 110
  5. Distinctive:

    Create reusable node groups, not one-off trees

    line 115
  6. Distinctive:

    Test at min/max parameter extremes

    line 117

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

Geometry Nodes

Reusable procedural systems. Parametric assets. Performance-aware instancing.

When to Use

  • Scatter systems (rocks, vegetation, debris)
  • Parametric buildings, roads, pipes, cables
  • Procedural variation without unique modeling
  • Kit assembly with randomization
  • Non-destructive iteration on large scenes

Workflow

Define Parameters → Build Node Tree → Create Node Group (GN_)
    → Test Variations → Bake/Instance Decision → Export Integration

Node Group Standards

  • Prefix: GN_[System]_[Descriptor]
  • Expose only necessary inputs (seed, density, scale range)
  • Document input ranges in group name or custom properties
  • Version node groups: GN_Scatter_Rocks_v02

Core Patterns

Scatter System

Mesh Surface → Distribute Points on Faces → Instance on Points
    → Randomize Rotation (Z) → Randomize Scale → Realize (optional)

Building Generator

Floor Count (input) → Repeat Mesh → Stack Instances
    → Window Cut Pattern → Material Variation → Output

Cable/Pipe Routing

Curve Input → Curve to Mesh (profile) → Subdivide → Set Material
    → Multiple curves from single path node

Rock Formation

Ico Sphere → Displace (noise) → Decimate → Instance Scatter

Randomization

ParameterTypical Range
Scale0.8–1.2 (uniform or per-axis)
Rotation Z0–360°
Density0.1–2.0 per m²
SeedInteger for reproducibility

Always expose seed as group input for art direction iteration.

Performance Rules

ScenarioApproach
Game exportRealize instances → decimate → export mesh
Background scatterKeep instanced; limit count
Hero proceduralBake to static mesh for engine
Viewport previewLimit instance count attribute

Reusable Systems Library

GroupPurpose
GN_Scatter_ObjectsGeneric surface scatter
GN_Array_ModularLinear modular repetition
GN_Curve_PipePipe/cable along curve
GN_Wall_VariantParametric wall sections
GN_Vegetation_ClusterTree/bush clustering

MCP Integration

  1. Create geometry nodes modifier via MCP
  2. Configure group inputs via MCP
  3. Query instance count and final polycount
  4. Realize geometry for export via MCP
  5. Organize GN objects in dedicated collection

Integration with Export

Before export:

  1. Apply geometry nodes modifier OR
  2. Realize instances and merge OR
  3. Export as instances if engine supports (Unreal HISM)

Document which approach per target engine.

Constraints

MUST DO

  • Create reusable node groups, not one-off trees
  • Expose seed and density as inputs
  • Test at min/max parameter extremes
  • Realize/bake before game export unless engine supports instances
  • Name groups with GN_ prefix

MUST NOT DO

  • Million-instance scatter without LOD/culling plan
  • Nested realize operations (performance killer)
  • Hardcode values that should be inputs
  • Export procedural without polycount validation
  • Skip variation testing at boundary values

Reference Guide

TopicReferenceLoad When
Scatter recipesreferences/scatter-systems.mdEnvironment scatter
Building generatorsreferences/building-generators.mdArchitectural procedural

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.