fsd-architecture

Name: fsd-architecture
Availability: InStock
Author: Arsen

Enforce FSD layer rules and HR isolation via static import analysis.

Updated Aug 23, 2026

Search Tags:#architecture #fsd #frontend-architecture #module-boundaries #hr-isolation #import-constraints

Ready to run

npx skills add https://github.com/arsen-ask-lx/.claude_file_4all --skill fsd-architecture-arsen-ask-lx

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fsd-architecture
Source: https://github.com/arsen-ask-lx/.claude_file_4all/tree/main/skills/fsd-architecture
Command: npx skills add https://github.com/arsen-ask-lx/.claude_file_4all --skill fsd-architecture-arsen-ask-lx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

FSD (Feature-Sliced Design) architecture and HR isolation rules govern frontend module structure and dependencies. This guide provides a structured framework to plan frontend tasks, review imports, and check architectural boundaries between HR and Audit sections.

Core Features & Use Cases

Defines allowed import directions across layers (app ← pages ← widgets ← features ← shared) and documents where each layer can depend on others.
Clarifies responsibility boundaries for each layer (app, pages, features, widgets, shared) and lists prohibited dependencies to prevent architectural violations.
Provides a concrete HR isolation policy, with examples of prohibited cross-domain imports and ADR-alignment checks to ensure consistent frontend architecture.

Quick Start

Audit a frontend project to verify FSD layer rules and HR isolation compliance.

Frequently Asked Questions about fsd-architecture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I enforce Feature-Sliced Design architecture rules during frontend code reviews?▼

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.

What is HR isolation in frontend architecture and how does it work?▼

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.

Can I check FSD module boundaries and layer dependencies automatically?▼

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.

What's the best way to plan frontend tasks using Feature-Sliced Design?▼

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.

Why do FSD architectural boundary checks fail between HR and Audit sections?▼

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.

Does fsd-architecture support ADR compliance checks for frontend modules?▼

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.