DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to generate a matching set of game sprites and icons with Skills

Have an agent produce sprites, icons, and props in one style, with transparent backgrounds, through Scenario.

  • Top pick
  • Content
  • Intermediate
  • 30 minutes
  • From the README
  • Claude Code
  • Cursor
  • Codex

Who it is forAn indie game developer who needs dozens of consistent item icons and sprites before a playtest.

The problemHand-drawing or prompting one asset at a time gives inconsistent style, and cutting out backgrounds by hand is slow.

The outcomeA folder of sprites and icons in a shared style with transparent backgrounds, ready to drop into a project.

What you need first

  • A Scenario account, signed in through OAuth or an API key
  • An AI coding agent that supports Agent Skills, such as Claude Code, Cursor, or Codex
  • npx, to run the skills installer
  • The Scenario MCP server connected to the agent at https://mcp.scenario.com/mcp

Steps

  1. npx skills add scenario-labs/skills --skill scenario
  2. npx skills add scenario-labs/skills --skill scenario-game-assets (inferred, check the README)
  3. For Claude Code, run claude mcp add --transport http scenario https://mcp.scenario.com/mcp, or add the same URL to your MCP client and sign in.
  4. Ask the agent for the icon list, one line per asset, and let the scenario-game-assets skill run a style-consistent batch.
  5. Have the agent download the finished files to your project folder.

Prompt for your agent

Using the scenario-labs/skills repo, generate a batch of sprites and icons from the list in <item-list-file>, keeping one art style and transparent backgrounds. Save the files to <output-folder> and report how many succeeded. Verify that each PNG opens and has an alpha channel.

Caveat. The Skills need the Scenario MCP server connected and a Scenario account, so the first run depends on that sign-in succeeding.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page