explaingit

mmaterone/retrodex

19TypeScriptAudience · vibe coderComplexity · 3/5Setup · moderate

TLDR

A local pixel art editor built to work hand-in-hand with AI coding agents like Codex. Codex generates and edits sprites programmatically while you do the manual finishing, both working on the same files without conflicts.

Mindmap

mindmap
  root((Retrodex))
    What it does
      AI plus human editing
      Sprite cleanup pipeline
      Conflict prevention
    Editor Tools
      Brush eraser fill
      Selections and layers
      Animation timeline
    Export Formats
      PNG GIF WebP
      SVG and Lottie
    Tech Stack
      TypeScript API
      Python cleanup
      Browser canvas
    AI Integration
      JSON CLI
      Local API
      Coordinate edits
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Things people build with this

USE CASE 1

Let an AI agent generate a game sprite, then open it in the browser editor to fix small details by hand.

USE CASE 2

Automate bulk pixel art edits across many frames using the CLI without touching the browser UI.

USE CASE 3

Create animated sprite sheets with frame controls and export as GIF or Lottie for use in games or apps.

USE CASE 4

Run an image through the cleanup pipeline to snap AI-generated art onto a proper pixel grid before editing.

Tech stack

TypeScriptPythonBrowser CanvasLocal APIJSON CLI

Getting it running

Difficulty · moderate Time to first run · 30min

Requires running a local API server and has a Python-based cleanup pipeline alongside the TypeScript components. Active prototype, expect rough edges.

No license information was mentioned in the explanation.

In plain English

Retrodex is a local pixel art editor designed to work alongside an AI coding agent called Codex. The idea is that Codex handles the generation and programmatic editing of pixel art, while you handle the manual finishing work, and both operate on the same files through the same system without stepping on each other. The workflow goes roughly like this: you ask Codex to create a sprite, it generates an image and runs it through a cleanup pipeline before opening it for editing. The cleanup step matters because AI-generated images that look like pixel art are rarely on a clean grid at the right size. The pipeline detects the underlying pixel grid, removes backgrounds, trims leftover colors from image generation, and scores the result before handing it off. Only after cleanup passes does the image open in the browser-based editor for you to work on directly. The browser editor is a canvas tool with the standard pixel art toolkit: brush, eraser, fill, color picker, shape tools, selections (box, lasso, magic wand), a layer mask system, and an animation timeline with frame controls. Exports cover a wide range of formats including PNG, GIF, WebP, SVG, and Lottie. Changes save automatically to a local folder. Codex interacts with the system through a JSON command-line interface and a local API running on your machine. It can read the current pixel map of any frame, apply brush strokes at specific coordinates, manage selections, and trigger exports, all without needing to click through the browser UI. Mutations include a revision guard so that if you and Codex both make changes at roughly the same time, they do not silently overwrite each other. The project is described as an active prototype rather than a finished product. The core image cleanup logic is written in Python, and the API, CLI, and web editor are written in TypeScript.

Copy-paste prompts

Prompt 1
I have Retrodex running locally. Write a script using its JSON CLI to generate a 16x16 walking character sprite, clean it up, and export it as a PNG.
Prompt 2
Using the Retrodex local API, write TypeScript code that reads the current pixel map of frame 1, changes all red pixels to blue, and saves the result.
Prompt 3
I'm using Retrodex with Codex. How do I set up the workflow so Codex generates sprites into the watched folder and I can edit them in the browser without conflicts?
Prompt 4
Write a Codex prompt that creates a simple 8x8 coin spin animation in Retrodex with 4 frames and exports it as a GIF.
Prompt 5
Explain how Retrodex's revision guard works and how I should structure my manual edits to avoid overwriting Codex's changes.
Open on GitHub → Explain another repo

← mmaterone on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.