TL;DR: Someone on Reddit compiled 70+ unofficial ChatGPT slash commands, like /steelman, /failuremap, and /driftcheck, that GPT recognizes without any plugin or setup. They work because the model treats them as intent signals, not built-in features. Here’s what’s actually worth using.
Why These Work at All
ChatGPT has no native slash command system. What it has is pattern recognition. Commands like /eli5, /tldr, and /steelman are shorthand conventions the model has seen enough times in training data that it interprets them as directives.
That’s the whole trick. You’re not invoking a feature: you’re shaping the context window. The more unambiguous your intent signal, the better the output.
Think of it this way: when you type /steelman before a prompt, you’re not pressing a button. You’re telling the model what kind of thinker you want it to be for the next response. The slash is just a convention that makes the signal cleaner. You could write “argue the strongest case against my position” and get similar results, but /steelman is faster and the model has seen it enough to know exactly what you mean. The shorthand removes ambiguity, and removing ambiguity is most of the work in prompting.
This also means these commands aren’t magic. If a command is too obscure, the model may interpret it loosely or skip the prefix entirely. The ones that work most reliably are tied to clear, common analytical tasks: summarize, simplify, argue against, identify failure modes. The more a command maps to a recognizable thinking job, the more consistently it delivers.
Breaking Down the Categories
The list splits into six groups. Core Execution is the most immediately practical: /frictionaudit identifies what makes a task hard to start, /goodenough defines the minimum acceptable version of something, /antiproject flags ideas that shouldn’t become projects. These three alone would justify the whole library.
To make /frictionaudit concrete: paste in a task you’ve been avoiding and ask GPT to run it. The output will typically surface things like “unclear first step,” “requires a decision you haven’t made yet,” or “depends on a resource you don’t have access to.” That diagnosis is more useful than generic productivity advice because it targets the actual blocker, not your willpower.
Self-Awareness is the most underrated section. /driftcheck compares your current behavior against your stated goals. /dopaminecheck asks whether you want something for meaning or stimulation. /identitytrap catches you when you’re chasing aesthetics instead of outcomes. Not prompting tricks: forcing functions.
/identitytrap is worth singling out. It’s designed to catch situations where you’re pursuing something because it fits a story you tell about yourself, not because it actually moves the needle. Building a second newsletter because you see yourself as a media operator. Buying a course because you see yourself as someone who invests in their skills. The question it prompts GPT to ask is simple: is this decision driven by evidence or self-image? That one question can save a lot of time and money.
Decision-Making has the heaviest hitters. /steelman presents the strongest possible opposing argument before you commit to a position. /sunkcost evaluates whether you’re continuing out of logic or emotional attachment. /irreversible flags which decisions deserve extra caution. Use these before any high-stakes choice, not after.
/sunkcost is particularly sharp. Feed it a project you’re on the fence about quitting, and it will separate the legitimate reasons to continue (real future value, clear path forward) from the emotional ones (already invested six months, feels like quitting). It won’t make the decision for you. But it will show you what kind of reasoning you’re actually using, which is most of the work.
Communication and Information rounds it out with the everyday commands: /eli5, /5whys, /redflags, /futureyou. You’ve likely run these by instinct already, just without the slash prefix.
Use Cases
- ⚡ /failuremap before starting any new project, to predict how it breaks before you build it
- 🔍 /driftcheck during weekly reviews, to confirm your actions are matching your stated priorities
- ⚖️ /steelman before any high-stakes decision, to stress-test your own conviction first
Prompt of the Day
Try this one on your next project plan:
/failuremap [describe your project or commitment]
GPT will predict the most likely failure modes in practice, not in theory. Run it before you spend serious time or money. It won’t prevent every failure: it’ll make the failures less surprising when they arrive.
When you get the output, pay attention to the failure modes that feel uncomfortable to read. Those are the ones worth sitting with. The easy ones to dismiss are usually the ones that actually happen. If the model surfaces something like “you’ll lose momentum three months in when results are slow,” and your first instinct is to skip past it, that’s the signal to stop and build a specific plan for month three before you do anything else.
The One Thing to Remember
Don’t memorize the full list. Pick the 5-10 commands that map to your actual workflow gaps and ignore the rest. The person who built this library, u/Obsessivefrugality, said as much: “some of them are more directed at my particular use cases, so your mileage may vary.”
That’s the honest framing. A command library isn’t a productivity upgrade: it’s a menu. Order what you actually need.
A practical way to build your shortlist: think about the three types of decisions or tasks where you consistently get stuck or make poor calls. Then find two or three commands that directly address each one. If you regularly overcommit to new projects, /antiproject and /sunkcost belong on your list. If you have trouble explaining technical ideas to non-technical people, /eli5 and /reframe should be in your rotation. Match the tool to the recurring problem, not to what sounds most impressive on paper.
The original thread is in r/ChatGPTPromptGenius. Drop a comment there if you have commands worth adding to the list.
Frequently Asked Questions
Q: Should I add these commands to my custom instructions or use them one at a time?
Start with testing them case-by-case to see which ones actually click for your workflow. Once you’ve identified your favorites (usually 5-7), move those to custom instructions for speed. You can always add new ones later or swap them out as your needs change.
Q: Do these “non-official” commands actually work if ChatGPT doesn’t officially recognize them?
They work because they force clarity. The slash notation isn’t magic, it’s a way to signal your intention to both yourself and ChatGPT. When you use /goodenough or /frictionaudit, you’re not accessing a secret mode; you’re shaping how the question gets asked, which directly improves the response. Users report tangible results because naming the intention focuses your thinking.
Q: How do I know which command to use for my specific situation?
The post author suggested testing for your use case since everyone’s needs differ. Start with your biggest pain point: if you overthink, try /goodenough; if you’re stuck starting, try /next10; if you have too many ideas, try /antiproject. Pick 2-3 and test them for a week to see what sticks. The best commands are the ones you’ll actually use repeatedly.
Non official chatgpt commands
by u/Obsessivefrugality in ChatGPTPromptGenius