kuvio

Implement Kuvio components for the Alkaa Design System using Compose Multiplatform.

1.6k|163|Updated Jan 10, 2018
One-click install
npx skills add https://github.com/igorescodro/alkaa --skill kuvio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kuvio
Source: https://github.com/igorescodro/alkaa/tree/main/.claude/skills/kuvio
Command: npx skills add https://github.com/igorescodro/alkaa --skill kuvio

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of translating finalized design specifications into reusable, theme-aware Compose Multiplatform components within the Alkaa Design System.

Core Features & Use Cases

  • Component Implementation: Follows strict naming, structure, and styling conventions for Kuvio components.
  • Design Spec Translation: Ensures components accurately reflect finalized design decisions.
  • Use Case: After a new button design is approved in the Alkaa Design System, use this Skill to implement it as a KuvioButton composable, ensuring it's theme-aware and follows all established patterns.

Quick Start

Implement the new Kuvio component by following the workflow outlined in the SKILL.md file, starting with extracting the design spec.

Frequently Asked Questions about kuvio

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement Compose Multiplatform components from a design system specification?

To implement Compose Multiplatform components, you translate finalized design specifications into theme-aware composables by following strict naming, code structure, and styling conventions for reusable UI primitives.

What is the process for translating an approved design into a Kotlin UI component?

Translating an approved design into a Kotlin UI component involves extracting the design spec, then creating a composable that adheres to established patterns, externalizes strings, and ensures full theme-awareness.

Does this workflow support text, icons, cards, and dialogs in Kotlin UI development?

Yes, this workflow supports text, icons, cards, and dialogs in Kotlin UI development, providing specific guidance on structuring these categories as reusable and theme-aware primitives within the design system.

Can I use this approach to build reusable primitives for an existing Kotlin design system?

Yes, you can use this approach to build reusable primitives for an existing Kotlin design system. It guides the creation of new components ensuring they strictly follow established naming conventions and theme-awareness.

What are the limitations when adding new composables to a Compose Multiplatform design system?

A key limitation is that new composables must strictly adhere to the design system's finalized specifications. Deviating from established naming conventions, code structure, or skipping externalized strings breaks the component pattern.