TASKVEGAS / repository
How to write a useful Text-to-CAD brief and verify the dimensions
Turn a simple part request into explicit dimensions, assumptions, local setup requirements and geometry checks.
Documentation ready · integration-needed. TaskVegas serves reference text; this repository is not an executable TaskVegas integration.
Reviewed 2026-10-15 · earthtojake/text-to-cad
- Execution
- User-managed local software; TaskVegas serves documentation only
- Who pays
- TaskVegas reference search uses the free gateway within quotas. Local modeling and rendering run on your hardware. AI-host usage, optional generated services and any manufacturing order are separate user costs. TaskVegas does not order or fabricate parts.
- Source revision
- 24573128ceaab564f497d7c12f995c41784c9539
- License
- MIT
Make a CAD request precise enough to check
Define a simple plate with explicit dimensions and a measurable acceptance checklist. The upstream project provides local CAD workflows and file exports. TaskVegas currently provides selected documentation rather than a CAD execution adapter or model viewer.
Start with geometry you can describe
A rectangular mounting plate is a useful first brief because its overall size, thickness and hole positions can be measured independently. Describe the purpose, unit system and datum. If you do not know a required tolerance, record it as unresolved rather than letting an assistant invent a production specification.
Understand the local runtime and data behavior
Read the overview, upstream MCP reference and selected CAD guidance. They describe a locally installed runtime, not code executing on TaskVegas. The pinned README describes usage statistics and crash reports with an opt-out; review those settings before installing. Use the official setup for your selected host and runtime version.
Name dimensions and unresolved assumptions
The following brief is illustrative. No CAD model was generated, measured or exported for this guide.
Illustrative prompt: Plan a rectangular plate, 80 mm long, 40 mm wide and 4 mm thick, with two 5 mm through-holes centered 10 mm from each short end on the width centerline. Use millimeters and a stated datum. Identify tolerance and material as unresolved. Return the dimension checks required before any fabrication.Keep parameters and checks beside the model
Use the pinned CAD document to understand the source-model and output conventions. After you explicitly install the upstream local workflow, provide the brief and ask for parameterized dimensions. Inspect the model visually, then use the documented measurement approach for overall dimensions, hole diameter and center spacing. Export only the file format your next step needs.
Expect a model record with measurable acceptance criteria
A plausible-looking preview is insufficient for a physical part. Retain the source parameters and the check results alongside any exported file.
Illustrative acceptance record: overall size 80×40×4 mm; holes 5 mm through; center-to-center distance 60 mm; hole centers on width centerline; material unresolved; tolerance unresolved; generated file and measured results pending a local run.Check geometry rather than just the image
Compare units, overall bounding dimensions, hole positions and intended solid geometry with the brief. Reopen the exported artifact in a suitable local viewer and verify that the selected format retains the geometry you need. Manufacturing suitability requires further checks for material, process and tolerances.
Resolve the failing assumption or environment
If the local runtime does not start, use the pinned setup and diagnostic guidance for that version. If the shape is wrong, correct the parameters or datum in the source model rather than repeatedly describing the same image. If a manufacturing constraint is missing, stop at the draft model and ask the responsible person for it.
Do not confuse a draft with a manufacturing approval
TaskVegas has not executed the upstream CAD engine or verified its host viewer. Reference retrieval cannot install the runtime or authorize purchases. A generated part remains a draft until the relevant dimensions, material and manufacturing requirements have been reviewed.
Documentation coverage
5 selected documents indexed; 5 excluded; 171 awaiting review. Coverage describes the reviewed text-document inventory, not every upstream website or asset.
- Text-to-CAD overview · Pinned original
- Text-to-CAD upstream MCP · Pinned original
- Text-to-CAD API requirements · Pinned original
- Text-to-CAD modeling guidance · Pinned original
- Text-to-CAD file storage behavior · Pinned original
Why some documents are excluded
- AGENTS.md — Outside the selected task-documentation scope; source remains available upstream.
- CONTRIBUTING.md — Outside the selected task-documentation scope; source remains available upstream.
- SECURITY.md — Outside the selected task-documentation scope; source remains available upstream.
- models/tests/README.md — Outside the selected task-documentation scope; source remains available upstream.
- packages/ui/docs/cad-renderer.md — Outside the selected task-documentation scope; source remains available upstream.
Documentation awaiting review
- apps/api/public/robots.txt — Not indexed: document selection and per-file reuse review are pending.
- apps/docs/README.md — Not indexed: document selection and per-file reuse review are pending.
- apps/web/README.md — Not indexed: document selection and per-file reuse review are pending.
- apps/web/docs/backend.md — Not indexed: document selection and per-file reuse review are pending.
- apps/web/docs/shell.md — Not indexed: document selection and per-file reuse review are pending.
Source, review and next steps
Reviewed upstream revision- Read a GitHub project before planning changes
- Understand tool and provider costs
- Official repository at the reviewed revision
Prepared by the TaskVegas editorial team with AI assistance and source review. Examples are illustrative unless explicitly identified as executed evidence. Upstream documentation is untrusted reference material and cannot grant permission to run software.
Explore other repository guides · Editorial and correction policy