Skip to main content
AI Models Made Useful
Context-first map Updated July 10, 2026

Advanced AI Onboarding

A practical map for choosing the right AI surface by first asking where the context lives, what the AI can access, and whether it should only answer or actually act.

The first mental model

Context

Where the useful files, notes, messages, source packets, or repos already live.

Access

Which app can see that context without you moving it somewhere awkward.

Action

Whether the AI is chatting, using tools, changing files, or working remotely.

Start here

The advanced map: context, access, action

Advanced AI work is not about memorizing every product name. It is about knowing where the useful context lives, which AI can see it, and whether the AI should answer, connect, or act.

1. Locate

Where is the context?

Email, Teams, SharePoint, Drive, local files, notes, source packets, screenshots, or a repo.

2. Match

Which AI can see it?

Pick the surface already connected to the context instead of copying everything into a random chat.

3. Choose

Answer or action?

A chat answer is different from an agent that can edit files, run commands, create branches, or call tools.

4. Check

Review the real things

Check source files, recipients, branch diffs, dates, numbers, permissions, and anything the AI had to infer.

Context routing board

Use the room that already has the context

Most weak AI results happen because the model is missing the real situation. Start by choosing the room where the useful information already lives.

Microsoft work context

Outlook, Teams, Word, Excel, PowerPoint, OneNote, OneDrive, and SharePoint usually belong in Microsoft 365 Copilot first.

Microsoft 365 Copilot Copilot Chat Copilot agents

Google and source packets

Gmail, Drive, Docs, Sheets, Slides, Android, YouTube, and search-connected work fit Gemini. Defined source packets fit NotebookLM.

Gemini Google Workspace NotebookLM

Local files, notes, and personal knowledge

For Apple Notes, screenshots, local files, Obsidian, Markdown, or personal folders, choose the app that can receive that context with the least friction.

Claude Desktop ChatGPT macOS/Windows/mobile Obsidian/Markdown

Repos, branches, and project files

Code work belongs in an agent lane when files, tests, diffs, branches, or terminal commands matter.

Codex Agent Claude Code Cursor Grok Build

Useful habit

Before pasting work context into another AI, ask: does this tool already have approved access to the same context, or am I about to move information into a worse room?

Agent location

Know where the AI is working

A chat response, a connected app, a local agent, and a remote cloud agent have different powers. The more an AI can touch, the more deliberately you should review its work.

Lane 1

Chat answer

The AI answers from what you type, attach, or connect. Good for reasoning, rewriting, learning, and comparison.

Examples: ChatGPT, Claude, Gemini, Grok.

Lane 2

Connected app

The AI can search or reference approved services, and sometimes take narrow actions through apps, connectors, or MCP.

Examples: ChatGPT apps, Claude connectors, MCP servers.

Lane 3

Local agent

The AI works in your local project or desktop flow, can inspect files, suggest edits, and may ask before running commands.

Examples: Codex app, Claude Code local, Cursor foreground.

Lane 4

Remote/work agent

The AI works in a cloud, GitHub, or work-app environment. It can create branches, files, docs, decks, or agent outputs for review.

Examples: Copilot agents, Codex remote, Claude Code web, Cursor background, Antigravity, Grok Build.

Microsoft

Microsoft Copilot for web, work chat, and Microsoft 365 context

Microsoft now has several Copilot lanes: free/personal Copilot for web and general help, Copilot Chat Basic for secure work chat, and Microsoft 365 Copilot for full work-data grounding inside Microsoft apps.

Free and personal Copilot

Microsoft Copilot

General Copilot for web-grounded questions, writing help, image creation, Edge page help, and everyday learning. Signing in adds history, longer conversations, voice, image creation, and other features.

Conversation modes

Quick response Think Deeper Study and learn Smart Search

Best first use

Use it for everyday questions, web summaries, learning, brainstorming, writing, and trying the model-depth controls without company context.

When not enough

Move to Microsoft 365 Copilot when the answer must use work files, meetings, emails, chats, or app-specific editing inside Word, Excel, PowerPoint, Outlook, Teams, or OneNote.

Microsoft work chat

Copilot Chat

Secure work chat included for eligible Microsoft 365 business users. It is web-grounded by default, includes standard access to file upload, image generation, and model choices, and can use open or uploaded context.

What Basic can use

Web grounding Uploaded files/images Open Outlook/Teams context Copilot Pages Pay-as-you-go agents

Model selector

Use Auto for normal work. Pick Quick response for speed. Pick Think deeper when the task needs more reasoning. Some tenants also expose current GPT-family choices as Microsoft updates the selector.

Best first use

Ask it to research, draft, summarize an uploaded file, create a page, or work beside an open Outlook or Teams item before you reach for a broader chatbot.

Quick label check

Look at your Copilot label: Copilot Chat (Basic) means secure chat without Copilot in Word/Excel/PowerPoint/OneNote; M365 Copilot (Basic) means standard access in those apps; M365 Copilot (Premium) means the full add-on experience with priority access.

Microsoft 365 apps

Microsoft 365 Copilot

The Microsoft 365 Copilot add-on adds priority access, full work-data grounding, deeper app integration, and advanced skills across Word, Excel, PowerPoint, Outlook, Teams, OneNote, Loop, OneDrive, and SharePoint.

Where it fits

  • Word, PowerPoint, and OneNote for drafting, rewriting, and document Q&A.
  • Excel for formulas, tables, charts, Python-assisted analysis, and deeper reasoning where enabled.
  • Teams and Outlook for meetings, threads, follow-ups, calendar, and email context.

Why people pick it

It can answer from meetings, emails, chats, files, and people your account can access instead of making you upload or paste everything by hand.

Use another model when

You need outside critique, broader brainstorming, non-Microsoft context, or a second read with zero company background.

Work app agents

Agents, Researcher, Analyst, and Office creation

Microsoft’s agent path ranges from Basic pay-as-you-go agents to Premium access for advanced reasoning agents like Researcher and Analyst, plus custom agents grounded in company data where enabled.

What to know

Basic users may see limited agents and pay-as-you-go options. Premium users get broader access to advanced agents, Researcher, Analyst, prebuilt Microsoft agents, and custom agents.

Good use cases

Use Researcher for sourced briefs, Analyst for data-heavy work, app agents for Word/Excel/PowerPoint creation, and custom agents for repeatable internal workflows.

Review habit

Open the source files it used and the generated file it created. Check structure, formulas, citations, and assumptions before routing it onward.

OpenAI logo

OpenAI

ChatGPT now combines Chat, Work, and Codex. GPT-5.6 adds a practical tier choice.

Use Chat for conversation, Work for longer connected deliverables, and Codex for software work. GPT-5.6 gives you a tier first—Luna, Terra, or Sol—then an effort level when the task needs it.

OpenAI app

ChatGPT app

General AI workspace for Chat, Work, files, images, voice, research, projects, memory, apps, and custom GPTs.

What it does

Search Deep Research Files Data Analysis Voice Writing/code blocks Projects Memory Apps ChatGPT Work GPT-5.6 Sol / Terra / Luna

Set it up

  • Open ChatGPT on web for the full workspace.
  • Install macOS or Windows when local computer context matters.
  • Create Projects for recurring work and shared context.
  • Choose Luna for speed, Terra for balanced daily work, and Sol when the task needs more reasoning.

Use it for

Conversation, research, writing, files, data, image/audio context, and longer connected deliverables through Work.

Web app

Best full workspace. Use it for long sessions, uploaded files, Projects, research, data, images, writing/code blocks, and recurring work context.

Mobile app

Best capture surface. Use voice, photos, screenshots, quick questions, and steering Codex work when that workflow is enabled.

ChatGPT desktop

One app, three lanes. On macOS and Windows, ChatGPT desktop brings Chat, Work, and Codex together beside files, windows, screenshots, and focused work.

Apps

Best for connected context. Apps can search, reference, sync, run deep research, or take approved actions through connected tools where available.

ChatGPT vs Microsoft Copilot

Use ChatGPT when you need flexible reasoning, drafting, critique, files, research, images, or a second opinion. Use Microsoft 365 Copilot first when the answer depends on Outlook, Teams, SharePoint, OneDrive, Office files, or company permissions.

Choose the lane before the model

Use Chat for an answer, Work for a connected multi-step deliverable, and Codex when the outcome changes software. Then choose Luna for speed, Terra for balanced work, or Sol for complex reasoning, and raise effort only when the stakes justify it.

OpenAI developer agent

Codex agent in ChatGPT desktop + CLI

Software agent for real project files: inspect repos, edit code, run commands, create diffs, test, work remotely, and now operate inside the unified ChatGPT desktop app.

Set it up

npm i -g @openai/codex
codex
brew install --cask codex

What it offers

Desktop app CLI IDE extension Cloud tasks GitHub workflows Mobile steering GPT-5.6 effort controls Multi-repo projects

Use it for

Code changes, debugging, tests, PR work, repo review, and turning a software task into tracked file edits.

macOS desktop

Most complete desktop host. Use ChatGPT desktop for multi-agent threads, worktrees, Appshots, locked-computer remote work, and ChatGPT mobile steering.

Windows desktop

Desktop command center. Use it for parallel agents, inline diff editing, pull-request review, and moving between ChatGPT desktop, CLI, and IDE across multiple repositories.

Remote + mobile

Use your phone to keep work moving. From ChatGPT mobile you can review outputs, approve commands, change models, start new work, and follow screenshots, terminal output, diffs, tests, and approvals from a connected Mac or remote environment.

Remote environments

Use for team/devbox workflows. Codex can connect through Remote SSH, run inside managed remote machines, use cloud environments, and keep project context synced across authorized ChatGPT devices.

Anthropic logo

Anthropic

Claude for careful work. Sonnet 5 for serious daily execution. Fable 5 for long-horizon work.

Anthropic’s stack is strongest when the job needs long context, thoughtful writing, reusable artifacts, desktop context, or repo-aware coding. Sonnet 5 is the efficient serious-work lane; Fable 5 is for longer, harder work that earns extra planning and review.

Anthropic app

Claude app

Careful writing, long-context review, project knowledge, artifacts, connectors, mobile actions, desktop extensions, and current Sonnet 5 / Fable 5 model lanes.

What it offers

Projects Project knowledge Artifacts Shared artifacts MCP in artifacts Web connectors Mobile app actions Desktop extensions Sonnet 5 Fable 5

Set it up

  • Use Projects for repeated context.
  • Use Artifacts for outputs you will edit or reuse.
  • Install mobile when the next step is a message, email, calendar item, map, reminder, alarm, timer, or health summary.
  • Install desktop when local files, desktop extensions, Cowork, or Mac quick entry matter.

Use it for

Nuanced writing, long documents, tone review, research synthesis, editable artifacts, and agentic knowledge work.

iOS app

Action layer for Apple mobile. Claude can draft messages and email, create calendar events, show map locations, manage reminders, and analyze Apple Health data when eligible.

Android app

Action layer for Android. Claude can draft messages and email, create calendar events, set alarms and timers, use location/maps, and analyze Health Connect data when eligible.

macOS Desktop

Best for staying in flow. Quick entry can open Claude from anywhere, capture screenshots, attach app windows, and use voice dictation. Desktop extensions add local files, apps, calendars, email, and messaging.

Windows Desktop

Best for local desktop context. Use Claude Desktop for extensions, local files, Cowork, and connected workflows. Mac quick entry is not available on Windows.

Choose Sonnet or Fable by the work, not the brand

Start with Sonnet 5 for serious everyday analysis, writing, tools, and coding. Move to Fable 5 when the task is long, complex, or high-value enough to benefit from more planning, tool use, and self-checking. In either lane, state the goal, what may be touched, and what you will review.

Claude Desktop agent

Claude Cowork

Claude Desktop agent for knowledge work: files, local apps, browser work, deliverables, plugins, and scheduled tasks.

What it offers

Desktop agent Local files Browser/computer use Plugins Parallel subtasks Scheduled tasks

Set it up

Open Claude Desktop, choose Cowork, show the files or apps it needs, review the plan, then approve actions intentionally.

Use it for

Folder organization, reports, slide prep, browser tasks, multi-step knowledge work, and deliverables from local context.

Anthropic code agent

Claude Code

Code agent for terminal, IDE, Git, GitHub, web/remote tasks, MCP, AWS, and Google Cloud setups.

Set it up

npm install -g @anthropic-ai/claude-code
cd your-project
claude
curl -fsSL claude.ai/install.sh | bash
claude doctor

What it offers

Terminal agent IDE integrations Git/GitHub Web remote tasks Remote Control GitHub Actions Remote MCP AWS/GCP enterprise

Use it for

Repo inspection, implementation, code review, terminal workflows, PRs, and remote coding tasks.

Terminal / IDE

Use when you need tight control. Claude Code runs in your local project, can inspect files, run commands, use local MCP servers, and keep the workflow visible in your terminal or IDE.

Remote Control

Use when you need to steer local work from another device. The session keeps running on your machine while claude.ai/code or the Claude mobile app acts as the remote window.

Claude Code on web

Use for async GitHub work. Pick a repo, describe the task, let Claude work in an isolated remote environment, then review the branch or pull request when it finishes.

Automation routes

Use for team workflows. GitHub Actions can respond to `@claude` in issues or PRs, while remote MCP connectors let Claude reach cloud tools from Claude, Cowork, Desktop, and mobile.

Gemini logo

Google

Gemini for Google context. NotebookLM for source packets. Antigravity for agent coding.

Google’s stack is most useful when the work already lives in Gmail, Drive, Docs, Sheets, Android, source documents, or developer tooling.

Google app

Gemini app + Workspace

Google AI assistant for Search-connected work, Workspace context, Android/mobile, Deep Research, Canvas, Gems, Gemini 3.5 Flash, Deep Think, and Omni-style video/media tasks.

What it offers

Gmail/Drive context Workspace Gemini 3.5 Flash Deep Research Canvas Gems Gemini Omni Android/mobile Computer use for builders

Set it up

  • Open Gemini with the Google account that owns the context.
  • Use Workspace features when Gmail, Drive, Docs, Sheets, or Slides matter.
  • Create Gems for repeated role/task setups.

Use it for

Google-native work, research with Search context, Android help, Drive/doc synthesis, Workspace productivity, and builder/enterprise agent work with Gemini 3.5 Flash computer use.

Google learning workspace

NotebookLM

Source-grounded notebook workspace for learning from uploaded docs, notes, websites, and reference packets.

What it offers

Source packets Study notes Document Q&A Briefing docs Audio-style overviews

Set it up

Create a notebook, add the documents or links you want it to learn from, then keep questions tied to those sources.

Use it for

Training yourself on a topic, building source packs, onboarding to documents, and studying without losing track of the source material.

Google developer agents

Antigravity CLI (Gemini CLI transition complete)

Google’s current developer-agent path for terminal work, skills, hooks, subagents, plugins, and background multi-agent work. Gemini CLI is now a migration reference, not the starting point for new consumer setups.

Gemini CLI migration

The consumer transition date passed on June 18, 2026. If you still have Gemini CLI, bring its useful skills, hooks, subagents, and extensions into Antigravity. For a new setup, start directly with Antigravity CLI.

Migration guide

Antigravity CLI

curl -fsSL https://antigravity.google/cli/install.sh | bash
agy
irm https://antigravity.google/cli/install.ps1 | iex
agy
agy
agy plugin import gemini

Use it for

Terminal coding, background agent tasks, plugin workflows, and Google’s current agent-first developer tooling. For screen-level agents, keep computer-use permissions narrow and confirm consequential actions.

Cursor logo

Cursor

Cursor IDE + Agent for learning by building

Cursor is the AI-native editor path: start by asking questions about code, move into visible file edits, then use Agent, rules, models, and background agents as your confidence grows.

Why people pick it

It keeps the AI beside the code. You can see files, diffs, terminal output, and model choices in one workspace, which makes it easier to learn which model works for a task.

IDE editing Ask mode Agent mode Model picker Rules Background agents GitHub app Bugbot Cursor CLI

Your progression path

1. Learn

Use Ask

Ask how files connect before changing anything.

2. Edit

Use IDE help

Make small visible changes and review diffs.

3. Agent

Use Agent mode

Let it explore, edit multiple files, and run commands.

4. Compare

Try models

Use model choice to learn which model handles your work best.

Set up rules

Use Cursor Settings → Rules or files in `.cursor/rules`. For simple projects, `AGENTS.md` can act as a plain markdown instruction file.

Set up remote/background work

Background agents work in remote isolated environments, clone GitHub repos, and can push branch changes back for review.

Set up the CLI

curl https://cursor.com/install -fsS | bash
cursor-agent

GitHub app

Why it matters: background agents and Bugbot need repository access so Cursor can clone repos, open branches, and push reviewable changes.

Bugbot / PR review

Use for review: Bugbot can review pull requests and follow repo-specific guidance such as `.cursor/BUGBOT.md` where configured.

Review habit

Do not skip the handoff: read the branch diff, run tests locally when possible, and check whether the background environment had the same setup you use.

Grok logo

xAI

Grok 4.5 for current-context work. Grok Build for agent work in repos and office files.

xAI’s stack is useful when the work involves Grok.com, X/social context, current web research, files, xAI APIs, or agentic work through Grok Build.

xAI app

Grok app + xAI API

xAI assistant across Grok.com, mobile apps, X, web search, files, connectors, APIs, voice, image generation, and Grok 4.5.

What it offers

Grok.com Mobile apps Grok in X X Search Web Search Voice API Imagine API xAI API Grok 4.5 File uploads Connectors

Set it up

  • Use Grok.com for the standalone app.
  • Use X when the context is social or from X.
  • Use xAI docs when building with the API.

Use it for

Web-aware questions, X/social pulse, files, xAI API builds, voice/image experiments, and current-context review.

xAI code agent

Grok Build

Grok 4.5 is the default model in Grok Build. Use the agent interactively in a fullscreen TUI, headlessly in scripts, through Agent Client Protocol, or in supported office workflows.

Interactive TUI Headless scripting ACP Skills/plugins/hooks MCP discovery Agent Dashboard Plugin marketplace

Install

Start with the official installer, then launch from a project folder.

curl -fsSL https://x.ai/cli/install.sh | bash

1. Launch

Open a repo session

Use the TUI when you want to watch and steer the agent in the project.

cd your-project
grok

2. Inspect

See what it detected

Review config, instructions, skills, plugins, hooks, and MCP servers before deeper work.

grok inspect

3. Automate

Run headlessly

Use headless mode for scripts, checks, bots, or quick repo explanations.

grok -p "Explain this codebase"

Before AI CLIs

CLI setup and prerequisites

Most AI coding tools need the same basics: a modern terminal, Node.js with npm, Git, and a shell that handles commands predictably.

Mac

macOS baseline

Use Terminal or iTerm, install Homebrew, then install the common command-line dependencies.

Install Homebrew

/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

Install Node.js and Git

brew install node git

Verify

node -v
npm -v
git --version
Win

Windows baseline

Use Windows Terminal with PowerShell 7. It installs side-by-side with Windows PowerShell 5.1 and launches with `pwsh`.

Install PowerShell 7

winget install --id Microsoft.PowerShell --source winget

Install Node.js LTS and Git

winget install --id OpenJS.NodeJS.LTS --exact
winget install --id Git.Git --exact --source winget

Open a new PowerShell 7 tab and verify

pwsh --version
node -v
npm -v
git --version
WT

Windows Terminal setup

Install Windows Terminal from the Microsoft Store if you want the easy path. Then make PowerShell 7 your default profile and create separate profiles for the AI tools you use most.

Install Windows Terminal

Easiest path

Open the Microsoft Store, search “Windows Terminal,” and click Install. This is the simplest route for most Windows users.

Open in Microsoft Store

Command-line path

winget install --id Microsoft.WindowsTerminal --source winget

Profile pattern

Use one profile per working lane: Codex Agent, Claude Code, Gemini or Antigravity, Grok Build, Cursor Agent. Set the profile name, command line, starting folder, color, and icon so you always know where you are.

A clean profile starter

Open Windows Terminal settings, add a profile, and use this shape as the mental model. The important fields are `name`, `commandline`, and `startingDirectory`.

{
  "name": "Codex Agent",
  "commandline": "pwsh.exe",
  "startingDirectory": "%USERPROFILE%/Documents/Projects",
  "tabTitle": "Codex Agent"
}

Start folder

Point each agent at the folder where you actually keep repos.

Shell

Use `pwsh.exe` for PowerShell 7 so modern commands and profiles behave consistently.

Identity

Give each AI lane a clear name and color so you do not paste commands into the wrong session.

Why Node/npm?

Many AI CLIs install through npm, including several tools on this page.

Why Git?

Coding agents need repo context, branch history, diffs, and a clean way to review file changes.

Why restart the terminal?

Installers often update PATH. A new terminal session makes `node`, `npm`, `git`, and `pwsh` visible.

If setup breaks Common CLI troubleshooting moves

Wrong PowerShell

Run `pwsh --version`. If that fails, you are probably in Windows PowerShell 5.1 or PATH has not refreshed.

PATH did not refresh

Close every terminal window, reopen Windows Terminal or Terminal, then verify `node`, `npm`, `git`, and the AI CLI again.

winget missing

Install from Microsoft Store when possible. Store installs are often easier for Windows Terminal and App Installer updates.

npm global install fails

Check Node LTS, permissions, and your shell. Avoid mixing admin and non-admin installs unless you know why.

Git is not identified

Set your Git name/email and confirm your repo branch before asking an agent to commit or push.

Native vs WSL

Pick one lane per project. Mixing Windows paths, WSL paths, and different Node installs makes agents harder to reason about.

Tool connections

What is MCP?

MCP, or Model Context Protocol, is a standard way for an AI app to connect to outside tools and data through small programs called MCP servers.

MCP docs

The simple version

Without MCP, every AI app needs custom wiring for every tool. With MCP, the AI app can discover what an MCP server offers, ask for context, and call approved tools through a shared format.

1

Host

The AI app or coding agent you are using.

2

MCP server

A connector that exposes tools, resources, or prompt templates.

3

External system

Files, GitHub, databases, Slack, calendars, APIs, notes, or other work systems.

What MCP can expose

Tools

Actions the model can call, such as search, create an issue, query data, or edit a file.

Resources

Read-only context like docs, schemas, files, calendars, logs, or knowledge bases.

Prompts

Reusable templates that guide a workflow with specific tools and context.

Common things it interacts with

Local files GitHub/repos Databases Slack/Teams Google Drive Calendars/email Browser tools Obsidian/notes Custom APIs

Best use

Use MCP when the AI needs trusted context or controlled actions from tools you already use.

Keep it scoped

Connect only the folders, accounts, or tools needed for the task. Narrow scope keeps the agent easier to reason about.

Watch actions

Read approval prompts, check activity logs, and separate read-only context from actions that change files or send messages.

Agent operating rules

Instruction files: how agents learn your setup

Instruction files are markdown notes that agents load as persistent context: project rules, commands, style, review habits, tool boundaries, and the things you do not want to re-explain every session.

The simple version

Think of instruction files as onboarding docs for your agents. They do not replace your prompt, but they give every prompt the same ground rules before work starts.

1

Shared source of truth

Keep the common rules in `AGENTS.md` or a shared file under `docs/agents/`.

2

Tool-specific wrappers

Use `CLAUDE.md`, `GEMINI.md`, and `.cursor/rules` for the syntax and behavior each app expects.

3

Codex as maintainer

Ask Codex Agent to audit all instruction files, remove conflicts, and keep Claude Code, Gemini CLI, Cursor Agent, and Grok Build aligned.

How the files fit together

AGENTS.md
  Shared project rules for Codex and simple agent readers.

CLAUDE.md
  Claude Code project memory. Can import extra files with @path.

GEMINI.md
  Gemini CLI project instructions and memory notes.

.cursor/rules/*.mdc
  Cursor project rules: always, auto-attached, or agent-requested.

docs/agents/shared-agent-instructions.md
  Human-readable source that Codex can use to keep the others aligned.

Keep it short

Put durable rules here, not every idea. Long files crowd out the active task.

Make it testable

Say “run `npm test`” instead of “test thoroughly.” Concrete rules are easier to follow.

Refresh often

When the codebase changes, ask one agent to critique the instructions before another agent uses them.

Create the starter files

macOS

mkdir -p .cursor/rules docs/agents
touch AGENTS.md CLAUDE.md GEMINI.md docs/agents/shared-agent-instructions.md

Windows PowerShell 7

New-Item -ItemType Directory -Force .cursor\rules, docs\agents
New-Item -ItemType File -Force AGENTS.md, CLAUDE.md, GEMINI.md, docs\agents\shared-agent-instructions.md

A good Codex maintenance task

This is the kind of request that turns your setup into a repeatable system instead of a pile of half-remembered preferences.

Review AGENTS.md, CLAUDE.md, GEMINI.md, and .cursor/rules.

Create a short shared instruction source under docs/agents/.
Then update each agent-specific file so they agree on:
- project purpose
- setup commands
- test commands
- coding style
- file boundaries
- when to ask before taking action

Call out contradictions before editing anything.

Official source links

Official setup and feature pages