Module 04 · For instructors · Print-ready

Facilitator Guide.

A 60-minute lesson plan for teaching terminal basics with this site as the playground. Read aloud the italicized "Say this" blocks; everything else is for you.

Total time

60 min

Group size

Up to 20

Prereqs

None

Output

12 cmds

What students will leave knowing

What a terminal is, what a shell is, and why they are not the same thing.
How to navigate the file system: pwd, ls, cd.
How to make, read, and remove files and folders.
The convention of command · flags · arguments well enough to read any new command.
How to read an error message instead of fearing it.

Materials

Each student has a laptop with this site open. No installs.
Projector or shared screen for the instructor to model commands.
A whiteboard or shared doc for the "anatomy of a command" sketch.

Before class

Open Concepts on your projector; have Playground in a second tab.
Choose which OS most of your students are on and set the toggle. (Same lessons; commands swap.)
Print the Assessment sheet if you'll use it after.

Part 1 · Mental model 0 – 10 min

Open with a hand-raise.

3 min

Calibrate the room. Reduce intimidation. Set the frame: "terminal is the text-based door to the same files Finder shows."

Hands up if you've ever opened the terminal. Keep them up if you've used it more than ten times. Anyone here who would describe themselves as "comfortable" with it? — OK, lower your hands. The goal for the next hour is to get every hand up on that first question, and a few of you to "more than ten times" by the end.

If most of the room says they've never used it, slow Part 1 down. If most have, speed through and spend the saved time in the playground.

The four layers.

5 min

Establish the You → Terminal → Shell → Kernel → Hardware stack. The mental model carries the rest of the lesson.

Open the Concepts page to Figure 1 (the diagram). Walk through it slowly, in both directions: you type "ls", the keystrokes go to the terminal (which is dumb), then to the shell (which understands), then to the kernel (which does the work). Then the bytes come back the same way.

The terminal is just a window. It shows pixels and forwards your typing. The thing that actually understands what you wrote — that's the shell. On your Mac, the shell is called zsh. On Windows it's PowerShell. They're programs, not magic.

Students often think "terminal" and "shell" are synonyms. Correct it gently every time it comes up. The mental model breaks without this distinction.

Anatomy of a command.

2 min

Give students a parser for every future command they'll see online.

Show Figure 4 (command · flags · arguments) on Concepts. Sketch it on the board. Use ls -la ~/Documents as the example.

Every command has the same shape. A verb, optional adverbs, optional nouns. Once you see the shape, you can read commands you've never seen before.

Part 2 · First commands 10 – 30 min

Have everyone run Lessons 1–2 in the Playground.

12 min

pwd, ls, cd. Build the navigation reflex.

Push students to type, not read. Walk the room. When someone gets stuck, don't tell them the command — ask "what are you trying to find out?" Most stuckness is conceptual, not syntactic.

Many students try to "navigate" by clicking. Catch them gently. The point of this part of the lesson is keyboard fluency. Encourage them to close the cursor on touchpads and tap-to-click.

When a student says "it's not doing anything," 80% of the time they didn't press Enter. Make pressing Enter the joke of the day.

The cd → pwd → ls habit.

5 min

Plant the muscle memory before they need it.

I want you to do something repetitive on purpose. After every cd, run pwd to confirm where you ended up, then ls to see what's there. Three commands, in that order, every time, for the rest of class. It will feel slow. In a week it'll be automatic, and you'll never get lost.

This is the single highest-leverage habit you can give a beginner. Most "I'm lost" panics later in their careers trace back to skipping pwd.

Lesson 3: Making things.

5 min

mkdir, touch. The "look at Finder!" moment.

When students make a folder, have them switch to Finder/Explorer and see it appear. This is the lightbulb. Most beginners genuinely don't believe the terminal is touching the same files until they see it.

You just made a folder. Now switch to Finder. Look at your Desktop. It's there. Read that: it's the same filesystem. The terminal and Finder are two doors into the same building.

Part 3 · Read, write, delete 30 – 50 min

Lessons 4 and 5.

14 min

cat, echo, >, cp, mv, rm.

Let students work through these mostly independently. Float and unblock. The redirect operator > trips people up — be ready to explain it twice.

rm has no Trash. Say this out loud, then say it again. If you're worried, have students do all rm work inside a ~/Desktop/practice/ folder so accidents don't matter. Make the safety rule visible.

The error-reading exercise.

5 min

Replace fear of errors with curiosity about them.

Have students try to break things. Run cd nonsense. Run cat that-file for a file that doesn't exist. Read the error out loud as a group. Identify which layer (shell? kernel?) produced it.

Errors are not the terminal yelling at you. They're the terminal telling you, precisely, what it couldn't do. Read them like signs on a door, not like report cards.

Part 4 · Wrap-up & Recall 50 – 60 min

Run Recall Mode together.

8 min

Surface the gaps. The act of recalling is the act of learning.

Have each student work through Recall on their own laptop. Don't help with answers until they've used at least one hint. The point is to pull from memory, not to score perfectly.

Students will be tempted to peek at the playground or Concepts page. That defeats the purpose. Set a norm: "Recall is closed-book on purpose."

Closing prompt.

2 min

Give them a frame for what to do next.

One assignment between now and next class. Pick anything you'd normally do in Finder or Explorer — moving a file, making a folder, opening something — and do it in the terminal instead. Just once a day. You don't have to be efficient. You have to be a person who has used it.

Common pitfalls cheat sheet

"Nothing's happening." They didn't press Enter. Or they typed into the terminal-app menu, not the terminal window itself.
"It says command not found." Typo, or a flag with a typo, or Mac command on Windows or vice versa. Re-check the OS toggle on this site.
"It says permission denied." The file or folder is protected. Don't have them sudo their way out of it in a beginner class — too much rope. Move to a different file.
"Where did my file go?" They probably rm'd it. Verify, console, and move on. Future lesson: use -i for safety.
"My computer is going to break." Reassure: nothing in this lesson is destructive outside of rm. Repeat that the playground is simulated.
The student who's done in 20 minutes. Point them at Learning Outcomes "Not yet" list. There's always more.

What this guide does not teach

If anyone asks about any of these, the honest answer is "not today, but here are the words you'll want to look up later":

Permissions (chmod, chown, sudo).
Environment variables and shell configuration (.zshrc, $PATH).
SSH and remote work.
Package managers (brew, apt, winget).
Shell scripting beyond simple && chains.
Git. (Use the Git Playground for that.)

Sending students away knowing what they don't know is more valuable than pretending to cover everything.