Agent skill

Mobile Design

by xenitV1 in xenitV1/Antigravity-Workflows

Mobile-first design thinking and decision-making for iOS and Android apps.

MITAuto-check: notesMobile

Install Mobile Design

skills CLI
$ npx skills add xenitV1/Antigravity-Workflows --skill mobile-design -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install xenitV1/Antigravity-Workflows mobile-design --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/xenitV1/Antigravity-Workflows.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/mobile-design .claude/skills/mobile-design && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
mobile-design
GitHub stars
130
Used in
2 other repos
Token cost
~3.7k tokens
SKILL.md length
971 words
Files
14 (incl. scripts)
Skills in repo
42
Repo updated
First seen
Licence
MIT

At a glance

Mobile-first design thinking and decision-making for iOS and Android apps.

  • Building React Native
  • SKILL.md covers 🔧 Runtime Scripts, 🔴 MANDATORY: Read Reference…, ⚠️ CRITICAL: ASK BEFORE… and 📱 Platform Decision Matrix, plus 6 more sections
  • Runs Python scripts from its folder; calls python
  • Native mobile apps

What it does

Mobile Design is an agent skill from xenitV1/Antigravity-Workflows. 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.

Its SKILL.md is about 3.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 14 other files, including scripts (for example `decision-trees.md`, `mobile-backend.md` and `mobile-color-system.md`).

It sits in Mobile, covering Mobile UI design and Cross-platform mobile apps. It works with iOS, Flutter and React Native. The licence is MIT.

When your agent uses it

  • Building React Native
  • Native mobile apps

Example prompts

  • “/mobile-design”

Requirements

  • Python 3
  • Pre-approved tools (allowed-tools): Read, Glob, Grep, Bash

What it can do on your machine

Read from SKILL.md and the folder at commit f0a1fa7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Glob
    • Grep
    • Bash

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Mobile Design loads about 3.7k tokens when it runs. Until then it costs about 63 tokens; SKILL.md has 971 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~63
When it runs · the whole SKILL.md, loaded when a task matches
~3.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Glob, Grep, Bash

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from xenitV1/Antigravity-Workflows at commit f0a1fa7, republished under its MIT licence (© xenitV1). 971 words, ~3,703 tokens.

Download SKILL.mdSave it as .claude/skills/mobile-design/SKILL.md (or your agent's skills folder). This skill also uses 13 other files; get the full folder from GitHub.
name
mobile-design
description
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.
allowed-tools
Read, Glob, Grep, Bash

Mobile Design System

Philosophy: Touch-first. Battery-conscious. Platform-respectful. Offline-capable. Core Principle: Mobile is NOT a small desktop. THINK mobile constraints, ASK platform choice.


🔧 Runtime Scripts

Execute these for validation (don't read, just run):

ScriptPurposeUsage
scripts/mobile_audit.pyMobile UX & Touch Auditpython scripts/mobile_audit.py <project_path>

🔴 MANDATORY: Read Reference Files Before Working!

⛔ DO NOT start development until you read the relevant files:

Universal (Always Read)
FileContentStatus
mobile-design-thinking.md⚠️ ANTI-MEMORIZATION: Forces thinking, prevents AI defaults⬜ CRITICAL FIRST
touch-psychology.mdFitts' Law, gestures, haptics, thumb zone⬜ CRITICAL
mobile-performance.mdRN/Flutter performance, 60fps, memory⬜ CRITICAL
mobile-backend.mdPush notifications, offline sync, mobile API⬜ CRITICAL
mobile-testing.mdTesting pyramid, E2E, platform-specific⬜ CRITICAL
mobile-debugging.mdNative vs JS debugging, Flipper, Logcat⬜ CRITICAL
mobile-navigation.mdTab/Stack/Drawer, deep linking⬜ Read
mobile-typography.mdSystem fonts, Dynamic Type, a11y⬜ Read
mobile-color-system.mdOLED, dark mode, battery-aware⬜ Read
decision-trees.mdFramework/state/storage selection⬜ Read

🧠 mobile-design-thinking.md is PRIORITY! This file ensures AI thinks instead of using memorized patterns.

Platform-Specific (Read Based on Target)
PlatformFileContentWhen to Read
iOSplatform-ios.mdHuman Interface Guidelines, SF Pro, SwiftUI patternsBuilding for iPhone/iPad
Androidplatform-android.mdMaterial Design 3, Roboto, Compose patternsBuilding for Android
Cross-PlatformBoth abovePlatform divergence pointsReact Native / Flutter

🔴 If building for iOS → Read platform-ios.md FIRST! 🔴 If building for Android → Read platform-android.md FIRST! 🔴 If cross-platform → Read BOTH and apply conditional platform logic!


⚠️ CRITICAL: ASK BEFORE ASSUMING (MANDATORY)

STOP! If the user's request is open-ended, DO NOT default to your favorites.

You MUST Ask If Not Specified:
AspectAskWhy
Platform"iOS, Android, or both?"Affects EVERY design decision
Framework"React Native, Flutter, or native?"Determines patterns and tools
Navigation"Tab bar, drawer, or stack-based?"Core UX decision
State"What state management? (Zustand/Redux/Riverpod/BLoC?)"Architecture foundation
Offline"Does this need to work offline?"Affects data strategy
Target devices"Phone only, or tablet support?"Layout complexity
⛔ AI MOBILE ANTI-PATTERNS (YASAK LİSTESİ)

🚫 These are AI default tendencies that MUST be avoided!

Performance Sins
❌ NEVER DOWhy It's Wrong✅ ALWAYS DO
ScrollView for long listsRenders ALL items, memory explodesUse FlatList / FlashList / ListView.builder
Inline renderItem functionNew function every render, all items re-renderuseCallback + React.memo
Missing keyExtractorIndex-based keys cause bugs on reorderUnique, stable ID from data
Skip getItemLayoutAsync layout = janky scrollProvide when items have fixed height
setState() everywhereUnnecessary widget rebuildsTargeted state, const constructors
Native driver: falseAnimations blocked by JS threaduseNativeDriver: true always
console.log in productionBlocks JS thread severelyRemove before release build
Skip React.memo/constEvery item re-renders on any changeMemoize list items ALWAYS
Touch/UX Sins
❌ NEVER DOWhy It's Wrong✅ ALWAYS DO
Touch target < 44pxImpossible to tap accurately, frustratingMinimum 44pt (iOS) / 48dp (Android)
Spacing < 8px between targetsAccidental taps on neighborsMinimum 8-12px gap
Gesture-only interactionsMotor impaired users excludedAlways provide button alternative
No loading stateUser thinks app crashedALWAYS show loading feedback
No error stateUser stuck, no recovery pathShow error with retry option
No offline handlingCrash/block when network lostGraceful degradation, cached data
Ignore platform conventionsUsers confused, muscle memory brokeniOS feels iOS, Android feels Android
Security Sins
❌ NEVER DOWhy It's Wrong✅ ALWAYS DO
Token in AsyncStorageEasily accessible, stolen on rooted deviceSecureStore / Keychain / EncryptedSharedPreferences
Hardcode API keysReverse engineered from APK/IPAEnvironment variables, secure storage
Skip SSL pinningMITM attacks possiblePin certificates in production
Log sensitive dataLogs can be extractedNever log tokens, passwords, PII
Architecture Sins
❌ NEVER DOWhy It's Wrong✅ ALWAYS DO
Business logic in UIUntestable, unmaintainableService layer separation
Global state for everythingUnnecessary re-renders, complexityLocal state default, lift when needed
Deep linking as afterthoughtNotifications, shares brokenPlan deep links from day one
Skip dispose/cleanupMemory leaks, zombie listenersClean up subscriptions, timers

Show full SKILL.md (363 more words)Show less

📱 Platform Decision Matrix

When to Unify vs Diverge
                    UNIFY (same on both)          DIVERGE (platform-specific)
                    ───────────────────           ──────────────────────────
Business Logic      ✅ Always                     -
Data Layer          ✅ Always                     -
Core Features       ✅ Always                     -
                    
Navigation          -                             ✅ iOS: edge swipe, Android: back button
Gestures            -                             ✅ Platform-native feel
Icons               -                             ✅ SF Symbols vs Material Icons
Date Pickers        -                             ✅ Native pickers feel right
Modals/Sheets       -                             ✅ iOS: bottom sheet vs Android: dialog
Typography          -                             ✅ SF Pro vs Roboto (or custom)
Error Dialogs       -                             ✅ Platform conventions for alerts
Quick Reference: Platform Defaults
ElementiOSAndroid
Primary FontSF Pro / SF CompactRoboto
Min Touch Target44pt × 44pt48dp × 48dp
Back NavigationEdge swipe leftSystem back button/gesture
Bottom Tab IconsSF SymbolsMaterial Symbols
Action SheetUIActionSheet from bottomBottom Sheet / Dialog
ProgressSpinnerLinear progress (Material)
Pull to RefreshNative UIRefreshControlSwipeRefreshLayout

🧠 Mobile UX Psychology (Quick Reference)

Fitts' Law for Touch
Desktop: Cursor is precise (1px)
Mobile:  Finger is imprecise (~7mm contact area)

→ Touch targets MUST be 44-48px minimum
→ Important actions in THUMB ZONE (bottom of screen)
→ Destructive actions AWAY from easy reach
Thumb Zone (One-Handed Usage)
┌─────────────────────────────┐
│      HARD TO REACH          │ ← Navigation, menu, back
│        (stretch)            │
├─────────────────────────────┤
│      OK TO REACH            │ ← Secondary actions
│       (natural)             │
├─────────────────────────────┤
│      EASY TO REACH          │ ← PRIMARY CTAs, tab bar
│    (thumb's natural arc)    │ ← Main content interaction
└─────────────────────────────┘
        [  HOME  ]
Mobile-Specific Cognitive Load
DesktopMobile Difference
Multiple windowsONE task at a time
Keyboard shortcutsTouch gestures
Hover statesNO hover (tap or nothing)
Large viewportLimited space, scroll vertical
Stable attentionInterrupted constantly

For deep dive: touch-psychology.md


⚡ Performance Principles (Quick Reference)

React Native Critical Rules
typescript
// ✅ CORRECT: Memoized renderItem + React.memo wrapper
const ListItem = React.memo(({ item }: { item: Item }) => (
  <View style={styles.item}>
    <Text>{item.title}</Text>
  </View>
));

const renderItem = useCallback(
  ({ item }: { item: Item }) => <ListItem item={item} />,
  []
);

// ✅ CORRECT: FlatList with all optimizations
<FlatList
  data={items}
  renderItem={renderItem}
  keyExtractor={(item) => item.id}  // Stable ID, NOT index
  getItemLayout={(data, index) => ({
    length: ITEM_HEIGHT,
    offset: ITEM_HEIGHT * index,
    index,
  })}
  removeClippedSubviews={true}
  maxToRenderPerBatch={10}
  windowSize={5}
/>
Flutter Critical Rules
dart
// ✅ CORRECT: const constructors prevent rebuilds
class MyWidget extends StatelessWidget {
  const MyWidget({super.key}); // CONST!

  @override
  Widget build(BuildContext context) {
    return const Column( // CONST!
      children: [
        Text('Static content'),
        MyConstantWidget(),
      ],
    );
  }
}

// ✅ CORRECT: Targeted state with ValueListenableBuilder
ValueListenableBuilder<int>(
  valueListenable: counter,
  builder: (context, value, child) => Text('$value'),
  child: const ExpensiveWidget(), // Won't rebuild!
)
Animation Performance
GPU-accelerated (FAST):     CPU-bound (SLOW):
├── transform               ├── width, height
├── opacity                 ├── top, left, right, bottom
└── (use these ONLY)        ├── margin, padding
                            └── (AVOID animating these)

For complete guide: mobile-performance.md


📝 CHECKPOINT (MANDATORY Before Any Mobile Work)

Before writing ANY mobile code, you MUST complete this checkpoint:

🧠 CHECKPOINT:

Platform:   [ iOS / Android / Both ]
Framework:  [ React Native / Flutter / SwiftUI / Kotlin ]
Files Read: [ List the skill files you've read ]

3 Principles I Will Apply:
1. _______________
2. _______________
3. _______________

Anti-Patterns I Will Avoid:
1. _______________
2. _______________

Example:

🧠 CHECKPOINT:

Platform:   iOS + Android (Cross-platform)
Framework:  React Native + Expo
Files Read: touch-psychology.md, mobile-performance.md, platform-ios.md, platform-android.md

3 Principles I Will Apply:
1. FlatList with React.memo + useCallback for all lists
2. 48px touch targets, thumb zone for primary CTAs
3. Platform-specific navigation (edge swipe iOS, back button Android)

Anti-Patterns I Will Avoid:
1. ScrollView for lists → FlatList
2. Inline renderItem → Memoized
3. AsyncStorage for tokens → SecureStore

🔴 Can't fill the checkpoint? → GO BACK AND READ THE SKILL FILES.


🔧 Framework Decision Tree

WHAT ARE YOU BUILDING?
        │
        ├── Need OTA updates + rapid iteration + web team
        │   └── ✅ React Native + Expo
        │
        ├── Need pixel-perfect custom UI + performance critical
        │   └── ✅ Flutter
        │
        ├── Deep native features + single platform focus
        │   ├── iOS only → SwiftUI
        │   └── Android only → Kotlin + Jetpack Compose
        │
        ├── Existing RN codebase + new features
        │   └── ✅ React Native (bare workflow)
        │
        └── Enterprise + existing Flutter codebase
            └── ✅ Flutter

For complete decision trees: decision-trees.md


📋 Pre-Development Checklist

Before Starting ANY Mobile Project
  • Platform confirmed? (iOS / Android / Both)
  • Framework chosen? (RN / Flutter / Native)
  • Navigation pattern decided? (Tabs / Stack / Drawer)
  • State management selected? (Zustand / Redux / Riverpod / BLoC)
  • Offline requirements known?
  • Deep linking planned from day one?
  • Target devices defined? (Phone / Tablet / Both)
Before Every Screen
  • Touch targets ≥ 44-48px?
  • Primary CTA in thumb zone?
  • Loading state exists?
  • Error state with retry exists?
  • Offline handling considered?
  • Platform conventions followed?
Before Release
  • console.log removed?
  • SecureStore for sensitive data?
  • SSL pinning enabled?
  • Lists optimized (memo, keyExtractor)?
  • Memory cleanup on unmount?
  • Tested on low-end devices?
  • Accessibility labels on all interactive elements?

📚 Reference Files

For deeper guidance on specific areas:

FileWhen to Use
mobile-design-thinking.mdFIRST! Anti-memorization, forces context-based thinking
touch-psychology.mdUnderstanding touch interaction, Fitts' Law, gesture design
mobile-performance.mdOptimizing RN/Flutter, 60fps, memory/battery
platform-ios.mdiOS-specific design, HIG compliance
platform-android.mdAndroid-specific design, Material Design 3
mobile-navigation.mdNavigation patterns, deep linking
mobile-typography.mdType scale, system fonts, accessibility
mobile-color-system.mdOLED optimization, dark mode, battery
decision-trees.mdFramework, state, storage decisions

Remember: Mobile users are impatient, interrupted, and using imprecise fingers on small screens. Design for the WORST conditions: bad network, one hand, bright sun, low battery. If it works there, it works everywhere.

© xenitV1, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 13 other files (scripts) in skills/mobile-design of xenitV1/Antigravity-Workflows.

  • SKILL.md
  • decision-trees.md
  • mobile-backend.md
  • mobile-color-system.md
  • mobile-debugging.md
  • mobile-design-thinking.md
  • mobile-navigation.md
  • mobile-performance.md
  • mobile-testing.md
  • mobile-typography.md
  • platform-android.md
  • platform-ios.md
  • scripts/mobile_audit.py
  • touch-psychology.md

Open the folder on GitHubat commit f0a1fa7

Used in 2 other repositories

We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in xenitV1/Antigravity-Workflows, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Mobile Design next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Mobile Design compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Mobile Design this skillxenitV1/Antigravity-Workflows1302 repos~3.7kAutomated safety check: NotesMIT
Mobile Designagent-skills-hub/agent-skills-hub111—~2.3kAutomated safety check: NotesMIT
Oma Mobilefirst-fluke/oh-my-agent1.3k—~2.4kAutomated safety check: PassMIT
Developing Mobile Appstelagod/code-abyss243—~258Automated safety check: PassMIT
Mobile Designirahardianto/awesome-agv157—~1.2kAutomated safety check: PassMIT
Mobile Apps Createforcedotcom/sf-skills1.1k—~1.4kAutomated safety check: PassApache-2.0

Similar skills

  • Mobile Design

    agent-skills-hub/agent-skills-hub

    Mobile-first design and engineering doctrine for iOS and Android apps.

    111 GitHub stars~2.3k tokensUpdated 7 days ago
    MobileAuto-check: notes
  • Oma Mobile

    first-fluke/oh-my-agent

    Implement Flutter, React Native, or native Swift apps. An agent skill from first-fluke/oh-my-agent.

    1.3k GitHub stars~2.4k tokensUpdated today
    MobileAuto-check passed
  • Developing Mobile Apps

    telagod/code-abyss

    Mobile development knowledge reference covering iOS (SwiftUI), Android (Jetpack Compose), React Native, and Flutter.

    243 GitHub stars~258 tokensUpdated 2 mo ago
    MobileAuto-check passed
  • Mobile Design

    irahardianto/awesome-agv

    Generates distinctive, production-grade mobile interfaces for Flutter and React Native.

    157 GitHub stars~1.2k tokensUpdated 4 days ago
    MobileAuto-check passed
  • Mobile Apps Create

    forcedotcom/sf-skills

    The entry point for building any Salesforce native mobile app on iOS or Android.

    1.1k GitHub stars~1.4k tokensUpdated 2 days ago
    MobileAuto-check passed
  • Apple Design

    vrcm-team/VRCM

    Cross-platform UI/UX design reviewer grounded in Apple's Human Interface Guidelines (122 pages pulled from developer.apple.com, including 57 component pages) plus a design-craft lens for…

    179 GitHub starsUsed in 1 repo~6.2k tokens
    MobileAuto-check passed

More from xenitV1/Antigravity-Workflows

All 42 skills in this repo
  • Parallel Agents

    xenitV1/Antigravity-Workflows

    Native multi-agent orchestration using Claude Code's Agent Tool.

    130 GitHub starsUsed in 9 repos~1.3k tokens
    Auto-check passed
  • Bash Linux

    xenitV1/Antigravity-Workflows

    Bash/Linux terminal patterns. An agent skill from xenitV1/Antigravity-Workflows.

    130 GitHub starsUsed in 8 repos~1k tokens
    Auto-check: notes
  • Performance Profiling

    xenitV1/Antigravity-Workflows

    Performance profiling principles. An agent skill from xenitV1/Antigravity-Workflows.

    130 GitHub starsUsed in 8 repos~772 tokens
    Auto-check: notes
  • Plan Writing

    xenitV1/Antigravity-Workflows

    Structured task planning with clear breakdowns, dependencies, and verification criteria.

    130 GitHub starsUsed in 8 repos~994 tokens
    Auto-check passed
  • Behavioral Modes

    xenitV1/Antigravity-Workflows

    AI operational modes (brainstorm, implement, debug, review, teach, ship, orchestrate).

    130 GitHub starsUsed in 7 repos~1.3k tokens
    Auto-check passed
  • I18n Localization

    xenitV1/Antigravity-Workflows

    Internationalization and localization patterns. An agent skill from xenitV1/Antigravity-Workflows.

    130 GitHub starsUsed in 7 repos~758 tokens
    Auto-check passed

Categories

Questions about Mobile Design

What does Mobile Design do?

Mobile-first design thinking and decision-making for iOS and Android apps. Mobile Design is an agent skill from xenitV1/Antigravity-Workflows. Mobile-first design thinking and decision-making for iOS and Android apps.

When should I use Mobile Design?

Mobile Design fits situations like: building React Native; native mobile apps.

How do I install Mobile Design in Claude Code?

Run `npx skills add xenitV1/Antigravity-Workflows --skill mobile-design -a claude-code`. Or copy the skill folder (skills/mobile-design in xenitV1/Antigravity-Workflows) into .claude/skills/mobile-design in your project. Claude Code loads it when a task matches its description.

How do I install Mobile Design in Codex?

Run `npx skills add xenitV1/Antigravity-Workflows --skill mobile-design -a codex`. Or copy the skill folder (skills/mobile-design in xenitV1/Antigravity-Workflows) into .agents/skills/mobile-design in your project. Codex loads it when a task matches its description.

Can I use Mobile Design in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add xenitV1/Antigravity-Workflows --skill mobile-design -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/mobile-design, .gemini/skills/mobile-design, .github/skills/mobile-design and .opencode/skills/mobile-design in your project.

What does Mobile Design need to run?

Going by SKILL.md and its folder, Mobile Design needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3. Its frontmatter pre-approves these tools: Read, Glob, Grep, Bash.

Does Mobile Design access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Mobile Design safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Mobile Design use?

Mobile Design is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Mobile Design use?

About 3.7k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Mobile Design?

Skills that share tags, products or a category with Mobile Design: Mobile Design (agent-skills-hub/agent-skills-hub, 111 stars), Oma Mobile (first-fluke/oh-my-agent, 1.3k stars), Developing Mobile Apps (telagod/code-abyss, 243 stars) and Mobile Design (irahardianto/awesome-agv, 157 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Mobile Design?

xenitV1 (a GitHub user) maintains it in xenitV1/Antigravity-Workflows, which has 130 GitHub stars. The repository holds 42 skills in this directory. The repository was last updated on January 14, 2026.

Source: xenitV1/Antigravity-Workflows on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.