Tripo

Everything Tripo does goes through tools/tripo/tripo.ts, the team's CLI for Tripo's Studio. It spends the subscription's credits. Read tools/tripo/README.md for every command, and run node tools/tripo/tripo.ts <command> --help for a command's options before using it.

• Check the login and credits first with node tools/tripo/tripo.ts balance. If it says TRIPO_STUDIO_COOKIE is missing or the login failed, stop and ask the developer to set or copy it again (README, Setup). Never ask for the cookie's value in chat.
• Say what it will cost before spending much. The README's table lists every command's credits; images and preset animations are free. Every command prints what it was charged, from Tripo's own history. Several models at once, or anything over about 100 credits, needs the developer's go-ahead.
• Chain by project. Each command prints one line of JSON; take project from it for the next command. Commands on a project wait for anything already running on it.
• Follow the style guide. Everything made for the game follows docs/art-style.md (D14): end every concept prompt with its concept paragraph, word for word, and check every model against its checklist. Don't give art/style/mood-medieval-town.png as a style reference: it is the earlier painted direction, kept as research.
• A model for the game that is not a character (a prop, tool, item, tree or rock) goes the whole way through the models skill: concept, model, clean-up, the game's data and the checks.
• Look at what you made. Read the images you generate, and render or open models before calling them done (docs/development.md, Blender).
• Rigs: the default, unreal, is the app's V3 rig with the only twist bones that carry skin, and the one our characters use (tools/characters/make_character.sh; its bone names are our animation libraries'). --skeleton tripo is the older V1 rig, kept for comparison. --type other rigs an animal or creature.
• Drafts are build output; what is kept is source art. Write drafts under an ignored folder such as tools/characters/out/. What the developers approve, and what the game's files are made from, goes in art/ and is committed (art/README.md).
• When a command breaks because Tripo changed its requests, or to check the CLI still matches the app, follow tools/tripo/MAINTAINING.md and fix the CLI. Don't call Tripo's API or web backend some other way.