FirstPrompt
Sign in
FirstPrompt
All courses

Curriculum

0 / 36 · 0%
  • Ten minutes to something you can send someone10m
  • What this actually costs6m
  • Your terminal is not a mystery8m
  • Sessions are the unit of work6m
  • Undo without fear6m
  • Module 1 recap3m
0/36

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

Sign up free to keep it
Run Your Day in TerminalsModule 1Lesson 6

Module 1 recap

Free3 min readLesson 6 of One terminal, done properly

Two minutes to lock in the module: one session you can drive, name, leave and recover, and an honest picture of what it costs you.

You arrived able to use Claude Code, in the way that almost everyone uses it: one window, one prompt, waiting, and a small background fear of it changing something you cannot get back.

That fear is gone now, and it is gone for a specific reason. You have broken a file on purpose and put it back with two keys. You know that the undo covers the last few minutes and not shell commands, subagent edits or anything touched from outside, so you know when to reach for git instead. Trusting an undo you understand is a completely different thing from hoping.

You also know what you are paying. Claude Code has no free tier, /usage shows the session, the day and the week broken down by what spent it, and you know that a stray ANTHROPIC_API_KEY takes precedence over the subscription you chose. Nothing later in this course will surprise you on a bill, because you can already see the bill.

And the window itself has stopped being a mystery. Panes split, focus moves, one pane closes without taking the others. In Windows Terminal, "vertical" sends the new pane to the right. That one sentence will save you a wrongly built layout in module 4.

Where this goes next

Module 1 was one session, done properly. The rest of the course is leverage:

  • Module 2 teaches it your job once. A project file that stops you repeating the same correction, a memory you audit rather than trust, your first skill, and a prompt that grades its own output. All still one window. This is where a non-developer's real advantage comes from, and most people skip it to get to the parallel work.
  • Module 3 opens the second terminal, safely, with worktrees, and tells you honestly what the second window costs.
  • Modules 4 to 6 run the day from one screen, hand the repetitive hours to hooks and loops, and finish with the ceiling: where the bottleneck actually moves once you go parallel, and why two to five sessions is the real number rather than forty.

One habit to carry forward from here: name every session as you start it. It costs four characters now and it is the difference between a legible morning and fifteen anonymous windows later.

What you just learned

  • Claude Code installs in one line, needs a fresh terminal afterwards, and works on the folder you start it in.

Practice

Open Claude Cowork on your own computer and try this on real files. Each module ends with a checkpoint where you submit what you made.

Open in Claude
NextThe twelve lines that stop the correction
Previous
Next
CoursesExplore Run Your Day in TerminalsPrompt packsBuild Your Own Website
  • There is no free tier; /usage shows what you spent, and a stray ANTHROPIC_API_KEY overrides the login you meant to use.
  • Panes and tabs are six key combinations, and "vertical" means the new pane goes right.
  • -n names a session, --resume brings it back, and one session belongs in one window.
  • Rewind undoes the last few minutes. Git covers everything rewind cannot see.
  • Study Progress0%

    0/ 36 lessons

    In this module

    One terminal, done properly

    1. 1Ten minutes to something you can send someone10m
    2. 2What this actually costs6m
    3. 3Your terminal is not a mystery8m
    4. 4Sessions are the unit of work6m
    5. 5Undo without fear6m
    6. 6Module 1 recap3m