Loading lesson…
Slash commands are the keyboard shortcuts of Claude Code. The built-ins handle plumbing; the custom ones are where teams encode their workflows.
Slash commands are special inputs starting with / that trigger meta-actions instead of going to the model. They control session state (`/clear`, `/compact`), surface help (`/help`), and let teams define custom workflows that anyone can run by name.
| Command | What it does | When to use |
|---|---|---|
| /clear | Resets session context | Starting unrelated work |
| /compact | Summarizes the session, replaces context with summary | Long session, context filling up |
| /init | Creates a starter CLAUDE.md | First time in a project |
| /help | Lists available commands | Forgot a name |
| /status | Shows current session state | Sanity check |
Custom commands let your team encode 'the way we do X' as a runnable name. They live in your project (typically under a `.claude/` folder) and become available as `/name`. Anyone with the repo gets the workflow for free.
The big idea: slash commands turn 'how we work' into a one-keystroke entry point. Master /compact, then build the few customs your team actually runs.
8 questions · take it digitally for instant feedback at tendril.neural-forge.io/learn/quiz/end-claude-code-slash-commands-creators
What is the main idea of "Slash Commands: Built-Ins And Custom"?
Which concept is most central to "Slash Commands: Built-Ins And Custom"?
Which use of AI fits this topic best?
What should a careful learner remember about "/compact is the daily move"?
You want to use AI after this lesson. What is the safest next step?
How should AI output about slash command be treated?
Name one way to verify an AI answer about slash command.
Which action would help you apply "Slash Commands: Built-Ins And Custom" responsibly?