/unpackBreaks complex ideas into discrete components, each defined separately.
Category: Thinking & Reasoning
Before / After
Explain CAP theorem.
/unpack CAP theorem.
What changes in Claude's response
Instead of one long paragraph that conflates terms, Claude defines each component independently first (Consistency, Availability, Partition Tolerance), shows how they interact, then explains the theorem. /unpack is how to learn anything dense — Kubernetes, OAuth flows, CRDTs — without ending up with a fuzzy mental model.
When NOT to use /unpack
Skip for things you already mostly understand. /unpack restarts from first principles, which is patronizing if you just had a small gap.
Codes that stack with /unpack
/unpack is one of 120 tested prompt prefixes. The full cheat sheet has before/after examples, warnings, combos, and 10 workflow playbooks.
See the full cheat sheet — from $5More Thinking & Reasoning codes
L99Pushes Claude to maximum reasoning depth. Less hedging, more opinion, longer answers.
/deepthinkForces Claude to reason through every layer before answering. Shows the work.
OODAObserve → Orient → Decide → Act. Best for time-pressured operational decisions.
CHAINLOGICShows each reasoning step explicitly so you can verify the logic, not just the conclusion.
/blindspotsAsks Claude to find what you're missing or assuming, not what you're asking.