kotlin-project-architecture-review

Evaluate Kotlin Multiplatform project architecture for layering, ownership, and module boundaries.

1|Updated Apr 22, 2026
One-click install
npx skills add https://github.com/cedric-champeix/SpoonFeeder --skill kotlin-project-architecture-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kotlin-project-architecture-review
Source: https://github.com/cedric-champeix/SpoonFeeder/tree/main/.claude/skills/kotlin-project-architecture-review
Command: npx skills add https://github.com/cedric-champeix/SpoonFeeder --skill kotlin-project-architecture-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture review for Kotlin Multiplatform projects ensuring maintainability and proper layering.

Core Features & Use Cases

  • Architecture alignment checks for KMP layers, ownership, and source-sets.
  • PR and migration review guidance to prevent coupling and ensure modularization.
  • Use Case: apply the review to a PR introducing a new shared module and validate its boundaries.

Quick Start

Review a Kotlin Multiplatform PR by applying architecture criteria to assess layer boundaries and ownership.

Frequently Asked Questions about kotlin-project-architecture-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review Kotlin Multiplatform architecture for a new shared module?

Review Kotlin Multiplatform architecture by assessing layer boundaries, ownership, and source-sets to ensure proper modularization. Apply these criteria to feature proposals and PRs to validate that shared and platform-specific code maintain correct separation and prevent coupling.

What does SSOT mean in Kotlin Multiplatform project architecture?

SSOT (Single Source of Truth) in KMP architecture ensures that state and logic have one definitive owner. Evaluating SSOT during an architecture review verifies that cross-module placement and state-holder roles maintain data consistency without duplicating shared logic.

Can I use this architecture review for Kotlin migrations and modularization decisions?

Yes, this architecture review applies to Kotlin migrations and modularization decisions. It evaluates cross-module placement, Android entry points, and boundary ownership to prevent coupling, ensuring maintainability when restructuring shared and platform-specific code.

How do I validate state-holder roles and boundaries in a KMP PR?

Validate state-holder roles by applying architecture criteria to assess SSOT, layer boundaries, and ownership within the KMP PR. This review confirms that shared and platform-specific code correctly assigns state management and prevents cross-module coupling.

What is the best way to prevent coupling when introducing shared modules in Kotlin Multiplatform?

The best way to prevent coupling is conducting an architecture review focused on layer boundaries, ownership, and source-sets. Assessing cross-module placement and Android entry points ensures that new shared modules maintain proper modularization and do not violate SSOT.

When do I need an architecture review for Kotlin Multiplatform projects?

You need an architecture review for KMP projects during feature proposals, PR reviews, migrations, and modularization decisions. It ensures maintainability by evaluating correct layering, state-holder roles, and proper ownership across shared and platform-specific code.