build-native-mobile-ui

Implement native mobile UIs with SwiftUI and Jetpack Compose.

9|3|Updated Jun 13, 2026
One-click install
npx skills add https://github.com/Sir-chawakorn/sanook-cli --skill build-native-mobile-ui
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: build-native-mobile-ui
Source: https://github.com/Sir-chawakorn/sanook-cli/tree/main/skills/build-native-mobile-ui
Command: npx skills add https://github.com/Sir-chawakorn/sanook-cli --skill build-native-mobile-ui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the complexity of building high-performance, accessible, and adaptive native mobile interfaces in SwiftUI and Jetpack Compose, preventing common issues like UI jank, state synchronization errors, and poor accessibility.

Core Features & Use Cases

  • Declarative UI Implementation: Provides patterns for efficient list rendering, state hoisting, and navigation stack management.
  • Adaptive Design: Offers guidance on implementing responsive layouts that handle different screen sizes, orientations, and accessibility settings like Dynamic Type.
  • Use Case: Use this skill when you need to build a complex list-detail screen that must adapt to both iPhone and iPad, requires dark mode support, and must pass strict accessibility audits for screen readers.

Quick Start

Use the build-native-mobile-ui skill to implement a state-hoisted list-detail screen in SwiftUI that supports navigation paths and dynamic type.

Frequently Asked Questions about build-native-mobile-ui

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

FAQPage Schema
How do I build adaptive list-detail views in SwiftUI and Jetpack Compose that support different screen sizes?

To build adaptive list-detail views in SwiftUI and Jetpack Compose, you implement declarative UI patterns that support responsive layouts. This approach handles varying screen sizes, orientations, and accessibility settings like Dynamic Type natively.

What is the best way to manage state and type-safe navigation in declarative mobile UI frameworks?

State management and type-safe navigation in declarative mobile UI frameworks are handled through state hoisting and navigation stack management. This prevents state synchronization errors and ensures type safety when routing between screens.

Does this approach support strict accessibility audits for screen readers on iOS and Android?

Yes, building native mobile UI with this approach ensures adherence to accessibility standards for screen readers. It provides specific guidance for implementing accessible screens that pass strict accessibility audits on both platforms.

How do I prevent UI jank and lifecycle errors when implementing native mobile screens?

To prevent UI jank and lifecycle errors in native mobile screens, you apply lifecycle-correct side effects and efficient list rendering patterns. This ensures high-performance UI execution and prevents common declarative state synchronization issues.

Can I use declarative UI patterns to build screens that support dark mode and Dynamic Type?

Yes, you can use declarative UI patterns to build screens supporting dark mode and Dynamic Type. The skill provides guidance on implementing responsive layouts that adapt to different accessibility settings and system appearances.

Why should I use native declarative frameworks instead of cross-platform tools for mobile UI development?

Native declarative frameworks ensure adherence to platform-specific design idioms for iOS and Android. This approach prevents UI jank and poor accessibility by leveraging built-in performance optimizations and native lifecycle management capabilities.