What problem does it solve?
Developers working in the devtools scope can accidentally create forbidden cross-package imports that break lazy loading, introduce circular dependencies, and defeat code-splitting between the shell, registry, and tool packages.
Core Features & Use Cases
- Import Rule Enforcement: Defines exactly which
@devtools/* packages may import from each other via an explicit allowlist table.
- Architecture Rationale: Explains why violations collapse the lazy-load boundary, create circular dependencies, and break the registry's discriminated union typing.
- Correct Pattern Guidance: Directs shared utilities into standalone libraries outside the
@devtools/* scope and routes app state through @devtools/bindings props.
- Use Case: When adding a new devtools package or refactoring an existing one, check the rules table before adding any
@devtools/* import to confirm it is permitted.
Quick Start
Ask the AI to review your changes in the devtools directory and verify that all cross-package imports comply with the devtools import boundary rules.