What problem does it solve? Jetpack Compose Modifier order silently changes UI behavior: backgrounds paint in the wrong region, click areas leak past visible bounds, clips fail to round corners, and graphicsLayer alpha applies to the wrong subtree. This Skill teaches how to read a Modifier chain top-to-bottom and reorder it correctly. ## Core Features & Use Cases - Chain Diagnosis: Maps symptoms (wrong paint region, wrong click area, wrong clip, wrong measurement, wrong graphicsLayer scope) to the specific reorder that fixes them. - Canonical Patterns: Covers padding vs background, clickable placement for 48dp touch targets, clip before background, graphicsLayer scope, and size vs padding semantics with wrong/right Kotlin examples. - Hoisting Guidance: Explains why remember { Modifier.… } is rarely a real performance win because Compose interns structurally-equal chains, and requires a FrameTimingMetric benchmark before hoisting. - Use Case: A reviewer sees Modifier.padding(16.dp).clickable { } in a diff and uses this Skill to explain why taps in the padding fire the ripple, then reorders the chain to match the design intent. ## Quick Start Ask the AI to review this Compose Modifier chain and explain why the background paints outside the rounded corners, then fix the order.