debugging-geometry

What problem does it solve?

This Skill eliminates the guesswork when debugging brepjs geometry failures, from invalid boolean results and empty degenerate shapes to STEP export crashes and cross-kernel divergences, cutting down hours of trial-and-error CAD debugging.

Core Features & Use Cases

• Failure Triage: Quickly categorize geometry issues (error results, bad geometry, degenerate shapes, kernel traps, kernel divergences) to jump straight to the relevant fix path.
• Numeric & Healing Guidance: Validate geometry with measurement checks, navigate the autoHeal pipeline correctly (avoiding the common short-circuit trap where healing passes never run), and escalate repairs appropriately.
• Boolean & Export Debugging: Diagnose boolean failure root causes (including the notorious #1126 disjoint-fuse corruption that causes silent STEP export crashes) and use the brep CLI for visual debugging and shape comparison.
• Use Case: If your brepjs boolean operation returns an Err, your exported STEP file triggers a WebAssembly.RuntimeError, or your part renders incorrectly, this Skill walks you through the exact steps to isolate and fix the issue.

Quick Start

Use the debugging-geometry skill to follow the step-by-step playbook to isolate and fix your brepjs geometry failure, starting with triaging the error class and running numeric sanity checks on your shape.