agentleFS
JiamingShi-JsPhysJiamingShi-JsPhys/3d-fabric/skills/closed-surface-uv-coverage/SKILL.md

closed-surface-uv-coverage

Skill2 starsChanged 3 days agoMITView on GitHub

Ensure textures and decals cover all visible surfaces of a closed or extruded Blender asset, especially front/back caps and sidewalls, instead of relying on partial projected planes, curves, or linework overlays. Use when back textures do not fill the model, side textures are missing, spin/turntable views expose plain sidewalls, or a model needs separate UV treatment for caps and side surfaces.

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

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use when: Full surface texture coverage, sidewall UVs, back cap UVs, closed mesh UV coverage audits, texture fill validation, side/back …

    line 10
  2. Distinctive:

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

    line 12
  3. Distinctive:

    if a clean side texture is unavailable, use a generated procedural side material plus baked glow/edge strip and document it.

    line 41
  4. Very specific:

    Use after geometry is locked and before final material/look/animation acceptance.

    line 55

≈ “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: Full surface texture coverage, sidewall UVs, back cap UVs, closed mesh UV coverage audits, texture fill validation, side/back turntable QA, replacing projected overlays with real surface materials.

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.

Closed Surface UV Coverage

This skill prevents a common false pass: a model looks textured from the front because it has a projected front image or curve overlays, but the closed surface has untextured back caps or plain sidewalls when viewed in a spin/turntable.

Failure modes to catch

  • Back detail is only a floating plane or curve overlay, not a material/UV on the back surface.
  • Sidewalls have procedural color only; no side UV island, generated/object coordinate material, or baked strip.
  • A back projection covers only a center shape and leaves the actual silhouette/back mesh plain.
  • Side/back QA uses front-biased frames and misses edge-on/back-on samples.
  • Decorative HUD/aura is mistaken for surface texture coverage.

Required surface taxonomy

For extruded/logo-like assets, classify visible surfaces before look-dev:

  1. front_cap — canonical front texture/decal.
  2. back_cap — back texture, back linework, or baked/procedural fill mapped to the real back cap.
  3. sidewall — depth surface connecting front/back, with its own UV parameterization or procedural material.
  4. overlay_context — HUD/aura/circles; never counted as model surface coverage.

Workflow

  1. Audit current coverage: list mesh material slots, UV layers, image texture nodes, and face counts for front/back/side material indices.
  2. Reject overlay-only fixes: curves/planes may add rim accents, but they do not satisfy back/side fill unless the mesh surface beneath is also textured/materialized.
  3. Create per-surface UVs:
    • front/back caps: project local X/Z to UV 0–1 or map into a back/front atlas rectangle;
    • sidewall: map perimeter arc length to U and depth/front-back coordinate to V;
    • if a clean side texture is unavailable, use a generated procedural side material plus baked glow/edge strip and document it.
  4. Assign true surface materials: back cap and sidewall mesh faces must have material nodes, active UVs, and/or generated coordinates. Optional curves are accents only.
  5. Validate turntable frames: sample front, 45°, side/edge-on, back-on, opposite 45°, and rest. Back and side frames must show surface fill, not just outlines.

Acceptance gates

  • Back cap mesh faces have either an image/procedural material with a declared UV/generated coordinate policy, not only separate curves.
  • Sidewall mesh faces have a sidewall material with UV/generated coordinates and visible depth treatment.
  • Overlay/context collections are excluded from coverage counts.
  • QA contact sheet includes back and edge-on frames.
  • A surface_coverage_report.json states which surfaces are image-textured, procedural, baked, or intentionally plain.

Handoff

Use after geometry is locked and before final material/look/animation acceptance. It complements blender-uv-texturing and atlas-uv-fitting: those skills explain UV/material setup; this skill enforces complete visible-surface coverage.

Script

  • scripts/surface_texture_coverage_audit.py audits selected mesh objects for UV layers, material image nodes, face material counts, and overlay-only warning patterns.

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.