Stop guessing which Claude codes to use.

/punch /trim Rewrite this feedback so it is specific and actionable. Original: [paste original feedback here]. Output should name the exact behavior, the exact impact, and the exact change requested.

/mirror /voice First read this email as a tone reference: [paste their original email]. Now write my reply. The reply needs to: [your actual content points]. Match their tone exactly — same formality, same length, same rhythm.

SENTINEL /blindspots /punch Review this code. Focus on: failure modes I haven't handled, security/auth gaps, race conditions, and assumptions that aren't enforced. For each issue: name the line, name the risk, name the fix. Code: [paste]

/hook /punch Rewrite the opening of this piece. Goal: a first sentence that makes the reader read the second. Audience: [who you're writing for]. Original opening: [paste]. Show 3 options ranked by which forces the next read most.

/ghost /punch /hook Write a LinkedIn post about: [topic]. Make it feel like a real person typed it on their phone — short paragraphs, specific examples, one strong opinion. No 'thrilled to share', no 'so honored', no list of hashtags. Length: 4-6 short paragraphs.

/punch /trim /raw Turn this into a Slack message. Goal: get [specific outcome you want from the recipient]. Three lines max. No greeting. No fluff. State the situation, state the ask, state the deadline. Original: [paste your rant]

L99 /punch /skeptic What should I do about [strategic question]? Context: [stage, constraints, what's been tried]. Don't give me 5 options. Give me the call you'd make and the one reason that matters most. If the question is wrong, say so.

/ghost /voice [casual / wry / direct / academic] /flow Draft a 600-word blog post on: [topic]. Audience: [who they are, what they already know]. Lead with [a specific anecdote / a contrarian claim / a concrete example]. End with one practical takeaway. No 'Furthermore', no 'In conclusion'.

/punch /voice [firm but warm] L99 They asked for [the discount / scope change / extension]. Here's the context: [the deal, your position, your walkaway]. Write the reply that holds my position, gives them a clear counter, and keeps the relationship intact.

L99 /punch PARETO I'm trying to decide [the actual decision]. Here are 5 sources: [paste or describe]. Don't summarize each one. Tell me: which 2-3 insights actually change the decision, what those insights are, and what I should do.

/blindspots /skeptic OODA Here's a problem I've been stuck on: [describe the problem and what you've tried]. What am I assuming that might be wrong? Then: if those assumptions ARE wrong, what's the actual problem and what should I do?

/simplify /raw Explain [technical concept] to someone who doesn't have a background in [the field]. Use a real-world analogy. No jargon. If you have to use a technical term, define it inline. Maximum 200 words.

/rephrase /trim Rephrase this sentence so it's unambiguous and short. Original: [paste]. Output should preserve all the meaning but cut the word count by at least 30%.

IDEATE /blindspots Generate 20 ideas for [the problem]. Skip the obvious 5. Include some that sound bad on first read. Then pick the 3 that are most interesting and explain why.