What problem does it solve? Adopting the shadcn-compose library in a Kotlin Multiplatform project risks compile errors from hallucinated component parameters, silent mixing of two design systems, and unnoticed breakage from the experimental Compose Foundation Styles API. This Skill enforces verified-against-source component usage and makes the experimental-API risk explicit before the dependency is added. ## Core Features & Use Cases - Verified component usage: Fetches real Shadcn* composable signatures directly from the shadcn-compose GitHub repo with fetch_component_signature.py, preventing guessed parameters like a nonexistent singleLine on ShadcnTextField. - Theme and preset setup: Guides Maven Central Gradle setup, the ShadcnTheme wrapper, and preset/baseColor/accent selection matched to app type. - Design system audits: Bundled scripts audit component parity, WCAG 2.1 contrast ratios, Compose stability/recomposition issues, render quality, and pixel-level visual diffs. - Use Case: A user asks to add a settings screen with ShadcnCard and ShadcnItemGroup; the Skill confirms the experimental-API risk was accepted, verifies each component's real signature, and generates the screen without double-drawn separators or invented slot composables. ## Quick Start Ask the agent to add shadcn-compose to your KMP project and build a settings screen using ShadcnCard and ShadcnItem components.
