Skip to content

arjun988/blender-skills / .claude/skills/asset-optimization

asset-optimization

Verified

Validates and optimizes Blender assets for polycount, topology, UV efficiency, material count, naming, collections, and game-ready performance. Use before export on all production assets via MCP.

Asset Optimization

Enforce budgets. Clean geometry. Game-ready validation gate before export.

When to Use

  • Before every export
  • After modeling complete
  • LOD generation
  • Scene-wide performance audit
  • Pre-delivery validation

Workflow

Audit → Identify Issues → Fix → Re-Audit → LOD Generation → Validation Report

Audit Checklist

Run via MCP scene queries where possible:

Geometry

  • Triangle count vs budget (../references/polycount-budgets.md)
  • Duplicate vertices merged
  • Loose geometry removed
  • Non-manifold fixed
  • Interior faces deleted
  • Applied transforms (scale 1,1,1)

UVs

  • Pack efficiency > 75%
  • Texel density consistent
  • No unintended overlaps

Materials

  • Count within budget
  • No unused slots
  • Names follow MAT_ convention

Organization

  • All objects named SM_ prefix
  • Collections organized per convention
  • Collision meshes in COL_Collision

Optimization Techniques

IssueFix
Over budgetRemove unseen geo, decimate, bake detail
High triangle count on flat surfacesReduce subdiv/bevel segments
Many draw callsMerge materials; atlas textures
Repeated geometryConvert to instances
Heavy modifiersApply and merge strategically

LOD Generation

LOD0: Full detail (hero)
LOD1: 50% tris — remove micro-bevels, small greebles
LOD2: 25% tris — decimate modifier; preserve silhouette
LOD3: 10% tris — impostor/card or simple proxy

Naming: SM_Asset_LOD0, SM_Asset_LOD1, etc.

Use Decimate modifier:

  • Planar mode for hard surface
  • Collapse mode for organic
  • Always verify silhouette after decimate

Modifier Cleanup

Before export:

  1. Apply stack OR export with modifiers per engine support
  2. Remove unused modifiers
  3. Collapse mirror/array if instances not needed
  4. Document which modifiers remain live

Scene Audit Report Template

## Optimization Report: [Asset/Scene]

**Total Triangles:** [count] (budget: [target])
**Draw Calls (materials):** [count]
**Objects:** [count]
**Issues Fixed:** [list]

### Per-Object Breakdown
| Object | Tris | Materials | Status |
|--------|------|-----------|--------|
| SM_... | ... | ... | PASS/FAIL |

MCP Integration

  1. Query polycount per object via MCP
  2. Query material count via MCP
  3. Run cleanup operations via MCP
  4. Generate LOD duplicates via MCP
  5. Validate naming conventions via MCP scene tree

Constraints

MUST DO

  • Run full validation before export
  • Document polycount in production brief
  • Create LODs for hero assets in games
  • Fix all non-manifold before export
  • Output validation report

MUST NOT DO

  • Export without budget check
  • Decimate deforming meshes without testing
  • Remove collision proxies
  • Skip naming convention validation
  • Optimize hero face/hands below animation needs

Reference Guide

TopicReferenceLoad When
Full validation../references/validation-checklist.mdFinal gate
Polycount budgets../references/polycount-budgets.mdBudget setting
LOD strategiesreferences/lod-strategies.mdLOD creation
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 468kUpdated Claude CodeCodexUnverifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 321kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 321kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 321kUpdated Claude CodeCodexVerifiedInstall