Skip to content
cccskills
FreePublished on GitHub

multiview-constraint-solver

Determine whether front/side/back/top reference templates can be satisfied by one rigid 3D Blender model, choose a canonical source policy, and emit constraints before rebuilding. Use when multiview bboxes, silhouettes, part counts, or depth ratios contradict each other.

The English summary is being prepared. Showing the original description.

Works withBlender
See how to install

Files included (2)

  • SKILL.md2.5 KB
  • scripts/view_constraint_report.py3.5 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

MCP backend

Use when: Orthographic template conflict detection, canonical view policy, rigid-vs-cheat-view decision, front/side/top dimension ratios, source-of-truth negotiation before reconstruction.

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.

Multiview Constraint Solver

Use this before another rebuild when references disagree. A renderer cannot make one rigid mesh satisfy mutually incompatible orthographic dimensions unless you allow view-specific cheats.

Workflow

  1. Normalize every reference view into a common axis contract:
    • front: width X, height Z;
    • side: depth Y, height Z;
    • top: width X, depth Y;
    • back: width X, height Z.
  2. Measure visible body bboxes, not labels/background/aura unless they are part of the model contract.
  3. Compare shared axes:
    • front width vs top width;
    • front/back height vs side height;
    • side depth vs top depth.
  4. If ratios differ beyond tolerance, write a conflict report and select a policy:
    • front_side_canonical: front brand read and side depth/height are authoritative;
    • front_top_canonical: front brand read and top footprint are authoritative;
    • corrected_templates_required: no rigid rebuild should claim final fit;
    • view_specific_cheats: separate camera/view variants allowed, not one rigid asset.
  5. Feed the chosen policy into fit-repair-optimizer before any geometry, UV, or lighting work.

Hard gates

  • Do not restart modeling until canonical policy exists.
  • Do not treat top-view aura/context as body depth.
  • Do not average contradictory dimensions unless the user explicitly asks for an approximate stylized compromise.
  • Record part-count disagreements separately from bbox disagreements.

Script

  • scripts/view_constraint_report.py reads a JSON file of per-view body bboxes and emits shared-axis compatibility and a suggested canonical policy.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Validate Blender animation attempts before accepting them by rendering contact sheets, checking silhouette stability, flicker, framing, subject dominance, layer separation, export compatibility, and motion-design coherence. Use after animation renders or when the user says motion/morph/outside elements look bad.

The English summary is being prepared. Showing the original description.

RobLe3/cc-blender-skill107Updated Oct 13, 2026

Detect texture-atlas regions and map each source part to its own UV rectangle or projected UV surface. Use when a texture pack must fit a Blender model 1:1, when textures look off/stretched, when alpha decals or lightmaps are provided, or before exporting a textured GLB for a brand mascot/logo.

The English summary is being prepared. Showing the original description.

RobLe3/cc-blender-skill107Updated Oct 13, 2026

Animate objects, cameras, lights, and properties in Blender — keyframes, F-curves, easing (Bezier, Linear, Sine, Bounce, Elastic), shape keys (morph targets / blendshapes / visemes), drivers (Python expressions on properties), NLA actions for reuse and layering. Use whenever the user asks to "animate this", "make it move / rotate / scale over time", "add keyframes", "loop / oscillate", "shape key / morph / blendshape", "visemes for lip sync", or any time-based property change. Make sure to use this skill even if the user does not say "animate" — also covers "spin it slowly", "make it wave", "fade in / out", "pulse", "facial expression".

The English summary is being prepared. Showing the original description.

RobLe3/cc-blender-skill107Updated Oct 13, 2026

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 covers "hero shot", "close-up", "from above", "shallow focus", "85mm portrait look".

The English summary is being prepared. Showing the original description.

RobLe3/cc-blender-skill107Updated Oct 13, 2026

Export Blender scenes to glTF/GLB (web/AR), FBX (game engines), OBJ (universal), USD (VFX pipelines), STL (3D printing). Includes Unreal collision hulls and Multires normal-map baking for low-poly export, per-format settings, embed/unpack textures, axis conversion, polygon optimization (Decimate), and target-platform validation. Use whenever the user asks to "export this", "save as glTF / FBX / OBJ / STL / USD", "package for Unity / Unreal / Three.js / web / AR / 3D print", or any output format conversion. Make sure to use this skill even if the user does not say "export" — also covers "package this for the web", "make it work in Unity", "send to Unreal", "save for 3D printing".

The English summary is being prepared. Showing the original description.

RobLe3/cc-blender-skill107Updated Oct 13, 2026

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", "moody atmosphere", "golden hour", "rim light". Pairs with blender-materials (lighting reveals materials) and blender-cameras (lighting + composition together = shot).

The English summary is being prepared. Showing the original description.

RobLe3/cc-blender-skill107Updated Oct 13, 2026

See all skills by RobLe3

Report a problem with this skill