skills.rest
leogallego
leogallegoCOMMUNITY
Explore all skills by this author →
𝕏@leogallegoredGitHub

kotlin-project-architecture-review

Evaluate architecture proposals and modularization for Kotlin Multiplatform projects.

1|Updated Apr 2, 2026
Search Tags:#architecture#android#modularization#kmp#multiplatform#data-layer#state-holder
One-click install
npx skills add https://github.com/leogallego/ansible-jane --skill kotlin-project-architecture-review-leogallego
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kotlin-project-architecture-review
Source: https://github.com/leogallego/ansible-jane/tree/main/skills/kotlin-project-architecture-review
Command: npx skills add https://github.com/leogallego/ansible-jane --skill kotlin-project-architecture-review-leogallego

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviews architecture decisions for Kotlin Multiplatform / Compose Multiplatform projects to ensure maintainability, clear ownership, and durable boundaries across layers.

Core Features & Use Cases

  • Evaluates module boundaries, state-holder strategies, and Android entry-point discipline.
  • Assesses PR structures, migrations, and long-term maintainability decisions.
  • Guides proper layering, domain vs data ownership, and source-set placement.

Quick Start

Analyze a Kotlin Multiplatform project and provide an architectural critique focusing on boundaries, ownership, and evolution.

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 module boundaries and maintainability?▼

To assess Kotlin Multiplatform architecture, evaluate module boundaries, source sets, and layering to ensure clear ownership and safe evolution. It checks domain vs data layers and platform-specific vs shared code for maintainable structure.

What is the best way to structure domain and data layers in a Compose Multiplatform project?▼

Structuring layers in Compose Multiplatform requires separating domain and data ownership across source sets. This ensures a single source of truth and unidirectional data flow, keeping shared code maintainable and diagnosable.

Does this approach evaluate PR structure and migrations for Android entry points?▼

Yes, evaluating PR structure and migrations includes checking Android entry-point discipline and state-holder strategies. This verifies that changes respect module boundaries and maintain durable architectural layers.

Can I use this to assess modularization decisions for a KMP project?▼

Yes, you can assess modularization decisions for KMP projects. It evaluates feature plans and module splits to ensure a clear single source of truth and explicit guidance for future changes across shared code.

Why does my Kotlin Multiplatform architecture lack a single source of truth across modules?▼

Architecture lacks a single source of truth when module boundaries and data ownership are poorly defined across source sets. Evaluating domain vs data layers and state-holder strategies ensures unidirectional data flow and clear ownership.

Related Skills

Explore More Software Engineering Skills→
cesau78cesau78

review-architecture

Audits code modules for duplication, boundary issues, and refactor opportunities.

Community
Intermediate
agnaldo4jagnaldo4j
1

circular-dependency-control

Detect and classify circular dependencies across Kotlin class, package, and Gradle module boundaries.

Community
Advanced
cedric-champeixcedric-champeix
1

kotlin-project-architecture-review

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

Community
Advanced
tmalcolm-0607tmalcolm-0607

lens-aspnet-structure

Enforce 5-layer architecture and dependency rules in LENS ASP.NET Core services.

Community
Advanced