← Back to home@full-aigc-plugins

maya-design-plugin

Inspect Maya scenes, capture reversible Playblasts, and restore every touched value.

Stars
0
Language
Python
Created
Sep 11, 2026
Updated
Oct 18, 2026

Introduction

Autodesk Maya Design

Plugin marketplaces

This plugin belongs to AIGC content creation.

CategoryMarketplacePurpose
Full-stack developmentFull Stack PluginsArchitecture and UI design, code understanding, quality checks, code review, workflow governance, and server operations
AIGC content creationFull AIGC PluginsImage, video, audio, music, 3D, and multimodal content creation

Autodesk Maya Design — inspect scenes and return reviewable previews

Inspect an authorized Maya scene, capture a reversible Playblast, and optionally return a Jimeng link through the official uploader, with every touched scene value restored afterwards.

Version Skills Maya License

English | 简体中文 · Install · Quick start · Skills · Architecture · Troubleshooting

Positioning

maya-design is a guarded runner, not a Maya reimplementation. It discovers mayapy on your machine, snapshots every scene value it is about to change, produces a white-model or material-aware Playblast, validates the resulting MP4 by parsing the container, then restores each snapshot field and verifies the restoration. The plugin never uploads without explicit authorization, never installs Python packages, and keeps local bridge tokens out of durable receipts.

The plugin ships no MCP server: the six Skills call mayapy through argv with explicit project and output scopes. The records under docs/verification/ mark the live Maya path NOT_RUN; this README does not claim otherwise.

Installation

Prerequisites

  • Autodesk Maya 2022 or newer installed on the same machine.
  • mayapy reachable through MAYA_LOCATION or on PATH.
  • Python 3.7 or newer, matching the interpreter embedded in your Maya build.
  • Development only: jsonschema from requirements-dev.txt.

Maya is commercial software and is not distributed through a package manager. Obtain it from your Autodesk account; the plugin does not download, license or bundle Maya.

From the plugin marketplace

codex plugin marketplace add partme-ai/full-aigc-plugins
codex plugin add maya-design@full-aigc-plugins

Restart the host and open a new task so the Skills load. Then ask for the diagnostic Skill before touching a scene.

Confirm the environment

codex plugin list

The entry should read maya-design@full-aigc-plugins. After that, run /maya-diagnose; it reports the discovered Maya version, Python version and module path count, or a typed failure code such as MAYA_NOT_FOUND instead of guessing.

Quick start

flowchart LR
    A[Authorized scene] --> B[Discover mayapy and ABI]
    B --> C{Supported?}
    C -->|no| D[Typed diagnostic]
    C -->|yes| E[Snapshot scene state]
    E --> F[Playblast capture]
    F --> G[Parse and validate MP4]
    G --> H[Restore and verify]
    H --> I{Upload authorized?}
    I -->|yes| J[Ephemeral Jimeng link]
    I -->|no| K[Local preview only]

Ask for an inspection first, then a reversible preview:

Inspect this Maya scene and list its cameras, frame range and render settings.
Then render a white-model Playblast from the current camera over the existing range,
restore the scene, and do not upload anything yet.

Expected observation: the camera and render settings are listed, the snapshot is taken, the MP4 is validated, and the restoration step confirms each value went back. A mismatch fails with RESTORE_UNCONFIRMED instead of reporting success.

What you can build

WorkflowBuilt-in pathVerifiable output
Read a scene before actingmaya-inspectScene receipt covering cameras, range, resolution, references and unknown plug-ins
Review a preview safelymaya-export-previewWhite-model or material Playblast plus codec, fps, size and SHA-256
Reuse an existing rendermaya-export-preview (existing_video)Registered local clip without touching the Maya session
Explain a broken environmentmaya-diagnoseTyped failure code, paths excluded from output
Hand a preview to Seedancemaya-seedance-pipelineValidated preview plus a Dreamina 3D handoff (experimental)

Skills

SkillWhat it does
maya-useRoutes a vague or orientation request to inspect, export-preview or diagnose.
maya-harnessCalling spec: read-only preflight, MAYA_LOCATION resolution and the no-runtime posture.
maya-inspectRead-only scene inventory producing a scene receipt.
maya-export-previewReversible Playblast export with an artifact receipt and restoration status.
maya-diagnoseClassifies Maya errors without installing anything.
maya-seedance-pipelineDrives a validated Playblast through the Dreamina 3D pipeline.

Slash commands

CommandWhat it does
/mayaEntry point; routes scene inspection, preview and diagnostics.
/maya-inspectRead-only scene inspection: hierarchy, references, materials, timeline.
/maya-export-previewReversible Playblast preview and optional Jimeng link.
/maya-diagnoseRuntime diagnostics: install location, Python, plug-ins and preflight.
/maya-seedanceExperimental Playblast → Seedance path with validation and download checks.

Configuration

SettingWhere it livesNotes
Maya installationMAYA_LOCATION environment variableUsed when mayapy is not on PATH
Maya Python versionMAYA_PYTHON_VERSION environment variableRead during ABI validation
CredentialsNoneThe plugin stores no secret and installs no package

Architecture and security

Codex owns orchestration; Maya owns scene data; this plugin owns the snapshot set, the argv-only bridge invocation and the validators. The authors receive no scene data.

  • Every temporary change (selection, current time, playback range, camera, active panel, render settings) is snapshotted and compared before and after the run.
  • Publication needs an explicit authorization for that specific response, and the returned link is never written into a durable receipt.
  • Diagnostics redact local paths; the bridge token exists only inside the mayapy subprocess.
  • Operations are bounded by a timeout and fail with TIMEOUT rather than running indefinitely; nothing retries automatically.
EvidenceStatus
Offline component suiteRecorded in docs/verification/offline.md
Real Maya discovery, Playblast capture, browser hand-offNOT_RUN; see docs/verification/maya-runtime.md
Supported rangeMaya 2022+ with mayapy; older versions and Linux installs without MAYA_LOCATION are out of scope

Troubleshooting

SymptomCheck firstResolution
MAYA_NOT_FOUNDMaya installation and MAYA_LOCATIONInstall Maya 2022+ or set MAYA_LOCATION
ABI_MISMATCHMaya version and embedded PythonPoint the runner at a supported Maya
MODULE_LOAD_FAILEDMaya module pathFix the environment; the plugin will not install packages
RESTORE_UNCONFIRMEDThe reported fieldInspect the scene before continuing; do not assume it is clean
MEDIA_INVALIDThe produced fileRe-run the Playblast; a parse failure is a hard failure
Live behaviour is expectedThe runtime recordOnly offline behaviour is verified on this host

Upgrade

codex plugin marketplace upgrade full-aigc-plugins
codex plugin add maya-design@full-aigc-plugins

Re-run /maya-diagnose after an upgrade; the supported Maya range and the receipt contract are versioned, and this release declares receipt contract 1.0.0.

Current packaged version: 0.2.1+codex.20261018 (development preview).

Contributing and support

Open functional issues at https://github.com/full-aigc-plugins/maya-design-plugin/issues. State the Maya version and Python ABI you verified against, whether the change alters the snapshot set or the receipt shape, and include the affected tests.

License

Apache-2.0 — see LICENSE and NOTICE.