aicad-draw

AI CAD Constraint Drawing

Use the bundled tools as the execution boundary. Do not emit raw AutoCAD commands from model text and do not hand-edit .aicad files.

Core workflow

1. Call aicad_capabilities once when entity, constraint, or output support is uncertain.
2. Determine whether dimensions uniquely define the drawing. Ask one focused question when a fit-critical dimension is missing; otherwise state harmless assumptions.
3. For a rectangle, circle, arc, or rectangular plate with one centered hole, call aicad_generate. Keep its default provider: offline unless the user explicitly chose a configured provider.
4. For other supported 2D geometry, call aicad_get_plan_schema, author a schema 2.0 plan, then call aicad_compile_plan.
5. Read the returned manifest and audit paths. Treat ok: true plus the generated manifest as the completion gate.
6. When visual review matters and a CAD renderer is available, hand the returned DXF path to it. Keep AutoCAD execution as a separate explicit step.

Plan every entity mathematically

For each entity, determine before submitting the plan:

• its functional purpose;
• the earlier point or entity it depends on;
• the minimum constraints that uniquely determine it;
• whether it closes, continues, parallels, or is perpendicular to earlier geometry;
• whether it duplicates geometry, has zero size, or creates an unintended gap.

Anchor the first line start or first radial center at origin. Prefer references to earlier endpoints, midpoints, and centers. Use an explicit origin-relative offset only when no earlier geometric point is appropriate.

Read plan-schema.md before authoring a non-template plan. Read examples.md for tool-call patterns. Read failure-recovery.md only after a tool rejects a request or plan.

Result handling

Return the most useful artifacts to the user:

• .dxf for portable geometric review;
• .aicad for the validated AutoCAD plugin executor;
• .scr only as an explicit AutoCAD script fallback;
• .audit.md for entity purpose, relations, and reasoning;
• .manifest.json for hashes, counts, and artifact inventory;
• .plan.json as the editable source of truth.