mcpField
M
multiview-constraint-solver

multiview-constraint-solver

github.com/roble3Creative & media128788 installsUpdated 2w ago
Repository

About multiview-constraint-solver

multiview-constraint-solver is a skill for resolving conflicting dimensions across orthographic reference views before rebuilding a model. It reports axis compatibility and requires a canonical-view policy before geometry, UV, or lighting work.

Key features

  1. 01Normalize axes across reference views
  2. 02Compare shared dimensions between views
  3. 03Report incompatible view constraints
  4. 04Select a canonical-view policy
  5. 05Track part-count conflicts separately

Use cases

  1. 01Resolving conflicting front, side, and top references
  2. 02Choosing authoritative dimensions before rebuilding
  3. 03Identifying when corrected templates are needed

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/roble3/cc-blender-skill --skill multiview-constraint-solver

After installing, type/multiview-constraint-solverin Claude Code to confirm it loaded.

Bundled filesscripts/view_constraint_report.py

Details

From the project README

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.

Comments

Markdown supported