Texture Driven Mesh Fitting logo

Texture Driven Mesh Fitting

Community
RobLe3
texture-driven-mesh-fitting

Reshape source-locked mesh boundaries so the geometry fits texture-atlas or decal contours 1:1 before final UV/material work. Use when textures look off because the model behind them does not match the source texture region, or when the mesh must adapt to the texture instead of stretching the texture onto an approximate mesh.

Overview

PublisherRobLe3
Repositorycc-blender-skill
Skill nametexture-driven-mesh-fitting
Stars
131
Forks
14
Bundled files
1
LicenseMIT
Links
  • 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.

  • 1 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 Texture Driven Mesh Fitting AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

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.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/RobLe3/cc-blender-skill/tree/main/plugin/skills/texture-driven-mesh-fitting
  4. 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.
2

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/texture-driven-mesh-fitting .claude/skills/texture-driven-mesh-fitting
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Texture Driven Mesh 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 Texture Driven Mesh 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 Texture Driven Mesh 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-driven geometry fitting, mesh boundary fitting to atlas masks, UV-preserving contour correspondence, point/landmark deformation, source mask to mesh repair.

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.

Texture-Driven Mesh Fitting

This skill fixes the common failure: a texture is mapped correctly, but the mesh silhouette underneath is wrong. The mesh adapts to the source contour; the texture is not stretched to hide a wrong mesh.

Preconditions

  • Structural parts are segmented (source-part-segmentation).
  • Each part has a contour/mask and, if textured, an atlas region (atlas-uv-fitting).
  • The object is source-locked in front X/Z before depth is added.
  • Canonical view policy is resolved (multiview-constraint-solver) if views conflict.

Workflow

  1. Extract source contour from the texture/wireframe region.
  2. Extract current mesh boundary in the same projected coordinate space.
  3. Build ordered contour correspondence by arc length, named landmarks, or seam/control points.
  4. Move boundary vertices to source contour positions.
  5. Move interior vertices by smooth interpolation, piecewise-affine warp, or thin-plate-spline style deformation.
  6. Preserve UV parameterization by remapping boundary-fitted local coordinates into the atlas rectangle.
  7. Re-render overlay; do not proceed to look-dev until texture-region silhouette passes.

Acceptance gates

  • Per-part source/product bbox center and size within tolerance.
  • Boundary maximum sample error below tolerance after normalization.
  • Texture atlas region does not visibly bleed outside the fitted mesh in front view.
  • Named landmarks (leaf_tip, base_left, base_right, face_corner, etc.) pass landmark-fit-repair.

Hard rules

  • If a texture crop has a different silhouette than the mesh, reshape the mesh first.
  • Do not use global UV stretching to hide geometry mismatch.
  • Boundary fitting must happen before side-depth/crown deformation.
  • Do not tune material/light to compensate for geometry/UV misfit.

Scripts

  • scripts/contour_correspondence_report.py reports bbox, centroid, and sampled contour deltas between a source mask and a render/object mask.

Sources distilled

  • Piecewise-affine/landmark warping gives a practical mesh deformation model.
  • Thin-plate-spline style deformation is appropriate for smooth mascot/logo surfaces when landmarks are sparse.
  • Blender mesh vertices/UV layers can be edited directly; BMesh is useful for cleanup after deformation.

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 Texture Driven Mesh Fitting AI skill do?

Reshape source-locked mesh boundaries so the geometry fits texture-atlas or decal contours 1:1 before final UV/material work. Use when textures look off because the model behind them does not match the source texture region, or when the mesh must adapt to the texture instead of stretching the texture onto an approximate mesh.

Why use Texture Driven Mesh Fitting on TypingMind?

Because you install it once and use it with any model. Texture Driven Mesh 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 Texture Driven Mesh Fitting in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/RobLe3/cc-blender-skill/tree/main/plugin/skills/texture-driven-mesh-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 Texture Driven Mesh 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 Texture Driven Mesh Fitting?

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

Is the Texture Driven Mesh 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

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇