Writing good requests
How to describe a task so Vector gets it right, and how to check the result.
Start from something concrete
The most reliable requests point at something that already exists: the open design, a drawing, a photo with dimensions, a hand sketch, or a scan. Attach it, or paste the local path for CAD files, and say what should change.
| Instead of | Try |
|---|---|
| Make a phone holder. | Make a desk stand for the phone in the attached photo. It is 75 × 160 × 9 mm. Tilt it 15° and leave room for the charging cable at the bottom. |
| Fix this model. | The fillet near the top flange fails after I changed the wall thickness. Find the first failing feature and repair it without changing other dimensions. |
| Add holes. | Add four M5 clearance holes on a 60 mm square pattern, centered on the top face. |
Give units, constraints, and intent
- State units and key dimensions. Vector works in the units you give it.
- Name what must not change: “keep the outside dimensions”, “don’t touch the mounting holes”.
- Describe intent, not only geometry: “the lid should snap on and come off by hand”.
- Ask for parameters when you’ll iterate: “drive the length and hole spacing from named parameters”.
Ask for checks
For anything that has to fit or move, ask Vector to measure the result: clearances, distances, wall thickness, interference, ratios, or a STEP export that reopens. It measures the solid rather than repeating your numbers back.