What problem does it solve? When multiple workflows duplicate the same operational logic, bug fixes in one path fail to propagate to others and behavior drifts. This Skill provides a decision framework for splitting code into an orchestration layer (actions owning domain rules) and a service layer (shared operational mechanics). ## Core Features & Use Cases - Two-layer architecture pattern: Actions own business rules, auth, state transitions, and error classification; services own reusable operations like sandbox creation, email sending, and provider interactions. - Extraction guidance: Rules for when to extract shared logic (repeated across 2+ callers) versus when to keep logic in actions (single-caller, domain-specific code). - Migration checklist: A step-by-step process to extract one block, replace one caller, verify, then migrate the rest without breaking flows. - Use Case: You are adding a feature that sends welcome emails and notice the same email-sending logic exists in two other flows. Use this Skill to extract a shared email service while keeping opt-in policy in the actions. ## Quick Start Ask the agent to review your action files and decide which repeated operational logic should move into a shared service layer.
