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.
How do I install this agent skill?
npx skills add https://github.com/roble3/cc-blender-skill --skill multiview-constraint-solverIs this agent skill safe to install?
- Gen Agent Trust Hubpass
This skill is a diagnostic tool for 3D modeling workflows in Blender. It analyzes geometric references (front, side, top views) to identify dimension conflicts and suggests a reconciliation policy. The provided script strictly handles JSON data processing with no dangerous network or system operations.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
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
- 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.
- Measure visible body bboxes, not labels/background/aura unless they are part of the model contract.
- Compare shared axes:
- front width vs top width;
- front/back height vs side height;
- side depth vs top depth.
- 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.
- Feed the chosen policy into
fit-repair-optimizerbefore 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.pyreads a JSON file of per-view body bboxes and emits shared-axis compatibility and a suggested canonical policy.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/roble3/cc-blender-skill/multiview-constraint-solver">View multiview-constraint-solver on skillZs</a>