agentleFS
EL4CTEOEL4CTEO/blender-skills/skills/blender-retopology-uv/SKILL.md

blender-retopology-uv

Skill1.2k starsChanged 3 days agoMITView on GitHub

Retopology and UVs in Blender 5.3 - auto retopo (Quadriflow, Decimate, planar), deformation edge flow, seams, unwrap (Angle Based, Minimum Stretch, Smart), pixel-margin packing, texel density measure/set, lightmap UV2, UDIMs, mirrored UVs. Use to turn sculpts/scans/AI meshes into game meshes or prep UVs for texturing/baking.

Trending

More talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 14 mentionsNov 2026: 4 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the EL4CTEO/blender-skills repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about EL4CTEO/blender-skills

The biggest 5 of 18 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 18

Talked about on GitHub (18 times).

On GitHub · 18

13 more on GitHub

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    Keep poles (3/5-edge verts) out of bending areas.

    line 27

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

Retopology & UVs

The execution model is in blender-core.

Retopology

Automatic (scripts/auto_retopo.py -- --objects Sculpt --tris 8000 --method ...) makes <name>_low and leaves the source hidden:

MethodUse forNotes
quadrifloworganic props, static characters, scansclean quads. Voxel-remeshes first so the input is manifold (retries on the source if that fails); UVs are lost (re-unwrap)
decimatebackground props, LODs, AI-generated mesheskeeps UVs/shape, gives triangles. Fast
planarhard-surface CAD/boolean resultsdissolves flat areas; keeps seams/sharp/material/UV borders

Manual (hero characters, anything that deforms). Set up a new mesh object with a Shrinkwrap modifier (PROJECT, target = sculpt), snapping to FACE_PROJECT + use_snap_project, and the source in a different viewport color/x-ray. Clean loops with mesh.relax_edge_loops / space_edge_loops_evenly (LoopTools, built in since 5.3). Auto retopo isn't good enough for deforming hero meshes, because the edge flow below matters.

Edge flow rules for deforming meshes

  • Concentric loops around the eyes and mouth (≥3 rings). The nasolabial loop flows from the nose wing to the mouth corner.
  • 3 loops at every bending joint (elbow, knee, finger knuckles), plus a loop on each side to keep volume. The shoulder needs extra loops for raising the arm.
  • Keep poles (3/5-edge verts) out of bending areas. Put them on flat, stiff regions (chest, back of skull).
  • Distribute quads evenly, with density where deformation and silhouette need it. Use triangles only in hidden, non-deforming spots.
  • Character tri budgets in 2026: mobile 5–15k, Roblox body ≤ 10.7k total, console/PC third-person 30–80k, hero/cinematic 100k+. Check the target in blender-game-optimization.

UVs

  1. Seams: hide them (under arms, inner legs, back of the head, under parts), follow hard edges, cut cylinders on the back side. Rule for game meshes: every hard edge (>~60°, sharp_edge) must be a UV seam, or the normal map shows artifacts. scripts/uv_pack.py --seams-from-sharp 60 does this.
  2. Unwrap: --method seams (Angle Based with marked seams), --method min_stretch (SLIM, 4.3+, least distortion on organics), --method smart (hard-surface/auto, --angle 66).
  3. Straighten rectangular islands (Follow Active Quads, live only) so trims and pixel grids line up.
  4. Average island scale + pack with margin in pixels: 2k → 8 px, 4k → 16 px, mobile 1k → 4 px. --shape CONCAVE gives the tightest pack (slow headless). The default AABB is instant.
  5. Texel density (scripts/texel_density.py --res 2048): keep spread ≤ 1.3 within an asset. Set it with --set <px/m>; if fits_0_1 is false, change res or density.
  6. QA: blender-asset-qa reports zero-area UV faces and overlap %.

Texel density targets (px/m; studio baselines, not laws)

Contextpx/m
First-person hero / weapons1024–2048
First-person environment512–1024
Third-person games512 (console/PC), 256 (mobile)
Top-down / strategy128–256
Roblox~256–512 per texture: 5×5 studs → 256², 10×10 → 512², 20×20 → 1024²
Everything in the same scene should share one density. The exception is hero assets, kept within 2x.

Special cases

  • Mirrored/stacked UVs save space but break unique bakes. Move the duplicate islands exactly +1 U (outside 0–1) during baking, then move them back. Their normal maps must be mirror-safe (tangent space handles it in engines with MikkTSpace).
  • Lightmap UV2 (--lightmap, gives UVMap_Lightmap): no overlaps, every island inside 0–1, generous margin. Unreal/Unity can generate their own; ship one only if the engine pipeline wants it. Keep UV0 active for texturing.
  • UDIMs (film/hero): islands in tiles 1001+ (U offset 1 per tile). Texture node image source="TILED". Game engines mostly don't support UDIMs.
  • Trim sheets: unwrap the strips, then scale/move the islands onto the trim rows (V positions from the trim layout). Islands may exceed 0–1 in U for tiling.
  • Roblox: exactly one UV set, all inside 0–1. Overlaps are allowed.

Gotchas

  • 5.0+: UV selection is shared across UV maps (.uv_select_* attributes). Old BMLoopUV.select code fails.
  • uv.* operators run in Edit Mode and act on selected faces. Select everything first (scripts handle this).
  • Headless uv.pack_islands with CONCAVE/CONVEX + rotation can take 2–25 s even on tiny meshes. Use AABB while iterating.
  • Unwrap warning "failed to solve island": the island has no seams (closed shape). Add seams.
  • Apply scale before measuring texel density, or the density reads wrong (the scripts use world space and already account for scale).

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.