roble3/cc-blender-skill

mascot-logo-reconstruction

Orchestrate a fail-gated, source-locked Blender reconstruction of mascots, logos, brand avatars, and stylized flat characters from wireframes, texture packs, and orthographic views.

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/roble3/cc-blender-skill --skill mascot-logo-reconstruction

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

MCP backend

Use when: Brand mascot/logo 3D reconstruction, exact part counts, texture-driven model matching, repeated “does not match reference” feedback, or full pipeline coordination across analysis, contour mesh, registration, UV fitting, validation, animation, and export.

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.

Mascot / Logo Reconstruction

This is the top-level skill for 1:1 brand mascot reconstruction. It chains the specialized skills and enforces stop/go gates.

Harmonization requirement

For mascot/logo work, use blender-skill-harmonizer first when multiple source types or validation failures are present. It sets canonical source policy and prevents conflicts between reconstruction, UV, fit-repair, lighting, export, and animation skills.

Skill chain

  1. reference-analysis-validator — source inventory, manifest, part counts, masks.
  2. orthographic-registration — shared front/side/back/top coordinate contract.
  3. contour-to-mesh — structural meshes from measured silhouettes.
  4. atlas-uv-fitting — per-part texture/UV fitting.
  5. blender-materials / blender-lighting — only after geometry and UVs pass.
  6. reference-analysis-validator again — overlay gates before export.
  7. blender-export — export only after gates pass.
  8. blender-animation — only after static model is accepted.

Non-negotiable order

Static reference fidelity comes before animation and beauty rendering.

measure → manifest → contour meshes → depth registration → UV fit → overlay validation → export → animation

Hard gates

  • expected structural part count equals Blender scene/export structural part count.
  • front silhouette overlay passes threshold.
  • face/features landmarks pass tolerance.
  • side/back/top renders match their registered envelopes.
  • texture atlas regions are mapped per part.
  • optional aura/background is separated from base structural GLB.

Modeling guidance

  • Treat mascots/logos as designed symbols, not natural objects. Symmetry is not guaranteed.
  • Do not infer hidden leaves/petals from radial math.
  • Avoid primitive-first construction when a silhouette exists.
  • Use semantic object names and validation prints.

Source-manifest structural part invariant

Create exactly the structural parts declared by the source manifest. Extra background arcs, glow, aura, shadows, guide marks, and decorative rings are context/decor unless the manifest explicitly promotes them to structural geometry.

Front-plane rotation rule

In this Blender coordinate convention, the front camera looks along the Y axis and the reference silhouette lives in the X/Z plane. Therefore 2D rotations inside the front view are rotations around the Y axis, not around Z. Use rotation_euler = (0, angle, 0) for 2D component orientation in the front projection. Z rotation spins objects into/out of screen-space incorrectly for X/Z-plane meshes.

Output contract

Every final reconstruction folder should include:

  • reference_manifest.json
  • registration_report.json
  • atlas_regions.json
  • validation/front_mask_validation.json
  • validation/front_overlay_reference.png
  • named .blend
  • base .glb
  • optional aura/context .glb
  • BUILD_NOTES.md with pass/fail gates

Related by task

from this repository

More skills

All skills
roble3
Community

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

installs
2
GitHub stars
116
Updated
Oct 12
roble3
Community

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

installs
2
GitHub stars
109
Updated
Oct 12
roble3
Community

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

installs
2
GitHub stars
109
Updated
Oct 12
roble3
Community

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

installs
2
GitHub stars
109
Updated
Oct 12