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
- keysforthewin/thisofficeedited, first seen Jul 24, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- keysforthewin/thisoffice★ 097% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository33 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/3d-fabric.mdcCursor rule
- 3d-fabricSkill
- animation-quality-gateSkill
- blender-animationSkill
- blender-camerasSkill
- blender-exportSkill
- blender-lightingSkill
- blender-materialsSkill
- blender-modelingSkill
- blender-pro-workflowSkill
- blender-renderingSkill
- blender-skill-harmonizerSkill
- blender-uv-texturingSkill
- closed-surface-uv-coverageSkill
- contour-to-meshSkill
- fit-repair-optimizerSkill
- landmark-fit-repairSkill
- mascot-logo-reconstructionSkill
- multiview-constraint-solverSkill
- multiview-fit-loopSkill
- orbital-hud-motionSkill
- orthographic-registrationSkill
- quality-refinement-autoloopSkill
- reference-analysis-validatorSkill
- reference-look-calibrationSkill
- reference-to-3dSkill
- source-part-segmentationSkill
- text-to-blenderSkill
- texture-driven-mesh-fittingSkill
- texture-state-animationSkill
- wireframe-to-3dSkill
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
- Distinctive: line 10
Use when: Texture atlas region detection, per-part UV mapping, front-projected UVs, decal/lightmap handling, texture validation against …
- Distinctive: line 12
Before the first Blender call, read ../text-to-blender/references/mcp-backends.md.
- Very specific: line 32
Run scripts/atlas_region_detector.py on basecolor/decal/aura atlases.
- Distinctive: line 34
Create/activate UV map per mesh.
- Very specific: line 57
Verify supplemental maps share the same region layout before connecting roughness/bump/emission/lightmap.
- Distinctive: line 59
Do not map a full rosette/composite atlas region onto individual petals unless the mesh is a single rosette sheet.
≈ “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.
Files
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
- Run
scripts/atlas_region_detector.pyon basecolor/decal/aura atlases. - Name regions semantically in
atlas_regions.json. - Create/activate UV map per mesh.
- Remap local 0-1 UVs into the matching atlas rectangle.
- Audit the GLB/export material node graph: Principled BSDF + Image Texture nodes.
- 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:
- Detect candidate regions from basecolor/decal/lightmap.
- Reject decorative/aura/composite-preview regions unless the target is context/aura.
- Match structural parts by role, aspect ratio, and relative size.
- Manually rename ambiguous regions before automated UV assignment.
- 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.pyproposes part→atlas-region mappings using aspect/size similarity. Treat output as a draft; semantic names still win.
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
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.

