adding-operations

Standardize adding geometric operations to the brepjs CAD library.

77|7|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/andymai/brepjs --skill adding-operations
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adding-operations
Source: https://github.com/andymai/brepjs/tree/main/.claude/skills/adding-operations
Command: npx skills add https://github.com/andymai/brepjs --skill adding-operations

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the guesswork and inconsistent implementation when adding new geometric shape operations to brepjs, preventing missing exports, failing CI checks, and invalid geometry outputs.

Core Features & Use Cases

  • Standardized implementation workflow: Covers kernel capability checks, *Fns.ts implementation with branded types and input validation, and error handling patterns.
  • Complete export surfacing: Guides users through all 6 required export layers, from the internal implementation file to the public API, sub-path entries, namespace APIs, and fluent wrapper methods.
  • CI and quality gate compliance: Includes steps to regenerate function-lookup documentation, pass lint/typecheck/knip checks, and meet 91% test coverage thresholds.
  • Use Case: Use this Skill when you need to add a new fillet, draft, or shell operation to brepjs, expose an existing kernel function in the public API, add a method to the shape() fluent wrapper, or fix missing exports flagged by lint or CI.

Quick Start

Use the adding-operations skill to implement and surface a new geometric shape operation in brepjs, including all required exports, tests, and CI gate passes.

Frequently Asked Questions about adding-operations

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

FAQPage Schema
How do I add a new geometric operation to brepjs without failing CI checks?

Adding geometric operations to brepjs requires implementing the *Fns.ts file with branded types and input validation, surfacing exports across all 6 required layers, and passing 91% test coverage, lint, and knip quality gates.

What are the required export layers for exposing a kernel function in the brepjs public API?

Exposing a brepjs kernel function requires surfacing it across 6 export layers: the internal implementation file, public API, sub-path entries, namespace APIs, and fluent shape wrapper methods.

Why does my new CAD shape operation fail the lint or knip checks in CI?

Your CAD shape operation fails knip or lint checks because it is missing required export flags across the 6 layers or lacks regenerated function-lookup documentation, which this workflow resolves.

How do I add a method to the shape() fluent wrapper for a new TypeScript CAD operation?

Adding a method to the shape() fluent wrapper requires implementing the geometric operation with branded types in *Fns.ts and routing it through all 6 required export layers in brepjs.

What test coverage threshold must new geometric operations meet in brepjs?

New geometric operations in brepjs must meet a 91% test coverage threshold to pass project quality gates and CI checks.