E1 · Two commands
10 minIn a session for one of your projects, type /output-style and choose concise. Work for a bit, then type /recap.
Done when: The replies got shorter, and /recap gave you a one-line summary of what you did.
Lesson 7 · 16 min
Customize: slash commands, mods, and your routine
Five short commands change how Claude works: undo, see what’s taking up space in the conversation, summarize, work toward a goal, and give shorter answers. Mods change how Claude Code looks, but you should check them first. At the end, Carla picks three new things from the course and writes her routine for the week. You’ll make yours.
Start the lesson
In this lesson, you’ll
- 1The 5 slash commands that help the most
- 2What a mod does and what it can access
- 3Check a mod before installing
- 4Write your routine with 3 new things
Goal: Adjust Claude with slash commands and mods, then build your routine with the new things you learned.
01Your toolbox
Tap or click each part. A routine is what turns a tool into a habit.
Scroll down: each step below lights up its part of the diagram.
- 1/5
Slash
A slash command is a shortcut that starts with / and changes how Claude works in that session. Type / in the message box and choose from the list. No coding needed.
- 2/5
Mods
A mod is a type of plugin (add-on), which is why its menu is called /plugin. It changes how Claude Code looks and behaves: a bar showing how much of the conversation you’ve used, an alert when something finishes, or a new command. It appears in the app’s Code tab (and also in the terminal and VS Code, a code editor).
- 3/5
Check
A mod doesn’t run on its own: it can access whatever Claude Code can, including your files. So before installing, ask Claude to check what the mod does. If something goes wrong later, ask Claude to turn off the mod or use the /plugin menu. This part is optional and more technical.
- 4/5
Your weekly
No one uses thirteen new things all at once. Pick three, say what day or when you’ll use each one, and why. A week from now, replace the one that didn’t stick.
- 5/5
Turn a tool into a habit
Commands for everyday use, mods only after checking them, and a short routine with three new things.
Commands adjust the session; mods adjust Claude Code; your routine decides what you actually use.
02The 5 commands, with Carla’s example
Type / in the message box (in the app’s Code tab) and choose from the list. If a command doesn’t appear, update the app and check again. If it still doesn’t appear, ask Claude: "how do I use /recap in this app?". In the terminal (optional), they work the same way.
1. /rewind
Takes the conversation back to before a bad answer, as if it never happened. The shortcut is to press Esc twice.
Better than arguing with Claude: go back and ask in a different way. It rewinds the conversation; if the bad answer already changed a file, ask Claude to check the file.
Carla
She asked only for the title of lesson 1, and Claude replied with the whole lesson. /rewind, then a new, clearer request.
2. /context
Context is everything Claude is considering in this conversation: history, files it has read, and instructions. /context shows a color-coded chart of how much space each part takes up.
A full conversation gets slower and uses more of your limit.
Carla
She saw that three old scripts were taking up a lot of space, so she started a new session for lesson 2.
3. /recap
Gives you a one-line summary of the session right away. Useful when you come back from lunch and can’t remember where you left off.
After a few exchanges, Claude also makes this summary on its own.
4. /goal
Give Claude a clear goal, and it keeps working until it reaches it. A clear goal can be measured: "5 exercises, each with an answer," not "good exercises."
Without a measure, it doesn’t know when to stop.
5. /output-style
Changes how the responses are written. Choose concise for shorter, more direct answers.
Good for everyday use; switch back to the default style when you want a longer explanation.
03Carla’s commands on a work morning
One at a time, in the course folder’s session.
Short answers and a recap
/output-style concise /recap
A measurable goal
/goal Create curso-planilhas/aula-2/exercicios.md with 5 VLOOKUP exercises, each with a sample spreadsheet and the correct answer.
See what’s taking up the conversation
/context
Simulation: illustrative example
Lesson 2 outline (VLOOKUP) written and approved; the exercises are still missing.
- Created curso-planilhas/aula-2/exercicios.md.
- 5 exercises, each with a sample spreadsheet and an answer.
- Checked all 5 answers by applying the formula to the sample spreadsheets.
Goal reached.
- /goal without a measure ("make good exercises"): Claude doesn’t know when it’s done.
- Argue instead of going back: after a bad answer, use /rewind and ask in a different way.
04Mods: check before installing (optional, more technical)
You can skip this if you just want to use the app as it is. Ready-to-use examples: 18 mods in Portuguese, tested, in the inematds/inema-mods repository on GitHub. GitHub is a site where people store and share code; a repository is a project folder there.
1. Update
Mods require Claude Code version 2.1.287 or later. In the app, just keep it up to date; in the terminal (optional), claude --version shows the number.
Older version: the mod won’t appear, and it’s not a problem with the mod.
2. Ask for a check
Mods aren’t isolated: they can read your files and run commands, just like Claude Code. So have Claude check first: it runs a check command (claude plugin validate) in the mod’s folder.
This check shows when the mod acts on its own (the hooks) and what it asks to use. You don’t need to understand the command: the prompt below asks for a summary in plain language.
No terminal
In the app’s Code tab, paste the prompt below: Claude will run the check itself.
3. Install or decline
Read the plain-language summary: what it reads, what it runs, and whether it uses the internet. Unsure? Don’t install it.
To install or turn off mods, type /plugin in the message box and use the menu that opens. The change takes effect when you close the menu.
4. Emergency exit
If Claude starts acting strangely after you add a mod, ask in that session: "turn off the mod [name]" or "uninstall the mod [name]". Or type /plugin in the message box and turn off the mod in the menu; it takes effect when you close the menu.
For terminal users only (optional): claude --safe-mode opens Claude Code without any customizations if it won’t open properly.
05Carla’s prompt: check a mod (optional)
Paste this into a session in the Code tab or terminal. Replace the link with the link to the mod you want.
Check before installing
I want to check a mod before installing it: <link to the mod on GitHub> Examples of mods: https://github.com/inematds/inema-mods Download it to a separate folder and run claude plugin validate there. Explain it in up to 5 lines, without technical terms: - when it acts (hooks) - whether it reads my files, runs commands, or uses the internet - how to turn it off later Don’t install anything until I reply YES.
If something goes wrong · ask Claude
Turn off the mod <mod name> and tell me what the list of enabled mods looks like.
Terminal (optional) · if Claude Code won’t open properly
claude --safe-mode
Simulation: illustrative example
What this mod does: shows a bar in the footer with how much of the conversation has been used.
- When it acts: after each response, to update the bar.
- Files: doesn’t read your work files.
- Commands and internet: doesn’t run external commands or use the internet.
- Turn it off: /plugin → disable.
Validation passed without errors. Should I install it? Reply YES.
- The mod asks to use the internet without a clear reason.
- It reads folders outside the project.
- Claude can’t explain what a section of code does.
If any of these apply, don’t install it.
06Check your routine
Write 3 numbered lines: new thing | when you use it | what for. The page checks whether each line mentions something new from the course and a day or time, and whether the 3 new things are different. This is a format check: you decide whether the routine works for you.
rotina.md
07Practice: your toolbox
You can manage commands and routines in the app. Checking a mod (E2) is optional and more technical.
E2 · One checked mod (optional)
15 minChoose a mod from inematds/inema-mods and paste Carla’s prompt with its link. Read the summary before replying.
Done when: You have, in up to 5 lines and in simple words, what the mod can access and how to turn it off; installing it or not is your choice.
E3 · Your routine
10 minChoose 3 course features you’ll use and write one line for each: feature | when you’ll use it | what for. Paste them into the checker above and save as rotina.md: the checker’s "Download file" button saves the ready-to-use file. Or ask Claude, in the Code tab: "create rotina.md in the project folder with this text" and paste in your routine.
Done when: rotina.md is saved, and the checker replies "OK: routine with 3 features, each with a day or time".
08Test what you learned
The explanation appears after your answer.
Question 1 of 5
Claude gave you a bad answer, and you want to ask another way as if it hadn’t happened. What’s the fastest way?
Correct
/rewind takes the conversation back to before the bad answer, so you can ask again. Discussing it fills up the conversation and doesn’t always fix things; /recap only summarizes.Not this one
/rewind takes the conversation back to before the bad answer, so you can ask again. Discussing it fills up the conversation and doesn’t always fix things; /recap only summarizes.Review: The 5 commands, with Carla’s exampleQuestion 2 of 5
Why ask Claude to check a mod before installing it?
Correct
Mods run without isolation: they can read files and run commands. claude plugin validate shows which events a mod acts on and what it requests.Not this one
Mods run without isolation: they can read files and run commands. claude plugin validate shows which events a mod acts on and what it requests.Review: The 5 commands, with Carla’s exampleQuestion 3 of 5
Which of these is a good /goal?
Correct
A clear goal is measurable: it says how many and what each item needs to include. "Good" or "improve" doesn’t tell you when to stop.Not this one
A clear goal is measurable: it says how many and what each item needs to include. "Good" or "improve" doesn’t tell you when to stop.Review: Carla’s commands on a work morningQuestion 4 of 5
You installed a mod, and Claude Code started acting strangely. What should you do first?
Correct
Turning off the mod fixes things without losing anything: ask Claude or use the /plugin menu (this also works when you close the menu). If you use the terminal, you can also run claude --safe-mode to start without customizations.Not this one
Turning off the mod fixes things without losing anything: ask Claude or use the /plugin menu (this also works when you close the menu). If you use the terminal, you can also run claude --safe-mode to start without customizations.Review: The 5 commands, with Carla’s exampleQuestion 5 of 5
Which of these is a good routine?
Correct
One new thing, a clear moment, and a reason. “All the new things” and “whenever I can” don’t become habits.Not this one
One new thing, a clear moment, and a reason. “All the new things” and “whenever I can” don’t become habits.Review: Check your routineTest complete
You got {a} out of {n} right. Get them all right to mark the lesson as complete.Choose an option. The explanation appears after your attempt.
09The lesson in three sentences
Slash/rewind goes back, /context shows what’s taking up space, /recap summarizes, /goal pursues the goal, /output-style shortens.
ModsThey change how Claude Code looks, without isolation: ask Claude to check first and, if it goes wrong, to turn it off (or use /plugin). Optional.
RoutineThree new things, each with a day or moment and a reason, saved in rotina.md.