← ClaudeAtlas

mobile-app-design-systemlisted

Interview the user about their app, research current mobile UI/UX trends live, then generate one unified iOS + Android design system (not iOS-first) — grid/spacing/safe-area/type-scale math, accessibility floors, visual design (color, materials, iconography, trend-informed styling), a motion spec (duration/easing/spring tokens, Reduce Motion fallback), and a real mockup in the user's actual tooling (SwiftUI/Compose/Flutter/React Native/Framer code, or Figma — never a generic HTML stand-in) with working motion — a few key screens or the full end-to-end app, screen-by-screen — on both platforms side by side. Use whenever the user wants to design a mobile app's UI/UX end to end, wants a modern polished interface with real animation for an app idea or startup, wants current/trendy design, or mentions "design system", "design tokens", "UI/UX flow", "motion design", "8pt grid", or "type scale". Always interview and research live first — never from assumptions, stale trends, or one platform only.
zeiprone/mobile-app-design-system · ★ 0 · Web & Frontend · score 62
Install: claude install-skill zeiprone/mobile-app-design-system
# Mobile App Design System Builder Generates a complete, current, good-looking mobile app design system for a specific app: the structural rules that make an interface work (grid, spacing, safe areas, typography math, accessibility floors) and the visual/UX layer that makes it look like something worth opening today (color, materials, motion, iconography, key-screen mockups, and the flow connecting them) — tailored to the actual app the user is building, not a generic checklist. ## Why interview + live research come first Every real decision here — grid columns, density mode, accessibility rigor, color system, which visual trends actually apply — depends on what the app is, who it's for, what it's built with, and what mobile UI currently looks good in the wild *this year*. Skipping the interview produces a document that looks thorough but doesn't fit the product. Skipping live trend research produces visuals that look dated the moment training-data-era assumptions get baked in instead of verified — mobile design trends (materials, layout styles, motion language) shift meaningfully year over year, and platform vendors rename and redesign their own visual languages often enough that last year's assumption can be flatly wrong. ## Workflow ### 1. Interview Ask the questions in `references/interview-questions.md` — platform(s), design/build tooling, primary use case and content density, brand tone, accessibility rigor, theming, existing constraints (brand colors, reference a