TemplateA fixed outline for the deliverable: which sections it has, which fields it needs and how long each part can be.SkillA saved set of instructions for one part of a job, which Claude loads when it needs it. Think of it as a playbook page written for the model.HookA check that runs automatically at a set point, for example after Claude writes a section or before a command runs, to make sure the work is right before it moves on. A hook can block the step if something is wrong.HarnessThe program wrapped around the model. It decides what the model can see and what it can touch: which tools it gets, which commands need permission, what runs in a sandbox. Claude Code is a harness. Think of a harness on a horse: it steers and restrains, but the horse still does the walking.SandboxA walled-off space on your computer where some of the agent's commands run, so they can't reach the rest of your files or network.Deny ruleA hard rule in the harness, such as "never read this folder." It's checked before anything else, and the model can't talk its way past it.Auto modeA Claude Code setting where a separate AI checker approves most of the agent's commands, instead of asking a person each time.MCP (Model Context Protocol)A standard way to plug a model into tools and data, like a universal adapter. With MCP, Claude can search, read files or call another system. MCP gives the model access. It doesn't decide the order of the work.HITL (human in the loop)A person checks the AI's work before it moves on or goes out the door. Teams do it because the model's output isn't reliable enough to ship on its own: someone has to catch what's missing and fix what's wrong. It raises quality, but every deliverable still waits on a person, so you don't get the time savings you were promised.HeadlessRunning Claude with no person at the keyboard, on a server or in a container in the cloud.Session and orchestratorA session is one running conversation with Claude. An orchestrator is a session whose job is to start other sessions, hand each one a task and check what comes back.Context window and context engineeringThe context window is everything the model can see on a given call: instructions, examples, files and history. Context engineering is deciding exactly what goes into it, step by step.