Loading...
Loading...
Found 17 Skills
(Mobile-First · Touch-First · Platform-Respectful)
Mobile-first design and engineering doctrine for iOS and Android apps. Covers touch interaction, performance, platform conventions, offline behavior, and mobile-specific decision-making. Teaches principles and constraints, not fixed layouts. Use for React Native, Flutter, or native mobile apps.
Mobile UX patterns, touch interactions, gesture design, mobile-first principles, app navigation, and mobile performance
Mobile-first design thinking and decision-making for iOS and Android apps. Touch interaction, performance patterns, platform conventions. Teaches principles, not fixed values. Use when building React Native, Flutter, or native mobile apps.
Create distinctive, production-grade mobile interfaces with high design quality using Flutter. Use this skill when the user asks to build mobile apps, screens, widgets, animations, or UI components. Generates creative, polished Flutter code that avoids generic standard widget aesthetics.
Use when the user needs mobile app design and development patterns for React Native, Flutter, or SwiftUI — including platform HIG compliance, gestures, and offline-first architecture. Triggers: user says "mobile", "iOS", "Android", "React Native", "Flutter", "SwiftUI", "app design", "mobile navigation", "touch targets", "offline-first".
Make a web screen feel native inside a phone app — a paywall, an onboarding or quiz, an offer, an update screen, any screen rendered in a WKWebView / Android WebView or shipped as a Superwall surface. The rules a native screen follows and a web page doesn't: press feedback on every control, hover gated to real pointers, 16px inputs and the keyboard, motion with real easing and durations, size-aware type, worst-case content, dark mode from the host, iOS vs Android conventions, and the audit before it ships. Use when building or reviewing any screen of that kind for iOS or Android, with or without a design reference, or when a screen "feels like a website" on a phone. For the Superwall framework's own mechanics (insets, routing, products, push) read superwall-framework; for React Native / Expo screens use the platform's own components instead.
Senior UX/UI Design Director for mobile app design auditing across all platforms (iOS, Android, cross-platform). Triggers on "UI建议", "审美讲义", "交互建议", design audit, UI review, UX audit, or premium design feedback. Provides three-tier proposals (Safe/Balanced/Avant-Garde), aesthetic formulas, motion physics, and brand consistency checks. Specializes in "Young Luxury" mobile experiences grounded in Apple HIG and Material Design 3.
Elite mobile app image-generation skill for creating premium, app-native screen concepts and flows. Designed for iOS, Android, and cross-platform mobile products. Prioritizes clean hierarchy, comfortably readable text, strong multi-screen consistency, controlled color palettes, non-generic creative direction, textured surfaces, image-led composition, tasteful custom iconography, and clean phone mockup framing. By default, screens should be shown inside a subtle premium iPhone or similar phone mockup with a visible frame, while the main focus stays on the app content itself. This skill generates images only. It does not write code.
Comprehensive design guide for web and mobile applications. Contains 50+ styles, 97 color palettes, 57 font pairings, 99 UX guidelines, and 25 chart types. Use when the user requests UI/UX work (design, build, create, implement, review, fix, improve).
Framework (OSS). Build and maintain a design system inside an Expo app - a reusable theme of design tokens (color, spacing, typography, radius, shadow, motion), reusable component structure with variant/size/state prop conventions, and rules for when to extract a repeated view into a shared component. Use when creating or organizing theme files and design tokens (theme.ts / theme/), extending an existing theme or styling library (NativeWind, Tamagui, Restyle, Unistyles) in its own idiom, standardizing styles so screens (including AI-generated ones) look consistent and polished, building an in-app component library, or auditing an app for design-system drift (hardcoded colors, spacing, fonts). For platform styling specifics (semantic colors, HIG rules, native controls) use expo-native-ui; for Tailwind/CSS setup use expo-tailwind-setup; for folder layout of a new app use expo-project-structure.
Use when making design decisions, reviewing UI for HIG compliance, choosing colors/backgrounds/typography, or defending design choices - quick decision frameworks and checklists for Apple Human Interface Guidelines