Token导航 LogoToken导航

Agent Skill · 研究检索

mobile-app-design-standards(移动应用程序设计标准)

用于辅助界面设计、视觉规范、排版、配色、布局和交互体验优化。它适合让 Agent 根据产品场景整理页面结构、生成 UI 方案、检查视觉一致性或改进组件层级。使用时需要结合现有品牌、设计系统和用户任务,不应只堆装饰元素;涉及真实页面改动时,应通过截图或浏览器预览检查文本溢出、对齐和响应式表现。

mobile-app-design-standards 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 12,156。

总安装 10,524周安装 249GitHub Stars 21下载 2,832核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:mobile-app-design-standards(移动应用程序设计标准)
来源仓库:https://github.com/awesome-skills/mobile-app-design
仓库路径:skills/mobile-app-design-standards
安装命令:
npx skills add https://github.com/awesome-skills/mobile-app-design --skill 'Mobile App Design Standards'
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/awesome-skills/mobile-app-design --skill 'Mobile App Design Standards'

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

mobile-app-design-standards 用于辅助界面设计、视觉规范和交互体验优化,适合生成 UI 方案或检查一致性。适用于需要整理页面结构或改进组件层级的界面设计场景。使用时需结合品牌和设计系统,避免堆砌装饰元素。涉及真实页面改动时应通过截图或预览检查文本溢出和对齐。

适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/mobile-app-design-standards

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/awesome-skills/mobile-app-design --skill 'Mobi…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

mobile-app-design-standards 怎么安装?

在终端执行 npx skills add https://github.com/awesome-skills/mobile-app-design --skill 'Mobile App Des…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

mobile-app-design-standards 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

mobile-app-design-standards 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

mobile-app-design-standards 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

mobile-app-design-standards 用的人多吗?

公开数据是累计安装 10,524 次,近一周安装 249 次,下载 2,832 次,GitHub 21 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

mobile-app-design-standards 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
mobile-app-design-standards

移动应用程序设计标准 · 本页

10,52421需要联网未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Mobile App Design Standards

Comprehensive guidance for designing mobile applications that follow platform conventions, accessibility standards, and modern UX best practices.

Purpose

Apply platform-specific design guidelines, interaction patterns, and accessibility standards when designing, reviewing, or improving mobile application interfaces. Ensure designs are consistent, accessible, performant, and follow 2026 industry best practices.

When to Use This Skill

Use this skill when:

  • Designing new mobile app screens or features
  • Reviewing existing UI/UX implementations
  • Planning interaction flows and navigation
  • Establishing design systems or style guides
  • Making platform-specific design decisions
  • Optimizing for accessibility or performance
  • Modernizing legacy mobile interfaces

Core Design Principles

Platform-Native Conventions

iOS (Human Interface Guidelines):

  • Navigation: Back button in top-left, primary action in top-right
  • Tab bar at bottom with 3-5 items
  • Large titles for hierarchy
  • System fonts: San Francisco (designed for small sizes)
  • Haptic feedback for confirmations
  • Swipe gestures for navigation

Android (Material Design):

  • Navigation: Back in top-left, overflow menu in top-right
  • Bottom navigation or navigation drawer
  • Floating Action Button (FAB) for primary actions
  • System fonts: Roboto
  • Ripple effects for touch feedback
  • Navigation drawer for hierarchical content

React Native Cross-Platform:

  • Use platform-specific components where behavior differs
  • Respect platform conventions for navigation patterns
  • Test on both iOS and Android devices
  • Consider using React Navigation for platform-aware navigation
  • Use Platform API for conditional rendering

Touch Targets and Spacing

Minimum Sizes:

  • iOS: 44 × 44 points minimum for all interactive elements
  • Android: 48 × 48 dp minimum for all touch targets
  • Spacing between targets: minimum 8dp/pt

Best Practices:

  • Larger targets for primary actions (56dp FAB on Android)
  • Adequate spacing prevents accidental taps
  • Consider thumb zones on large screens
  • Test with actual fingers, not mouse clicks

Typography Standards

Minimum Sizes:

  • Body text: 16sp/pt minimum (14sp absolute minimum)
  • Labels: 11-12pt minimum
  • Avoid text smaller than 11pt for legibility

Hierarchy:

  • Clear visual hierarchy through size, weight, color
  • Consistent scale across the app (e.g., 12/14/16/20/24/32pt)
  • Use platform system fonts unless brand requires custom
  • Support dynamic type (iOS) and font scaling (Android)

Color and Contrast

WCAG Standards:

  • Normal text: 4.5:1 contrast ratio minimum
  • Large text (18pt+): 3:1 contrast ratio minimum
  • UI components: 3:1 contrast ratio for boundaries

Color Usage:

  • Don't rely solely on color to convey information
  • Provide alternative indicators (icons, labels, patterns)
  • Support dark mode where applicable
  • Test color blindness scenarios

Component Architecture

Container/Presentational Pattern

Presentational Components:

  • Focus on rendering UI elements
  • Receive data via props
  • No state management or business logic
  • Highly reusable and testable

Container Components:

  • Handle data fetching and state
  • Manage business logic
  • Pass data to presentational components
  • Connect to app state/context

Atomic Design Methodology

Atoms: Basic building blocks (buttons, inputs, icons)

  • Single-purpose components
  • Highly reusable
  • Consistent styling

Molecules: Simple component groups (form fields, search bars)

  • Combine atoms into functional units
  • Maintain single responsibility

Organisms: Complex component assemblies (headers, cards, forms)

  • Combine molecules and atoms
  • Represent distinct sections

Templates: Page-level layouts

  • Define structure and placement
  • No real content

Pages: Specific instances

  • Real content applied to templates
  • Actual screens in the app

Accessibility (a11y)

Screen Reader Support

Labels and Hints:

  • All interactive elements need accessible labels
  • Use accessibilityLabel (React Native) or contentDescription (Android)
  • Provide hints for complex interactions
  • Announce dynamic content changes

Navigation:

  • Logical focus order (top to bottom, left to right)
  • Skip navigation for repetitive content
  • Clear heading hierarchy
  • Announce screen changes

Cognitive Accessibility

Reduce Cognitive Load:

  • Clear, concise labels (avoid jargon)
  • Consistent patterns throughout app
  • Progressive disclosure (show what's needed)
  • Clear error messages with recovery steps

Focus Management:

  • Highlight focused elements clearly
  • Support keyboard navigation where applicable
  • Maintain focus context during navigation

Performance Optimization

Perceived Performance

Loading States:

  • Skeleton screens for content loading
  • Progress indicators for operations >1 second
  • Optimistic UI updates (show action immediately)
  • Prevent layout shift during load

Responsiveness:

  • Touch feedback within 100ms
  • Visual feedback for all interactions
  • Smooth animations (60fps target)
  • Debounce rapid inputs

React Native Best Practices

Component Optimization:

  • Use React.memo for expensive components
  • Implement shouldComponentUpdate or useMemo
  • Lazy load heavy components
  • Virtualize long lists (FlatList, SectionList)

Bundle Optimization:

  • Code splitting for large apps
  • Remove unused dependencies
  • Optimize image sizes and formats
  • Use Hermes engine (Android)

Design System Essentials

Consistency Checklist

Visual Consistency:

  • Unified color palette (primary, secondary, accent, neutrals)
  • Typography scale defined (font sizes, weights, line heights)
  • Spacing system (4pt/8pt grid or similar)
  • Component library documented
  • Icon set consistent in style and size

Behavioral Consistency:

  • Navigation patterns unified
  • Button actions predictable
  • Form validation consistent
  • Error handling standardized
  • Loading states uniform

Component Documentation

Document each component with:

  • Purpose and use cases
  • Props and their types
  • Visual variants (states, sizes, styles)
  • Accessibility requirements
  • Platform-specific considerations
  • Usage examples

2026 Design Trends (Optional Enhancement)

AI-Driven Interaction

Predictive UI:

  • Anticipate user needs based on context
  • Smart defaults in forms
  • Personalized content ordering
  • Contextual suggestions

Conversational Interfaces:

  • Voice interaction support
  • Natural language input
  • Progressive disclosure through conversation

Advanced Visual Design

Spatial Computing:

  • Consider depth and layering
  • Subtle parallax effects
  • 3D elements where appropriate
  • Immersive experiences

Micro-Interactions:

  • Delightful animation details
  • Haptic feedback coordination
  • Sound design for actions
  • Emotional engagement

Workflow Integration

Design Phase

  1. Define requirements - Understand user needs and business goals
  2. Research patterns - Review platform guidelines and competitors
  3. Sketch wireframes - Low-fidelity layouts first
  4. Create prototypes - Interactive mockups for testing
  5. Validate designs - User testing and accessibility checks

Review Phase

When reviewing designs or implementations:

  1. Check platform conventions (iOS vs Android)
  2. Verify touch target sizes (44pt/48dp minimum)
  3. Test color contrast ratios (WCAG AA minimum)
  4. Validate accessibility labels
  5. Confirm consistency with design system
  6. Review performance considerations

Implementation Phase

  1. Use presentational/container pattern
  2. Build atomic components bottom-up
  3. Implement accessibility from start
  4. Test on real devices (both platforms)
  5. Optimize for performance
  6. Document component usage

Additional Resources

Reference Files

For detailed platform-specific guidance, consult:

Platform Guidelines:

  • references/ios-guidelines.md - Comprehensive iOS HIG summary (SF Fonts, Navigation, VoiceOver, Haptics)
  • references/android-guidelines.md - Material Design 3 essentials (Components, Motion, TalkBack)
  • references/platform-differences.md - iOS vs Android quick reference (navigation, gestures, components)

Implementation Guides:

  • references/accessibility-checklist.md - Complete WCAG 2.1 AA testing guide (screen readers, contrast, touch targets)
  • references/performance-patterns.md - React Native optimization (FlatList, animations, bundle size, memory)
  • references/common-mistakes.md - Common design errors and fixes (touch targets, typography, accessibility, forms)
  • references/ui-libraries.md - React Native UI library comparison (Paper, Elements, Tamagui, NativeBase)

Example Files

Working code examples in examples/:

  • profile-screen-example.tsx - Complete profile screen with Atomic Design, accessibility labels, performance optimization
  • form-validation-example.tsx - Accessible form with real-time validation, proper keyboard types, error handling
  • optimized-list-example.tsx - FlatList with virtualization, React.memo, skeleton loading, pull-to-refresh
  • design-system-config.ts - Complete design tokens (colors, typography, spacing, shadows, component variants)

Utility Scripts

Development tools in scripts/:

  • check-contrast.py - WCAG contrast ratio validator (usage: python check-contrast.py "#FFFFFF" "#000000")
  • validate-touch-targets.sh - Validates minimum 44pt/48dp touch targets (usage: ./validate-touch-targets.sh src/)
  • accessibility-audit.sh - Audits for missing labels, roles, and a11y issues (usage: ./accessibility-audit.sh src/)

Quick Reference

Touch Targets

  • iOS: 44×44pt minimum
  • Android: 48×48dp minimum

Typography

  • Body: 16sp/pt minimum
  • Labels: 11pt minimum

Contrast

  • Text: 4.5:1 minimum
  • Large text: 3:1 minimum
  • Components: 3:1 minimum

Navigation

  • iOS: Back top-left, action top-right, tabs bottom
  • Android: Back top-left, menu top-right, FAB bottom-right

Performance

  • Touch feedback: <100ms
  • Animations: 60fps target
  • Loading indicators: >1 second operations

平台分布

Codex

34.78%
按下载量换算985

Claude

30.37%
按下载量换算860

Cursor

19.48%
按下载量换算552

Gemini CLI

9.99%
按下载量换算283

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills