mcpField
F
fit-repair-optimizer

fit-repair-optimizer

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

About fit-repair-optimizer

fit-repair-optimizer is a skill for planning repairs after 3D model validation failures. It turns findings into an ordered queue with dependencies, write scopes, and acceptance gates.

Key features

  1. 01Order repairs by stage
  2. 02Decide whether tasks can run in parallel
  3. 03Check conflicts across view templates
  4. 04Define queue fields and acceptance gates
  5. 05Route recurring failures to skill improvement

Use cases

  1. 01Turn validation failures into a repair queue
  2. 02Coordinate geometry, UV, and material fixes
  3. 03Handle conflicts between view templates

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/roble3/cc-blender-skill --skill fit-repair-optimizer

After installing, type/fit-repair-optimizerin Claude Code to confirm it loaded.

Bundled filesscripts/fit_repair_queue.py

Details

From the project README

Fit Repair Optimizer

This skill converts validation failures into an executable repair queue. The source templates are the contract; the current model is disposable.

Decision: sequential or parallel?

Use sequential repair when failures are coupled:

  1. Canonical view / source conflict unresolved.
  2. Front silhouette or part count fails.
  3. Geometry dimensions fail before UVs can be trusted.
  4. Texture region boundaries depend on geometry changes.
  5. Lighting/look depends on final material placement.

Use parallel repair only for independent tracks with disjoint write scopes:

  • geometry recipe/placement tuning;
  • atlas-region classification;
  • material/look calibration;
  • validation tooling improvements.

Do not parallelize two tasks that both edit the same Blender recipe, object transforms, or UV assignment file.

Mandatory repair order

0 source-conflict / multiview-rigidity gate
1 structural part count
2 front silhouette and landmarks
3 side/back/top depth and projection
4 UV/texture region fit
5 material/light/look calibration
6 export and final validation

If an earlier stage fails, later stages may be analyzed but must not be finalized.

Source-conflict gate

Before repair, use multiview-constraint-solver to check whether templates are mutually satisfiable. If the same physical axis receives incompatible ratios across views, write a conflict report and require a canonical policy:

  • front+side canonical;
  • front+top canonical;
  • corrected template sheet;
  • view-specific cheat renders only, not a rigid 3D model.

Repair queue schema

Each repair item must include:

  • id
  • stage
  • view_scope
  • failure
  • measured_delta
  • proposed_action
  • write_scope
  • parallel_group
  • blocked_by
  • acceptance_gate

Skill-gap rule

If the same failure recurs twice, stop and invoke quality-refinement-autoloop before another rebuild. The autoloop must capture evidence, diagnose the missing method, sanitize the lesson into generic publishable guidance, patch the relevant skill(s), validate the skill stack, then return here with a new repair queue. Common routing:

  • geometry mismatch → contour-to-mesh, orthographic-registration, or this skill;
  • UV/texture mismatch → atlas-uv-fitting;
  • lighting mismatch → add/look-calibrate guidance to blender-lighting or a look-calibration skill;
  • validation mismatch → multiview-fit-loop / reference-analysis-validator.

Output

Write a project repair plan such as ALIGNMENT_REPAIR_QUEUE.json and a human-readable ALIGNMENT_REPAIR_METHOD.md.

Comments

Markdown supported