Mobile Design

This is the antidote to treating mobile like "desktop but smaller." It forces you to assess feasibility before designing anything using an MFRI scoring system across platform clarity, performance, and accessibility. The hard bans are especially useful: no ScrollView for long lists, no touch targets under 44px, no tokens in AsyncStorage. It includes mandatory reading checklists that vary by platform (iOS vs Android vs both) and won't let you proceed without explicitly stating framework, navigation pattern, and offline requirements. Best for teams who keep shipping janky lists, broken gestures, or apps that feel like responsive websites crammed into a WebView. The performance doctrine section alone (with actual FlatList and Flutter const patterns) justifies keeping this loaded.

install copies · 90 days. Times the install command was copied on this site in the last 90 days, bots filtered.: 6
skills.sh installs: 3K
GitHub stars: 43.1K
last updated: Jul 14, 2026

View on GitHub

Install

$ npx -y skills add sickn33/antigravity-awesome-skills --skill mobile-design --agent claude-code

Installs into .claude/skills of the current project.

Files

Mobile Design System

(Mobile-First · Touch-First · Platform-Respectful)

Philosophy: Touch-first. Battery-conscious. Platform-respectful. Offline-capable. Core Law: Mobile is NOT a small desktop. Operating Rule: Think constraints first, aesthetics second.

This skill exists to prevent desktop-thinking, AI-defaults, and unsafe assumptions when designing or building mobile applications.

1. Scope and risk

Use the existing project/platform requirements and preserve its conventions. Ask only for missing information that changes the implementation. Do not require an interview or framework switch for a targeted fix. The former MFRI score was an unvalidated heuristic with inconsistent dimensions/range; it is not a safety or release gate. Record concrete interaction, data, accessibility and performance risks instead.