roble3/cc-blender-skill

closed-surface-uv-coverage

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.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/roble3/cc-blender-skill --skill closed-surface-uv-coverage

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

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.
  1. 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.
  2. 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.

タスクに関連する項目

同じリポジトリから

関連する Skills

すべての Skills
roble3
コミュニティ

blender-modeling

Create and edit 3D meshes in Blender — primitives, hard-surface modeling, mesh operators, modifier stacks (Bevel, Subdivision, Boolean, Mirror, Array, Solidify), bmesh-level edits, retopology basics. Use whenever the user asks to "make/model/create/build a 3D object", "shape/sculpt this", "add a cube/sphere/cylinder/etc.", "extrude/inset/bevel this face", "add a modifier", or any geometry-creation request that isn't a wireframe trace. Make sure to use this skill even if the user does not say "mo

導入数
2
GitHub Stars
116
更新日
10月12日
roble3
コミュニティ

blender-cameras

Set up Blender cameras with cinematic intent — focal length, depth of field (f-stop / focus object), composition (rule of thirds, leading lines), animated cameras (orbit, dolly, push-in), tracking constraints. Use whenever the user asks to "set up the camera", "frame the shot", "make it look cinematic / hero / portrait / wide-angle / telephoto", "add depth of field", "orbit the camera", or any composition/framing request. Make sure to use this skill even if the user does not say "camera" — also

導入数
2
GitHub Stars
109
更新日
10月12日
roble3
コミュニティ

blender-lighting

Light Blender scenes professionally — three-point setups, HDRI environments, studio/cinematic/dramatic configurations, light groups, color temperature, soft vs hard shadows. Use whenever the user asks to "light the scene", "set up lighting", "make it look cinematic / dramatic / studio / outdoor / sunset", "add a key light", "use HDRI", or any lighting-related request. Make sure to use this skill even if the user does not say "light" — also covers "make it look professional", "studio shot", "mood

導入数
2
GitHub Stars
109
更新日
10月12日
roble3
コミュニティ

blender-pro-workflow

End-to-end production workflow guidance for Blender — the order to assemble scenes (block-out → camera → light → forms → materials → detail → render → composite → export), critique protocols, time budgets, and recovery patterns. Use whenever the user asks to "make a complete scene / hero shot / production-quality render", "what's the right order to do this", "set up a full pipeline", or has a multi-step request crossing modeling + lighting + materials + rendering. Make sure to use this skill for

導入数
2
GitHub Stars
109
更新日
10月12日