Atlas Uv Fitting

Community

RobLe3

atlas-uv-fitting

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.

Overview

Publisher	RobLe3
Repository	`cc-blender-skill`
Skill name	`atlas-uv-fitting`
Stars	131
Forks	14
Bundled files	2
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
2 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by RobLe3 on GitHub. Read the source before you install it.

Installation

Install the Atlas Uv Fitting AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/RobLe3/cc-blender-skill/tree/main/plugin/skills/atlas-uv-fitting
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/RobLe3/cc-blender-skill.git /tmp/cc-blender-skill
mkdir -p .claude/skills
cp -r /tmp/cc-blender-skill/plugin/skills/atlas-uv-fitting .claude/skills/atlas-uv-fitting

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Atlas Uv Fitting in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Atlas Uv Fitting on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Atlas Uv Fitting is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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.py on 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.py proposes part→atlas-region mappings using aspect/size similarity. Treat output as a draft; semantic names still win.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Atlas Uv Fitting AI skill do?

Why use Atlas Uv Fitting on TypingMind?

Because you install it once and use it with any model. Atlas Uv Fitting is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Atlas Uv Fitting in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/RobLe3/cc-blender-skill/tree/main/plugin/skills/atlas-uv-fitting. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Atlas Uv Fitting?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Atlas Uv Fitting?

As many as you like. As long as a model supports skills, you can use Atlas Uv Fitting with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Atlas Uv Fitting AI skill free?

Yes. It is published on GitHub by RobLe3 under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Archify

NousResearch

OrganizationPopular

Validated interactive HTML diagrams, upstream-maintained.

Auteur

Design and build cinematic, award-level web pages.

Concept Diagrams

Generate flat, minimal educational SVG visuals as HTML.

Hyperframes

Render MP4/WebM videos from HTML compositions.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

MCP backend

Atlas UV Fitting

Supplemental map sanity rule

Hard rules

Workflow

Sources distilled

Semantic atlas mapping

Additional script

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now