Skip to main content

The Tools

Two plain markdown files you paste into Claude. One generates a personalized architecture deck for a founder. The other generates custom editions of the generator itself.

Hand-drawn line illustration in warm terracotta and cream: a loopy hand presses an ink stamp onto a cream sheet while identical stamped sheets recede to the right, watched by an abstract face drawn in a single line.


1. Build on Claude: the personalized architecture read

File: /tools/build-on-claude.md

For any founder or builder, in an accelerator or not. Copy the file, paste it into Claude (best: Claude Code inside your repo, so it reads your context first), and it interviews you for the gaps, then generates a clickable deck personalized to your product: where you sit among the four ways to build, working code for your case, honest cost arithmetic, the trade-offs including when NOT to build on Claude, and a copyable build brief that starts your first real build session.

It is honest by construction: if the right answer for you is one API call and no agent, the deck says so. If staying provider-portable is right for your situation, the deck says that too.

2. Customize the generator: mint your own edition

File: /tools/customize-the-generator.md

For evangelists, accelerator partners, community leads, and agencies. Paste it into your harness and it interviews you about your audience (a batch, a vertical, a community), pulls the most relevant proof rows from The Index, and emits a customized edition of the generator carrying your name, your audience tuning, and your call to action.

The honesty bar carries through every edition and cannot be customized away. A generator that flatters its audience burns the operator's name with it.

How the pieces fit

The wiki is the evidence layer: The Index holds all 256 published builds, and /llms-full.txt carries the whole wiki as one machine-readable file. The tools are the action layer: they read that evidence at generation time, so every deck's proof slide quotes real published numbers, never inventions.

Paste chain, end to end: an operator customizes the generator, a founder runs their edition and gets a deck, the deck hands them a build brief, the brief starts the build. Every artifact generates the next one.

Further Reading