Terminal commands every beginner needs — 8 to stop fearing the black window

Here's the thing to understand up front: a vibe-coder doesn't need the terminal to write code. AI writes the code. The terminal is for running it — the AI says "run npm run dev", and all you need is to not freeze in front of the black window.

Eight items cover it. And a small spoiler: the most important one isn't a command at all.

If the very word "terminal" still sounds scary — start with what it actually is, then come back.

1. pwd — where am I?

The terminal always "stands" in some folder, and every command runs there. pwd prints where you are right now. It's the first command when something goes wrong: half of all beginner errors are commands run from the wrong folder.

2. ls — what's in here?

Shows the contents of the current folder. A quick "am I where I think I am" check: you see package.json — you're in the project folder. You don't — see item 3.

3. cd — enter a folder

cd my-project

The main navigation command. cd .. — one level up. Two catches:

• Spaces in names. The terminal reads cd my project as two different folders. Write cd "my project" — in quotes.
• Don't type the full name. Type the first letters and hit Tab — the terminal completes it for you. That's not cheating; everyone does it.

4. mkdir — create a folder

mkdir new-project

Creates a folder without entering it. The everyday combo: mkdir new-project, then cd new-project.

5. npm install and npm run dev — feed it and start it

Strictly speaking these belong to npm, but you'll meet them more often than anything else: the first installs the project's dependencies, the second starts it on localhost. They run only from the project folder — the one holding package.json.

The famous Could not read package.json error doesn't mean "the project is broken." It means "you're in the wrong folder": pwd, ls, cd — and it starts.

6. Ctrl+C — stop what you started

The promised most-important non-command. After npm run dev the terminal "hangs": no response, no new commands. It hasn't hung — it's working: your server lives in it, and lives exactly as long as the window is open.

Ctrl+C politely stops the running process and gives the terminal its voice back. That's how you shut down a server — not by closing the window. Slam the window shut and the process may keep living in the background, so the next launch greets you with the «port already in use» error.

7. Arrow up — repeat without retyping

Press ↑ — the terminal fills in the previous command. Again — the one before it. Your whole history sits under two keys, so "memorizing commands" isn't a thing: type it once — scroll it forever after.

8. clear — tidy the screen

When the screen fills with logs and errors — clear (or Ctrl+L) wipes it. Running processes aren't affected; it's pure hygiene: a fresh error on an empty screen is far easier to read.

Separately: the command not to run

Out on the internet and in AI answers you'll meet rm — file deletion. It has no trash bin: what's deleted is gone. And rm -rf deletes whole folders, silently and irreversibly.

The rule is simple: don't run anything containing rm until you understand exactly what it deletes. Copy-pasting that from an unverified source is the worst beginner habit. In doubt — ask the AI what a command does before running it, not after.

Is Windows the same?

Almost. PowerShell supports pwd, ls, cd, mkdir, and the up arrow; npm and Ctrl+C — even more so. Differences appear in rarer commands, but at this list's level there are none.

Do I need to memorize all this?

No. Tab and the up arrow do half the work, and this list isn't vocabulary to cram — it's a first-week cheat sheet. After that your fingers remember on their own.