Simple explanation
Welcome to Day 10. Inside every Claude Code session there is a shortcut menu that most non-developers never discover. Today you find it and start using it. What are slash commands? Slash commands are shortcuts you type with a forward slash. Instead of typing a long instruction — you type one short command and Claude Code knows exactly what to do. Think of them like keyboard shortcuts but for AI instructions. How to see all available commands Inside any Claude Code session — type: /help Press Enter. Claude Code shows you every available command. The 6 slash commands every non-developer should know: /help — Shows everything Claude Code can do. Use this whenever you are stuck or want to explore. /clear — Clears the current conversation and starts fresh — but keeps your CLAUDE.md memory intact. Use this when a session gets too long or goes in the wrong direction. /compact — Summarises the conversation so far and keeps going. Use this in long sessions to stop Claude Code getting confused by too much history. Add details: "/compact keep the file names and the last error message" for better summaries. /plan — Switches to Plan Mode instantly — same as pressing Shift + Tab twice. Useful when you are mid-session and want to plan the next step before executing. /model — Switches between Claude models. Use Sonnet for everyday tasks — faster and cheaper. Switch to Opus for complex problems that need deeper thinking. /review — Asks Claude Code to review everything it just built and check for obvious problems. Run this after any Auto Mode session before you look at the result yourself.
What to do
The power move: /compact in long sessions When a session runs long — Claude Code starts to lose track of earlier decisions. Type /compact with specific instructions about what to remember: "/compact keep the color codes, the file structure, and the last three changes we made" Claude Code summarises everything important and continues with a clear head. This single command prevents the most common source of mistakes in long sessions. Today's practical task 1. Open a Claude Code session. 2. Type /help and read through what is available. 3. Ask Claude Code to make three small changes to your homepage — one at a time. 4. After the third change — type /compact and tell it what to remember. 5. Make one more change and check that it still remembers your project context. 6. Finally, type /review and ask Claude Code to check the changes for obvious problems. Get familiar with these shortcuts now. They become second nature quickly — and they save a meaningful amount of time every single week.
Copy-paste prompt
/compact Please summarise this session. Keep: the exact file names we changed, the color codes used, the current state of the homepage, and the last problem we solved. Forget everything else. Confirm what you have remembered before continuing.
Course note
Key takeaway
Type /help to see every available shortcut. Use /compact in long sessions to keep Claude Code focused. Use /review after any Auto Mode build to catch problems before you do. These three alone save hours every week.