fsd-architecture

To enforce Feature-Sliced Design architecture during frontend code reviews, statically analyze import directions across layers like app, pages, widgets, features, and shared to identify prohibited dependencies and boundary violations.

HR isolation in frontend architecture is a policy preventing cross-domain imports between HR and Audit sections, ensuring distinct responsibility boundaries and consistent ADR compliance across module layers.

You can check FSD module boundaries by applying static analysis to imports, verifying allowed dependency directions across app, pages, widgets, features, and shared layers, and flagging architectural violations.

The best way to plan frontend tasks using Feature-Sliced Design is to map dependencies across allowed layers like app, pages, widgets, features, and shared, while clarifying responsibility boundaries to prevent architectural violations.

FSD architectural boundary checks fail between HR and Audit sections due to prohibited cross-domain imports that violate HR isolation policies and ADR compliance rules governing module structure.

Yes, fsd-architecture supports ADR compliance checks by statically analyzing imports and layer boundaries to verify alignment with documented architectural decisions and HR isolation policies.