Building The Meme Factory

The Problem with PRDs

Product Requirements Documents are important. They are also, almost without exception, painful to read. The format rewards completeness over clarity. You end up with tables nobody scans, requirements nobody remembers, and approval sections that exist purely for compliance theater.

I had a real system to document. Tool Bag is the infrastructure layer behind every project I build. It manages MCP server configuration, skill registries, plugin packaging, and cross-model orchestration. 41 active skills. 6 plugins. 5 MCP servers. A benchmark framework. A context tier system. A tri-model routing architecture.

Writing that as a standard PRD would produce a document that was accurate, thorough, and completely ignored.

The Solution: Memes

So I gave the document a fictional leadership team made entirely of internet memes.

Doge became the CEO. His approval comment: "Much PRD. Very document. Wow." Grumpy Cat is the CTO who reluctantly approved with "I hate it. Ship it." Drake runs architecture, naturally right-paneling every good decision. Bad Luck Brian leads QA. Evil Kermit is the CISO whispering "do it" about every security shortcut. The bobblehead employees are contractually obligated to agree with everything.

The format is corporate satire. The content is real.

What It Actually Documents

Behind the meme characters, the PRD covers a production system with real numbers.

MCP Gateway: 5 servers exposing 86 tools through Docker MCP Toolkit v0.40.0. Context7 for documentation lookup, Exa for search, GitHub for repo operations, Linear for project tracking. BrightData is registered but broken at the OAuth discovery layer. The PRD calls this out with a "This Is Fine" badge.

Skills Registry: 41 active skills across 6 plugins. Each plugin covers a domain: UI/UX design, B2B ABM, marketing websites, documentation lookup, and more. Every skill was benchmarked across 6 dimensions.

Benchmark Framework: The scoring system measures trigger precision (does the skill fire when it should), token economy (does it stay within budget), clarity, output conformance, boundary containment, and overall coherence. After a full benchmark-and-fix cycle, the portfolio average reached 88.7 with 56% at A-grade.

Context Tier System: A 4-tier token budget model. Tier 0 is 300 tokens, always resident (CLAUDE.md directives). Tier 1 is 1,500 tokens loaded on demand (project memory). Tier 2 is 4,000 tokens triggered by stack detection (framework docs). Tier 3 is unbounded, loaded only on explicit request (full specs). The meme equivalent column describes Tier 2 as "Things you Google every single time."

Multi-Model Orchestration: Claude Opus handles architecture and critical review. Codex handles implementation and refactoring. Gemini handles visual design and image generation. OMC coordinates all three. The PRD describes how each model "got the job."

Why It Works

The meme framing does three things a standard PRD cannot.

First, it makes the document memorable. People remember that Grumpy Cat reluctantly approved the architecture. They remember the bobbleheads who approve everything. That recall means they also remember the architecture itself.

Second, it invites reading. A 2,000-word technical spec is a chore. A 2,000-word technical spec with Drake memes is something people will actually open voluntarily.

Third, it surfaces real problems without the political overhead. The "This Is Fine" badge on BrightData's broken OAuth is simultaneously a joke and a status report. The bobbleheads satirize rubber-stamp approval culture while still documenting the actual sign-off process.

The Build

The PRD is a single HTML file with custom CSS. No React, no build tools, no framework. Just markup and styling. The color palette uses meme-inspired tokens: Doge Gold, Grumpy Blue, Kermit Green, Drake Purple. The layout is responsive with card grids for the architecture overview and standard tables for data-heavy sections.

I built it in one session. The technical content was already documented across vault notes and ai-memory files. The creative layer was the new work. Mapping meme characters to corporate roles, writing approval comments that were both funny and informative, and designing badge styles that communicated real status through humor.

The Lesson

Documentation does not have to be boring to be thorough. Making it entertaining is not unprofessional. It is a distribution strategy. The best technical document in the world is worthless if nobody reads it.

Doge approved this message.