feature-sliced-design

Name: feature-sliced-design
Availability: InStock
Author: feature-sliced

Official Feature-Sliced Design (FSD) v2.1 skill for applying the methodology to frontend projects. Use when the task involves organizing project structure with…

view source

installs

stars

karma

SKILL.md

Feature-Sliced Design (FSD) v2.1

Source: fsd.how | Strictness can be adjusted based on
project scale and team context.

1. Core Philosophy & Layer Overview

FSD v2.1 core principle: "Start simple, extract when needed."

Place code in pages/ first. Duplication across pages is acceptable and does
not automatically require extraction to a lower layer. Extract only when the
same code is currently being used in multiple places (not hypothetically),
the usages do not always change together, and the boundary has a focused
responsibility.

Not all layers are required. Most projects can start with only shared/,
pages/, and app/. Add features/ and entities/ only when they provide
clear value. Do not create empty layer folders "just in case." The widgets/
layer is discouraged (see the callout below).

related skills

semantically similar in the cross-vendor index

clawhub

80% match

Effector Fsd

Use when designing, reviewing, generating, or refactoring Feature-Sliced Design project structure for Effector ecosystem applications: layers, slices, segmen...

don't have the plugin yet? install it then click "run inline in claude" again.