Terminal 101, for Designers
I've been noticing something in my conversations with product designers about transitioning to AI tools: an aversion to the terminal. Folks who never coded, or are a bit foreign to the development process (totally understandable, plenty of us are), find its lack of a simple UI and its special syntax threatening.
What I try to explain to them is this: you'll barely use the actual terminal. Day to day it's mostly a gateway, the door you open to get to Claude. Once Claude is running, you're just talking to a chatbot that happens to be dressed like a terminal. Think of it as a chatbot with Game Boy graphics, which honestly makes it kind of charming. The terminal itself is for the occasional computer-wide install, or a command Claude asks you to run, and if you're ever unsure, ask Claude and it'll walk you through it.
So before you install anything (that's the next post), let me hand you the two ideas that make the terminal make sense.
It's a conversation: The terminal is a text box that talks back. You type a command, hit return, the computer answers, and then it waits for your next one. That's the entire interaction model. Kinda like LLMs. We all spent the last few years learning to type instructions into a box and read the response. The terminal was prompting before prompting was cool. It's like that band from Williamsburg, Brooklyn that was using an electric bagpipe before anyone knew what Williamsburg was.
You're always standing somewhere. A terminal window is always inside a folder, the same folders you see in Finder. Type ls (list) and it tells you what's around you. Type cd Documents (change directory) and you walk into your Documents folder. Type cd .. and you step back out. It's Finder without the pictures. Or, closer to the truth, it's a text adventure game: you are in a folder called Desktop. You see 14 files.
This matters because commands do their thing wherever you're standing. It's the first thing that trips everyone up, and it's also the key to everything later: when you run Claude Code inside a folder, that folder becomes its workspace. Where you stand is what it sees.
That's it. Conversation plus location. Put those together and you realize the terminal is basically an old school LLM. The same type-and-it-answers loop, except instead of natural language it demands a special syntax, and instead of inferring your context it has to be told exactly where you're standing. The world's most pedantic chatbot. Everything else is vocabulary, and here's the thing: you barely need any of it.
Once Claude is in there, it'll handle most of the vocabulary for you. And for the little typing you still do yourself, the terminal meets you halfway, in three ways it doesn't advertise.
It finishes your words. Start typing a folder name and press tab: the terminal completes it for you. Type cd Des, hit tab, and it becomes cd Desktop/. Half the typos you're worried about making, you'll never get to make.
It remembers what you typed. Press the up arrow and your last command reappears, ready to run again. Press it again and you walk further back in time. Nobody in the history of terminals has typed the same command twice; they just press up.
You can drag things into it. This one surprises everyone: drag a folder from Finder onto the terminal window and it types that folder's path for you. If spelling out the path to something deeply buried feels like a hike, type cd (with the space), drag the folder in, and hit return. You're there.
That's the whole tour. A conversation, a location, and a machine that finishes your words. The next step is giving it something worth talking to: in the next post we install Claude Code. One copy-paste, five minutes.