compose-ui

Name: compose-ui
Author: hanamizuki

104stars8forks

How to install compose-ui?

hanamizuki/solopreneur/compose-ui

$npx -y skills add hanamizuki/solopreneur --skill compose-ui

Installs into the current project.

Summary

Best practices for building UI with Jetpack Compose, focusing on state hoisting, detailed performance optimizations, and theming. Use this when writing or refactoring Composable functions.

Files · 1

View on GitHub

SKILL.md

1	# Jetpack Compose Best Practices
2
3	## Instructions
4
5	Follow these guidelines to create performant, reusable, and testable Composables.
6
7	### 1. State Hoisting (Unidirectional Data Flow)
8	Make Composables stateless whenever possible by moving state to the caller.
9
10	* Pattern: Function signature should usually look like:
11	```kotlin
12	@Composable
13	fun MyComponent(
14	value: String, // State flows down
15	onValueChange: (String) -> Unit, // Events flow up
16	modifier: Modifier = Modifier // Standard modifier parameter
17	)
18	```
19	* Benefit: Decouples the UI from simple state storage, making it easier to preview and test.
20	* ViewModel Integration: The screen-level Composable retrieves state from the ViewModel (`viewModel.uiState.collectAsStateWithLifecycle()`) and passes it down.
21
22	### 2. Modifiers
23	* Default Parameter: Always provide a `modifier: Modifier = Modifier` as the first optional parameter.
24	* Application: Apply this `modifier` to the root layout element of your Composable.
25	* 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.
26
27	### 3. Performance Optimization
28	* `remember`: Use `remember { ... }` to cache expensive calculations across recompositions.
29	* `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.
30	```kotlin
31	val showButton by remember {
32	derivedStateOf { listState.firstVisibleItemIndex > 0 }
33	}
34	```
35	* Lambda Stability: Prefer method references (e.g., `viewModel::onEvent`) or remembered lambdas to prevent unstable types from triggering recomposition of children.
36
37	### 4. Theming and Resources
38	* Use `MaterialTheme.colorScheme` and `MaterialTheme.typography` instead of hardcoded colors or text styles.
39	* Organize simple UI components into specific files (e.g., `DesignSystem.kt` or `Components.kt`) if they are shared across features.
40
41	### 5. Previews
42	* Create a private preview function for every public Composable.
43	* Use `@Preview(showBackground = true)` and include Light/Dark mode previews if applicable.
44	* Pass dummy data (static) to the stateless Composable for the preview.

People who liked this also viewed

6 picks

Type

web-design-guidelinesReview UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".SkillsJul 2026483k29k
lark-slides飞书幻灯片：创建和编辑幻灯片。创建演示文稿、读取幻灯片内容、管理幻灯片页面（创建、删除、读取、局部替换）。当用户需要创建或编辑幻灯片、读取或修改单个页面时使用。当用户给出 doubao.com 的 /slides/ URL/token 时，也应直接使用本 skill，不要因为域名不是飞书而回退到 WebFetch；路由依据是 URL 路径模式和 token，而不是域名。不负责：云文档内容编辑（走 SkillsJul 2026332k16k
design-taste-frontendTaste-Skill - gives your AI good taste. stops the AI from generating boring, generic slop SkillsJul 2026280k66k
ui-ux-pro-maxUI/UX design intelligence for web and mobile. Searchable local database with 84 styles, 192 color palettes, 74 font pairings, 192 product types, 98 UX guidelines, 104 icon entries, 16 GSAP motion presSkillsJul 2026280k109k
caveman-helpQuick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".SkillsJul 2026249k92k
codebase-designShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-nSkillsJul 2026225k182k

compose-ui

104stars8forks

View on GitHub

How to install compose-ui?

hanamizuki/solopreneur/compose-ui

$npx -y skills add hanamizuki/solopreneur --skill compose-ui

Installs into the current project.

Summary

Best practices for building UI with Jetpack Compose, focusing on state hoisting, detailed performance optimizations, and theming. Use this when writing or refactoring Composable functions.

Files · 1

View on GitHub

SKILL.md

1	# Jetpack Compose Best Practices
2
3	## Instructions
4
5	Follow these guidelines to create performant, reusable, and testable Composables.
6
7	### 1. State Hoisting (Unidirectional Data Flow)
8	Make Composables stateless whenever possible by moving state to the caller.
9
10	* Pattern: Function signature should usually look like:
11	```kotlin
12	@Composable
13	fun MyComponent(
14	value: String, // State flows down
15	onValueChange: (String) -> Unit, // Events flow up
16	modifier: Modifier = Modifier // Standard modifier parameter
17	)
18	```
19	* Benefit: Decouples the UI from simple state storage, making it easier to preview and test.
20	* ViewModel Integration: The screen-level Composable retrieves state from the ViewModel (`viewModel.uiState.collectAsStateWithLifecycle()`) and passes it down.
21
22	### 2. Modifiers
23	* Default Parameter: Always provide a `modifier: Modifier = Modifier` as the first optional parameter.
24	* Application: Apply this `modifier` to the root layout element of your Composable.
25	* 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.
26
27	### 3. Performance Optimization
28	* `remember`: Use `remember { ... }` to cache expensive calculations across recompositions.
29	* `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.
30	```kotlin
31	val showButton by remember {
32	derivedStateOf { listState.firstVisibleItemIndex > 0 }
33	}
34	```
35	* Lambda Stability: Prefer method references (e.g., `viewModel::onEvent`) or remembered lambdas to prevent unstable types from triggering recomposition of children.
36
37	### 4. Theming and Resources
38	* Use `MaterialTheme.colorScheme` and `MaterialTheme.typography` instead of hardcoded colors or text styles.
39	* Organize simple UI components into specific files (e.g., `DesignSystem.kt` or `Components.kt`) if they are shared across features.
40
41	### 5. Previews
42	* Create a private preview function for every public Composable.
43	* Use `@Preview(showBackground = true)` and include Light/Dark mode previews if applicable.
44	* Pass dummy data (static) to the stateless Composable for the preview.

People who liked this also viewed

6 picks

Type