Component Boundary Identifier

Analyze a codebase to identify natural boundaries where modules, services, or components can be cleanly separated. This skill applies coupling analysis, cohesion measurement, dependency graph construction, bounded context identification from Domain-Driven Design, and the strangler fig pattern to guide systematic modularization or microservice extraction.

When to Use This Skill

Use this skill when you need to:

• Decompose a monolith into microservices or modular components
• Identify which parts of a codebase should be extracted into separate packages or libraries
• Reduce coupling between modules to improve maintainability
• Plan a migration from monolithic to service-oriented architecture
• Identify bounded contexts in a domain model for DDD implementation
• Evaluate whether a proposed module boundary is clean or will create excessive cross-cutting concerns
• Analyze a codebase before a large-scale refactoring effort
• Apply the strangler fig pattern to incrementally migrate functionality

Trigger phrases: "find module boundaries", "component boundaries", "service extraction", "decompose monolith", "coupling analysis", "cohesion analysis", "bounded context", "strangler fig", "modularization", "microservice boundaries"