# I built a Claude Code plugin that makes 8-direction game sprites from one illustration. Notes on structuring a skill around paid API steps — retained record

> Retained reddit record from reddit:ClaudeCode.

Canonical: https://highsignal.app/data/records/6e281cd9c3ff4975

[← sources](https://highsignal.app/data)


source: [reddit](https://highsignal.app/data/reddit) (reddit:ClaudeCode)  published 2026-11-10 19:03 ingested 2026-11-11 02:42

[original source ↗](https://www.reddit.com/r/ClaudeCode/comments/1xsvjdm/i_built_a_claude_code_plugin_that_makes/)

## retained text



```
Disclosure: this is my own project, free and MIT. Sharing it mostly for how it’s put together as a Claude Code plugin, since that part took the most iteration.

**What it does:** SpriteCast turns one character illustration into 8-direction walk, run, jump and attack strips for a game, at the game’s exact camera angle and drawn in the illustration’s style. A 3D model and rig (Tripo) set the pose for every frame; an image model redraws each render in your style.

**How the plugin is structured**

* [**SKILL.md**](http://SKILL.md) **stays short; the procedures live in** `reference/*.md` (characters, sitting, touch-up). Claude reads the reference only when the task needs it, which kept the always-loaded part small.
* **Plain Python scripts do the work** (`charpipe.py render / draw / finish / pack`), so everything can also be run without Claude. The skill’s job is the judgement calls between the steps.
* **Every paid step is gated.** Each script prints its cost and refuses without `--yes`, and the skill says to ask the user before each one, never to chain paid steps because the last one “looked fine”. That rule came from wasting money early on.
* **API keys through the plugin’s** `userConfig` (marked sensitive, so they’re stored in the system credential store). A SessionStart hook exports them for the scripts, and the skill is told never to ask for a key in chat or write one to a file.
* **The scripts measure, Claude looks.** Every drawn frame gets an outline-overlap score against its 3D render, and a wrongly placed weapon is redrawn automatically. Claude still has to look at every facing, because a score can’t see a head drawn facing backwards inside a correct outline.

**Prompting lessons from the image side**

* Describing the motion made it worse: “raise it overhead, swing it down” had the umbrella drawn overhead in frames where the render held it at the side. Naming the action and telling each cell where the prop is, or that the body hides it, fixed it.
* A flaw in the 3D model can be fixed in words: one line in the spec’s `notes` removed dark streaks from every frame.

**Numbers:** in the example, all 64 run frames and all 64 jump frames fit their 3D poses on the first drawing. A walking character costs about $1.7 of image generation plus \~85 Tripo credits. The example’s rig is in the repo, so with `"draw": false` you can run the 3D side with no keys.

    claude plugin marketplace add Sunghwan0112/spritecast
    claude plugin install spritecast@spritecast

[https://github.com/Sunghwan0112/spritecast](https://github.com/Sunghwan0112/spritecast)

Happy to go into any of it, especially the gating and the frame checks.
```



document fetched 2026-11-11 00:40 · canonical https://reddit.com/r/ClaudeCode/comments/1xsvjdm/i_built_a_claude_code_plugin_that_makes
