Skip to content

arjun988/blender-skills / .claude/skills/uv-workflow

uv-workflow

Verified

Production UV unwrapping for seam placement, UV packing, texel density, UDIM, lightmap UVs, and modular UV layouts. Use when preparing meshes for texturing and engine export in Blender via MCP.

UV Workflow

Efficient UV layouts with consistent texel density. Seams at hidden edges. Engine-ready.

When to Use

  • After topology locked, before texturing
  • Modular kit UV atlas planning
  • Lightmap UV channel setup
  • UDIM workflows for hero assets

Workflow

UV Planning → Seam Marking → Unwrap → Texel Density Check
    → Pack → Mirror/Overlap Decision → Lightmap UV (if needed) → Validation

Seam Placement Rules

Place seams at:

  • Back of head, spine centerline
  • Inner arms, inner legs
  • Bottom of chin, underside of objects
  • Panel edges on hard surface (construction seams)
  • Hidden areas under clothing/overlaps

Never place seams on:

  • Face (front)
  • Primary gameplay-visible surfaces
  • Deforming joint centers (relocate to nearby hidden area)

Texel Density

Formula: Texel Density = Texture Resolution / UV Island Size in UV space

Target consistency across visible surfaces:

Asset TierTarget TD (px/m)
Hero512–1024 px/m
Standard256–512 px/m
Background128–256 px/m

Use same density for modular kit pieces sharing atlas.

Unwrap Methods

MethodUse When
Smart UV ProjectQuick blockout UVs only
Follow Active QuadsStrip UVs (roads, limbs)
Cube ProjectBoxy hard surface
Lightmap PackLightmap channel
Manual seam + UnwrapProduction default

UV Packing

  • Margin: 0.002–0.01 UV units (engine dependent)
  • Rotate islands for maximum packing efficiency
  • Group islands by material ID
  • Keep related islands near each other in UV space
  • Use UVPackmaster or native pack for production

Mirrored UVs

  • Mirror UVs for symmetrical characters (save texture space)
  • Offset mirrored islands slightly if engine requires unique bakes
  • Mark mirrored halves in object naming: _L / _R meshes if separate

UDIM Workflow

For hero assets exceeding single 4K texture:

  • Tile 1001: head
  • Tile 1002: torso
  • Tile 1003: limbs
  • Document tile assignment in production brief

Lightmap UVs

Second UV channel requirements:

  • No overlapping islands
  • Consistent texel density less critical
  • Larger margin (0.02+) for light bleed prevention
  • Pack separately from texture UVs

Modular UV Atlas

1. Plan shared atlas resolution (2048/4096)
2. Assign UV islands per module to atlas regions
3. Trim sheet regions for repeating detail
4. Vertex color variation for module differentiation
5. Document atlas layout for texture artist

MCP Integration

  1. Mark seams via MCP if supported
  2. Execute unwrap via MCP
  3. Query UV island count and pack efficiency
  4. Assign UV channels via MCP
  5. Validate no overlapping UVs (except intentional mirror)

Validation Checklist

  • No unintended overlapping UVs
  • Consistent texel density on visible surfaces
  • Seams hidden at gameplay angles
  • UV islands within 0–1 (or UDIM tiles assigned)
  • Lightmap channel separate if required
  • Pack efficiency > 75%

Constraints

MUST DO

  • Plan UVs before final modeling (topology informed by UV needs)
  • Maintain texel density consistency
  • Hide seams at logical construction edges
  • Create lightmap UVs for baked lighting pipelines
  • Document atlas layout for modular kits

MUST NOT DO

  • Smart UV Project as final production UVs
  • Overlapping UVs on unique surface detail (unless mirrored)
  • Inconsistent texel density on same asset tier
  • Seams across faces or primary visible surfaces
  • Skip packing margins

Reference Guide

TopicReferenceLoad When
Texel density calcreferences/texel-density.mdHero assets
Trim sheetsreferences/trim-sheets.mdModular kits
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: 470kUpdated 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: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated 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: 322kUpdated Claude CodeCodexVerifiedInstall