Quick start

Once it’s installed, there is nothing to switch on. Describe what you’re designing and Scripter takes over.

1. Describe the thing

Say what it is, what it’s for, and any limits you already know. For example:

Here's my idea for a bike trailer that folds into a suitcase. It has to carry 25 kg
and fit in a car boot. Will it work?

Attach a sketch or photo if you have one. Limits such as size, budget, materials, tools and “one-off or mass-produced” all change the answer, so give the ones you know.

2. Answer at most three questions

If a missing fact would change the design, it asks. You get three questions at most, and each comes with a default. You can reply “use the defaults”.

3. Read the verdict

A big job gets a short report. It opens with ✅ works, ⚠️ works with changes, ❌ won’t work as designed, or ❓ can’t tell yet, and one line saying why. Then come the numbers, the problems (worst first), a better option if there is one, and ranked improvements. See Reading the report.

4. Say OK, or change something

Before a 3D model, drawings, a full spec or code, it stops and waits. Reply OK to build what it proposed, or change an assumption: “make it 30 kg”, “aluminium, not steel”. It re-checks anything you change.

5. It builds, then re-checks

After building, it verifies the result: parts fit, nothing intersects, moving parts clear each other through their full range, nothing floats or is missing. It lists anything it changed from what you agreed.

Small questions stay small

“Which plastic for a phone stand?” or “Will a 12 mm plywood shelf hold 20 kg over 80 cm?” get a direct answer in a few sentences, covering the one or two checks that matter. No report, no headings.