# Design Better Mobile Experiences

Mobile interfaces often fail when desktop patterns ignore touch, platform behavior, accessibility, offline use, and device limits. This skill supplies focused guidance and a local source audit.

## Install

```bash
npx skillstore add sickn33/mobile-design
```

## Metadata

- Status: approved
- Slug: sickn33-mobile-design
- Skillstore revision: r2
- Version status: missing
- Tree hash: dbb3c1afb4fa1ebdca63a12426f7588763a9543088a6f19387c032904f6e92d7
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/mobile-design
- Ref: 81e05e636292629114b76cbb3922fbe57672fc02
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: network, external\_commands
- Quality score: 75
- Public page: https://skillstore.pages.dev/skills/sickn33-mobile-design
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-mobile-design/manifest

## Capabilities

- Assesses mobile feature feasibility across platform clarity, interaction complexity, performance, offline use, and accessibility.
- Guides touch targets, thumb-zone placement, gestures, haptics, typography, color, navigation, and platform conventions.
- Compares React Native, Flutter, SwiftUI, and Jetpack Compose choices for stated project needs.
- Reviews mobile performance, secure storage, offline behavior, API design, testing, debugging, and release readiness.
- Audits React Native and Flutter source files with a local Python script using documented heuristic checks.
- Reports detected issues, warnings, passed checks, and an overall compliance result.

## Use Cases

- Review a new mobile screen: Evaluate touch ergonomics, accessibility, platform conventions, loading states, error recovery, and performance before implementation.
- Audit a cross-platform codebase: Identify heuristic React Native or Flutter issues affecting lists, gestures, storage, navigation, typography, offline behavior, and testing.
- Plan release readiness: Create a focused validation checklist for low-end devices, accessibility, secure storage, offline handling, logging, and platform-specific behavior.

## Prompt Templates

### Check one screen

```
Review this [screen description] for [iOS, Android, or both]. Check touch targets, accessibility, feedback, loading, errors, and platform conventions.
```

### Improve a user flow

```
Analyze this [user flow] built with [framework]. Recommend navigation, gesture alternatives, offline states, error recovery, and platform-specific changes.
```

### Audit mobile source

```
Audit this [project or file set] for React Native or Flutter mobile risks. Prioritize findings by user impact and explain required validation.
```

### Design a mobile architecture

```
Plan [feature] for [platforms] using [framework]. Include feasibility scoring, navigation, data synchronization, security, performance budgets, accessibility, tests, and release checks.
```

## Limitations

- The audit script uses regular expressions, so findings require human verification and may include false positives or missed issues.
- The script checks selected JavaScript, TypeScript, JSX, TSX, and Dart files, while skipping native iOS and Android directories.
- Guidance does not replace real-device testing, platform documentation, security review, accessibility testing, or performance profiling.
- Useful recommendations require the target platform, framework, navigation model, offline needs, device range, and audience.

## Best Practices

- State the target platforms, framework, devices, audience, navigation model, and offline requirements before requesting recommendations.
- Validate recommendations with platform guidelines, physical devices, accessibility tools, and performance profilers.
- Treat script findings as review leads, then confirm each issue in its complete source and runtime context.

## Anti Patterns

- Do not apply one identical interaction model to iOS and Android without evaluating platform expectations.
- Do not accept regex audit output as proof of correctness, security, accessibility, or production readiness.
- Do not optimize appearance while ignoring touch reach, loading, recovery, offline behavior, memory, battery, and low-end devices.

## Security Audit

- Audited at: 2026-08-04T14:34:57.855\+00:00
- Summary: All 141 static findings are false positives caused by mobile-platform prose, Markdown backticks, placeholder URLs, regex search terms, and Dart key parameters. The local audit script reads supported source files only within the current workspace and makes no network requests or external command calls. No prompt injection, data exfiltration intent, or other semantic security issue was found.

## Stats

- Views: 179
- Downloads: 22
- Favorites: 0
- Popularity score: 0