MO

mobile-design

Evaluates mobile design feasibility and interaction complexity using the MFRI framework to prevent desktop-based design patterns.

Install

mkdir -p .claude/skills/mobile-design && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/675" && unzip -o skill.zip -d .claude/skills/mobile-design && rm skill.zip

Installs to .claude/skills/mobile-design

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

(Mobile-First · Touch-First · Platform-Respectful)
50 charsno explicit “when” trigger
Intermediate

Key capabilities

  • →Calculates feasibility using the MFRI score formula
  • →Evaluates platform-specific navigation requirements
  • →Identifies potential performance bottlenecks
  • →Audits accessibility risk levels
  • →Determines necessity of offline-first architecture

How it works

Calculates a numerical risk score based on accessibility, platform clarity, and performance constraints to determine if a design is safe or dangerous.

Inputs & outputs

You give it
Feature description or UI screen plan
You get back
MFRI score and mandated design actions

When to use mobile-design

  • →Assess mobile feasibility of a new feature
  • →Optimize touch interaction patterns
  • →Improve mobile battery usage and performance
  • →Implement offline-capable mobile workflows

About this skill

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.

2. Choose the relevant checks

For a new app, establish platform, framework, audience, device classes, navigation, offline needs and actual output. For existing work, reuse that context. Read only the reference material needed for the changed behavior. User scope and repository instructions take precedence over this skill's suggested ceremony.

3. Mandatory Reference Reading (Enforced)

Reference map (read what the task needs)

FilePurposeStatus
mobile-design-thinking.mdAnti-memorization, context-forcingContext reference
touch-psychology.mdFitts’ Law, thumb zones, gesturesTask-dependent
mobile-performance.md60fps, memory, batteryTask-dependent
mobile-backend.mdOffline sync, push, APIsTask-dependent
mobile-testing.mdDevice & E2E testingTask-dependent
mobile-debugging.mdNative vs JS debuggingTask-dependent

Platform-Specific (Conditional)

PlatformFile
iOSplatform-ios.md
Androidplatform-android.md
Cross-platformBOTH above

Read the relevant platform guidance before changing platform-specific behavior.


4. AI Mobile Anti-Patterns (Hard Bans)

🚫 Performance Sins (Non-Negotiable)

❌ NeverWhy✅ Always
ScrollView for long listsMemory explosionFlatList / FlashList / ListView.builder
Unmeasured row churnMay cause avoidable workProfile identity/state updates; memoize only where useful
Index as keyReorder bugsStable ID
JS-thread animationsJankNative driver / GPU
console.log in prodJS thread blockStrip logs
Blanket memoization claimsCan add complexity without benefitProfile and apply targeted optimization

🚫 Touch & UX Sins

❌ NeverWhy✅ Always
Undersized hit areaMiss tapsUse platform logical units: typically 44pt iOS / 48dp Android
Gesture-only actionExcludes usersButton fallback
No loading stateFeels brokenExplicit feedback
No error recoveryDead endRetry + message
Ignore platform normsMuscle memory brokeniOS ≠ Android

🚫 Security Sins

❌ NeverWhy✅ Always
Tokens in AsyncStorageEasily stolenSecureStore / Keychain
Embedded app secretsCan be extractedKeep server secrets on server; secure per-user credentials
Disabled TLS verificationMITM riskValid platform TLS; pinning only for a justified managed threat model
Log sensitive dataPII leakageNever log secrets

5. Platform Unification vs Divergence Matrix

UNIFY                          DIVERGE
──────────────────────────     ─────────────────────────
Business logic                Navigation behavior
Data models                    Gestures
API contracts                  Icons
Validation                     Typography
Error semantics                Pickers / dialogs

Platform Defaults

ElementiOSAndroid
FontSF ProRoboto
Min touch44pt48dp
BackEdge swipeSystem back
SheetsBottom sheetDialog / sheet
IconsSF SymbolsMaterial Icons

6. Mobile UX Psychology (Non-Optional)

Fitts’ Law (Touch Reality)

  • Finger ≠ cursor
  • Accuracy is low
  • Reach matters more than precision

Rules:

  • Primary CTAs live in thumb zone
  • Destructive actions pushed away
  • No hover assumptions

7. Performance Doctrine

React Native (fixed-height illustrative pattern)

const Row = React.memo(({ item }) => (
  <View><Text>{item.title}</Text></View>
));

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

<FlatList
  data={items}
  renderItem={renderItem}
  keyExtractor={(i) => i.id}
  getItemLayout={(_, i) => ({
    length: ITEM_HEIGHT,
    offset: ITEM_HEIGHT * i,
    index: i,
  })}
/>

Flutter (illustrative static widget)

class Item extends StatelessWidget {
  const Item({super.key});

  @override
  Widget build(BuildContext context) {
    return const Text('Static');
  }
}
  • const everywhere possible
  • Targeted rebuilds only

8. Implementation evidence

State the target platform, changed behavior and checks actually performed. Profile representative devices/data; a static pattern scan cannot measure touch targets, contrast, frame rate, battery, platform navigation or secure storage behavior.

9. Framework choice

Preserve an existing stack unless a change is requested. For new work compare team experience, native integrations, accessibility, deployment policies and measured workload constraints. Expo OTA is bounded by runtime compatibility and store policies; it does not authorize bypassing review or delivering arbitrary native code. No framework is universally fastest or smallest.

10. Release Readiness Checklist

Before Shipping

  • Platform hit targets checked in logical units
  • Offline handled
  • Secure storage used
  • Lists optimized
  • Logs stripped
  • Tested on low-end devices
  • Accessibility labels present
  • Concrete risks and any unavailable checks documented

11. Related Skills

  • frontend-design – Visual systems & components
  • frontend-dev-guidelines – RN/TS architecture
  • backend-dev-guidelines – Mobile-safe APIs
  • error-tracking – Crash & performance telemetry

Final Law: Mobile users are distracted, interrupted, and impatient—often using one hand on a bad network with low battery. Design for that reality, or your app will fail quietly.


When to Use

This skill is applicable to execute the workflow or actions described in the overview.

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Audit helper and limits

Run python scripts/mobile_audit.py . --json from the intended project directory. The helper is read-only, bounded and advisory. It never imports project code and never declares compliance; compliant is null. Exit 2 means incomplete inspection or no detected mobile source. Source-pattern hints can match comments or miss behavior spread across files. Validate findings before editing. No simulator, real-device, screen-reader or GPU run was performed in this catalog review.

Use touch guidance, typography, color, navigation and decisions for focused checks. Code blocks are version-sensitive fragments, not certified complete apps; verify current APIs before execution.

When not to use it

  • →Desktop-only application development
  • →UI tasks where design system already exists and is locked

Limitations

  • →Requires explicit platform definition
  • →Subjective score interpretation may vary if dimensions aren't explicitly provided

How it compares

It forces an objective risk assessment before work begins, rather than letting the agent assume standard desktop patterns.

Compared to similar skills

mobile-design side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
mobile-design (this skill)1496moReviewIntermediate
mobile-games119moNo flagsIntermediate
iOS Animation Graphics Skill07moNo flagsIntermediate
mobile-ios-design2727moNo flagsIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

unity-developer

sickn33

Build Unity games with optimized C# scripts, efficient rendering, and proper asset management. Masters Unity 6 LTS, URP/HDRP pipelines, and cross-platform deployment. Handles gameplay systems, UI implementation, and platform optimization. Use PROACTIVELY for Unity performance issues, game mechanics, or cross-platform builds.

142357

architect-review

sickn33

Master software architect specializing in modern architecture patterns, clean architecture, microservices, event-driven systems, and DDD. Reviews system designs and code changes for architectural integrity, scalability, and maintainability. Use PROACTIVELY for architectural decisions.

109320

angular

sickn33

Modern Angular (v20+) expert with deep knowledge of Signals, Standalone Components, Zoneless applications, SSR/Hydration, and reactive patterns. Use PROACTIVELY for Angular development, component architecture, state management, performance optimization, and migration to modern patterns.

100129

frontend-slides

sickn33

Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to build a presentation, convert a PPT/PPTX to web, or create slides for a talk/pitch. Helps non-designers discover their aesthetic through visual exploration rather than abstract choices.

95195

minecraft-bukkit-pro

sickn33

Master Minecraft server plugin development with Bukkit, Spigot, and Paper APIs. Specializes in event-driven architecture, command systems, world manipulation, player management, and performance optimization. Use PROACTIVELY for plugin architecture, gameplay mechanics, server-side features, or cross-version compatibility.

9078

fastapi-pro

sickn33

Build high-performance async APIs with FastAPI, SQLAlchemy 2.0, and Pydantic V2. Master microservices, WebSockets, and modern Python async patterns. Use PROACTIVELY for FastAPI development, async optimization, or API architecture.

79181

Search skills

Search the agent skills registry