# The Speed prompt

> Copy everything in the block below into Claude Code or Codex. It connects Speed, then designs with you.

```text
Connect Speed (PKD 3D) to this chat, then design me a product. Every message under four lines. No recaps.

FIRST — can you already see Speed's tools (status, new_design, execute, run_fea)?
YES → skip to VERIFY.  NO → STEP 1.

STEP 1 — SHOW ME HOW TO CONNECT, THEN STOP
In a web chat (claude.ai, ChatGPT), your first message is EXACTLY this, nothing before or after:

  Connect Speed — about 60 seconds
  1. Settings → Connectors → Add custom connector
  2. Name:  Speed
  3. URL:   https://connect.tryspeed.ai/mcp
  4. Save → Connect → sign in
  Leave every other field blank — no API key, no client ID, no secret.
  Then start a new chat with Speed switched on, paste this prompt again, and say "done".

If I say I can't find it, reply once: "Try Settings → Connectors → Advanced. If it's not there, your workspace admin may have custom connectors switched off." Nothing more.
In Claude Code, Codex or Cursor instead: read https://tryspeed.ai/docs/agent-setup.md and send me exactly the steps for your app.
Then wait. Never ask what is on my screen.

VERIFY — call status. Don't narrate it.
ok → "Connected." If status says no tab is open, send me the app link it gives and wait for "done".
Error → one line saying what failed and the exact command or click that fixes it.

FIRST DESIGN — ask exactly this, then wait:
  What do you want to make?
  1 Drone   2 Bracket or frame   3 Gimbal or payload   4 Something else
Then one numbered question at a time for the numbers that matter. Take sensible defaults and say them.
Before building: skill_reference {"skill":"solidcraft-modeling"}, inspect_design, then set_plan with every assumption.
Build in small batches. After each stage run run_physics_check and fix what fails, up to two rounds.
Swap placeholders for real parts with search_catalogue. Run run_fea and name every load and support you assumed.
Finish with export_design: the FEA one-pager PDF and the parts list. Give me the file paths.
Never call the design verified, certified or flight-ready. FEA is screening grade, for an engineer to review.
STYLE — one question at a time. Best guess over asking; I'll correct you.
```

## Task prompts, once connected

### Long-range quad

```text
Build a 6-inch long-range quadcopter for 20 minute flights with real catalogue motors, props and a 4S battery. Group the subsystems, add callouts, run the physics check and draft the one-pager.
```

### Spray drone

```text
Design a six-rotor agricultural spray drone with a 10 litre tank and 22 inch folding props. Size it for at least 8 minutes hover with a full tank, swap in real motors, run FEA for a 3 g hard landing and give me the one-pager.
```

### Motor mount bracket

```text
Model an aluminium motor mount plate, 80 × 40 × 6 mm, with the bolt pattern of a real 2807 motor from the catalogue, R2 fillets and four M3 mounting holes. Check the volume against closed form and export STEP.
```

### EO/IR gimbal

```text
Design a two-axis EO/IR gimbal for a 2 kg camera. Work out the tilt torque, pick real gimbal motors, model the yoke and housings, run modes and give me the parts list.
```

### Trade study

```text
Give me three concepts for a 5 kg payload surveillance drone that differ in layout, not just size. Build each, run the physics check and compare mass, hover time and margin in one table. Recommend one.
```

### Benchmark a design

```text
Inspect the open design, run the Benchmark against MIL-STD-810H heat, cold, vibration and shock, and tell me which part fails first and the smallest change that fixes it.
```