— Superwall Icons

Most icon sets ship as a dependency — an npm package you install and version, or (shadcn-style) a pile of components you copy in. This one ships as neither. It's a single Markdown file at/icons.md: the whole set as compact codes, plus the handful of lines an agent needs to render them. Point an agent at the file and it implements the rendering itself. superwall.com is simply one consumer — it keeps its own hardcoded copy, exactly like anyone else would.

Each icon is a 7×7 grid — 49 bits — packed into a ~10-character base36 code. No fonts, no sprite sheet, no build step. The source of truth is a database an admin edits right here on this page; the Markdown is generated from it live.

It's a small piece of a bigger idea our growth team runs on: the boundary between human work and agent work isdocumentation.

The rule is blunt: if it isn't documented, it doesn't exist. Everything downstream — feature pages, the changelog, integrations, this icon set — is scraped and generated at build time from those docs, in a git-backed CMS that agents manage end to end (usually Claude, in Slack). The site rebuilds itself nightly.