What problem does it solve? Managing images, fonts, and UI strings across Android, iOS, and Desktop often leads to duplicated resources, hardcoded strings, and inconsistent translations. This Skill defines how to use the official Compose Multiplatform composeResources system so all shared resources live once in commonMain and are accessed through the type-safe generated Res accessor. ## Core Features & Use Cases - Shared resource organization: Places images in drawable/, fonts in font/, strings in values/strings.xml, and other files in files/ under commonMain/composeResources. - Type-safe access: Enforces access via the generated Res object with painterResource(), Font(), and stringResource() instead of raw paths or hardcoded literals. - i18n consistency: Requires every supported language to have a values-<locale>/strings.xml containing exactly the same keys as the default file. - Use Case: Add the Dongle font and a welcome string to a Kotlin Multiplatform app, then render them identically on Android, iOS, and Desktop without duplicating files per platform. ## Quick Start Ask the assistant to add a shared image, font, or translatable UI string to the Compose Multiplatform project using composeResources and reference it from a Composable.