Kotlin Multiplatform Modularization

Use this skill when designing, reviewing, or refactoring module boundaries in a Kotlin Multiplatform project.

This skill is intentionally strict. Its purpose is to keep module boundaries meaningful, dependency direction clean, ownership clear, visibility tight, and project growth manageable.

Primary goals

The modularization strategy should optimize for:

• reusability
• strict visibility control
• scalability
• ownership
• encapsulation
• testability
• build performance
• clear app entry points
• separation of platform-specific dependencies from reusable code