> ## Documentation Index
> Fetch the complete documentation index at: https://deepline.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Claude Code Usage

> Guide Claude Code through discovery, authoring checks, and an evidence-based pilot review.

[Human guide: work with your agent →](https://deepline.com/docs/human/sdk-v2/claude-code.md)

Use Claude Code to produce one checked, reviewable pilot. Ask for an outcome
and evidence, not an unexplained sequence of provider calls.

## Before you start

[Install the plugin](https://deepline.com/docs/claude-plugins.md) or use the
[coding-agent setup](https://deepline.com/docs/sdk-v2/coding-agents.md). Work inside the intended project folder.

```bash theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
deepline auth status --json
```

Confirm the workspace before processing the file.

## 1. State the input and acceptance rule

```text theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
Use leads.csv with first_name, last_name, and domain.
Find work emails through an inspected maintained contract.
Create a representative CSV-safe pilot before the full file.
Keep accepted, unresolved, and failed rows with their source identity.
Show the run ID, validation evidence, and recorded Deepline usage.
Do not update a CRM or sequencer.
```

The requested output is your review contract. It does not change a prebuilt's
schema or create an automatic approval system.

## 2. Require discovery before execution

Ask Claude to search and describe the current Play or tool. For example:

```bash theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
deepline search "verified work email CSV waterfall" --type prebuilts --json
deepline describe prebuilt/name-and-domain-to-email-waterfall-batch --json
```

Compare required fields and header mappings with the actual file.
For custom source, require `deepline plays check <file>` before a run.
A successful check validates supported structure, not business accuracy.

## 3. Review a bounded pilot

Use [Batch CSV enrichment](https://deepline.com/docs/sdk-v2/batch-csv.md) to select records without breaking
quoted CSV fields. Ask Claude to explain which rows represent difficult cases.

After the pilot, inspect the saved run, exported rows, and scoped usage.
A useful review reconciles every source ID to a result or explicit exception.

> [!TIP]
>
> The intended person and company match. Unresolved rows remain visible. The
> selected output fields and recorded usage support the scale decision.

## 4. Repeat only the approved method

If the Play, input mapping, or acceptance rule changes, check the changed method.
Do not expand an unreviewed route because a small run merely completed.

Ask Claude why a specific row was accepted or held. Use its evidence to correct
the rule before processing the full file.
See [Design for agents](https://deepline.com/docs/designed-for-agents.md) for the reasoning behind these boundaries.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.