AnyCompany Support Workshop · Take-Home Reference

Glossary & Cheat Sheet

Plain-English definitions and the commands worth committing to muscle memory. Keep this open while you work — most friction comes from not knowing a shortcut already exists.

← Back to workshop home

📖Glossary

Plain-English definitions for the technical terms you'll hear in this workshop. Knowing these also helps when you talk to your IT or engineering team — you'll speak their language.

🔎
API
A way for two software systems to talk to each other. When Claude connects to Jira or Slack, it uses their APIs — like a universal adapter between apps.
Claude Code
Anthropic's AI assistant that runs in the terminal. Unlike the Claude website, Claude Code can read and edit files, run commands, and take actions on your computer.
Claude Cowork
The browser-based Claude environment used in this workshop. Same Claude, but with a built-in code editor, file explorer, terminal, and preview panel — nothing to install.
Code Editor (VS Code)
The editor that lives inside Claude Cowork. It looks like a text editor but has a built-in terminal, file explorer, and preview panel.
Directory
Another word for folder. cd (change directory) is how you navigate between them in the terminal.
Docker
Software that runs applications in self-contained boxes called containers. You don't need Docker for this workshop — it only comes up if you ask Claude to containerise a script during the Day 1 vibe-coding lab.
Git
A tool that tracks every change ever made to a set of files — like Google Docs version history, but for any type of file.
GitHub / GitLab / Bitbucket
Websites where teams store and share their Git repositories. Different companies use different platforms — they all do the same job.
Hook
A shell command that runs automatically at a defined point in Claude's lifecycle — for example, after a file is edited or before a tool is used. Analogy: a doorbell. Something arrives, an action starts.
IDE (Integrated Development Environment)
A software application that helps people write code — like VS Code. Think of it as Microsoft Word, but for writing programs instead of documents.
Markdown
A lightweight formatting language that uses simple symbols (# for headings, **bold**, - for bullets). Claude outputs Markdown naturally, and VS Code can preview it as a formatted document.
MCP (Model Context Protocol)
An open standard that lets Claude connect to external tools like Jira, Slack, or Notion. Analogy: kitchen equipment — the skill is the recipe, MCP is the oven and fridge that let Claude actually cook.
MCP server
A small program that translates between Claude and a specific tool's API. Like a human interpreter in a meeting — Claude talks to the server, the server talks to the app.
Node.js
A runtime that lets JavaScript run outside of a browser — often used for web servers and tools. When you see node or npm in a command, Node.js is involved.
npm
A tool that installs software packages for JavaScript / Node.js programs. When you see npm install, it's just downloading the dependencies a program needs to run.
Path
The address of a file or folder on your computer. For example: /workshop/sample-files/lab-2/meeting-transcript.txt.
Plugin
A self-contained bundle of components (skills, agents, hooks, MCP servers) that extends Claude Code. Shared across projects and teams.
Python
A popular programming language used for data analysis, automation, and AI. Claude Code can write and run Python scripts on your behalf — you don't need to know Python to benefit from it.
Repository (repo)
A folder tracked by Git. Contains all the files for a project plus the full history of every change ever made.
Skill
A reusable instruction set that teaches Claude how to perform a specific task. Analogy: a recipe card. Skills live in SKILL.md files and are triggered by name or description.
Steering
Persistent house rules that apply to every Claude conversation in a workspace — tone, conventions, constraints. Stored as Markdown so your whole team uses the same defaults. Analogy: house rules for every guest.
Terminal
A text-based window where you type commands. In this workshop, the terminal is inside the Code Editor (bottom panel).
VS Code
Short for Visual Studio Code — a popular code editor made by Microsoft. This workshop uses a browser-based version (inside Claude Cowork) so nothing needs to be installed.

🛑Stop or Interrupt

Something running away from you? These are your emergency brakes.

KeyWhat it does
Esc Interrupt Claude mid-response — stops it immediately so you can type again. The conversation is preserved.
Ctrl + C Cancel whatever you're typing, or exit Claude when the prompt is empty. Also the universal "stop" for terminal commands.

🌀When Claude Is Stuck or Looping

Claude sometimes gets stuck trying to fix a small detail, or loops on the same step for several minutes. You don't need to wait it out.

SituationWhat to do
Claude is taking too long on a minor detail Press Esc, then redirect — "That's good enough, skip the rest."
Claude keeps retrying the same failing step Press Esc, then redirect — "Stop, try a completely different approach."
The conversation feels tangled or off-track Type /clear to start fresh — your files are kept, only the conversation resets.
You just installed a new Skill, plugin, or MCP server and it isn't showing up Run /reload-plugins, or exit and restart Claude with /exit then claude.
💡
Pro tip: If a Skill or plugin still won't load after /reload-plugins, the file might be in the wrong folder. Ask a facilitator to check the path.

⚡Claude Slash Commands

The commands you'll reach for most often. Type / on an empty prompt to see every command available in your setup, including custom skills.

CommandWhat it does
/clearStart a fresh conversation without losing any of your files — the safest reset.
/exitExit Claude Code and return to the terminal prompt.
/resumeResume a previous conversation from within Claude Code.
/renameRename the current conversation to something memorable (makes /resume easier later).
/reload-pluginsReload Skills and plugins — use this if a newly installed Skill isn't showing up.
📌
Slash commands are local. They control your Claude session — they're never sent to the model and don't use any tokens. Type /help any time for the full list in your environment.

💻Terminal Commands

You don't need to memorise these — but knowing them makes you feel like a pro.

CommandWhat it doesExample
pwdShow your current folder location/workshop
lsList files and folders in the current directory—
cd folder-nameMove into a foldercd sample-files
cd ..Go up one folder levelcd ..
cd ~Go to your home foldercd ~
cat filenamePrint the contents of a filecat meeting-notes.md
clearClear the terminal screen—

🔧If Something Goes Wrong

Don't panic — everything here has an easy fix.

What you seeFix
command not found Typo — copy the command directly from the workshop using the copy button.
Permission denied Try from your home folder (cd ~). Ask a facilitator if it persists.
No such file or directory Wrong path — check spelling, or ask Claude: "What files are available in the sample-files folder?"
Claude keeps asking questions Answer in plain English, or say "Use your best judgement and proceed."
🛟
Still stuck? Raise your hand. Every facilitator in the room has seen the error before. The workshop is designed so no single bug should block your progress.
🔒
Reminder: Never paste real customer data, PII, or production credentials into Claude during this workshop. All sample data provided is synthetic.
AnyCompany Support Workshop · 2-Day Generative & Agentic AI · ← Back to home