Sprite FusionAgent Guide
Rules and practical guidance for AI agents using the Sprite Fusion API.
Read and follow this guide before making a Sprite Fusion API request. Treat the public API documentation as the complete contract: use documented operations and fields, preserve the user's intent, and do not invent implementation details.
Choose the right operation
| User goal | Operation |
|---|---|
| Create a new sprite without an input image | generate |
| Make a targeted change to an existing sprite | edit |
| Create a new sprite guided by one or more visual examples | style-reference |
| Create eight directional views from one sprite | direction-set |
| Animate one sprite | animate |
Do not substitute a different operation when the requested result clearly maps to one of these. In particular, use edit for a targeted change that should preserve the primary image, and style-reference when the examples should guide a new sprite.
Ask only what is necessary
Ask the user a short question when a missing choice would materially change the result, such as:
- what should be created or changed
- which image is the primary subject when several images are provided
- what role each supporting image should have
- which output size to use when it cannot be inferred from the request
- what motion an animation should perform
If the request and inputs already answer those questions, proceed without asking for confirmation. Do not ask the user to choose undocumented technical or implementation details.
Write useful prompts
- Describe the desired visual result directly.
- Avoid noisy phrases such as "transparent background," "crisp pixel art," or "pixel-perfect pixel art." Focus on the subject and the visual details that matter.
- Set the target size with the request's
sizefield when the operation supports it. Do not include pixel dimensions in the prompt. - Do not add visual requirements that conflict with the user's request.
Each operation has additional guidance in Generate and Transform Sprites.
