Work
WritingAI2026

PUFGY

Ship real products with AI — the rules, rituals and small machines that turn a brilliant amnesiac collaborator into a compounding one.

Visit pufgy.com

The problem

An AI collaborator starts every session with no memory of the last one. Most of what gets written about that is prompt tricks — they fix one conversation and nothing after it. The thing that actually compounds is boring: the artifacts, habits and small machines around the work, so that session two starts where session one ended instead of starting over.

What I built

  • Volume 1 is The Claude Playbook, written in English and German — maps your codebase can explain, sessions that boot, proofs instead of promises, and ship discipline.
  • Dual-audience by design: every how-to passage carries a copy-paste block you can feed straight to your own agent, so the book changes a setup and not just a reader's mind.
  • The site's "Measured, not marketed" panel is regenerated from the project's own session logs on every build, never typed by hand — with a footnote that names what those numbers do not prove.
  • Written the way it teaches: one chapter per file, and a leak gate that runs before every commit so no private name, domain or key can walk out onto a public page.
  • Volume 2, The TikTok Shop Playbook, is next in the series — same discipline, different arena.

A look inside

pufgy.com — The Claude Playbook hero with the cover card
pufgy.com — Volume 1 of the shipping series, with the honest call to action: get the book, soon.

The result

The site is live at pufgy.com. The book is not out yet, and the page says so plainly: "In the making — EN & DE. The waitlist opens here with the launch." A complete English first draft exists — preface, ten chapters and an appendix — and is in review; the release channel is deliberately still open.

Built with

Markdown manuscript (one chapter per file)Cloudflare Workers (static site)Node build toolingEN + DE