architect-frontend-fsd
Skill14 starsChanged 22 days agoApache-2.0View on GitHub
Explain Feature-Sliced Design (FSD) for frontends, including layers, slices, segments, public APIs, and dependency boundaries.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- ontology-of-everything/SemanticSkillsword for word, first seen Nov 15, 2026
Other versions1 project uses a version of this.
Word for word · 1
- ontology-of-everything/SemanticSkills★ 14100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository22 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- agent-dx-cliSkill
- architect-4cSkill
- architect-4rSkill
- architect-frontend-feature-firstSkill
- concept-designSkill
- concept-modelSkill
- data-knowledge-architectSkill
- personal-knowledge-architectSkill
- read-it-reframe-it-own-itSkill
- simplify-javaSkill
- agent-dx-cli-cnSkill
- architect-4c-cnSkill
- architect-4r-cnSkill
- architect-frontend-feature-first-cnSkill
- architect-frontend-fsd-cnSkill
- concept-design-cnSkill
- concept-model-cnSkill
- data-knowledge-architect-cnSkill
- personal-knowledge-architect-cnSkill
- read-it-reframe-it-own-it-cnSkill
- simplify-java-cnSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 47
Keep page-specific UI, state, and requests in the page slice.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Feature-Sliced Design for frontends
Based on the official Feature-Sliced Design specification.
FSD groups code into layers by responsibility, slices by their meaning to the product, and segments by purpose. Slices keep related changes together. Public APIs give consumers a stable entry point.
Architecture shape
<source root>/
app/routes/
pages/product-details/{ui,api}/
widgets/product-gallery/ui/
features/add-to-cart/{ui,model}/
entities/product/{model,ui}/
shared/{ui,api}/| Layer | Responsibility |
app | Entry points, routing, global styles, and dependency wiring. |
pages | Full screens or major route content, including page-specific UI, state, and requests. |
widgets | Self-contained UI blocks reused across pages or serving as independent regions within a page. |
features | Reusable user actions with business value, such as adding an item to a cart. |
entities | Business entities and their models, data access, or UI representations, such as products. |
shared | General UI components, API clients, configuration, and libraries. |
app and shared contain segments directly. The other layers contain slices, which contain segments. Common segments include ui for presentation, model for state and rules, api for external interactions, lib for supporting code, and config for settings. Use layers and segments as their responsibilities arise. processes is deprecated.
Dependency boundaries
- From highest to lowest, the layers are
app → pages → widgets → features → entities → shared. Imports across slices target strictly lower layers and can skip intermediate layers. Modules within a slice can reference one another, as can segments withinappor withinshared. - Consumers access a slice through its public API. Segments in
appandsharedalso provide public entry points. Export what consumers need explicitly. Within a slice, import internal modules directly. - Compose sibling slices in a higher layer. When two entities have a direct model relationship,
@xcan expose a dedicated API to the named consumer. For example,entities/product/@x/orderservesentities/order.
Pages first
Keep page-specific UI, state, and requests in the page slice. A request specific to product details belongs in pages/product-details/api. When multiple pages reuse the add-to-cart action, features/add-to-cart owns the behavior and exposes an entry point for those pages.
Relationship to feature-first
Feature-first typically groups modules by business capability, then separates responsibilities within each module. FSD defines global layers, groups slices by product meaning within those layers, and governs imports between slices through the layer order.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

