What problem does it solve?
Writing UI screens in the Alkaa project requires strict adherence to architectural conventions: a three-layer Screen/Loader/Content structure, exclusive use of Kuvio design system components, adaptive two-pane layouts for tablets and desktop, and dark/light previews. This Skill encodes all those rules so generated composables pass review on the first attempt.
Core Features & Use Cases
- Three-layer screen scaffolding: Enforces the public
<Feature>Screen → internal <Feature>Loader (ViewModel injection, state collection) → internal stateless <Feature>Content pattern.
- Adaptive layout guidance: Provides the
isSinglePane flow from NavGraph entry through Loader branching into ListDetailPaneScaffold for list-detail screens on wide windows.
- Design system enforcement: Mandates Kuvio components over raw Material widgets, multiples-of-4 padding, Snackbar over Toast, and dual dark/light previews.
- Use Case: When adding a new settings screen to Alkaa, the Skill produces a stateless Content composable, a Loader that collects ViewModel state via
koinViewModel(), and correct previews, while flagging mistakes like injecting a ViewModel outside the Loader.
Quick Start
Ask the AI to create a new composable screen for an Alkaa feature following the write-composable conventions, for example a task detail screen with adaptive two-pane layout.