An open, evolving playbook for agencies going AI-native. Tracked problems, documented fixes, compounding knowledge. Built and maintained by reverseBits. Contributions welcome from any agency, studio, or indie operator.
If you only read one section, read this one.
Hit a problem? → Open an issue. Pick the "Problem report" template. Fill 3 fields. Done.
Want to share a tool, workflow, or learning? → Use one of the other templates. Same page.
Looking for a fix someone already figured out?
→ Browse /docs — every solved problem has a clean, linkable doc there.
Just want to chat or ask a question? → Discussions.
That's the whole contributor loop. Stop here if you're filing or reading. Everything below is for maintainers.
Not cheatsheets. Not hype threads. A tracked, searchable, versioned knowledge base of the real problems agencies hit adopting Claude, MCPs, skills, plugins, and agentic workflows — and the fixes, tools, and workflows that actually worked.
Two layers:
- Issues — raw problems, evidence trails, in-flight investigations.
/docs— promoted, curated fixes. Stable URLs. Shareable. This is the compounding asset.
A problem starts as an issue. When it's solved, the fix lands as a doc in /docs via PR, and the issue closes with a link to the doc.
- Looking for a known fix? Browse
/docsby category (/docs/mcp,/docs/skills, etc.). - Want to see in-flight work? Open Issues, filter by label.
- Want the process in action? Read
/examples— two worked end-to-end walkthroughs.
mcp · skills · cost · workflows · tooling
New categories get created only when an issue genuinely doesn't fit. Full definitions in MAINTAINING.md.
Want to go beyond filing an issue? See CONTRIBUTING.md. Short. Covers how to promote an issue to a doc via PR.
Running triage, labels, the project board, or the promotion bar? See MAINTAINING.md.
See SETUP.md.
Content under CC BY 4.0. Code snippets under MIT.