# Platform notes: running CRAFT on Claude, ChatGPT, Gemini, and others

Contents
1. Why this file exists
2. Feature map (what each name means where you are)
3. Claude
4. ChatGPT
5. Gemini
6. Coding agents and CLIs
7. Anything else
8. Rules that never change

---

## 1. Why this file exists

The skill body names features by their Claude names (Artifacts, extended
thinking, Projects). CRAFT follows the open Agent Skills standard and may be
running inside ChatGPT, Gemini, Codex, Gemini CLI, Cursor, or another agent.
Map the names to what exists where you are, and keep the behavior the same.

## 2. Feature map

| Skill body says | Claude | ChatGPT | Gemini | CLI / coding agent |
|---|---|---|---|---|
| Side-panel editor | Artifacts | Canvas | Canvas | Write to a file; show the diff |
| Thinking / reasoning mode | Extended thinking | A reasoning ("thinking") model | Thinking mode / Deep Think | Whatever the agent exposes; otherwise reason in a separate section before the answer |
| Standing context | Project instructions; profile preferences; memory | Project instructions; Custom Instructions; memory | Gem instructions; Saved info; personal context | AGENTS.md / GEMINI.md / CLAUDE.md / rules files |
| Attached files | Uploads and project files | Uploads, project files, GPT Knowledge | Uploads, Gem knowledge, Drive | The working directory |
| Search | Web search, Research | Web search, Deep Research | Search grounding, Deep Research | Fetch tools if present |
| Memory writes | "Remember this" when memory is on | Saved memories | Saved info ("remember that...") | None; suggest a rules-file line instead |
| Invoke explicitly | Say "use my CRAFT skill" | `@craft` | Name the skill | `/craft` or the agent's skill command |

## 3. Claude

Everything in the body applies as written. Present long deliverables as
artifacts. When the user attaches a `.skill` or `.zip`, you can read it from
the uploads directory. The handshake skips the greeting so installs verify
byte-for-byte.

## 4. ChatGPT

- Put long deliverables in Canvas when it is available; otherwise a fenced
  block.
- Custom Instructions are capped at 1,500 characters per field; when
  producing paste text for the user, respect that cap and say the count.
- Memory is a rewritten summary, not verbatim storage. When asked to save
  the CRAFT core, save it as one memory and confirm; do not create
  duplicates on a second install.
- `@craft` is the explicit invocation. Mention it once when the user asks
  how to trigger the skill on purpose.

## 5. Gemini

- Canvas is the side-panel editor. Deep Research benefits from a CRAFT brief
  (audience and decision) before it runs.
- Saved info applies to regular chats, not inside Gems. Skills apply inside
  Spark tasks. Say which surface a given rule will reach.
- Skip the Gem builder's magic-wand rewrite when helping the user set up a
  Gem; it can drop the handshake line.
- Gemini can save Saved info from conversation. Save the CRAFT core as short
  entries rather than one long one.

## 6. Coding agents and CLIs (Claude Code, Codex, Gemini CLI, Cursor)

- The "deliverable" is usually a file change. Lead with the smallest change
  that fixes the problem, show the diff, and explain only the non-obvious
  lines.
- The tune line becomes: "Say 'revert', 'also handle X', or 'add a test'."
- Tech Talk section 19 (code and software) is the relevant vocabulary.
- Standing context lives in the repo's rules file; when the user wants CRAFT
  defaults to persist, offer a five-line block for that file rather than
  memory.

## 7. Anything else

If a feature has no equivalent, fall back to the plainest version: reasoning
in a separate section, deliverables in fenced blocks, and paste text for the
user with the location named. Never claim a capability you do not have.

## 8. Rules that never change

The greeting, the commands, the handshake text, KEEP / CHANGE / LEAVE, part
+ action + result, one question at a time, no invented facts, options then
a verdict. The container changes; the judgment does not.
