← ClaudeAtlas

fit-repair-optimizerlisted

Turn multiview fit reports into a sequential or parallel repair queue for aligning Blender products to source-of-truth templates. Use after validation shows disalignment, when the agent must iteratively fix wireframe, texture, lighting, or projection mismatches, and when a recurring failure should stop the rebuild loop for a diagnosis.
MAX-786/claude-3d-harness · ★ 6 · AI & Automation · score 74
Install: claude install-skill MAX-786/claude-3d-harness
# 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