3dviz-pro-max

Choose this when your agent can work on a local visualization project and you want guidance about scene structure, visual direction and verification. It is less suitable when you expect a hosted text-to-3D service to deliver a finished asset without a local toolchain. Project overview.

For an initial check, choose a nontechnical scene you can judge directly, such as a small courtyard with three distinct objects. Anatomy or engineering diagrams add separate factual and geometry requirements. A visually attractive frame does not establish that a medical or mechanical model is correct.

Choose one installation route

The installation documentation distinguishes agent-specific skill directories and Claude Code plugin loading. Copy the whole skills/3dviz-pro-max/ directory, including its data and references. Do not install multiple copies without knowing which one the agent will discover.

For a Claude Code checkout-based plugin session, the README documents:

claude --plugin-dir /path/to/3dviz-pro-max

Replace the example path with the actual repository checkout. For Codex, use a skill directory recognized by your installed version and confirm the skill appears in the session’s available skills. The project does not claim that every installation route has been tested. Compatibility record.

Confirm the entry point before generating anything

Find the installed 3dviz-pro-max skill.
Report the exact local entrypoint you loaded.
Identify one recipe suitable for a small fantasy courtyard.
Do not generate files or install tools yet.
If the skill is unavailable, say so rather than using a guessed copy.

Open the reported path and verify that accompanying data exists beside the skill. A plausible description of the skill is not proof that the local copy was loaded.

Prepare only the tools your scene needs

The project’s browser-capture helper needs an optional Playwright installation. Blender 4.2 LTS or later is recommended by the README, not a universal requirement. Determine the chosen workflow first; a missing renderer or capture tool should be reported explicitly rather than hidden behind a simulated screenshot.

Editorial example; not a scene generated for this page:

Use the confirmed 3dviz-pro-max skill to make a small courtyard scene.
Include one cottage, one tree and a clearly separate stone path.
Use a single daylight view with an orbit camera and a reset control.
Reuse the current project and available tools; list missing prerequisites.
Before building, state which recipe or starting point you will use.
After building, run it if the required tools are available.
Return the launch steps and an actual captured frame if you observed one.
Report generated files, observed behavior and skipped checks separately.
Do not claim a render was inspected if you could not open it.

Verify that the three objects are distinguishable, orbit changes the view, and reset restores the intended starting camera. Check the console for errors. If only source files were generated, record that as source generation rather than a functioning visualization.

A useful iteration changes one visible issue at a time: an obstructed path, an unreadable silhouette, or a camera that clips through the scene. Keep the accepted objects and controls intact while correcting that issue.

The repository differentiates authored recipes, knowledge records, tested kits and observed scenes. Those counts describe different kinds of material. We do not turn them into a success rate or a promise that every recipe can be rendered in your environment. Published limitations.

Its compatibility record reports particular observed loading paths and explicitly leaves others untested. Consult that record for your agent and version. A successful plugin validation checks packaging; it is not a rendering test.

The project’s own work is MIT-licensed, but third-party materials retain their own terms. The README calls out separate anatomy-mesh and font licenses, and a recording whose redistribution rights were not confirmed. Check the source and attribution of any asset you intend to export or publish; do not infer rights from the repository license alone. License and credits.

When uninstalling or updating, first identify the copy your agent actually loaded. Follow the installation guide for that route and preserve any scene files you authored separately from the skill package.