domains / families / science / fluidsim

fluidsim

combined

Plans, configures, inspects, restarts, and analyzes bounded FluidSim computational-fluid-dynamics simulations with explicit numerical-validity and HPC safety checks. Use for FluidSim solver selection, parameter review, FFT/MPI setup, output diagnostics, or restart compatibility. Framework for computational fluid dynamics simulations using Python. Use when running fluid dynamics simulations including Navier-Stokes equations (2D/3D), shallow water equations, stratified flows, or when analyzing turbulence, vortex dynamics, or geophysical flows. Provides pseudospectral methods with FFT, HPC support, and comprehensive output analysis.

When to use

• FluidSim solver selection
• parameter review
• FFT/MPI setup
• output diagnostics
• restart compatibility
• periodic Cartesian pseudospectral CFD
• numerical-validity checks
• HPC safety checks

When not to use

• treating completed runs as evidence of numerical convergence
• treating stable time steps as evidence of physical validity
• treating smooth plots as evidence of numerical convergence
• treating closed program exit as evidence of physical validity
• claiming GPU acceleration
• installing unrelated CUDA wheels as a FluidSim backend
• automatically submitting or launching MPI jobs

Skill page

Conflict

The two skills cover the same domain (FluidSim CFD) but diverge significantly in procedure, safety constraints, and technical accuracy. The first skill (K-Dense-AI) is a rigorous, safety-focused workflow that mandates explicit resource planning, pilot runs, and specific version pins (0.9.0), while explicitly correcting API field names (e.g., `cfl_coef` vs `CFL`). The second skill (Vibe-Skills) is a general-purpose guide that includes a broader solver list (shallow water, stratified) and a simpler 5-step workflow, but it contains a likely API error (using `CFL` instead of `cfl_coef` for 0.9.0) and lacks the strict HPC safety checks. Because the first skill's safety constraints are critical for HPC usage and the second skill provides broader solver context, neither is a pure reproduction of the other. Combining them allows for a robust workflow that includes the safety checks of the first and the solver breadth of the second, while resolving the API conflict in favor of the version-specific correction in the first.