
from tech-leads-club
Group components into logical business domains to plan service-based architecture.
This skill analyzes components of a codebase and groups them into logical business domains (e.g., Customer, Billing, Ticketing) to prepare for service extraction and domain-driven refactoring. It provides a step-by-step process: identify domains, assign components, validate groupings, propose namespace refactors, and produce a domain map and refactoring plan.
Use this skill when planning migration to a service-based architecture, performing domain-driven design, or preparing to extract domain services from a monolith. Not intended for creating brand-new domains from scratch or low-level coupling analysis (use specialized coupling-analysis skills instead).
Pure instructional skill for grouping architectural components into business domains for DDD/service-based architecture planning. No scripts or executable code — entirely documentation-based. SKILL.md is thorough but repetitive, with the same examples repeated across sections. Fitness function snippets are illustrative pseudocode, not runnable.
Safe skill — no security concerns whatsoever. Main issue is verbosity and lack of scripts/references separation. The skill reads more like a comprehensive guide than a focused agent skill. Could be improved by extracting patterns and best practices into references/ and keeping SKILL.md lean with triggers and output contracts.