Michael Gardon · CHIEF AI Accelerator
Accelerator / Curriculum / Reference
Reference Sheet

AI Vocab Reference Across LLMs

Every major AI system has the same core functionality, but each one calls it something different. This guide matches them up, so you can find the equivalent feature in whatever tool you actually use.

Pre-read · Module 1
Tools Covered

Four systems, one set of ideas

ClaudeAnthropic
ChatGPTOpenAI
M365 CoPilotMicrosoft 365
GeminiGoogle
A note on CoPilot

"CoPilot" is a family. This sheet means M365 CoPilot — the chat surface inside Word, Excel, Outlook, and Teams, the one most execs encounter at work — unless flagged. Copilot Studio is the separate agent-building product, called out where relevant.

Ring 1

Tool concepts

The conversation surface

ConceptClaudeChatGPTM365 CoPilotGemini
A single conversationChatChatChatChat
A new threadNew chatNew chatNew chatNew chat
Underlying model selectorModel dropdown (Sonnet / Opus / Haiku)Model dropdown (GPT-5, etc.)Mostly hidden; "Smart" vs "Quick"Model dropdown (Pro, Flash)
Web access"Web search" tool toggle"Web" toggleBuilt-in (BizChat / Work mode)Built-in

Telling it who to be / how to behave

ConceptClaudeChatGPTM365 CoPilotGemini
Persistent "about me / how to respond"Settings → Profile → "What should Claude call you" + traitsSettings → Personalization → Custom InstructionsLimited; partial via "personalization" settings"Saved info" / personalization
One-off role for this chatJust write it in the promptJust write it in the promptJust write it in the promptJust write it in the prompt
API-level system prompt"system" parameter"system" roleN/A for end users"system_instruction"
Watchout

"Custom Instructions" in ChatGPT and "Profile traits" in Claude do similar things but apply differently. ChatGPT's are global. Claude's profile is global; Project instructions override per-project. M365 CoPilot has the weakest per-user personalization.

Ring 2

Collaborator concepts

Grouping work + giving it context

ConceptClaudeChatGPTM365 CoPilotGemini
A folder for related chats + files + instructionsProjectsProjectsPages + grounded sourcesGems (closest, but lighter)
Upload reference filesDrag into Project or chatDrag into Project or chatReference files via @mention or attachAdd files in Gems / attach
Auto-grounding in your company dataNo (must upload)No (must upload)Yes — M365 graph (SharePoint, OneDrive, email, Teams, calendar)Workspace grounding (Drive, Gmail, Calendar) — varies by edition
The biggest asymmetry in the sheet

M365 CoPilot's killer feature is auto-grounding in your company data. Claude and ChatGPT require explicit uploads. Gemini sits in between. For CoPilot users, knowledge-library work happens in M365 itself — folder structure, naming, permissions. For Claude/ChatGPT users, it's about uploading and structuring files into Projects.

Encoding a reusable workflow — Ring 2's core skill

ConceptClaudeChatGPTM365 CoPilotGemini
A reusable "do this kind of work this way"Claude SkillsCustom GPTsAgents (Copilot Studio) or simpler PromptsGems
Lightweight reusable promptProject-level instructionsCustom GPT descriptionPrompt library / saved promptsGem
Sharing with teamSkill share (org or public)GPT shared via link or workspaceAgent shared via M365 adminGem shared in workspace
Vocabulary alert

This is the row most likely to cause confusion. Teach "build a skill" and a CoPilot exec will hunt for a button labeled "skill" and find nothing. Translation: in CoPilot the same idea is an Agent (heavier, built in Copilot Studio) or a saved Prompt (lighter). Most execs only need the lighter version to start.

Style / voice

ConceptClaudeChatGPTM365 CoPilotGemini
Reusable voice / toneStyles (chat-level)Style baked into Custom GPT or Custom InstructionsTone presets per taskBuilt into a Gem
Ring 3

Delegate concepts

This whole ring is the most volatile vocabulary. The principle — trust calibration, bounded delegation, verification — is stable. The buttons move every six months.

Running on a schedule

ConceptClaudeChatGPTM365 CoPilotGemini
Recurring scheduled taskScheduled Tasks (Claude Code / Cowork)Tasks (in ChatGPT)Power Automate flows triggered by CopilotScheduled actions (limited)

Letting it take actions in other systems

ConceptClaudeChatGPTM365 CoPilotGemini
Connect to external systemsMCP servers (Model Context Protocol)Actions in Custom GPTs; ConnectorsConnectors + Power AutomateExtensions + Workspace apps
Built-in tool catalogMCP marketplaceGPT Store actions / AppsM365 admin connectorsExtensions
Watchout

MCP (Anthropic-led, now adopted broadly) is becoming the cross-vendor standard for tool connection. Worth knowing the term even if not every exec's tool uses it yet.

Memory across sessions

ConceptClaudeChatGPTM365 CoPilotGemini
Persistent memory across chatsLimited (Project-scoped)Memory (global, user-controlled)Personalization signals from M365 graphSaved info / personalization
Watchout

ChatGPT's Memory is the most aggressive at remembering — users should know they can view and delete it. Claude is more conservative by design. CoPilot's "memory" is your M365 activity, not stored conversational memory.

Autonomous multi-step agents

ConceptClaudeChatGPTM365 CoPilotGemini
Agent that plans + executes a multi-step taskClaude Agents (Sonnet w/ tools), Skills with tools, Claude CodeGPT Agents (formerly Operator-style), Custom GPTs w/ ActionsCopilot Studio Agents, Researcher / Analyst agentsProject Mariner, Gemini agents (research, deep research)
The Constant

The principles that don't change

Regardless of tool, these stay true. This is what the curriculum actually teaches.

01 · The 4 C's

Context, Charge, Constraints, Cut. Durable. Every model rewards specificity in these four dimensions.

02 · The Chief of Staff frame

Durable. AI is a relationship, not a feature.

03 · The Three Rings

Tool → Collaborator → Delegate. Durable. Every tool maps to these.

04 · Encoding your judgment

Durable. The artifact's name changes — Skill / GPT / Agent / Gem — but the practice is the same.

05 · Trust calibration

Durable. Every automation needs verification regardless of platform.

How To Use This Sheet

Recognition, not recall

  • Distribute as a pre-read before Module 1. Identify which column is yours.
  • Reference during drills. When the lesson says "encode a workflow," point to the relevant row.
  • Expect a half-life. This sheet gets updated quarterly. The buttons move; the principles don't.
  • Don't memorize. The point is recognition, not recall. You look it up.