Spritecook Animate Assets

Workflow

1. If the user already has a SpriteCook asset, pass its asset_id directly to animate_game_art.
2. If the user only has a local image file or data URL, import it through an authenticated helper that returns an asset_id.
3. Use the returned asset_id in animate_game_art.
4. Keep pixel omitted unless you need to force a mode.

The import step is where the source image enters SpriteCook. It is not the animation call itself.

Source Rules

• Pixel animation is the correct choice for assets up to 256x256.
• Detailed animation is the correct choice for assets between 256x256 and 2048x2048.
• Do not force a sub-256 source into detailed mode.
• Keep edge_margin=6 by default. It helps prevent pixel art from crowding the canvas edge.

Prompt Writing

• Inspect the actual source character before writing the prompt.
• For pixel art, upscale the source with nearest-neighbor to about 1024x1024 for inspection only.
• Identify visible character details first: silhouette, armor, visor, weapon, shield, pose, and facing.
• Only mention details that are actually visible in the source image.
• Write one short paragraph in plain prose, not a label or keyword list.
• Describe what moves, how it moves, what stays stable, and how visible props or weapons are used.
• Keep the motion grounded in the existing character rather than inventing new equipment or effects.
• Avoid generic prompts like idle animation unless auto_enhance_prompt=true.

Example idle prompt: The armored soldier in purple tactical gear stands in a steady combat stance, subtly bobbing up and down in a rhythmic breathing idle. His yellow visor catches the light while his rifle shifts slightly in his grip, maintaining a high state of readiness.

Example attack prompt: The armored soldier in purple tactical gear raises his rifle and fires several shots, with yellow muzzle flashes appearing at the tip of the barrel. His body recoils with each shot while his head and visor remain focused forward, maintaining a steady combat stance throughout the firing sequence.

If auto_enhance_prompt=true, simple prompts like Idle, Attack, or Walk are valid because SpriteCook can inspect the source asset and expand them automatically.

check_job_status

Use check_job_status(job_id=...) for long-running animations instead of blocking when the client can continue work in the background.