mobile-design
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.
This skill is part of a pack
Install the whole pack to get every skill the task needs, in one command.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "mobile-design" from https://skillstore.io/skills/sickn33-mobile-design.md and its manifest at https://skillstore.io/api/skills/sickn33-mobile-design/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "mobile-design". Review a checkout screen for both iOS and Android.
Expected outcome:
- Place the primary payment action within the lower thumb zone.
- Use platform-native back behavior and preserve entered form data.
- Provide loading, retry, offline, validation, and payment failure states.
- Verify touch targets, screen-reader labels, text scaling, and contrast.
Using "mobile-design". Audit a React Native product list with slow scrolling.
Expected outcome:
- Prioritize list virtualization and stable item identifiers.
- Check item memoization, render callback stability, image sizing, and logging.
- Profile on a low-end physical device before accepting performance changes.
Using "mobile-design". Plan navigation for a cross-platform account area.
Expected outcome:
Use shared information architecture with platform-native back behavior, deep links, state restoration, accessible labels, and explicit authentication boundaries.
Security Audit
SafeAll 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.
Risk Factors
🌐 Network access (3)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-mobile-design/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-mobile-design?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-mobile-design?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-mobile-design/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-mobile-design.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
sickn33. (2026). mobile-design security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-mobile-design/audits/5BibTeX citation
@techreport{sickn33-sickn33-mobile-design-2026,
author = {sickn33},
title = {mobile-design security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/sickn33-mobile-design/audits/5},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "mobile-design security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-08-04"
url: "https://skillstore.io/skills/sickn33-mobile-design/audits/5"
identifiers:
- type: other
value: "skillstore:sickn33-mobile-design:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
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.
Try These Prompts
Review this [screen description] for [iOS, Android, or both]. Check touch targets, accessibility, feedback, loading, errors, and platform conventions.
Analyze this [user flow] built with [framework]. Recommend navigation, gesture alternatives, offline states, error recovery, and platform-specific changes.
Audit this [project or file set] for React Native or Flutter mobile risks. Prioritize findings by user impact and explain required validation.
Plan [feature] for [platforms] using [framework]. Include feasibility scoring, navigation, data synchronization, security, performance budgets, accessibility, tests, and release checks.
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.
Avoid
- 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.