compose-expert

Create shared Compose UI components with Material3 theming for Android and Desktop.

Updated Jan 19, 2026
One-click install
npx skills add https://github.com/kedokato-dev/skill-agent --skill compose-expert-kedokato-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: compose-expert
Source: https://github.com/kedokato-dev/skill-agent/tree/main/compose-expert
Command: npx skills add https://github.com/kedokato-dev/skill-agent --skill compose-expert-kedokato-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The Compose Expert skill helps teams design and reuse cross-platform UI components across Android and Desktop, reducing duplication and ensuring consistent visual patterns.

Core Features & Use Cases

  • Shared composables: centralize common UI components in commonMain to minimize duplication and ensure consistent behavior across platforms.
  • State management: patterns like remember, derivedStateOf, and produceState to optimize recomposition and responsiveness.
  • Theming and visuals: Material3 theming with shared color schemes and typography for a unified look.
  • Iconography: consistent custom ImageVector icons and patterns built from PathData for unified iconography.
  • Platform guidance: advice on when to share UI versus keep platform-specific navigation/UX, with delegation to android-expert and desktop-expert as needed.

Quick Start

Identify a reusable UI component, move it under commons/commonMain, hoist its state, and wire platform-specific wrappers if needed. Then apply Material3 theming and test on both Android and Desktop.

Frequently Asked Questions about compose-expert

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I share Compose UI components across Android and Desktop?

Share Compose UI components by moving them into commonMain, hoisting their state, and applying Material3 theming to ensure consistent behavior across Android and Desktop.

What is the best way to manage state in Kotlin Multiplatform Compose to avoid unnecessary recomposition?

Manage state in Kotlin Multiplatform Compose using patterns like remember, derivedStateOf, and produceState to optimize recomposition and improve responsiveness across shared components.

Does this approach work with Material3 theming and custom ImageVector icons?

Material3 theming works with shared color schemes and typography, while custom ImageVector icons built from PathData ensure consistent iconography across Android and Desktop platforms.

When should I keep platform-specific UI instead of sharing composables in Kotlin Multiplatform?

Keep platform-specific UI when handling navigation or platform APIs, delegating those tasks to android-expert or desktop-expert while centralizing shared visual components in commonMain.

How do I ensure statically typed parameters when building shared Compose UI?

Ensure statically typed parameters in shared Compose UI by enforcing state hoisting and delegating platform-specific navigation and APIs to the appropriate platform experts.