agentleFS
JiamingShi-JsPhysJiamingShi-JsPhys/3d-fabric/skills/orthographic-registration/SKILL.md

orthographic-registration

Skill2 starsChanged 3 days agoMITView on GitHub

Register front, side, back, and top orthographic reference views into a shared Blender coordinate contract. Use when a 3D model must match multi-view wireframes/templates, when side/back/top silhouettes are off, or before adding depth to a front-locked contour model.

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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: Multi-view mascot/object reconstruction, depth fitting from side/back/top views, orthographic blueprint alignment, reference …

    line 10
  2. Distinctive:

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

    line 12
  3. Very specific:

    Run scripts/register_views.py on the available view images.

    line 26
  4. Distinctive:

    Create orthographic reference planes/image empties with a single shared scale.

    line 27
  5. Distinctive:

    Add Y depth from side/top envelopes using modifiers/displacement or vertex groups.

    line 30
  6. Very specific:

    If views disagree, front brand read wins.

    line 35

≈ “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: Multi-view mascot/object reconstruction, depth fitting from side/back/top views, orthographic blueprint alignment, reference planes/cameras with shared scale and centerline.

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.

Orthographic Registration

This skill prevents the common failure where the front view looks plausible but the side/back/top views are wrong.

Coordinate contract

  • Front view defines X/Z silhouette.
  • Side view defines Y/Z depth envelope.
  • Top view defines X/Y spread.
  • Back view defines rear silhouette/material only; it must not rewrite the front silhouette.

Workflow

  1. Run scripts/register_views.py on the available view images.
  2. Create orthographic reference planes/image empties with a single shared scale.
  3. Align centerline and bbox centers before modeling.
  4. Lock front X/Z boundary vertices.
  5. Add Y depth from side/top envelopes using modifiers/displacement or vertex groups.
  6. Validate all four cameras before export.

Failure policy

If views disagree, front brand read wins. Document the conflict in registration_report.json.

Front-plane rotation rule

In this Blender coordinate convention, the front camera looks along the Y axis and the reference silhouette lives in the X/Z plane. Therefore 2D rotations inside the front view are rotations around the Y axis, not around Z. Use rotation_euler = (0, angle, 0) for 2D component orientation in the front projection. Z rotation spins objects into/out of screen-space incorrectly for X/Z-plane meshes.

Sources distilled

  • Blender Image Empty/reference image controls for orthographic blueprints.
  • OpenCV homography/alignment and geometric transforms for view registration.

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.