vibeFlow-skills

Use when preparing, running, debugging, post-processing, or extending VibeFlow/VibeCAE CalculiX finite-element structural workflows from 0-caseDict/caseDict, including Abaqus-style .inp files, ccx solver runs, cgx visualization handoff, materials, sections, contacts, loads, constraints, .frd/.dat/.sta outputs, and reusable CalculiX case templates.

Use when eliciting VibeCAE requirements, creating, editing, explaining, validating, or extending VibeFlow 0-caseDict/caseDict, mapping user intent to a solver-neutral physical/numerical problem definition, deciding whether a case may advance to geometry, mesh, run, postprocess, or report, and recording unresolved questions, decisions, assumptions, artifacts, and error status in the single source of truth.

Use when preparing, running, debugging, post-processing, or developing VibeFlow/VibeCAE Code_Aster structural FEM and multiphysics workflows, including MED mesh handoff, .comm/.export files, material and boundary mapping from 0-caseDict/caseDict, run_aster execution, validation, and Code_Aster Python command development.

Use when preparing, running, debugging, post-processing, or extending VibeFlow/VibeCAE Elmer finite-element multiphysics workflows from 0-caseDict/caseDict, including ElmerSolver SIF files, ElmerGrid mesh conversion, materials, bodies, boundary conditions, coupled physics, MATC/user functions, and reusable Elmer case templates.

Use when preparing, running, debugging, post-processing, or extending VibeFlow/VibeCAE FDS fire, smoke, ventilation, combustion, sprinkler, evacuation-adjacent, and thermal hazard workflows from 0-caseDict/caseDict, including .fds input files, mesh blocks, devices, slices, boundary conditions, HRR output, Smokeview handoff, and reproducible fire-safety studies.

Use when preparing, running, debugging, validating, or developing VibeFlow/VibeCAE FEniCS or FEniCSx finite-element PDE workflows, including Python weak forms, dolfinx/dolfin environments, mesh and boundary-tag handoff, solver setup, post-processing, reusable PDE modules, and traceability to 0-caseDict/caseDict.

Use when creating, editing, validating, importing, exporting, or developing VibeFlow/VibeCAE geometry workflows with FreeCAD or FreeCADCmd, including interactive CAD handoff, scripted parametric CAD, STEP/STL/FCStd exchange, geometry repair, FreeCAD macro/workbench development, and traceability back to 0-caseDict/caseDict.

Use when preparing, running, debugging, post-processing, or extending VibeFlow/VibeCAE FreeFEM finite-element scripting workflows from 0-caseDict/caseDict, including .edp PDE scripts, variational formulations, mesh generation/import, boundary labels, parameter studies, MPI runs, and reusable PDE/FEM prototyping templates.

Use when generating, editing, validating, repairing, importing, exporting, or documenting VibeFlow geometry from 0-caseDict/caseDict, especially CadQuery parameterized CAD, STEP/STL organization, computational-domain construction, named faces/regions/interfaces, geometry manifests, and geometry-to-mesh handoff.

Use when preparing, running, debugging, post-processing, or extending VibeFlow/VibeCAE LAMMPS molecular dynamics and particle simulation workflows from 0-caseDict/caseDict, including LAMMPS input scripts, data files, potentials, fixes, computes, dumps, restarts, Python post-processing, and optional custom LAMMPS package or style development.

Use when selecting, generating, validating, converting, or debugging VibeFlow meshes from 0-caseDict/caseDict and geometry artifacts, including blockMesh, Gmsh, snappyHexMesh, hybrid workflows, boundary layers, y+ targets, local refinement, feature capture, patch/region/zone naming, checkMesh quality gates, and OpenFOAM conversion preparation.

Use when preparing, running, debugging, validating, or developing VibeFlow/VibeCAE workflows for MOOSE-based applications, including HIT .i input files, MOOSE app executables, materials/kernels/boundary conditions, TestHarness, custom app/module development, and traceability to 0-caseDict/caseDict.

Use when preparing, running, debugging, post-processing, or extending VibeFlow/VibeCAE Nektar++ spectral/hp element workflows from 0-caseDict/caseDict, including XML session files, high-order meshes, incompressible/compressible solvers, FieldConvert/NekMesh, boundary conditions, polynomial order, filters, and reusable high-order CFD/PDE templates.

Use when selecting, generating, running, or debugging VibeFlow OpenFOAM cases from 0-caseDict/caseDict, and when developing, repairing, documenting, compiling, or integrating OpenFOAM UDF code under UDF/, including custom solvers, libraries, boundary conditions, functionObjects, fvOptions, source terms, turbulence/model extensions, Make/files, Make/options, wmake validation, and UDF/README.md development documentation.

Use when preparing, running, debugging, post-processing, or extending VibeFlow/VibeCAE OpenLB lattice-Boltzmann workflows from 0-caseDict/caseDict, including C++ applications, lattice units, geometry indicators, boundary conditions, parallel builds, VTK output, and reusable LBM templates.

Use when preparing, running, debugging, post-processing, or extending VibeFlow/VibeCAE OpenRadioss explicit dynamics workflows from 0-caseDict/caseDict, including Starter/Engine decks, materials, contacts, boundary conditions, loads, time controls, restart/output files, crash/impact/blast/drop studies, and reusable explicit-dynamics templates.

Use when planning, extracting, validating, plotting, visualizing, or summarizing VibeFlow OpenFOAM results from C-run and 0-caseDict/caseDict, including postProcessing data, probes, forces, forceCoeffs, samples, field files, solver logs, Python metrics, ParaView/pvpython scenes, evidence tables, figures, animations, and report-ready artifacts.

Use when planning, drafting, revising, validating, or completing a VibeFlow/VibeCAE report from 0-caseDict/caseDict and artifacts in A-geo, B-mesh, C-run, and D-post, including problem statement, assumptions, geometry, mesh, physical models, materials, boundaries/loads/initial conditions, numerical setup, results, limitations, conclusions, evidence traceability, figure/table selection, and report readiness checks.

Use when preparing, running, debugging, or extending VibeFlow/VibeCAE Scilab numerical computing workflows from 0-caseDict/caseDict, including scripts, functions, optimization, control, signal processing, data reduction, plotting, Xcos handoff, and reusable scientific-computing utilities.

Use when preparing, running, debugging, post-processing, or extending VibeFlow/VibeCAE SU2 CFD, heat-transfer, adjoint, deformation, and optimization workflows from 0-caseDict/caseDict, including SU2 config files, mesh conversion, history monitoring, restart files, and reusable SU2 case templates.

Use when checking, diagnosing, documenting, or separating VibeFlow/VibeCAE toolchain/environment failures from case-definition failures, including OpenFOAM bashrc and utilities, Python, virtualenv, CadQuery/OCP, Gmsh CLI/Python API, ParaView/pvpython, FreeCAD, Code_Aster, FEniCS/FEniCSx, MOOSE, LAMMPS, Scilab, SU2, FDS, Elmer, CalculiX, FreeFEM, OpenRadioss, Nektar++, OpenLB, solver commands, PATH/module issues, and stage-specific readiness before geometry, mesh, run, postprocess, or report work.