Enforce module boundaries via barrel files.

ESLint plugin for imports and module boundaries — drop-in replacement for eslint-plugin-import, 3.1x faster end-to-end, zero-config migration.

The eslint-plugin package is an ESLint plugin that contains a collection of recommended ESLint rule configurations which you can extend from in your own ESLint configs, as well as an Nx-specific lint rule called enforce-module-boundaries.

An agent harness for code repositories: one command that is the definition of done, plus mechanically enforced module boundaries. TypeScript-first, not TypeScript-only.

The eslint-plugin-nx package is an ESLint plugin that contains a collection of recommended ESLint rule configurations which you can extend from in your own ESLint configs, as well as an Nx-specific lint rule called enforce-module-boundaries.

Controls the entropy of the codebase by enforcing code module boundaries. Ships bridges for pi, Claude Code, and Devin CLI.

Architecture as Code — layers, module boundaries, and circular dependency detection

ESLint plugin to enforce internal module boundaries (no imports from another module's internal/)

Neutral normalization layer for values crossing Funesterie, A11 and runtime module boundaries.

Enforce the Recursive Deep Modules convention from paths alone: nested module boundaries for ESLint, oxlint, and Biome, plus cycle detection and structural checks.

The eslint-plugin-nx package is an ESLint plugin that contains a collection of recommended ESLint rule configurations which you can extend from in your own ESLint configs, as well as an Nx-specific lint rule called enforce-module-boundaries.

ESLint plugin that enforces one semantic top-level concern per TypeScript module.

Eslint plugin checking architecture boundaries between elements

ESLint plugin to enforce module boundaries

Element descriptors and matchers for @boundaries tools

Agents should invoke this skill for architecture reviews, module boundaries, dependency direction, coupling/cohesion, SOLID concerns, system design trade-offs, layering, service boundaries, or design decisions before implementation.

ESLint rules for module boundary enforcement: no cross-module @internal imports, no @internal re-exports in barrels, no star re-exports from non-barrel files

<p align="center"> <img src="https://raw.githubusercontent.com/softarc-consulting/sheriff/main/logo.png" width="320" style="text-align: center"> </p>

Build-time server-only and client-only module boundaries for Vite.

- Have an existing nx workspace. For creating this, see [nrwl's documentation](https://nx.dev/latest/angular/getting-started/nx-setup). - .NET SDK is installed, and `dotnet` is available on the path. For help on this, see [Microsoft's documentation](https