mobile-design

Standardize mobile-first design guidelines across iOS and Android platforms.

1|1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/zzafergok/skills --skill mobile-design-zzafergok
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mobile-design
Source: https://github.com/zzafergok/skills/tree/main/03-mobile-development/mobile-design
Command: npx skills add https://github.com/zzafergok/skills --skill mobile-design-zzafergok

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Mobile teams often apply desktop-centric design thinking to apps, leading to inconsistent experiences, poor performance, and hard-to-maintain interfaces. This guide standardizes mobile-first, touch-aware constraints and platform conventions to prevent cross-platform drift.

Core Features & Use Cases

  • A structured decision framework (MFRI) to assess feasibility and risk before building features.
  • Mandatory pre-work: explicit platform, framework, navigation, offline, and device considerations.
  • Extensive reference readings, anti-patterns, and platform unification guidance to align teams.
  • Release readiness and checkpoint processes to ensure performance, accessibility, and reliability.

Quick Start

Follow the Mobile Design System guidelines before coding to align on platform targets and performance expectations.

Frequently Asked Questions about mobile-design

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

FAQPage Schema
How do I maintain platform consistency across iOS and Android mobile apps?

To maintain platform consistency across iOS and Android, apply a mobile-first design system that standardizes touch-aware constraints, navigation patterns, and platform conventions to prevent cross-platform drift.

What is mobile design debt and how do I reduce it in native and cross-platform apps?

Mobile design debt occurs when desktop-centric thinking is applied to mobile apps. You reduce it by standardizing mobile-first guidelines, specifying offline capabilities, and enforcing performance and accessibility constraints during design and code reviews.

How do I assess feasibility and risk before building mobile app features?

Assess feasibility and risk before building mobile app features by using a structured decision framework like MFRI to evaluate explicit platform targets, framework choices, navigation flows, and device considerations.

Does this mobile-first design approach work with React Native and Flutter?

Yes, this mobile-first design approach works with React Native and Flutter. It provides platform-consistent patterns and unification guidance suitable for product teams delivering cross-platform mobile applications.

When should I not use desktop-centric design thinking for mobile interfaces?

You should avoid desktop-centric design thinking for mobile interfaces when building native or cross-platform apps, as it leads to inconsistent experiences, poor performance, and hard-to-maintain UI without offline capability or touch-aware constraints.

What checkpoints should I follow for mobile release readiness?

For mobile release readiness, follow design system checkpoints that verify performance budgeting, accessibility adherence, platform clarity, and offline capability during both code reviews and design reviews.