vibeflow-geometry

Process CadQuery geometry from caseDict into mesh-ready STEP and STL artifacts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Geometry generation and preparation from 0-caseDict/caseDict to stable, exportable artifacts that downstream meshing and solver workflows can consume reliably.

Core Features & Use Cases

  • Parametric CadQuery geometry generation from geometry.parameters and geometry.entities
  • Organize/export STEP and STL artifacts and manage geometry manifests
  • Align named bodies, domains, regions, and interfaces to downstream mesh and solver backends
  • Validate geometry consistency and perform repairs when needed
  • Prepare artifacts for geometry-to-mesh handoff and reproducible case execution

Quick Start

Execute the geometry generation flow to produce mesh-ready artifacts from 0-caseDict/caseDict geometry.

Frequently Asked Questions about vibeflow-geometry

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

FAQPage Schema
How do I generate mesh-ready CAD geometry from a parametric caseDict?

To generate mesh-ready CAD geometry from a parametric caseDict, process the geometry parameters and entities to produce repeatable STEP and STL artifacts. This aligns named bodies and regions for reliable downstream meshing.

Why does my CadQuery geometry fail downstream mesh generation workflows?

CadQuery geometry fails downstream mesh generation when named entities are misaligned or exports lack stable paths. Enforcing parameter naming and geometry validation ensures artifacts are consistently consumed by meshing backends.

Can I use CadQuery to organize and export STEP and STL artifacts for solver workflows?

Yes, you can use CadQuery to organize and export STEP and STL artifacts for solver workflows. Parametric geometry generation manages manifests and aligns domains and interfaces for reproducible case execution.

What is geometry-to-mesh handoff and when do I need it for CAD validation?

Geometry-to-mesh handoff prepares validated CAD artifacts for consumption by mesh generation tools. You need it when converting parametric geometry into stable STEP and STL exports for downstream solver workflows.

Does vibeflow-geometry support named entity alignment for downstream mesh and solver backends?

Yes, vibeflow-geometry supports named entity alignment for downstream mesh and solver backends. It aligns named bodies, domains, regions, and interfaces to ensure consistent geometry artifact consumption.

What are the limitations of using parametric CAD generation without stable export paths?

Without stable export paths, parametric CAD generation produces inconsistent artifacts that downstream meshing and solver workflows cannot reliably consume. Enforcing parameter naming and robust validation prevents these handoff failures.