Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
ccheney avatar

Feature Slicing

  • 196 installs
  • 57 repo stars
  • Updated July 7, 2026
  • ccheney/robust-skills

Decompose large product features into thin vertical slices that can be planned, built, reviewed, and shipped incrementally with lower risk.

About

Helps engineers and product owners break complex features into small, end-to-end vertical slices that deliver user value early, simplify reviews, and keep robust software delivery predictable.

  • Vertical slice decomposition
  • Incremental delivery planning
  • Scope reduction without losing value
  • Traceable implementation units
  • Reduced integration risk

Feature Slicing by the numbers

  • 196 all-time installs (skills.sh)
  • Ranked #1,063 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
  • Data as of Aug 3, 2026 (Skillselion catalog sync)
npx skills add https://github.com/ccheney/robust-skills --skill feature-slicing

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs196
repo stars57
Last updatedJuly 7, 2026
Repositoryccheney/robust-skills

What it does

Decompose large product features into thin vertical slices that can be planned, built, reviewed, and shipped incrementally with lower risk.

Files

SKILL.mdMarkdownGitHub ↗

Feature-Sliced Design Architecture

Frontend architecture methodology with strict layer hierarchy and import rules for scalable, maintainable applications. FSD organizes code by business domain rather than technical role.

Official Docs: feature-sliced.design | GitHub: feature-sliced

---

THE IMPORT RULE (Critical)

Modules can ONLY import from layers strictly below them. Never sideways or upward.

app → pages → widgets → features → entities → shared
 ↓      ↓        ↓          ↓          ↓         ✓
 ✓      ✓        ✓          ✓          ✓      (external only)
ViolationExampleFix
Cross-slice (same layer)features/authfeatures/userExtract to entities/ or shared/
Upward importentities/userfeatures/authMove shared code down
Shared importing upshared/entities/Shared has NO internal deps

Exception: app/ and shared/ have no slices, so internal cross-imports are allowed within them.

---

Layer Hierarchy

LayerPurposeHas SlicesRequired
app/Initialization, routing, providers, global stylesNoYes
pages/Route-based screens (one slice per route)YesYes
widgets/Complex reusable UI blocks (header, sidebar)YesNo
features/User interactions with business value (login, checkout)YesNo
entities/Business domain models (user, product, order)YesNo
shared/Project-agnostic infrastructure (UI kit, API client, utils)NoYes

Minimal setup: app/, pages/, shared/ — add other layers as complexity grows.

---

Quick Decision Trees

"Where does this code go?"

Code Placement:
├─ App-wide config, providers, routing    → app/
├─ Full page / route component            → pages/
├─ Complex reusable UI block              → widgets/
├─ User action with business value        → features/
├─ Business domain object (data model)    → entities/
└─ Reusable, domain-agnostic code         → shared/

"Feature or Entity?"

Entity (noun)Feature (verb)
user — user data modelauth — login/logout actions
product — product infoadd-to-cart — adding to cart
comment — comment datawrite-comment — creating comments
order — order recordcheckout — completing purchase

Rule: Entities represent THINGS with identity. Features represent ACTIONS with side effects.

"Which segment?"

Segments (within a slice):
├─ ui/      → React components, styles
├─ api/     → Backend calls, data fetching, DTOs
├─ model/   → Types, schemas, stores, business logic
├─ lib/     → Slice-specific utilities
└─ config/  → Feature flags, constants

Naming: Use purpose-driven names (api/, model/) not essence-based (hooks/, types/).

---

Directory Structure

src/
├── app/                    # App layer (no slices)
│   ├── providers/          # React context, QueryClient, theme
│   ├── routes/             # Router configuration
│   └── styles/             # Global CSS, theme tokens
├── pages/                  # Page slices
│   └── {page-name}/
│       ├── ui/             # Page components
│       ├── api/            # Loaders, server actions
│       ├── model/          # Page-specific state
│       └── index.ts        # Public API
├── widgets/                # Widget slices
│   └── {widget-name}/
│       ├── ui/             # Composed UI
│       └── index.ts
├── features/               # Feature slices
│   └── {feature-name}/
│       ├── ui/             # Feature UI
│       ├── api/            # Feature API calls
│       ├── model/          # State, schemas
│       └── index.ts
├── entities/               # Entity slices
│   └── {entity-name}/
│       ├── ui/             # Entity UI (Card, Avatar)
│       ├── api/            # CRUD operations
│       ├── model/          # Types, mappers, validation
│       └── index.ts
└── shared/                 # Shared layer (no slices)
    ├── ui/                 # Design system components
    ├── api/                # API client, interceptors
    ├── lib/                # Utilities (dates, validation)
    ├── config/             # Environment, constants
    ├── routes/             # Route path constants
    └── i18n/               # Translations

---

Public API Pattern

Every slice MUST expose a public API via index.ts. External code imports ONLY from this file.

// entities/user/index.ts
export { UserCard } from './ui/UserCard';
export { UserAvatar } from './ui/UserAvatar';
export { getUser, updateUser } from './api/userApi';
export type { User, UserRole } from './model/types';
export { userSchema } from './model/schema';
// ✅ Correct
import { UserCard, type User } from '@/entities/user';

// ❌ Wrong
import { UserCard } from '@/entities/user/ui/UserCard';

Avoid wildcard exports — they expose internals and harm tree-shaking:

// ❌
export * from './ui';

// ✅
export { UserCard } from './ui/UserCard';

---

Cross-Entity References (@x Notation)

When entities legitimately reference each other, use the @x notation:

entities/
├── product/
│   ├── @x/
│   │   └── order.ts    # API specifically for order entity
│   └── index.ts
└── order/
    └── model/types.ts  # Imports from product/@x/order
// entities/product/@x/order.ts
export type { ProductId } from '../model/types';

// entities/order/model/types.ts
import type { ProductId } from '@/entities/product/@x/order';

Guidelines: Keep cross-imports minimal. Consider merging entities if references are extensive.

---

Anti-Patterns

Anti-PatternProblemFix
Cross-slice importfeatures/afeatures/bExtract shared logic down
Generic segmentscomponents/, hooks/Use ui/, lib/, model/
Wildcard exportsexport * from './button'Explicit named exports
Business logic in sharedDomain logic in shared/libMove to entities/
Single-use widgetsWidget used by one pageKeep in page slice
Skipping public APIImport from internal pathsAlways use index.ts
Making everything a featureAll interactions as featuresOnly reused actions

---

TypeScript Configuration

{
  "compilerOptions": {
    "baseUrl": ".",
    "paths": {
      "@/*": ["./src/*"]
    }
  }
}

---

Reference Documentation

FilePurpose
references/LAYERS.mdComplete layer specifications, flowcharts
references/PUBLIC-API.mdExport patterns, @x notation, tree-shaking
references/IMPLEMENTATION.mdCode patterns: entities, features, React Query
references/NEXTJS.mdApp Router integration, page re-exports
references/MIGRATION.mdIncremental migration strategy
references/CHEATSHEET.mdQuick reference, import matrix

Resources

Official Sources

  • Official Documentation: https://feature-sliced.design
  • GitHub Organization: https://github.com/feature-sliced
  • Official Examples: https://github.com/feature-sliced/examples
  • Specification: https://feature-sliced.design/docs/reference

Community

  • Awesome FSD: https://github.com/feature-sliced/awesome (curated articles, videos, tools)

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.