What Pixeldex is

Pixeldex is a small website with five things on it: a library of copy-paste Claude prompts for game-dev tasks, a set of end-to-end walkthroughs that ship real games, a library of CC0 pixel art sprites we made ourselves, a free in-browser sprite spec builder for multi-directional and isometric art, and an opinionated blog on the craft of solo indie dev in 2026.

Everything is opinionated. Every prompt is tested in a real project. Every walkthrough finishes a game. The site itself is plain HTML hand-rolled by one person — no framework, no build step, hosted on Cloudflare Pages for $0.

Why it exists

Solo game devs in 2026 face a strange problem: AI co-devs like Claude are good enough that you can ship a real game by yourself, but the prompts and patterns that make that work are scattered across reddit threads, paywalled YouTube channels, and "10 ChatGPT prompts for game dev" listicles where the prompts are visibly bad.

Pixeldex is a single, opinionated, in-public collection of actually-good prompts for game dev with Claude. The goal is that the next solo dev shouldn't have to derive the same five player-controller prompts from scratch the way the last one did.

Who built it

Pixeldex is made by one person, in their evenings, as part of a small portfolio of indie tools shipped during a personal sprint. Not a startup, not a content farm, not a YouTube channel funnel. Just a website that exists because the maker wanted it to exist.

The handle is on GitHub (link will be wired up when the public repo launches).

How it stays free

Pixeldex's running cost is approximately $14 a year — that's the domain registration. Cloudflare Pages hosts it for free at any traffic level we're likely to hit. There's no database, no backend, no subscriptions. The site is plain HTML files on a CDN.

If we ever need to add infra (e.g. a community submission system, or a search index), we'll add it on the smallest free tier that works. If something would force us to charge users, we don't add it.

How it stays honest

A few rules:

Can I contribute?

Not yet via a public repo, but yes via direct contact. If you have a prompt that's worked for you in a real shipped project, email it to the address in the footer (when one exists) or open an issue on the eventual GitHub. We'll vet it like any other prompt — does it return drop-in code, does it have a testable "what good looks like" criterion — and credit you in the prompt page if it lands.