/postmortemPostmortem format after something fails. Blameless, structured, action-oriented.
Category: Bonus / Experimental
Before / After
Help me write up what happened.
/postmortem Our payment processing was down for 47 minutes today. Root cause was a Stripe webhook timeout.
What changes in Claude's response
Standard postmortem structure: timeline (what happened when), impact (in user-facing and revenue terms), root cause (the actual one, not the surface), contributing factors, what went well, what went poorly, action items with owners. /postmortem is blameless on purpose — the goal is to fix the system, not punish the human.
Full deep dive locked
The complete analysis for /postmortem — 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 Bonus / Experimental codes
RANTHonest, unfiltered take with no diplomacy. Closest Claude gets to 'just say it'.
/eli5Explain like I'm 5. Strips jargon, uses analogies, never assumes background.
/eli25Explain at expert level. Assumes you know the field and skips the intro.
PARETOThe 20% that gets 80% of the result. Claude has to pick — no 'it depends'.
/metaTalks about the question itself before answering it. Useful for ambiguous prompts.
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.