agentleFS
JiamingShi-JsPhysJiamingShi-JsPhys/3d-fabric/skills/fit-repair-optimizer/SKILL.md

fit-repair-optimizer

Skill2 starsChanged 3 days agoMITView on GitHub

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 skill gaps should trigger self-refinement before another rebuild.

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

8 rules. About 0 are common, 5 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Use when: Iterative source-of-truth alignment repair, choosing sequential vs parallel correction order, generating fit repair queues, …

    line 10
  2. Distinctive:

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

    line 12
  3. Distinctive:

    Use sequential repair when failures are coupled:

    line 19
  4. Distinctive:

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

    line 27
  5. Distinctive:

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

    line 34
  6. Distinctive:

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

    line 48
  7. Very specific:

    Before repair, use multiview-constraint-solver to check whether templates are mutually satisfiable.

    line 52
  8. Very specific:

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

    line 85

≈ “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: Iterative source-of-truth alignment repair, choosing sequential vs parallel correction order, generating fit repair queues, stopping on contradictory templates, or coordinating geometry/UV/lighting fixes from validation reports.

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.

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.

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.