architecture-navigation

Layer boundary import violations occur when code imports upward instead of downward or sideways. This Skill provides a troubleshooting table mapping common boundary and kernel abstraction errors to concrete resolution steps for brepjs's four-layer architecture.

The best way to determine module placement is using a layer placement decision tree that classifies new code by its dependencies. This Skill provides a step-by-step list to categorize code into the correct brepjs layer, ranging from kernel utilities to high-level sugar.

Registering a new source directory in boundary validation scripts ensures CI checks recognize the new module and enforce downward-only import rules. This Skill satisfies requirements for registering directories and adhering to cross-directory import naming conventions.

Pre-commit checks fail when new operations violate the strict four-layer import boundary rules or are placed in the wrong layer. Use this Skill to place operations in the correct Layer 2 module and follow the API ladder pattern to pass boundary checks.

The API ladder pattern is used for adding new operations like 2D shape operations to brepjs. This Skill ensures you follow the pattern and adhere to cross-directory import naming conventions to maintain kernel abstraction and pass CI validation.