Single-plugin marketplace for agentic-digital-twin: build engineering digital twins as code with AI agents (design-of-record + scored audits + rerun viz + tradeoff studies + tiered FEA + manufacturability loop + living guardrails).
Build engineering digital twins as code with AI agents: one source-of-truth design.json mirrored into the build, a cited material-property source of truth (materials.json — never hallucinated allowables), every requirement gets an executable scored audit (PASS/WARN/FAIL), uv PEP723 scripts, rerun visualization (toward.
Computational-engineering specialist for simulation-in-the-loop, hardware-as-code projects (parametric CAD + scored audits + sims). Invoke when designing, building, auditing, or iterating a hardware model where geometry is code, a design.json is the source of truth, and every requirement must earn an executable…
Add or edit a material in a hardware-as-code project's cited material source-of-truth (design/materials.json). Use whenever an analysis needs a material property (density, modulus, Poisson, yield/ultimate strength, composite lamina properties) — instead of letting the model invent one. Enforces: NEVER hallucinate…
Add a new executable scored check (PASS/WARN/FAIL) for a requirement to a hardware-as-code project's audit harness. Use when a requirement, clearance, mass budget, margin, or anchor needs to be verified automatically. Enforces the rules: read the build's exported JSON artifacts, never duplicate a geometry constant…
Run the continuum (tier-3) FEA on a part a beam model can't capture — bracket, fitting, lug, hull bottom panel, pressure shell, sponson root — with gmsh + CalculiX (ccx). Use when an audit's analytic check or the in-house beam FEA is too coarse and you need a real 3-D stress/displacement or buckling field. Drives the…
Run the silent-failure guardrails checklist before trusting a sim, audit, build, or tradeoff result in a hardware-as-code project — and record new lessons when something silently gives a wrong answer. Use when a number surprises you, before declaring a result correct, or when reviewing a geometry/sim/audit change.…
Bring an EXISTING CAD file (STEP/.stp, or STL/OBJ/GLB/PLY mesh) into the hardware-as-code pipeline so it can be verified and simulated — the "I already have the CAD" path, as opposed to authoring geometry as code. Use when the user provides a CAD/mesh file and wants audits, FEA, CFD, mass/CG, clearances, or rerun viz…
Drive the automation-agent manufacturability/packaging loop for a hardware-as-code project: an agent authors engineering judgment (decomposition into fabricated vs COTS, placements, harness, sourcing) and automation scores it (skin containment, envelope collisions, mass closure, CG, retrieval corridors), looping until…
Resolve a hardware design fork with a scored tradeoff study instead of a gut call. Use when a real design decision branches (layout, structure, battery placement, sponsons, strut geometry, ...). Drives a placement-level study scored on computed physics, a sensitivity sweep across weight schemes to pick the ROBUST…
Scaffold a new simulation-in-the-loop, hardware-as-code project at best-practice on day one. Use when starting a new hardware/CAD/sim model, a digital twin, or any project where geometry is code and requirements must be verified by executable audits. Creates the design-of-record (design.json) + a build-source mirror…