The lab

The problemMy sprite pipeline generates animation frames with video AI. The green background is never quite the same green twice. Normal chroma keying assumes one color: it either left green fringes or ate the sprite's edges.

Why I built itI needed clean sprites for my own games and got tired of hand-fixing edges frame by frame.

The buildSamples the border pixels of each frame independently, takes the circular mean of the saturated hues to find that frame's actual background color, removes pixels near that hue, despills the green rim glow, then erodes the alpha edge.

What didn't workKeying against a fixed green value. The generated frames varied enough in hue that edge cleanup was inconsistent across a single sheet. Per-frame sampling replaced it.

Technical decisionsTests run on synthetic frames instead of image fixtures, so the repo stays small and the tests stay deterministic.

Built withPython, NumPy, Pillow. MIT.

The problemMy second brain is a few hundred markdown notes. Links rot quietly: a renamed note, a deleted heading, an alias that stopped matching. Obsidian shows you one broken link when you trip over it. I wanted all of them in one pass.

The buildImplements Obsidian's actual link-resolution rules (full path, path suffix, basename, aliases, case-insensitive, heading and block anchors), then lints every note. Exit codes and a --json mode so it runs in CI.

Technical decisionsCode fences, inline code, and comments are masked before link scanning, so example links in documentation don't count as real ones. That one choice removed most false positives.

Built withTypeScript on Node's native type stripping. No dependencies, no build step. MIT.