# Salesforce Org Discovery Kit

Status: DRAFT, NOT APPROVED. Not yet run end to end in a developer org or sandbox. A named reviewer must sign off before this is treated as tested.

A first-hour kit for a Salesforce org you did not build. It works with the Salesforce CLI, Setup and a coding agent (Claude Code, Cursor, Codex or VS Code). Nothing here needs Clientell.

## What is in the folder

| File | What it is |
|---|---|
| `first-hour-checklist.md` | One page. What to do, in order, in your first hour in a client org. |
| `queries.md` | Twelve SOQL and Tooling API queries, each with the `sf` command and what the result does not tell you. |
| `CLAUDE.md` | A project file for the client org. Copy it to the root of the project. Claude Code reads it as `CLAUDE.md`. For Cursor, Codex or VS Code, paste the same text into that tool's instruction file. |
| `skills/salesforce-org-discovery/SKILL.md` | A Claude Code skill: a numbered procedure that maps the org and writes a one-page summary. |
| `findings-log-template.md` | One table to record what you found, how sure you are, and how to check it. |

## How to use it

1. Get a sandbox that is a recent copy of the client org. Do not start in production.
2. Create a Salesforce DX project and retrieve the metadata you need.
3. Copy `CLAUDE.md` to the project root and replace the bracketed parts.
4. Copy `skills/salesforce-org-discovery/` to `.claude/skills/salesforce-org-discovery/`.
5. Work through `first-hour-checklist.md`. Use `queries.md` for the counts.
6. Record what you find in `findings-log-template.md`.

## Rules the kit follows

- Sandbox first. Production only with the client's written sign-off.
- Ask for counts, names and structure. Do not copy client record contents into chats, files or commits.
- If a thing cannot be proven unused, call it "unknown".
- Every claim in the findings has a way to check it.

## Limits

- The queries were written against the documented objects and have not been run against every org edition. Run each one once in a developer org or sandbox before you rely on it, and expect some to need changes.
- Metadata tells you what exists and what references what. It does not tell you what outside systems do, or why something was built.
- The Salesforce CLI command names are current as of the date the kit was written. Check `sf --help` if one is rejected.