Understanding Claude AI, Claude Code, and the vocabulary that comes with them
Claude is a family of large language models (LLMs) built by Anthropic, a safety-focused AI research company. Unlike a search engine that looks up answers, Claude generates responses by predicting what text is most useful given the conversation so far.
At its core, Claude is trained to be helpful, harmless, and honest — a set of values Anthropic calls Constitutional AI. This means Claude tries to give accurate, thoughtful replies while refusing requests that could cause harm.
Claude comes in several tiers, each balancing speed and capability:
You can use Claude through the web at claude.ai, via the API, or embedded in third-party apps. It handles tasks ranging from drafting emails and summarizing documents to writing code, tutoring students, and analyzing data.
claude to start an interactive session.Claude Code is Anthropic's official command-line interface (CLI) that brings Claude's intelligence directly into a developer's terminal and code editor. Instead of switching to a chat window, you interact with Claude from inside your project.
Where the regular Claude chat is a conversation, Claude Code is an agentic coding assistant: it can read your entire codebase, write and modify files, run tests, execute shell commands, and propose pull requests — all in one workflow.
Claude Code is designed around a key principle: you remain in the driver's seat. Every significant action (editing a file, running a command) requires your approval unless you explicitly grant broader permissions. This keeps the human in control of the actual repository.
It integrates natively with popular editors:
A reference glossary for Claude AI and Claude Code vocabulary.
/help, /clear, /review) that trigger built-in or custom skills inside Claude Code without writing a full natural-language prompt.Short phrases placed at the start of a prompt that shape how Claude responds — its role, format, tone, or reasoning approach.
Assigns Claude a specific persona or area of expertise. This shapes vocabulary, depth, and perspective across the entire response.
A single verb that names the task type — summarize, translate, explain, list, compare, critique, draft, debug, etc. — so Claude immediately knows what kind of output to produce.
Specifies the output structure — bullet list, numbered list, markdown table, JSON, CSV, HTML, or plain prose. Especially useful when the result will be pasted into another tool.
Adjusts reading level and register — "for a 10-year-old", "in simple terms", "as an expert", "formally", "conversationally". Keeps the content accessible to the intended reader.
Sets hard limits on length, language, tools, or scope — "in under 50 words", "using only Python", "without technical jargon", "in a single paragraph". Prevents over-explanation and shapes the output's size.
Instructs Claude to reason through a problem before giving a final answer — "think step by step", "reason through this", "show your work". Significantly improves accuracy on math, logic, and multi-step problems.
Provides reference material — code, text, data, or a document — before asking a question. Phrases like "given the following", "based on this", or "using this code" signal that Claude should ground its response in the supplied content.
Asks Claude to evaluate something rather than just describe it — "critique", "improve", "find weaknesses in", "what's missing from". Useful for refining essays, code, plans, or arguments.