firstprompt
Sign in
All courses

curriculum

0 / 40 · 0%
  • Anatomy of a prompt7m
  • The specificity lever6m
  • Context windows and /clear5m
  • Slash commands5m
  • @file and @directory5m
  • Module 2 recap3m
  • Checkpointquiz + ship
0/40

You're reading as a guest — progress saves to this device only.

Dashboard/Module 2/Lesson 4
FreeYour first prompt

Slash commands

5 min read·Lesson 4 of Your first prompt

Listen instead

Slash commands

2:07 · spoken companion to this lesson

0:002:07

Most of what you type to Claude is plain English. A handful of things are not requests at all — they are switches you flip on the session itself. Those start with /.

See them all

Type a single / and a list appears. Or ask for it explicitly:

/help

The list grows over time and depends on your setup, so /help is always the honest source of truth. Below are the ones worth knowing on day one.

The seven that matter

CommandWhat it does
/clearStart a new conversation with empty context
/compactSummarize the conversation to free up room, and keep going
/rewindOpen the undo menu (same as Esc Esc on an empty input)
/helpShow help and the available commands
/modelSwitch which Claude model is active
/initWrite a CLAUDE.md guide so Claude understands this project
/exitLeave Claude

You already know four of them. That is the point — there is not much to learn here.

/init is the one people miss

Run it once in any project you will come back to:

/init

Claude reads through your folder and writes a CLAUDE.md file describing what the project is and how it is organised. From then on, it reads that file at the start of every session in this folder.

The payoff is that you stop re-explaining your own project. In a folder with one HTML file the gain is small. In a real project it is the difference between Claude guessing your conventions and knowing them.

practice

Try this lesson in a guided terminal.

Next

@file and @directory

Open the CLAUDE.md it wrote and read it. If something is wrong, edit it — it is a plain text file, and correcting it is faster than correcting Claude every session.

Switch as needed, not by habit

/model

A picker opens. Bigger models think harder and cost more of your usage; smaller ones are faster. You do not need to touch this while you are learning — the default is chosen sensibly. Know it exists for when a task is genuinely hard and the answer keeps missing.

Slash command or plain English?

A simple test:

  • Changing something about the session? Slash command. /clear, /model, /exit.
  • Asking for work? Plain English. "In index.html, make the heading bigger."

Do not dress up a normal request as a command. There is no /refactor. Just say what you want.

Try it now

Run /init in your project folder, then open the CLAUDE.md it created and read it. Change one line so it describes the project the way you would describe it.

What you just learned

  • / shows every available command; /help is the source of truth.
  • /clear, /compact, /rewind, /init, /model, /help, /exit cover day one.
  • /init writes a CLAUDE.md so you stop re-explaining your project.
  • Slash commands control the session. Work is requested in plain English.

Next: pointing Claude at a specific file with @.

Next

Study Progress

0

0 / 40

lessons

In this module

Your first prompt

  1. 1Anatomy of a prompt7m
  2. 2The specificity lever6m
  3. 3Context windows and /clear5m
  4. 4Slash commands5m
  5. 5@file and @directory5m
  6. 6Module 2 recap3m
Take the checkpoint