Skip to content
Prompt & SolderHow to Ask Claude
All builds

Image: u/jethrocabaluna on Reddit

Worked Proof shown

A Godot plugin that turns Aseprite town drawings into scenes

A game maker had Claude Code build a plugin that turns named Aseprite layers into placed building and object scenes with collision traced from the pixels.

—

Credits

  • Reddit poster jethrocabaluna Source ↗

Earliest dated source: 18 Nov 2026

Video ↗

The full story

A pixel artist making a tactics RPG in Godot draws a whole town in Aseprite and names the layers by what they are, such as 'Building Inn', 'Object Tree', 'Exit' and 'Collision'. A Godot plugin then builds every building and object as its own scene, placed where it was drawn, with collision traced from the pixels, y-sorting and doors set up. Building interiors work the same way.

Claude Code wrote all the code while the artist did the art and decided how things should work. The repository's CLAUDE.md sets out who owns what and rules such as running the tests before claiming something is done, and decisions are kept in a document so later sessions do not reopen them. Claude runs Godot itself and checks screenshots, and also wrote a small Aseprite extension that keeps copies of repeated objects in sync.

How it was done

Tools

Themes

Loading themes…

Sources

From a short post by the maker, so the details are as they tell them.

  • Reddit: Built a Godot plugin with Claude Code that turns my Aseprite town drawings into playable scenesForum threadreddit.com
    Reddit poster: jethrocabalunaPosted 18 Nov 2026

    The maker's post in r/ClaudeCode describing the plugin and their Claude Code workflow.

  • The video: youtu.beVideoyoutu.be

    The maker's devlog video showing the town-building workflow.

Related builds

Finding related builds…

Prompt & Solder

An independent community project. Not affiliated with Anthropic.

What this is. Real projects where people used Claude to build, fix, port, revive or take apart something, from jailbroken Kindles to rebuilt DOS games, plus the times it went badly wrong. Every build links to where it was shared, and every source is listed here.

How far to trust it. We summarise what people reported and say what each build rests on: a full write-up with code, a short post, or a passing comment. We haven't tested them ourselves. Photos are shown from the original sources with credit. Only modify hardware you own, and back up first.

Privacy. No accounts. Analytics cookies (Google Analytics) only if you accept them; no ads or cross-site tracking. Searches are counted anonymously (just the words) to show what's popular, and so are clicks on Ask Claude (just the count). The Claude connector only receives the search words your Claude sends it.

How toAsk ClaudeEvery sourceStatsSubmit a buildPrivacyRSS