agentleFS
JiamingShi-JsPhysJiamingShi-JsPhys/3d-fabric/skills/texture-driven-mesh-fitting/SKILL.md

texture-driven-mesh-fitting

Skill2 starsChanged 3 days agoMITView on GitHub

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.

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

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use when: Texture-driven geometry fitting, mesh boundary fitting to atlas masks, UV-preserving contour correspondence, point/landmark …

    line 10
  2. Distinctive:

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

    line 12
  3. Distinctive:

    If a texture crop has a different silhouette than the mesh, reshape the mesh first.

    line 44
  4. Distinctive:

    Do not use global UV stretching to hide geometry mismatch.

    line 45
  5. Distinctive:

    Do not tune material/light to compensate for geometry/UV misfit.

    line 47

≈ “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-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.

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.