Vehicle Overall Design CAD Drafting Assistant

Problem

Vehicle overall design often starts with top-level parameters such as vehicle type, seat count, overall length, width, and height, axle count, and rated payload, then derives performance-related results covering power, economy, and running stability. Manual workflows can scatter input parameters, debug parameters, coefficients, and outputs, and later changes may require full recalculations, making version tracking harder. This skill turns that process into a traceable workflow: select a product, collect parameters one by one, call the calculation API, review results, then create a production order and track completion.

How it works

It works around the JXT mechanical components platform's vehicle overall design capabilities, including products such as passenger vehicle overall design, pure electric vehicle overall design, and truck overall design. The core workflow lists available products, reads the parameter structure, separates input_params, output_params, debug_params, and coefficient_params, and collects parameters incrementally. For option-based fields, it retrieves available choices before submission. After the first calculation, it stores the returned filename, presents input, debug, coefficient, and output values in a table, and supports incremental updates by sending only changed parameters with the same filename. Once the production order is created, it reports the guest_code and viewing link, then polls status at regular intervals to show waiting, in-progress, and completed states.

Boundaries

It is suited for engineering scenarios where overall design parameters, calculation results, and production order status need to be connected, especially when parameters are numerous and require repeated review or partial updates. It relies on existing product categories and parameter definitions, and it does not replace formal vehicle engineering standards or specialized work such as structural strength and crash safety. Parameter values, result tables, and order status are rendered from the platform API; option-based parameters are fetched before submission.