Most developers discover Claude Code slash commands the same way: they type a forward slash, see an autocomplete menu, learn that /help and /clear exist, and then plateau. They keep using two or three commands while the rest of the menu sits unused. If that sounds familiar, this guide is for you. The goal here is not to list every command (that is what a reference is for), but to give you a repeatable method to learn Claude Code slash commands until reaching for the right one is automatic. AI Drops is an independent project and is not affiliated with Anthropic.
Claude Code is Anthropic's agentic coding tool, and its slash commands are how you steer a session without leaving the prompt: clearing context, switching models, kicking off project setup, or running workflows you defined yourself. Fluency pays off quickly, because the commands you never learned are usually the ones that would save you the most time. Below is a learning system built on three ideas: use them daily, group them by the task you are doing, and use spaced repetition to make them stick.
Why learning slash commands is worth it
A coding session has state: a growing context window, a selected model, a working directory, and the task in front of you. Slash commands give you precise, low-friction control over that state. When you only know a couple of them, you pay a hidden tax: you re-type boilerplate, you let stale context pile up, and you run the wrong model for the job. Learning the full set turns those frictions into one or two keystrokes. The hard part is not difficulty (each command is simple) but recall: knowing the right command exists at the exact moment you need it.
That recall problem is exactly what a deliberate learning method solves. You do not need to study the commands like an exam. You need to encounter them often enough, in the right context, that the right one surfaces on its own. The three habits below do that.
Habit 1: Use them every day, on purpose
The fastest way to learn Claude code slash commands is to force a few new ones into your daily flow. Pick one command you do not currently use, write it on a sticky note, and use it deliberately for a week. When you switch tasks, reach for the context command instead of scrolling. When a refactor gets gnarly, switch models on purpose. Repetition in real work beats reading a list, because each use ties the command to a situation you will recognize again.
- Each morning, pick one command from the menu you have never used.
- Find a real moment in the day where it applies, and use it there.
- Notice what it did and when it was useful, so the trigger sticks.
- Repeat the next day with a new command, keeping last week's in rotation.
Habit 2: Group commands by the task you are doing
Memory works better when items are organized by when you would reach for them, not alphabetically. Instead of a flat list, group Claude Code's commands into a handful of task buckets. When you think "I need to refocus the model," your brain jumps to the context bucket; when you think "this needs a stronger model," it jumps to the model bucket. The table below is a starting taxonomy. The exact command names and arguments belong in the official Claude Code docs, since they evolve between releases, but the categories are stable.
| Task bucket | When you reach for it | What it does for you |
|---|---|---|
| Context | Switching between unrelated tasks, or a session getting long | Clear or compact the conversation to refocus the model and save tokens |
| Model | A task gets harder or easier than the current model suits | Switch Claude models (and effort levels) mid-session to match difficulty |
| Project | Starting work in a new or unfamiliar repository | Initialize a CLAUDE.md so future sessions begin with shared context |
| Review | Before committing or opening a pull request | Inspect and review changes without leaving the prompt |
| Meta | You are unsure what is available or how billing works | Help, config, permissions, login, and usage or cost inspection |
| Custom | A workflow you run again and again | Your own commands in .claude/commands or as skills |
Once you can name the buckets from memory, the individual commands inside each one are much easier to retain. For the full breakdown of built-ins and how to write your own custom commands, read our companion explainer, Claude Code Slash Commands: A Practical Guide. Use it as the reference; use this article as the method.
Habit 3: Use spaced repetition to make them stick
Daily use covers the commands you happen to need often. Spaced repetition covers the rest: the powerful ones you reach for rarely, which are precisely the ones you forget. The principle is simple. Review an item just before you would forget it, and each correct recall pushes the next review further out. A command you know cold shows up monthly; one you keep missing shows up tomorrow. Over a couple of weeks, the whole set moves into long-term memory with only a few minutes of review per day.
You can do this by hand with paper flashcards (command on one side, what it does and when to use it on the other), but the fastest path is a purpose-built app. /cards for Claude Code is a flashcards app that drills the slash commands (and other Claude Code concepts) with spaced repetition, so you study a couple of minutes a day and the recall comes for free in your editor. Think of it as the learning companion to release tracking: Claude Drops keeps you current on what ships, while /cards for Claude Code on the App Store makes sure you actually remember what you learn.
A two-week plan to fluency
If you want a concrete schedule, here is one that combines all three habits. It assumes a few minutes of review plus deliberate use during real work.
- Days 1 to 3: Learn the menu and the help command. Memorize the six task buckets above, not individual commands yet.
- Days 4 to 7: Add one new command per day from the context and model buckets, using each in real work the day you learn it.
- Days 8 to 11: Move to review and meta commands. Start a daily spaced-repetition review of everything so far.
- Days 12 to 14: Write your first one or two custom commands for workflows you repeat, then add them to your review deck.
For a printable companion to study from, our Claude Code slash commands cheat sheet lays the categories out at a glance. And if you want the broader philosophy of getting good at the tool, see the best way to learn Claude Code.
Stay current as commands change
Claude Code's command set keeps expanding, so fluency is a moving target: a command you mastered may gain new arguments, and entirely new ones appear. Two practices keep you ahead. First, watch what ships: browse the Claude Code changelog, or get Claude Drops (on the App Store) for a push notification the moment a new release lands. Second, keep studying what you track: add each new command to /cards for Claude Code so spaced repetition does the remembering for you. For exact, current syntax, the official Claude Code documentation is always the source of truth.
Bottom line: you learn Claude Code slash commands by using them daily, grouping them by task, and reviewing them with spaced repetition. Track releases with Claude Drops, drill the commands with /cards, and lean on the official docs for precise syntax. A couple of weeks of light, deliberate practice is all it takes to make the whole menu second nature.
Sources
Maintainer, Claude Drops
Ian builds Claude Drops and reads every Claude Code release so you don't have to. He writes plain-English guides to Claude Code's features, drawing directly from the official changelog and documentation.