Compose ui

Skill ShinKev/kmp-skill-library/ui/compose-ui

19 Claude AI skills for Kotlin Multiplatform (KMP) & Compose Multiplatform (CMP): architecture, networking, UI, testing, migration & build tooling for Android and iOS.

Install

npx -y skills add ShinKev/kmp-skill-library --skill compose-ui

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Best practices for building UI with Compose Multiplatform (CMP), focusing on state hoisting, performance optimizations, and theming. Shared composables live in commonMain. Use this when writing or refactoring Composable functions in KMP/CMP projects.

SKILL.md

2.8 KB, as published. Nobody here has run it

Compose Multiplatform Best Practices

Instructions

Follow these guidelines to create performant, reusable, and testable Composables.

1. State Hoisting (Unidirectional Data Flow)

Make Composables stateless whenever possible by moving state to the caller.

Pattern: Function signature should usually look like:

@Composable
fun MyComponent(
    value: String,              // State flows down
    onValueChange: (String) -> Unit, // Events flow up
    modifier: Modifier = Modifier // Standard modifier parameter
)

Benefit: Decouples the UI from simple state storage, making it easier to preview and test.
ViewModel Integration: The screen-level Composable retrieves state from the ViewModel. In commonMain, use collectAsState(); in Android-specific composables, collectAsStateWithLifecycle() is preferred. Pass state down as plain values.

2. Modifiers

Default Parameter: Always provide a modifier: Modifier = Modifier as the first optional parameter.
Application: Apply this modifier to the root layout element of your Composable.
Ordering matters: padding().clickable() is different from clickable().padding(). Generally apply layout-affecting modifiers (like padding) after click listeners if you want the padding to be clickable.

3. Performance Optimization

remember: Use remember { ... } to cache expensive calculations across recompositions.
derivedStateOf: Use derivedStateOf { ... } when a state changes frequently (like scroll position) but the UI only needs to react to a threshold or summary (e.g., show "Jump to Top" button). This prevents unnecessary recompositions.
```
val showButton by remember {
    derivedStateOf { listState.firstVisibleItemIndex > 0 }
}
```
Lambda Stability: Prefer method references (e.g., viewModel::onEvent) or remembered lambdas to prevent unstable types from triggering recomposition of children.

4. Theming and Resources

Use MaterialTheme.colorScheme and MaterialTheme.typography instead of hardcoded colors or text styles.
Organize simple UI components into specific files (e.g., DesignSystem.kt or Components.kt) if they are shared across features.

5. Previews

Create a private preview function for every public Composable.
Use @Preview(showBackground = true) and include Light/Dark mode previews if applicable.
Pass dummy data (static) to the stateless Composable for the preview.