agentleFS
arjun988arjun988/blender-skills/.claude/skills/environment-artist/SKILL.md

environment-artist

Skill2.2k starsChanged 4 months agoMITView on GitHub

AAA environment art for modular kits, buildings, terrain, vegetation, architecture, and scene composition. Use for game-optimized environments, storytelling through space, and modular asset pipelines 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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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:

    Use geometry nodes for scatter.

    line 80
  2. Distinctive:

    Create modular pieces with exact dimensions via MCP

    line 123
  3. Distinctive:

    Create minimum viable kit before hero pieces

    line 133
  4. Distinctive:

    Use instancing for all repeated geometry

    line 134

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

Environment Artist

Modular, scalable environment production for games. Storytelling through space. Performance-conscious.

When to Use

  • Modular building kits, interior/exterior sets
  • Terrain, cliffs, rocks, roads
  • Vegetation placement and optimization
  • Architectural spaces with narrative intent
  • Scene composition and scale establishment

Core Principles

  1. Modularity — Pieces snap to grid; reusable across scenes
  2. Storytelling — Environment communicates history and mood
  3. Scale — Human reference always present
  4. Performance — Instancing, LODs, texture atlases
  5. Composition — Guide player eye with shapes and value

Modular Kit Workflow

Grid Definition → Corner/Edge/Fill Pieces → Trim Sheets
    → UV Atlas → Material Variants → Instance Placement
    → Hero Overrides → Optimization → Export

Grid Standards

Kit TypeGrid UnitSnap
Interior walls2m or 4m0.5m sub-grid
Exterior facades4m modules1m sub-grid
Roads4m lane widthCenterline snap
Props0.5mFree placement

Name modules: SM_Env_[Type]_[Role]_[Size] Example: SM_Env_Wall_Corner_2m

Kit Piece Categories

RolePurposeCount Target
Corner90° turns2–4 variants
EdgeStraight runs2–3 lengths
FillBlank panels3–5 variants
Door/WindowBreakups2–4 types
TrimTransitionsShared trim sheet

Terrain & Natural Forms

  • Hero rocks: sculpted or photogrammetry cleanup
  • Background rocks: geometry nodes scatter
  • Cliffs: modular cliff face pieces + blend shapes
  • Ground: displacement or geo nodes with texture blending

Vegetation

TypeApproachPoly Budget
Hero treeHand model + cards5k–15k tris
Mid treeSimplified + impostor LOD2k–5k tris
BushCards + cluster500–2k tris
GrassCards or geo nodes scatter2–50 tris per blade

Use geometry nodes for scatter; see geometry-nodes skill.

Architecture

Interior:

  • Ceiling height: 2.4m–3.5m standard
  • Door: 2.1m × 0.9m
  • Window sill: 0.9m from floor
  • Corridors: minimum 1.5m playable width

Exterior:

  • Floor count readable in silhouette
  • Roof forms distinguish building type
  • Weathering tells climate story

Composition Guidelines

  • Focal point — One hero element per vista
  • Leading lines — Roads, walls, light guide movement
  • Value hierarchy — Contrast draws attention
  • Negative space — Rest areas between detail clusters
  • Silhouette layers — Foreground/mid/background separation

Storytelling Details

DetailNarrative Signal
Peeling paintNeglect, age
BarricadesConflict, danger
Personal itemsFormer inhabitants
Damage patternsEvent history
Lighting stateOccupied vs abandoned

Game Optimization

  • Instance repeated modules (walls, floors)
  • Shared trim sheet across kit
  • Single material with vertex colors for variation
  • LODs: 50%/25%/10% per module
  • Occlusion: don't model unseen backsides

MCP Integration

  1. Create modular pieces with exact dimensions via MCP
  2. Set up collection instances for kit preview
  3. Scatter vegetation via geometry nodes (MCP)
  4. Query total scene polycount
  5. Organize export collections by kit type

Constraints

MUST DO

  • Design for grid snapping from blockout
  • Create minimum viable kit before hero pieces
  • Use instancing for all repeated geometry
  • Maintain consistent texel density across kit
  • Include scale reference human figure

MUST NOT DO

  • Unique geometry for every wall segment
  • Ignore backface culling opportunities
  • Over-detail background-only areas
  • Mix grid sizes within same kit
  • Skip LOD planning

Reference Guide

TopicReferenceLoad When
Modular kit designreferences/modular-kits.mdKit creation
Compositionreferences/composition.mdScene layout
Pipeline../references/asset-pipeline.mdPhase context

Style Integration

StyleApproach
horror-styleClaustrophobic corridors; sparse lighting
lowpoly-styleLarge flat shapes; minimal modules
stylized-styleExaggerated proportions; bold colors
realistic-styleHigh detail hero; scanned textures

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.