WORSTCASEWhat's the worst that could happen? Specific, not theoretical.
Category: Bonus / Experimental
Before / After
What could go wrong?
WORSTCASE I'm about to push a database migration that adds a NOT NULL column to a 50M-row users table.
What changes in Claude's response
Claude lists the specific failure modes: 'the migration will lock the table for 20+ minutes', 'every read will block during the migration', 'if it fails halfway you'll have a partially-migrated table that's hard to roll back'. Then it tells you how to avoid each. /WORSTCASE is paranoid mode for high-stakes actions.
Full deep dive locked
The complete analysis for WORSTCASE — 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.