agentleFS
JiamingShi-JsPhysJiamingShi-JsPhys/3d-fabric/skills/atlas-uv-fitting/SKILL.md

atlas-uv-fitting

Skill2 starsChanged 3 days agoMITView on GitHub

Detect texture-atlas regions and map each source part to its own UV rectangle or projected UV surface. Use when a texture pack must fit a Blender model 1:1, when textures look off/stretched, when alpha decals or lightmaps are provided, or before exporting a textured GLB for a brand mascot/logo.

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 4 are distinctive, and 2 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.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use when: Texture atlas region detection, per-part UV mapping, front-projected UVs, decal/lightmap handling, texture validation against …

    line 10
  2. Distinctive:

    Before the first Blender call, read ../text-to-blender/references/mcp-backends.md.

    line 12
  3. Very specific:

    Run scripts/atlas_region_detector.py on basecolor/decal/aura atlases.

    line 32
  4. Distinctive:

    Create/activate UV map per mesh.

    line 34
  5. Very specific:

    Verify supplemental maps share the same region layout before connecting roughness/bump/emission/lightmap.

    line 57
  6. Distinctive:

    Do not map a full rosette/composite atlas region onto individual petals unless the mesh is a single rosette sheet.

    line 59

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

MCP backend

Use when: Texture atlas region detection, per-part UV mapping, front-projected UVs, decal/lightmap handling, texture validation against source templates.

Before the first Blender call, read ../text-to-blender/references/mcp-backends.md. Prefer official MCP for shared capabilities; preserve the selected backend for the whole task. Tool names in recipes are client/legacy examples: map them through that reference and its agent-host guide.

Atlas UV Fitting

This skill exists because assigning a texture material is not the same as fitting a texture.

Supplemental map sanity rule

Do not blindly wire emissive/roughness/bump/lightmap images into every atlas-mapped part. First verify the supplemental map has the same UV layout and semantic region as the basecolor. If it contains aura dots, guide marks, lightmap blobs, or decorations outside the part, leave it disconnected for that mesh and use constant roughness/bump plus explicit edge/glow geometry instead.

Hard rules

  • Atlas textures must be mapped by region; never apply the full atlas to every structural mesh.
  • Front-facing hero surfaces use front-projected UVs or a source-region rectangle.
  • Side/back surfaces use their own UV islands or procedural/baked fills.
  • Roughness, bump, normal, AO, and lightmap images are Non-Color.
  • Alpha decals must use alpha-connected materials and no black backing planes.
  • Base GLB should not include reference planes or optional aura unless explicitly requested.

Workflow

  1. Run scripts/atlas_region_detector.py on basecolor/decal/aura atlases.
  2. Name regions semantically in atlas_regions.json.
  3. Create/activate UV map per mesh.
  4. Remap local 0-1 UVs into the matching atlas rectangle.
  5. Audit the GLB/export material node graph: Principled BSDF + Image Texture nodes.
  6. Render texture overlay validation before export.

Sources distilled

  • Blender UV/Image Texture node uses UV maps for rendered/exported texture output.
  • Blender baking needs UV maps and active image targets.
  • Blender glTF exporter is most reliable with Principled BSDF, UVs, textures, normals.
  • Khronos glTF PBR: base color, metallic/roughness, normal maps are standard channels.

Semantic atlas mapping

Region detection is only a candidate list. For source-locked work, create an atlas_part_map.json that binds each structural part name to exactly one atlas region or declares procedural/no_texture.

Mapping order:

  1. Detect candidate regions from basecolor/decal/lightmap.
  2. Reject decorative/aura/composite-preview regions unless the target is context/aura.
  3. Match structural parts by role, aspect ratio, and relative size.
  4. Manually rename ambiguous regions before automated UV assignment.
  5. Verify supplemental maps share the same region layout before connecting roughness/bump/emission/lightmap.

Do not map a full rosette/composite atlas region onto individual petals unless the mesh is a single rosette sheet. Individual meshes need individual source regions.

Additional script

  • scripts/atlas_region_mapper.py proposes part→atlas-region mappings using aspect/size similarity. Treat output as a draft; semantic names still win.

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.