CAD Review

Audit the canonical input without changing the design. Treat visual evidence and analytic facts as different evidence classes: cad.look proves what is visible; cad.inspect supplies measurements, bounding boxes, identities, and source facts.

Workflow

1. Load this skill, then use the complete canonical review input embedded in the Host prompt.
2. Confirm the document, buildNumber, and build ID from the input. Use those exact values in every CAD call.
3. Treat the input checks as review scope. Inspect the complete build and use the suggested views and object IDs to decide where closer evidence is needed.
4. Call cad.look with the views needed to inspect the whole assembly. When objectIds is non-empty, pass them as focus; use a numerical zoom only if the first focused view is still too wide.
   • For one part's own geometry, pass relevant ids as isolate so surrounding objects cannot hide a defect.
   • For placement, fit, or clearance, use isolate with context: "ghost", or hide the enclosing part, so the interface remains visible in its real position.
   • Cite an isolated or hidden view only for geometry that remains visible in that view.
5. Call cad.inspect when a suspected problem depends on object identity, bounding boxes, source, distance, clearance, or another supported geometry fact. Inspection facts may support a finding, while every finding still requires image evidence.
6. Report only concrete problems:
   • P0: blocks handoff because the evidence shows a core functional failure, visible structural failure or safety hazard, collision, or required-interface problem.
   • P1: a significant fit, usability, completeness, or visible-quality problem that should be corrected before handoff.
7. Label each problem P0 or P1, explain it in natural language, and cite the exact imagePath and view from a successful cad.look result.
8. End your turn with the report as your final message. You have no write tools — the Host saves what you return. Do not write JSON, a schema, a code block, or one result per input check, and put nothing before or after the report.

When no concrete problem is found, write No P0 or P1 findings. and stop.

Do not claim finite-element performance, rated load, material certification, or physical test results. Missing evidence from those external validation methods is outside this visual review and must not be reported as a CAD problem.