Claude Skill

spatial-interchange

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

LLM Mart · 0 points · 0 views 0 listing impressions 0 install-command copies
Download dcc-mcp-dcc-mcp-core-skills_spatial-interchange-8d8c969.zip · 5 KB

Install

skills CLI npx skills add https://github.com/dcc-mcp/dcc-mcp-core/tree/main/skills/spatial-interchange
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install dcc-mcp-dcc-mcp-core@llmmart
Git git clone https://github.com/dcc-mcp/dcc-mcp-core.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole dcc-mcp/dcc-mcp-core collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Spatial Interchange

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.

Files (dcc-mcp-core)
  • references
    • CONVENTIONS.md 4.8 KB
      Loading…
  • scripts
    • plan_conversion.py 1.3 KB
      Loading…
  • SKILL.md 2.2 KB
    ---
    name: spatial-interchange
    description: >-
      Plan deterministic coordinate-axis and unit conversions between DCCs,
      engines, and interchange formats from explicit right/up/forward axes and
      meters-per-unit values.
    license: MIT-0
    compatibility: "dcc-mcp-core 0.19.91+, Python 3.7+"
    metadata:
      dcc-mcp:
        dcc: python
        recall-context:
          app_type: any
          domain: interchange
          workflow_stage: interchange
          task_category: query
        layer: infrastructure
        maintainer: dcc-mcp
        stage: interchange
        version: "1.0.0"
        tags: [pipeline, read-only, spatial, interchange]
        search-hint: >-
          coordinate conversion, axis conversion, unit conversion, handedness,
          DCC interchange, up axis, forward axis, meters per unit
        intent: "Plan an auditable axis and unit conversion before importing or exporting DCC data."
        side-effects:
          creates: false
          modifies: false
          file_output: false
          targets: []
        produces: [spatial_conversion_plan]
        requires: []
        tools: tools.yaml
        skill-reference-docs:
          - "references/*.md"
    ---
    
    # Spatial Interchange
    
    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](https://aike.github.io/3dtr/) 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.
    
  • tools.yaml 4.6 KB
    Loading…

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.