I kept googling the same things over and over: the flags for tar, the difference between git reset and git revert, what a /26 subnet works out to, the exact ffmpeg incantation to trim a video. The answers are always buried three scrolls deep in a blog post wrapped in ads.
So I built the reference I wanted: a set of 60 searchable developer cheat sheets that load instantly, filter as you type, and let you click any command to copy it. No sign-up, no pop-ups, and every one runs entirely in your browser (open DevTools, watch the Network tab while you search: zero requests).
A few I use constantly:
regex cheat sheet - character classes, lookarounds, flags, and ready-made patterns
git cheat sheet - grouped by task (stage, branch, rebase, undo, stash)
bash, jq, and CIDR / subnetting
languages: JavaScript, TypeScript, Python, Go, Rust, and more
infra: Docker, kubectl, Nginx, systemd, Terraform
How it is built
It is an Astro site on Cloudflare Workers. Every cheat sheet is a static page: the full dataset is baked into the HTML at build time, so filtering is just a tiny bit of vanilla JS over the DOM. No framework runtime, no client-side data fetching, no tracker. Each page is a handful of KB.
The click-to-copy is a single delegated listener on the whole page: click a code element, it copies the text and shows a toast. Because the data is real HTML in a real table, it also means search engines and AI assistants can actually read the content instead of waiting for JavaScript.
There is also a free, in-browser PDF toolkit (merge, split, reorder, rotate) that never uploads your files - pdf-lib and pdf.js do the work locally.
What I would add next
I am taking requests for cheat sheets and tools. What do you look up the most that still does not have a clean, fast reference? Drop it in the comments and I will build it.
Everything is at glunty.com - small tools, no nonsense.
Top comments (2)
You asked what we keep looking up, so here's mine: SQL window functions. The difference between RANK and DENSE_RANK, frame clauses, and a few ready patterns like "latest row per group" would earn a permanent tab from me. Separate thing, but telling people to open the Network tab and watch zero requests happen is the right way to make a privacy claim, a promise in the footer can't compete with that.
Running cheat sheets entirely in the browser is a nice durability choice. I would add offline behavior and source/version notes, because reference tools age quickly when the underlying commands change.