layer-detector

Layer detection works by enumerating standard and sliced layers like app, features, entities, widgets, and shared, then identifying segments, public API files, and export patterns to reveal your project's slice organization and architectural compliance.

Yes, FSD slice detection supports Next.js style aliasing by applying user-configurable layer aliases and path mappings to accurately identify layers like core/views and their underlying segments within your aliased project structure.

To audit public API presence, the detector identifies index.ts, index.tsx, and index.js files within each slice, counts files per segment, and surfaces export patterns to validate architectural boundaries and reveal structural inconsistencies.

The best way to map FSD layers for auditing is to run an analysis command against your repository's src directory, which produces a summarized layer map showing slice existence, segment organization, and file counts for architectural decisions.

Yes, the FSD layer detector works with custom segments by enumerating not only standard segments like ui, model, and api but also discovering and mapping custom segment folders within each slice to support flexible architectural patterns.