← Handbook   Project site   DEEN

Prompt collection

11 templates for typical design tasks – matched to CadPilot’s tools and their limits. Copy, fill in the marked parts, paste into Copilot Chat (agent mode).

As of: 26 Sep 2026 · The German templates are also stored in the project as Copilot prompt files and can be called as slash commands in VS Code.

How the templates work: they name the tools explicitly and ask for checks – show the plan first, measure the volume before and after, ask instead of guessing when something is ambiguous. Tools listed as “not reliable” in the handbook do not appear; a test in the project ensures this. The maturity levels next to the tool names come from the tool catalogue.

Not yet tried with real CATIA. The templates are derived from the handbook’s use cases and checked against the tool descriptions. The first live test will show which of them prove themselves in daily work.

Read and check

Profile of the active CATIA part: structure, parameters, main dimensions, mass

In VS Code as slash command: /bauteil-steckbrief
catia_list_documentsusable catia_get_active_document_infousable catia_list_featuresusable catia_get_parametersusable catia_get_inertialimited
Create a profile of the active CATIA part. Read only; do not change or save anything.

1. `catia_list_documents` and `catia_get_active_document_info`.
2. `catia_list_features`: structure of the main body in order.
3. `catia_get_parameters` with filter “‹parameter filter, e.g. Thickness (empty = all)›”.
4. `catia_get_inertia` with density ‹density in kg/m³, e.g. 2700 for aluminium›.
5. Main dimensions: CATIA V5 Automation has no bounding box – do not estimate; ask the user to measure the outer dimensions in CATIA and note this in the profile.

Output: table of features (name, type), table of parameters (name, value, unit), main dimensions in mm, volume in cm³, mass in kg. Point out anything unusual (default names, parameters without a comment, very long trees).

Check the active part against modelling and naming guidelines

In VS Code as slash command: /richtlinien-pruefung
catia_get_active_document_infousable catia_list_featuresusable catia_get_parametersusable
Check the active part against these guidelines, read only:

‹rules, e.g. “no default names such as Pad.3; parameter WallThickness ≥ 2.5 mm; at most one body; sets without ‘Geometrical Set’ in the name”›

Use `catia_get_active_document_info`, `catia_list_features` and `catia_get_parameters` (with filter).
Output: table rule | finding | OK/deviation | affected elements. You cannot check geometric rules (minimum radius, wall thickness everywhere, demouldability) with these tools – say so explicitly.

Check an assembly: components, part numbers, broken constraints

In VS Code as slash command: /baugruppen-check
catia_list_componentslimited catia_list_constraintsusable
Check the active assembly, read only:

1. `catia_list_components`: names and part numbers (report positions only if plausible; mark zero values as “not reliably measured”).
2. `catia_list_constraints`: all constraints with status.

Flag: broken constraints, duplicate part numbers, components whose name does not start with the part number‹further rule (optional)›.
Output as a table with OK/deviation. Do not create or change constraints – please do that manually in CATIA.

Find update errors: which feature fails and why

In VS Code as slash command: /update-diagnose
catia_check_updatelimited catia_list_featuresusable
The active part cannot be updated without errors. Find the cause.

1. `catia_check_update` without diagnosis: which features are not up to date? Show the list.
2. Ask me whether the diagnosis may run (it updates feature by feature and changes the model like an update). Only after my OK run `catia_check_update` with `diagnose: true`.
3. Name the first failing feature and quote CATIA’s error text verbatim. Show the features before and after it with `catia_list_features`.

Do not delete or change features. Suggest possible causes (e.g. open sketch, lost reference), but mark them as a guess.

Design and vary

New bracket base plate with through holes (circle + pocket) and mass check

In VS Code as slash command: /halter-grundplatte
catia_new_partusable catia_create_sketchusable catia_sketch_centered_rectangleusable catia_close_sketchusable catia_padusable catia_sketch_circleusable catia_pocketlimited catia_get_inertialimited
Design a bracket base plate in a new part “‹part name, e.g. ECU_Bracket›”.

- Plate ‹length in mm› × ‹width in mm› × ‹thickness in mm› on the XY plane, centred on the origin
  (`catia_new_part`, `catia_create_sketch` xy, `catia_sketch_centered_rectangle`, `catia_close_sketch`, `catia_pad`).
- Four through holes Ø ‹hole diameter in mm› on a ‹hole spacing X in mm› × ‹hole spacing Y in mm› rectangle, centred:
  new sketch on xy, four `catia_sketch_circle` (radius = diameter/2), `catia_close_sketch`, `catia_pocket` with the plate thickness.

Show the plan with all coordinates first. Measure after the pad and after the pocket with `catia_get_inertia` (density ‹density in kg/m³, e.g. 7850 for steel›) and compare with the expected volume (plate minus 4·π·r²·t). Result as a table. Do not save unless I ask for it.

Bolt circle with calculated coordinates (circles + pocket) instead of a circular pattern

In VS Code as slash command: /lochkreis
catia_create_sketchusable catia_sketch_circleusable catia_sketch_get_geometryusable catia_close_sketchusable catia_pocketlimited catia_get_inertialimited
Create a bolt circle in the active part on the ‹xy, yz or zx› plane:
pitch circle Ø ‹pitch circle diameter in mm›, ‹number of holes›, hole Ø ‹hole diameter in mm›, first hole at ‹start angle in degrees, e.g. 0›°, depth ‹depth in mm›.

1. Calculate the centres (x = r·cos φ, y = r·sin φ) and show the table with the calculation. Wait for my confirmation.
2. `catia_create_sketch`, one `catia_sketch_circle` per hole (radius = diameter/2), `catia_sketch_get_geometry` as a check, `catia_close_sketch`, `catia_pocket`.
3. Volume before/after with `catia_get_inertia`; expected decrease = count·π·r²·depth. If the volume increases or does not change: reverse the direction and report it.

Do not use the circular pattern tool (the axis cannot be selected).

Parameter variant study with a volume/mass table and reset

In VS Code as slash command: /variantenstudie
catia_get_active_document_infousable catia_get_parametersusable catia_set_parameterlimited catia_update_partusable catia_get_inertialimited
Run a variant study on the active part (only on a working copy).

1. Check with `catia_get_active_document_info` that the document is a working copy in the working folder; otherwise first create a copy with `catia_save_document(file_path=...)`.
2. Read the parameters “‹first parameter name›” and “‹second parameter name (optional)›” with `catia_get_parameters` and note the initial values.
3. For each combination of ‹values for parameter 1, e.g. 3; 3.5; 4› and ‹values for parameter 2 (optional)›:
   `catia_set_parameter` → `catia_update_part` → `catia_get_inertia` (density ‹density in kg/m³›).
4. Finally restore the initial values and confirm with a check measurement that the initial volume is reached again.

Output: table with parameter values, volume (cm³), mass (kg), deviation from the initial state (%). No statements about strength.

Create package space limits as planes and measure distances (target/actual)

In VS Code as slash command: /bauraum-abstand
catia_gsd_create_geosetusable catia_gsd_plane_offsetusable catia_measure_distancelimited
Check the package space of the active part.

1. Create a set “PackageSpace” with `catia_gsd_create_geoset`.
2. Create the limit planes with `catia_gsd_plane_offset`: ‹limits, e.g. “xy +180 mm (top), zx +60 mm (side)”›. Give them unique names.
3. Measure the minimum distances between ‹element name, e.g. PartBody› and each limit with `catia_measure_distance`.
4. Compare with the target ‹minimum distance in mm›.

Output: table limit | actual (mm) | target (mm) | OK/violation. On `AMBIGUOUS_REFERENCE` or `OBJECT_NOT_FOUND` name the candidates and ask – do not guess. No statement about motion envelopes or collisions between parts.

Material and product data

Apply a material and calculate the mass with the catalogue density

In VS Code as slash command: /werkstoff-masse
catia_get_materiallimited catia_set_materiallimited catia_get_inertialimited
Apply the material “‹material name as in the CATIA catalogue, e.g. Steel›” to the active part‹family (optional)›.

1. `catia_get_material`: which material is applied so far? Name it.
2. `catia_set_material` with the requested material. If CATIA does not find it, show the available materials it reports and ask me.
3. `catia_get_inertia` with the reported density. If the density is missing, ask me for the value – do not estimate.

Output: table material | density (kg/m³) | volume (cm³) | mass (kg), plus the previous material.

Check part number, revision and user properties and write them after approval

In VS Code as slash command: /eigenschaften-pflegen
catia_get_product_propertiesusable catia_set_product_propertieslimited catia_undo_lastlimited
Maintain the properties ‹of the active document or of a component, e.g. Bracket.1›.

1. `catia_get_product_properties`: show the current values as a table.
2. Propose the changes: ‹requested values, e.g. revision B, nomenclature “Bracket left”, material property S355›.
3. Only call `catia_set_product_properties` after my confirmation.

Then report the old and new values from the result. Tell me: this change cannot be undone with `catia_undo_last` – the old values are in the table.

Hand over

Review views as images and STEP/STL export into the working folder

In VS Code as slash command: /review-export
catia_set_viewusable catia_fit_allusable catia_screenshotlimited catia_exportusable
Create review material for the active document in the working folder ‹working folder, e.g. C:\Users\Name\CATIA_MCP_Work›:

1. For the views isometric, front and top: `catia_set_view`, `catia_fit_all`, `catia_screenshot` as `‹file name without extension›_<view>.jpg`.
2. `catia_export` as `‹file name without extension›.stp`‹further formats e.g. stl (optional)›.

Do not overwrite existing files (on `POLICY_BLOCKED` suggest a new name). Note: the image size matches the window. List all created files at the end.