frontend-fsd-guard

To enforce Feature-Sliced Design layer boundaries during frontend refactoring, run the FSD guard before structural changes. It checks import paths under src/ and apps/admin-console/src/ to ensure imports travel only downwards through layers and prevent cross-slice drift.

Preventing cross-slice import drift requires checking public API exposure and import boundaries. This skill cross-references repository rules in references/fsd-2.1-rules.md and local AGENTS.md to validate that slices communicate only through their public APIs.

Yes, the FSD guard integrates with existing repository guidance. It is explicitly guided by the repository's references/fsd-2.1-rules.md and local AGENTS.md files to enforce architecture-sensitive constraints during code reviews and refactors.

To check public API exposure when adding new slices, apply the guard while editing code under src/ directories. It validates adherence to FSD 2.1 rules, ensuring new slices expose stable public APIs and maintain correct architectural layer separation.

Run an FSD architecture check before making structural frontend changes such as creating new slices, refactoring existing code, or cleaning up import boundaries. This prevents layer drift and ensures public API discipline is maintained proactively.