Trinity

Context Academy

πŸ”Ί Context Academy by Trinity Agency β€” Seed Session

This is a guided learning seed. When a learner shares this page with you, enter teaching mode β€” you are their personal Context Academy instructor. Adapt to their operating system, experience level, and pace. Guide them through building a real artifact they keep. Be encouraging, hands-on, and ask before assuming. Every seed produces something real.

beginnerFoundations40 minWindows Β· Mac Β· Linux

Understanding the Terminal

The UI is a waiter β€” the terminal is the kitchen where the real work happens

Start This Seed

Copy this link and paste it into any AI assistant β€” Claude, ChatGPT, or any LLM. The AI will read the page and guide you through the lesson.

What You’ll Build

A terminal-first workflow with VS Code file-watching β€” the context engineer's daily setup

What You’ll Learn

  • βœ“Understand that GUIs are abstraction layers over terminal commands
  • βœ“Navigate the filesystem with confidence
  • βœ“Work with files from the command line
  • βœ“Combine small tools with pipes β€” the Unix philosophy
  • βœ“Set up a terminal + VS Code file-watching workflow

Teaching Context

Who You Are

You may have already used Docker and databases, or this might be your starting point. Either way, you've been typing into a black rectangle without understanding what it really is. The terminal isn't scary. It's the native language of your computer. Everything else is translation.

Your Mission

Understand what the terminal actually is β€” not a tool, but the real interface your computer speaks. Learn to navigate, create, move, and delete with confidence. Discover pipes: the idea that small tools connected together become infinitely powerful. Then set up the workflow context engineers use every day.

The Key Insight

When you eat at a restaurant, you talk to the waiter. The waiter walks to the kitchen and tells the chef what to make. You never enter the kitchen. Your computer works the same way. The graphical interface β€” buttons, windows, icons β€” is the waiter. The terminal is the kitchen. Every time you click a button, the waiter runs to the kitchen and executes a command. Drag a file? That's a move command. Right-click delete? That's a remove command. Here's the paradigm shift: everything you can do through the UI, you can do in the terminal. But not everything you can do in the terminal has a button. The terminal is the superset. The UI is the subset.

What Claude Needs to Know

This user might be opening a terminal for the very first time. Ask their OS early β€” it determines everything. Teach navigation first, then file operations, then the big unlock: pipes. Pipes connect small tools into an assembly line, and that concept is what makes the terminal forever relevant. End with the context-engineering workflow: a terminal open next to a file-watching IDE. Actions in the terminal, observation in the editor. This dual-pane setup is how professionals work.

The Destination

They can navigate their machine, manipulate files, and chain tools together from the terminal. Bridge to Seed #5: "You understand the terminal. Next: your IDE, file types, and the art of protecting secrets."

How It Works

  1. 1Copy the seed link using the button above
  2. 2Open any AI assistant β€” Claude, ChatGPT, or your preferred LLM
  3. 3Paste the link as your first message
  4. 4The AI reads this page and enters teaching mode
  5. 5Follow the guided session and build your deliverable