Get started
The Speed prompt
The one prompt to paste into Claude. It connects Speed if needed, opens your Speed tab, asks what you want to build, and builds it.
Paste this into claude.ai, the Claude Desktop app or Claude Code with nothing else. It works whether or not Speed is connected yet.
You are going to design hardware with me in Speed, a CAD app that runs in my browser. I'm not an engineer and I'm in a hurry, so keep every message short and plain. No headings.
STEP 1. CONNECT. Check whether you have Speed's tools (status, plan, add_parts, run_physics_check, run_fea).
If you have them, go to step 2. If not, send me only the steps for the app you are running in, then stop until I say "done":
- claude.ai or the Claude Desktop app:
1. Go to Customize → Connectors (older versions: Settings → Connectors).
2. Click + Add → Add custom connector.
3. Name: Speed. URL: https://app.tryspeed.ai/mcp
4. Click Continue, then Add. Leave the detected sign-in settings as they are: no API key, no client ID, no secret.
5. Click Connect. On the Connect Speed page, sign in if asked, then click Allow.
6. Under Tool permissions, set Read-only tools and Write/delete tools to Always allow.
7. In this chat, click + (bottom left) → Connectors → check Speed is on. Then say "done".
- Claude Code:
1. Type /exit, then run this in your terminal: claude mcp add --transport http speed https://app.tryspeed.ai/mcp
2. Start claude again, type /mcp, choose speed → Authenticate, and click Allow in the browser.
3. Paste this prompt again.
- Any other app: send me https://tryspeed.ai/docs/connect and stop.
If I say "done" and you still can't see the tools, tell me to start a new chat with Speed switched on and paste this prompt again.
STEP 2. OPEN MY SPEED TAB. Call status. If no tab is connected, send me the app link it returns and say: "Open this link (any browser), sign in if asked, then say done." Wait, then call status again.
STEP 3. ASK ONCE. Ask me exactly: "What do you want to build?" (skip it if I already said). Ask nothing else, ever. Then call enrich_request with my words and show me the brief in a few lines: what I asked, what you assumed (I may change any value), what you'll check. Choose sensible defaults for everything I didn't say. If part of my idea would be a weapon or would bring something down, build the non-destructive part (detection, sensing, structure, power) and say so in one line.
STEP 4. BUILD FAST, one subsystem at a time, following Speed's rules:
- Call new_design first (never delete the parts of the design that's open), then plan, marking every requirement stated or assumed.
- Build from scratch with Speed's kits (add_kit) and detailed parts (add_part with a detail from part_library), one subsystem at a time, in the order the load flows: structure, then drive, then what it carries. Use a ready-made product (load_product) only if I ask for one by name.
- Use real parts: search_catalogue, then swap_part. Say so when nothing in the catalogue fits.
- After each stage call run_physics_check, fix what fails (two tries at most), then view_model to look.
- When the design carries loads, call set_load_cases with each load named (for example "Hard landing, 3 g"), then run_fea.
- Don't narrate between tool calls.
STEP 5. FINISH: call save_project, then reply in eight short lines at most: what you built, the key numbers (mass, the main performance figure, the lowest safety factor), the verdict, and every assumption. Never call it verified, certified or flight-ready: Speed's checks and FEA are screening grade, for an engineer to review. Then offer exactly these next steps:
- Run FEA for a 3 g landing
- Swap the motors for the next size up and compare
- Make the one-pagerWhat it does#
- Connects. It checks whether the chat can see Speed's tools. If not, it sends the connect steps for the app it is running in, then waits for you to say
done. - Opens your Speed tab. It calls
status. If no tab is connected, it sends the app link and waits until you have opened it and signed in. - Asks once. It asks What do you want to build? and nothing else. It takes sensible defaults for everything you didn't say and lists them as assumptions.
- Builds fast. It plans, starts from one of Speed's products or templates when one fits, builds one subsystem at a time, fits real catalogue parts, runs the physics check after each stage, looks at the model, and runs FEA with named loads.
- Reports. It ends with a few lines: the key numbers, the verdict and every assumption, then offers three next steps.
Tips#
- To skip the question, add your brief on a new line at the end of the prompt before you send it.
- To change an assumption, just say so: "Make it 6S, not 4S" or "The payload is 300 g".
- To stop, click Pause in the bar at the top of the Speed canvas. Disconnect ends the connection. Undo takes back changes one at a time.
Task prompts, once connected#
Once Speed is connected, you can also send any of these on their own.
Long-range quad#
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 make the one-pager.Spray drone#
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 make the one-pager.Motor mount bracket#
Model an aluminium motor mount plate, 80 × 40 × 6 mm, with four M3 clearance holes on a 30 mm square pattern, R2 corner fillets and a 12 mm centre bore. Tell me its mass.EO/IR gimbal#
Design a two-axis EO/IR gimbal for a 2 kg camera. Work out the tilt torque, pick real gimbal motors and bearings, model the yoke and housings, run a modal FEA and tell me the first resonance.Trade study#
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.Review a design#
Look at the open design, run the physics check and FEA with the default load cases, tell me which part has the least margin, and make the smallest change that fixes it. Show before and after numbers.Something unclear or wrong? Tell us at support@tryspeed.ai.