← ClaudeAtlas

cmp-featurelisted

Use when adding a new screen, feature module or data source to this Compose Multiplatform app — creating or filling feature/<name> with contract, domain, data and presentation layers, a new ViewModel with Route and Content, a repository backed by Ktor, Room or DataStore, a navigation destination, or the Koin wiring for any of these.
whinstudio/skills · ★ 0 · AI & Automation · score 66
Install: claude install-skill whinstudio/skills
# Adding a screen or a feature This project uses one Gradle module per layer: `feature/<name>/{contract,domain,data,presentation}`. The code rules for what goes inside the files are in `cmp-code-rules`. ## 1. Decide where it goes - Something with its own data and its own destination is a feature module. A screen that only shows another view of an existing feature's data goes into that feature's `presentation`. - Look in `settings.gradle.kts` first. The generator may already have created the module. From the template release with the blank guide screen on, every planned feature is a complete module: `contract/Screens.kt` (`<Name>Destination`), `presentation` with `<Name>Screen` (Route + Screen), `<Name>UiState`, `<Name>Actions`, `<Name>ViewModel`, `<Name>Provider` and `<Name>Entry`, and an empty `@Module` in `data` and `domain` — all three registered in `appModules()`. Projects generated before that have starter files only in the first planned feature and empty shells (four `build.gradle.kts`, no sources) for the rest. Fill an existing module; do not create a parallel one. - When Compass started this run, its prompt names the module to use. Follow it. ## 2. Inspect before writing - The four `build.gradle.kts` files of the existing feature: which convention plugin each applies (`libs.plugins.feature.<layer>.plugin`) and which project dependencies it declares. - The package root, read from `contract/Screens.kt`. - The Koin module class(es) under `*/di/` an