Your AI agent makes the sprites
Connect SpriteCook to your editor. Your AI writes the game, SpriteCook makes the art.
Pick your editor
View the Claude plugin on GitHubClaude desktop app
Add the SpriteCook marketplace from the plugin repo, then install. Point and click, nothing to type.
Plugin repo
https://github.com/SpriteCook/claude-plugin- 1
Open the Code tab and click Customize in the sidebar.
- 2
Click the +, then Create plugin, then Add marketplace, then Add from a repository.
- 3
Paste the repo URL and hit Sync. Then install SpriteCook and connect your account.
Claude Code
Run these two commands inside a session.
Need a hand?
Watch the two-minute setup, or read the full guide with screenshots.
What you can ask for
Talk to your agent in plain language. It calls SpriteCook and drops the art into your project.
What it sets up
Watch the agent workflow in action
This section is a showcase, not an install guide. It demonstrates the kind of SpriteCook workflow an agent can drive inside your editor.
"Build me a fishing game"
You describe the game. Your agent plans the assets, generates them with consistent style, and wires them into your code.
Every asset matches
Style Reference
Generate one hero asset first. Pass its ID as reference_asset_id to everything after. Palette, proportions, and style match automatically.
Edit Existing
Need to tweak an asset? Pass its ID as edit_asset_id with a new prompt. "Add a red cape" or "make the sword glow."
Animation starts with an asset
Import Before Animate
If your agent starts from a local PNG or data URL, it should first import that image through POST /v1/api/assets/import and then animate the returned asset_id.
Keep Asset IDs Local
Strong agent workflows save important SpriteCook IDs in a local manifest like spritecook-assets.json so future animation, edit, and reference steps do not depend on the SpriteCook dashboard.