compose-slot-api-pattern

Replace primitive content parameters and boolean shape flags with @Composable slots to create reusable Jetpack Compose components. This enables flexible, caller-driven layouts instead of hard-coded content shapes across varying visual regions.

A nullable slot in Compose uses the type (@Composable () -> Unit)? = null for optional content. You should use it to provide optional trailing content while avoiding unnecessary layout space when the caller does not supply the slot.

Apply a receiver scope to a Compose slot API to allow layout-aware slot content. This pattern enables the passed composable content to access specific layout scopes, providing contextual awareness within the reusable component's structure.

Manage default values for optional Compose slots by colocating common visuals in a centralized XxxDefaults object. This ensures consistent component styling across multiple call sites while keeping the primary slot parameters clean.

Replace boolean flags with slots in Kotlin UI design when a component has multiple optional content regions across multiple call sites. Converting boolean shape flags into composable slots enables flexible caller-driven layouts instead of rigid visual variations.