mobile-design
Mobile-first design doctrine preventing desktop thinking, unsafe assumptions, and AI defaults in iOS and Android development.
- Enforces mandatory platform clarity (iOS, Android, or both) and framework selection before any design or implementation work begins
- Provides Mobile Feasibility & Risk Index (MFRI) scoring system to assess feature viability across platform clarity, interaction complexity, performance, offline dependence, and accessibility
- Bans 15+ common anti-patterns across performance (ScrollView for lists, inline renders, console.log in production), touch UX (sub-44px targets, gesture-only actions), and security (tokens in AsyncStorage, hardcoded secrets)
- Includes platform-specific conventions matrix, Fitts' Law guidance for touch interaction, and required code patterns for React Native (FlatList with memo/useCallback) and Flutter (const widgets)
- Mandates completion of mobile checkpoint and release readiness checklist covering touch targets, offline handling, secure storage, list optimization, and low-end device testing
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. Mobile Feasibility & Risk Index (MFRI)
Before designing or implementing any mobile feature or screen, assess feasibility.
MFRI Dimensions (1–5)
| Dimension | Question |
|---|
More from sickn33/antigravity-awesome-skills
docker-expert
You are an advanced Docker containerization expert with comprehensive, practical knowledge of container optimization, security hardening, multi-stage builds, orchestration patterns, and production deployment strategies based on current industry best practices.
15.0Knodejs-best-practices
Node.js development principles and decision-making. Framework selection, async patterns, security, and architecture. Teaches thinking, not copying.
11.2Ktypescript-expert
TypeScript and JavaScript expert with deep knowledge of type-level programming, performance optimization, monorepo management, migration strategies, and modern tooling.
8.3Kapi-security-best-practices
Implement secure API design patterns including authentication, authorization, input validation, rate limiting, and protection against common API vulnerabilities
7.0Kclean-code
This skill embodies the principles of \"Clean Code\" by Robert C. Martin (Uncle Bob). Use it to transform \"code that works\" into \"code that is clean.\"
6.6Knextjs-best-practices
Next.js App Router principles. Server Components, data fetching, routing patterns.
5.2K