An AI game-asset canvas workbench for indie game developers and 2D art teams.
中文说明 · Open AiAnimate · International site · Report an issue
AiAnimate helps a game team move from an idea or an uploaded reference to reusable game assets in one visual workspace. Instead of switching between isolated generators, you work with cards on a large canvas: connect the next action, configure the target card, run the task, inspect the result, and export the deliverables you actually need.
These are real AiAnimate game-asset outputs used to explain the product surface: an animation clip, a layer split, and a VFX frame.
Animation clip · layer split · VFX output
flowchart LR
A[Prompt or upload] --> B[Canvas card]
B --> C[Right-side +]
C --> D[Downstream card]
D --> E[Configure and run]
E --> F[Status and outputs]
F --> G[Download or deliverable package]
The canvas is the product’s primary structure. A connection records where an output came from and what the next action is; it does not silently start a task. The target card owns its parameters, status, preview, and deliverable outputs.
AiAnimate organizes the asset journey around cards and explicit deliverables:
- Images and references — start from text, an upload, or a visual reference.
- Transparent assets — turn a visual source into a reusable transparent PNG.
- Layers — split a source into editable game-art layers.
- Video — create a preview or source for the next canvas action.
- Animation clips — turn a source into a single action clip with a Sprite Sheet or Frames ZIP plus a manifest.
- VFX clips — turn a visual source into a transparent PNG Frames ZIP plus a manifest; MP4/GIF/poster are previews, not the final game deliverable.
- Deliverable packages — collect the outputs a user explicitly chooses to ship or reuse.
The goal is not only a good-looking preview. The goal is a traceable, downloadable, and reusable asset that a game project can actually consume.
- Open aianimate.cn or the international site.
- Enter a prompt or upload a source to create the first card.
- Use the card’s right-side
+to choose the next action. - Configure and run the new target card.
- Review the task status and outputs, then download them or add selected deliverables to a package.
The canvas keeps source, transformation, task status, and output lineage together. It makes the next useful action visible without turning the product into a technical node editor:
- cards represent assets, descriptions, tasks, and delivery;
- connections preserve provenance and input mapping;
- execution happens deliberately on the target card;
- preview files are distinguished from game-ready deliverables;
- download, personal assets, and deliverable packages remain separate user actions.
The public repository contains the developer-facing integration surface for the AiAnimate product. The hosted canvas remains the main product experience; these packages are optional automation and integration tools.
| Package | Purpose | Entry point |
|---|---|---|
@aianimate/cli |
Inspect capabilities and call the developer API from a terminal or script. | npx @aianimate/cli --json capabilities |
@aianimate/mcp |
Connect an MCP host such as Cursor or Codex to AiAnimate. | npx -y @aianimate/mcp |
Set the API endpoint explicitly when using an integration:
export AIANIMATE_API_KEY="your-developer-api-key"
export AIANIMATE_API_BASE_URL="https://aianimate.cn"Use https://aianimate.design for the international instance. Never commit an API key or put one in an issue, log, prompt, or generated-media URL.
This public repository is a focused public surface for AiAnimate: product entry points, developer package sources, package documentation, and release metadata. It is not a mirror of the private application monorepo or its production credentials.
Read SECURITY.md before sharing logs or configuration. Please report suspected credential leaks privately rather than opening a public issue with secrets.
See CHANGELOG.md for public repository and package release notes.