kotlin-project-architecture-review

Reviews Kotlin Multiplatform project architecture including layers, state holders, and modularization.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps maintain the structural integrity and long-term maintainability of Kotlin Multiplatform projects, ensuring adherence to best practices and architectural principles.

Core Features & Use Cases

  • Architecture Review: Evaluate the architecture of KMP projects for adherence to best practices.
  • Feature Proposal Analysis: Analyze feature proposals for structural fit and maintainability.
  • PR Structure Validation: Validate the structure of pull requests to ensure they don't introduce architectural issues.
  • Layer Boundaries and State Holder Design: Review the boundaries between layers and the design of state holders.
  • Android Entry-Point Discipline: Ensure Android components are used as lifecycle-bound entry points.
  • Use Case: When developing a KMP project, use this Skill to review the architecture of a new feature before it is implemented.

Quick Start

Run the 'kotlin-project-architecture-review' skill to review the architecture of your KMP project.

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 project architecture for maintainability?

To review Kotlin Multiplatform project architecture for maintainability, evaluate structural integrity, layer boundaries, state holder design, Android entry-point discipline, and source-set placement to ensure adherence to best practices.

What is the best way to validate pull request structure in a KMP project?

Validating pull request structure in a KMP project involves checking that the changes do not introduce architectural issues, verifying modularization, and ensuring proper source-set placement and layer boundary adherence.

How does state holder design affect Kotlin Multiplatform architecture?

State holder design affects Kotlin Multiplatform architecture by dictating how state is managed across layers; reviewing it ensures structural integrity, proper layer boundaries, and long-term project maintainability.

Can I analyze a feature proposal for structural fit before implementing it in Kotlin Multiplatform?

Yes, you can analyze feature proposals for structural fit in Kotlin Multiplatform by evaluating the proposed design against architectural principles, layer boundaries, and source-set placement before implementation.

Why does Android entry-point discipline matter in Kotlin Multiplatform projects?

Android entry-point discipline matters in Kotlin Multiplatform projects because it ensures Android components are used strictly as lifecycle-bound entry points, protecting layer boundaries and overall architectural integrity.

What are the limitations of automated architecture reviews for Kotlin Multiplatform projects?

Automated architecture reviews for Kotlin Multiplatform projects focus strictly on structural integrity and best practices like modularization and source-set placement, meaning they complement but do not replace human judgment on business logic.