Enforces Screen/View/Component layered architecture for Compose Multiplatform projects.
npx skills add https://github.com/AndVl1/claude-plugin --skill compose-arch
Please help me install this Agent Skill. Skill: compose-arch Source: https://github.com/AndVl1/claude-plugin/tree/main/skills/compose-arch Command: npx skills add https://github.com/AndVl1/claude-plugin --skill compose-arch
This skill provides a blueprint for implementing a strict Screen/View/Component layered architecture in Compose Multiplatform projects, ensuring clean separation of concerns and scalable code organization.
Create a new feature by following the feature directory structure, implement a sample screen with corresponding view, component, and use case, and wire up a DI module.
High-intent search queries and answers about installing and using this skill.
To structure a Compose Multiplatform project with strict layered architecture, separate code into Screen adapters, View UI, Component business logic, and Domain layers. This enforces clean separation of concerns and keeps feature slices scalable.
The feature-slice pattern in Compose Multiplatform organizes features into dedicated folders containing api, impl, and di directories. It enforces a one-class-per-file rule to maintain clean architecture and scalable code organization.
Yes, you can use Decompose for component lifecycle management in Compose Multiplatform. The architecture supports Decompose-based components to handle business logic and use cases, ensuring robust lifecycle management.
To wire up a new feature screen in Compose, follow the feature directory structure to implement a sample screen with its corresponding view, component, and use case. You then connect them using a DI module to complete the setup.
The best way to enforce separation of concerns in Kotlin Compose apps is applying a strict Screen, View, Component, and Domain layered architecture. This mandates domain and use-case layering alongside a file-per-class rule for maintainable code.
Compose Multiplatform feature code becomes difficult to maintain when lacking strict architectural discipline. Applying a UseCase, Repository, and DataSource workflow with dedicated feature slices solves this by ensuring clean separation of concerns.
ClankerGuruEvaluate Kotlin Multiplatform adoption and module strategy across JVM, Android, iOS, and JS targets.
kivo360Guide Kotlin development for Android, backend, and multiplatform projects.
QunnnnOrganize Go dependency injection wiring with uber-go/dig constructors.
leogallegoDefine Kotlin Multiplatform state-management contracts for UiState, effects, and actions.
