slice-decomposition

What problem does it solve?

This Skill helps you decide how to organize new functionality so you do not mix independent screens, overlapping workflows, and shared code into the wrong place.

Core Features & Use Cases

• New slice vs. extension: Decide whether a request should become its own slice or fit into an existing state machine.
• Shared code boundaries: Identify when logic belongs in shared code and when it should stay slice-specific.
• Architecture planning: Use it when decomposing features with multiple screens, entry points, or operations that may be triggered from different places.
• Use Case: A team is adding an edit screen and a delete action for the same entity; this Skill helps separate the edit flow, keep delete reusable, and avoid overloading one slice.

Quick Start

Ask me whether a proposed feature should be a new slice, an extension of an existing slice, or shared code.