/playbookRepeatable playbook for a recurring task. Not a recipe — a runbook with branches.
Category: Productivity Hacks
Before / After
How do we handle this?
/playbook How to handle a customer escalation that comes in via Twitter.
What changes in Claude's response
Output has decision points: 'first check if X. If yes, do A. If no, do B and check Y'. /playbook is for processes where the right action depends on what you find as you go. Usually 1-2 pages and branchy.
Full deep dive locked
The complete analysis for /playbook — including when NOT to use it, the failure modes, and the codes it stacks with — is in the full cheat sheet along with 119 other tested prefixes.
Lifetime updates · 7-day refund · 3 tiers
More Productivity Hacks codes
/tldrawSketch a workflow in plain English, get the implementation.
/templateGenerates a reusable template from a one-off output. Variables become `{{placeholders}}`.
/recipeStep-by-step recipe format. Ingredients, steps, time estimate, common mistakes.
/cheatsheetOne-page cheat sheet on any topic. Dense, scannable, no fluff.
/quickrefQuick reference card. Even denser than /cheatsheet — designed for one screen.
Get new codes + workflows weekly
Join 30+ developers getting tested prompt codes, skill files, and Claude workflows. One email when there’s something worth sharing.