feature-sliced-design

What it does

This skill provides an architectural framework for organizing software applications into concentric rings based on user features rather than technical layers. It enables developers to structure codebases where each slice encapsulates its own data, logic, and presentation, promoting modularity and scalability.

When to use it

• Building large-scale applications that require frequent feature additions without disrupting existing functionality.
• Refactoring legacy monolithic codebases into manageable, independent units of business logic.
• Creating teams where different developers work on distinct features with minimal merge conflicts.
• Designing systems where specific domains need strict isolation from core infrastructure concerns.

Key capabilities

• Defines a standard directory structure organizing code by feature boundaries.
• Encourages separation of concerns by isolating data, logic, and view layers per feature.
• Facilitates independent testing and deployment of individual feature slices.
• Reduces coupling between unrelated parts of the application.

Example prompts

• "Generate a project scaffold using feature-sliced-design for an e-commerce platform."
• "Refactor this monolithic user profile module into a standalone feature slice."
• "Explain how to structure a data layer in feature-sliced-design for a payment processing app."

Tips & gotchas

This approach works best when your application has clearly defined business domains; applying it too early in small projects may introduce unnecessary complexity. Ensure team members understand the architectural principles before committing to this structure, as initial setup requires upfront planning.