What problem does it solve?
Implementing new design system components in Compose Multiplatform often leads to inconsistent naming, hardcoded colors, missing dark-mode previews, and non-localizable strings. This Skill enforces the Alkaa Kuvio design system conventions so every new component is theme-aware, localizable, and consistent with existing primitives.
Core Features & Use Cases
- Guided Implementation Workflow: Eight structured steps covering design spec extraction, studying reference components, directory placement, implementation, string externalization, previews, and quality verification.
- Convention Enforcement: Strict rules for Kuvio naming prefixes, MaterialTheme color tokens, composable slot patterns, ~60-line function limits, and PascalCase constants.
- Automated Quality Verification: A shell script runs Gradle compilation and detekt/ktlint static analysis on the designsystem module.
- Use Case: After finalizing a design spec for a new task chip, use this Skill to scaffold KuvioTaskChip with proper slots, light/dark previews, externalized strings, and passing lint checks.
Quick Start
Implement a new Kuvio badge component for the Alkaa design system following the finalized design spec, with light and dark previews and verified code quality.