Skip to content

arjun988/blender-skills / .claude/skills/environment-artist

environment-artist

Verified

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.

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
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall