agentleFS
JiamingShi-JsPhysJiamingShi-JsPhys/3d-fabric/skills/multiview-constraint-solver/SKILL.md

multiview-constraint-solver

Skill2 starsChanged 3 days agoMITView on GitHub

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.

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use when: Orthographic template conflict detection, canonical view policy, rigid-vs-cheat-view decision, front/side/top dimension ratios, …

    line 10
  2. Distinctive:

    Before the first Blender call, read ../text-to-blender/references/mcp-backends.md.

    line 12
  3. Distinctive:

    Use this before another rebuild when references disagree.

    line 15
  4. Distinctive:

    If ratios differ beyond tolerance, write a conflict report and select a policy:

    line 29
  5. Distinctive:

    Do not restart modeling until canonical policy exists.

    line 38
  6. Distinctive:

    Do not treat top-view aura/context as body depth.

    line 39
  7. Distinctive:

    Do not average contradictory dimensions unless the user explicitly asks for an approximate stylized compromise.

    line 40

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.