agentsclimarketplace

Texture workflow

Skill arjun988/blender-skills/.cursor/skills/texture-workflow

Production texture workflow for atlases, baking AO/curvature/normal/roughness maps, decals, and texture memory optimization. Use for game-ready texture pipelines in Blender via MCP.From its SKILL.md

Install
npx -y skills add arjun988/blender-skills --skill texture-workflow

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.9 KB, 866 tokens by cl100k_base, as published. Nobody here has run it

Texture Workflow

Bake high-poly detail to efficient texture sets. Optimize memory. Engine-ready outputs.

When to Use

  • Baking sculpt detail to normal maps
  • Creating texture atlases for modular kits
  • PBR texture set generation
  • Decal placement and blending
  • Texture memory optimization

Workflow

High/Low Poly Setup → Cage Setup → Bake Maps → Composite
    → Atlas Pack → Engine Format Export → Validation

Standard PBR Texture Set

MapFormatNotes
Base ColorsRGB PNGNo embedded AO
NormalLinear PNGOpenGL convention unless engine specifies
RoughnessLinear PNGSingle channel
MetallicLinear PNGSingle channel
AOLinear PNGMultiply in shader, not base color
HeightLinear PNGOptional parallax
EmissionsRGB PNGMask-based
ORM PackedLinear PNGR=AO, G=Roughness, B=Metallic (Unreal)

Naming: T_[Asset]_[Map] per ../references/naming-conventions.md

Bake Setup

1. Low-poly mesh with UVs (active)
2. High-poly mesh (sculpt or detail) — selected
3. Cage extrusion: 0.01–0.05m (adjust per asset scale)
4. Ray distance: match cage
5. Bake margin: 16px minimum
6. Anti-aliasing: enabled

Maps to Bake

MapSourcePriority
NormalHigh→LowRequired
AOHigh or low (cavity)Required
CurvatureHigh sculptWear masks
PositionHighOptional (blending)
ThicknessSubsurface meshesCharacters

Texture Atlas Strategy

Modular kits share one atlas:

1. All modules UV'd to shared 0–1 or UDIM space
2. Bake each module to atlas regions
3. Trim sheet areas for repeating detail
4. Single material references atlas
5. Document region map for artists

Decals

  • Decal mesh projected on surface
  • Separate UV channel or atlas region
  • Blend via alpha mask
  • Limit decal overdraw in engine

Memory Optimization

TechniqueSavings
ORM packing3 textures → 1
Shared atlasN materials → 1 texture
Lower res on hidden surfaces50%+ memory
BC compression in engine4:1 or 6:1
Trim sheetsReuse detail across assets

Resolution Guidelines

See ../references/polycount-budgets.md texture section.

MCP Integration

  1. Setup bake objects via MCP
  2. Configure bake settings via MCP if supported
  3. Export baked images via MCP
  4. Assign baked textures to materials via MCP
  5. Query texture count and resolution

Validation Checklist

  • Normal map correct orientation (test in engine)
  • No UV seams visible in bake
  • AO not baked into base color
  • Consistent texel density in final textures
  • Texture resolution within budget
  • Files named per convention
  • sRGB vs Linear correctly assigned

Constraints

MUST DO

  • Bake high-poly detail before discarding sculpt
  • Use cage for clean normal bakes
  • Pack ORM for engine efficiency
  • Test normal map orientation in target engine
  • Document atlas regions for modular kits

MUST NOT DO

  • Bake without cage on complex shapes
  • Embed AO in base color (PBR standard)
  • Exceed texture budget without LOD justification
  • Use inconsistent normal map conventions
  • Skip margin in bake settings

Reference Guide

TopicReferenceLoad When
Bake troubleshootingreferences/bake-troubleshooting.mdBake artifacts
ORM packingreferences/orm-packing.mdUnreal/Unity export

What ships with it: 2 files

2.0 KB alongside SKILL.md

Gives 0 of the 12 instructions most automation workflows skills give in 866 tokens

Counted across 745 of the 1,008 authors here whose files we hold, read 2026-08-07

  • Write conventional commit messagesin 36 of 745, across 35 files
  • Delete branches after mergein 30 of 745, across 21 files
  • Make atomic commitsin 25 of 745, across 15 files
  • Write minimal code to pass testsin 22 of 745, across 10 files
  • Re-snapshot after navigation or DOM changesin 21 of 745, across 13 files
  • Use try-catch for error handlingin 20 of 745, across 8 files
  • Run tests before committingin 20 of 745, across 12 files
  • Write tests before implementationin 20 of 745, across 8 files
  • Configure branch protection rulesin 19 of 745, across 5 files
  • Explain the why in commit messagesin 19 of 745, across 9 files
  • Refactor code while tests remain greenin 19 of 745, across 6 files
  • Interact with elements using refsin 19 of 745, across 11 files

Said here and by no other author read

  • Bake high-poly detail before discarding sculpt
  • Use cage for clean normal bakes
  • Pack ORM for engine efficiency
  • Test normal map orientation in target engine
  • Document atlas regions for modular kits
  • Use separate UV channel or atlas region for decals

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,851. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.