Spatial Interchange

SkillDev tools

Plan deterministic coordinate-axis and unit conversions between DCCs, engines, and interchange formats from explicit right/up/forward axes and meters-per-unit values.

Instructions available. Your AI can read the instructions. Execution depends on the setup they require.

Add ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.

Then ask your AI: use the Spatial Interchange skill

What this skill tells your AI

The instructions your AI receives, as published by dcc-mcp/dcc-mcp-core in skills/spatial-interchange/SKILL.md and read by ahel’s review.

Use plan_conversion before a cross-DCC import or export when source and target coordinate conventions are known. The tool returns a pure conversion plan; the importing or exporting adapter remains responsible for applying it to scene data.

Do not infer a convention from a DCC name alone. Query the live scene, import settings, or file metadata first: Maya up-axis and units are scene settings, Blender FBX axes are operator settings, and USD stages carry upAxis and metersPerUnit metadata.

The 3D Transform Visualizer is a useful educational model for signed right/up/forward bases. It is not a file converter or a source of truth for a live scene.

Workflow

  1. Inspect source file/scene axes and physical units.
  2. Inspect the target scene/importer settings.
  3. Call plan_conversion with explicit signed axes and meters per unit.
  4. Apply the returned plan in the owning adapter/importer.
  5. Validate a landmark point, bounds, face orientation, normals, and animation.

Read references/CONVENTIONS.md for official defaults, runtime caveats, and the rules for positions, directions, transforms, and mesh winding.

Signals

GitHub stars
48
Forks
4
Last commit
Oct 2026
Advanced
Item type
skill
Key
spatial-interchange
Source
github.com/dcc-mcp/dcc-mcp-core