feature-sliced/documentation resource
Architectural methodology for frontend projects observed · 2026-08-28
Health v2 · maintenance only
67/100
- Activity 98
- Release rhythm 8
- Longevity 100
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 2061
- days_rel: 658
- days_push: 14
- n_releases_24m: 1
Adoption not part of the score
2353 stars · 224 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
Feature-Sliced Design (FSD) is an architectural methodology for organizing frontend application code into layers, slices, and segments, documented as a comprehensive specification and guide site. It is stack-agnostic and includes tooling such as the Steiger architecture linter, CLI folder generators, and LLM-friendly docs (llms.txt, agent skills).
Use cases
- structure a large frontend codebase with clear layers and boundaries
- migrate an existing custom frontend architecture to a standardized methodology
- prevent cross-imports and enforce module boundaries in a React/Vue app
- onboard new developers to a frontend project with a uniform folder structure
- automatically lint project structure against FSD rules with Steiger
- provide FSD conventions to AI coding agents via llms.txt and skills
When to choose
- you are building a frontend application (not a library) that has grown hard to maintain
- your team struggles with tangled imports and unclear module ownership
- you want a stack-agnostic, community-standardized architecture with active documentation
- you expect team growth and need a structure newcomers can quickly understand
When to avoid
- you are building a reusable library or component package rather than an application
- your current architecture works well and the team is small and comfortable
- you need a strict, enforced framework rather than a set of conventions you must apply yourself
Facets
learning-resource · maturity active
documentation developer-tools frontend web-development developer-tools tutorials cross-platform frontend-architecture feature-sliced-design methodology vertical-slices separation-of-concerns code-organization steiger llms-txt architecture web-server
10 sources
- readme: https://github.com/feature-sliced/documentation · fetched 2026-08-28 · 1430fcff0cb2
- homepage: https://fsd.how · fetched 2026-08-29 · edd96746b4e3
- site_page: https://fsd.how/docs/get-started/overview · fetched 2026-08-29 · 5cc9d5b1d4e7
- site_page: https://fsd.how/docs/llms · fetched 2026-08-29 · 8e391b205afc
- site_page: https://fsd.how/docs/reference/layers · fetched 2026-08-29 · 74014036a4ea
- site_page: https://fsd.how/docs/guides/migration/from-custom · fetched 2026-08-29 · 5e9e24da5574
- site_page: https://fsd.how/docs/reference/public-api · fetched 2026-08-29 · ab1fbfc58024
- site_page: https://fsd.how/docs/guides/issues/cross-imports · fetched 2026-08-29 · 7ba25bf76e13
- site_page: https://fsd.how/docs/guides/issues/excessive-entities · fetched 2026-08-29 · d59b25343ca0
- site_page: https://fsd.how/docs/get-started/faq · fetched 2026-08-29 · 165167aeefb2
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| feature-sliced/documentation | main | 67 |
For agents
markdown · JSON · MCP: product_card(name="feature-sliced/documentation")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem