Loading...
Loading...
Found 22 Skills
Build accessible, unstyled React UI components with Radix Primitives
Add UI polish with layout and styling
Manage design tokens, component libraries, and pattern documentation. Trigger with "design system", "component library", "design tokens", "style guide", or when the user asks about maintaining consistency across designs.
Best practices and example-driven guidance for building SwiftUI views and components. Use when creating or refactoring SwiftUI UI, designing tab architecture with TabView, composing screens, or needing component-specific patterns and examples.
Generate self-contained, beautiful HTML documents that replace walls of markdown. Use this skill whenever the user asks for a report, comparison, explainer, slide deck, diagram, post-mortem, status update, code walkthrough, design system showcase, prototype, or interactive editor — or mentions creating HTML outputs, dashboards, visual documentation, or "instead of markdown". Covers 10 battle-tested patterns: comparison, walkthrough, review, design-system, prototyping, diagram, deck, explainer, report, and editor.
Internal skill. Use cc10x-router for all development tasks.
Advanced Compose Multiplatform UI patterns for shared composables. Use when working with visual UI components, state management patterns (remember, derivedStateOf, produceState), recomposition optimization (@Stable/@Immutable visual usage), Material3 theming, custom ImageVector icons, or determining whether to share UI in commonMain vs keep platform-specific. Delegates navigation to android-expert/desktop-expert. Complements kotlin-expert (handles Kotlin language aspects of state/annotations).
Design user interfaces. Use when creating layouts, wireframes, or UI specifications. Covers design principles and UI patterns.
Creates frosted glass UI elements with blur, transparency, and subtle borders. Use when building overlays, floating controls, tooltips, or any element that should appear elevated with a translucent background.
Quick global settings — currency, language, region, units — belong in a persistent, low-profile location such as a header toolbar or footer. These controls are frequent but not primary, so they use small typography and stay out of the main content hierarchy. Use when designing global selectors, locale switchers, or user preference controls that apply across the whole product.