Claude Opus 5.5 + Tripo + Blender + UnityNot tested by us🇨🇳 CN

Turning The Little Prince into an explorable 3D game with Opus 5.5, Tripo, Blender and Unity: AI makes the assets and also drives the engines

Sac spent 16 days turning The Little Prince's journey between planets into a 3D story game you can play in the browser, then published the workflow: Fable 5.1 writes the PRD, GPT Image 2.5 makes scene and character references, Tripo generates 3D assets, Opus 5.5 builds scenes, rigs characters and wires animations through the Blender CLI and the official Unity MCP, and Astra fixes bugs. Reusable prompts are included for each step.

Visit site Claude Opus 5.5 + Tripo + Blender + Unity ↗
Pricing
Paid
Region
Global
Where it's from
Chinese community
Added
Oct 19, 2026
Version we used
Opus 5.5, Fable 5.1, GPT Image 2.5, GPT-6 Astra; Tripo H3.1 (props) and Smart Mesh P2.0 (characters); Blender CLI + Auto-Rig Pro; Unity + official Unity MCP, as described 2026-10-15
Categories
DesignCoding
Original author
Sac @Saccc_c ↗
Our test
Not tested by us
Cost / time
Paid Claude (Opus 5.5 / Fable 5.1) and ChatGPT (Image 2.5 / Astra) plans; Tripo is credit-based; Auto-Rig Pro is a paid Blender add-on; Blender and Mixamo are free, Unity Personal is free. The author took 16 days.
Source
X @Saccc_c(教程长文) ↗X @Saccc_c(游戏发布) ↗littleprince.dev ↗

The task

A solo creator with no 3D modeling or Unity background wants to turn a story into a 3D game with real scenes, animated characters and free exploration.

Steps

  1. Division of labor: Fable 5.1 writes the PRD (key scenes, characters, story) → GPT Image 2.5 makes scene and character images → Tripo generates the key 3D assets → Opus 5.5 writes the core code → Astra iterates and fixes bugs.
  2. Tooling: install the Blender CLI (to clean up Tripo models and build the rest of the 3D world) and the paid Auto-Rig Pro add-on (rigging and skinning); install the Unity app and Unity CLI, and add the Pipeline package to the project so Claude can drive Unity through the official Unity MCP.
  3. Scene references: following the PRD, get one scene image you like from Image 2.5, then add other angles (top-down for layout, three-quarter for heights and depth). The author's prompt (translated): "Based on the uploaded scene reference, generate a full overview reference of this scene, with multi-angle views of the whole environment and close-ups of details."
  4. Split the assets: have the AI decide which props Tripo should generate separately and which Opus 5.5 can build directly in Blender/Unity (prompt below), marked on the image for you to confirm. For scene props the author recommends Tripo's H3.1 model for detail.
  5. Build the scene: hand Opus 5.5 the exported Tripo props plus the multi-angle references and let it drive Blender + Unity to lay out the environment, place props and fix proportions. The author's prompt (translated): "Using the uploaded multi-angle interior/exterior references and the generated Tripo assets, replicate the reference perfectly, matching its striking look and detail." Then send screenshots from front, side and other cameras and iterate.
  6. Characters: generate a consistent four-view T-pose sheet with Image 2.5 → in Tripo pick multi-view to 3D, upload the four views, keep quad topology, max detail, model Smart Mesh P2.0 → if the untextured mesh looks clean, generate the texture; if not, regenerate parts with edit mesh.
  7. Rigging: give Claude the character model with the prompt the author tuned (translated): "Rig and skin the character with Auto-Rig Pro, aligning bones with the joints. Then test raising arms, bending legs and turning, and fix obvious deformation, stretching and clipping."
  8. Animation: download the FBX clips you need from Mixamo and have Opus 5.5 check they match the rig and wire them in. For contact moves like carrying a watering can, start from the closest base clip and have Opus 5.5 refine it in Blender with Auto-Rig Pro's arm IK so the hand stays on the handle and nothing clips or floats.

Prompt

I'm developing a game and my stack is Tripo + Blender + Unity. Based on the scene reference images we generated above, analyze in depth which assets are better generated with Tripo and which are better built directly in Blender.
Mark the assets that need Tripo on the image so I can confirm.

What the author says

In a 2026-10-13 post the author says it took 16 days with Opus 5.5 plus Tripo + Blender to turn each planet from the story into an explorable 3D scene, playable at littleprince.dev. The 2026-10-15 tutorial says it drew nearly 3 million views across platforms, and that most of the scene building, character work, coding and debugging was done by AI. Sac says they'll open-source the full code and more details on GitHub the following week.

Our test

We have no Tripo, Auto-Rig Pro or Unity setup and have not reproduced this workflow; steps, prompts and results are from the author's article. We only confirmed the game page littleprince.dev loads (2026-10-19).

How to get in

The original is a Chinese X article. Tripo (by VAST) is available internationally at studio.tripo3d.ai, Mixamo is Adobe's free animation library, and the game at littleprince.dev offers English and seven other languages (desktop Chrome/Edge with WebGPU).

Who it suits

Indie creators building a small 3D story game, interactive showcase or portfolio piece, and people already using agents like Claude Code who want to connect them to 3D tools.

Pitfalls

  • Lock one scene image you like before adding angles; otherwise the references drift in style and can't be replicated in 3D.
  • Not everything belongs in Tripo: have the AI split the list first; simple structures are built by Opus in Blender/Unity, Tripo handles complex props and characters.
  • Get a consistent four-view sheet first, and regenerate bad mesh areas in Tripo before texturing.
  • Stock Mixamo clips don't fit contact moves like holding a prop; refine with IK in Blender and check for clipping, slipping hands and floating props.
  • Auto-Rig Pro is paid; the Tripo link in the article carries the author's referral code, so go to studio.tripo3d.ai directly if you prefer.
  • The finished game needs a desktop browser with WebGPU (Chrome / Edge); phones and tablets aren't supported, per the notice on littleprince.dev.

More in this category