vibeflow-mesh

Generate, validate, and convert meshes for OpenFOAM workflows.

12|1|Updated May 19, 2026
One-click install
npx skills add https://github.com/sunrise-hjx/vibeFlow-skills --skill vibeflow-mesh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vibeflow-mesh
Source: https://github.com/sunrise-hjx/vibeFlow-skills/tree/main/vibeflow-mesh
Command: npx skills add https://github.com/sunrise-hjx/vibeFlow-skills --skill vibeflow-mesh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Convert and validate geometry into mesh-ready artifacts that faithfully represent the design intent while ensuring compatibility with OpenFOAM and the vibeflow solver backends, reducing manual meshing errors and rework.

Core Features & Use Cases

  • Automated mesher selection among blockMesh, gmsh, and snappyHexMesh (including hybrid workflows) based on geometry and caseDict.mesh.
  • Management of regions, interfaces, boundary layers, y+ targets, and local refinements to produce consistent, scalable meshes.
  • Support for mesh conversion readiness and artifact generation (e.g., B-mesh/C-run outputs, dictionaries) to streamline downstream solver runs.

Quick Start

Generate a production mesh by selecting the appropriate mesher from caseDict.mesh and geometry artifacts, then validate with checkMesh and prepare conversion-ready dictionaries.

Frequently Asked Questions about vibeflow-mesh

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate an OpenFOAM mesh from geometry for a VibeFlow workflow?

To generate an OpenFOAM mesh, the Skill selects an appropriate mesher like blockMesh, gmsh, or snappyHexMesh based on your geometry artifacts and caseDict settings, then validates the output with checkMesh to ensure conversion readiness.

How do I choose between blockMesh, snappyHexMesh, and gmsh for my mesh generation pipeline?

Mesh generation mesher selection is automated by evaluating your 0-caseDict geometry artifacts and caseDict.mesh parameters, automatically determining whether blockMesh, gmsh, snappyHexMesh, or a hybrid workflow best fits your boundary and refinement requirements.

Can I use a hybrid meshing workflow with snappyHexMesh and gmsh for OpenFOAM conversion?

Yes, hybrid mesh generation workflows combining snappyHexMesh and gmsh are supported. The Skill manages regions, interfaces, and boundary layers while preparing conversion-ready dictionaries for OpenFOAM solver backends.

What should I do if checkMesh validation fails after snappyHexMesh generation?

If checkMesh validation fails, review your caseDict mesh quality targets, boundary layer settings, and local refinement parameters. The Skill validates mesh artifacts against these defined criteria to reduce manual meshing errors and rework.

Why does my OpenFOAM mesh conversion fail due to incorrect region and interface naming?

OpenFOAM mesh conversion requires consistent region and interface naming. The Skill satisfies naming conventions defined by your 0-caseDict and geometry artifacts, ensuring generated mesh artifacts are fully prepared for solver backend conversion.