idea-analogist
想法群聊室 — 类比者角色。被 idea-team 主编排器调用,或用户单独说"类比一下"、"别的行业有没有"、"yes-and 扩展"、"X 让你想到什么"、"跨界启示"时触发。**专门做跨界类比 + yes-and 扩展——不评判、不挑刺、不要求事实证据**。Do NOT use when 用户要数据(用…
Mobile app UI design expert for iOS and Android. Use when designing app interfaces, creating design systems, ensuring accessibility, or following platform guidelines. Covers Material Design 3, Human Interface Guidelines, color theory, typography, and 2025 trends.
$ npx -y skills add majiayu000/spellbook --skill app-ui-design --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/app-ui-designContext preview
The summary Claude sees to decide when to auto-load this skill.
Mobile app UI design expert for iOS and Android. Use when designing app interfaces, creating design systems, ensuring accessibility, or following platform guidelines. Covers Material Design 3, Human Interface Guidelines, color theory, typography, and 2025 trends.
name: app-ui-design description: Mobile app UI design expert for iOS and Android. Use when designing app interfaces, creating design systems, ensuring accessibility, or following platform guidelines. Covers Material Design 3, Human Interface Guidelines, color theory, typography, and 2025 trends.
> Expert guidance for designing beautiful, accessible, and platform-native mobile app interfaces following 2025 best practices.
---
> These rules are mandatory. Violating them means the skill is not working correctly.
**All designs must meet WCAG 2.2 AA standards. Accessibility is not optional.**
❌ FORBIDDEN: - Color contrast below 4.5:1 for text - Touch targets smaller than 44×44pt (iOS) or 48×48dp (Android) - Information conveyed by color alone - Missing alternative text for images - Non-keyboard-navigable interfaces ✅ REQUIRED: - Minimum 4.5:1 contrast ratio for normal text - Minimum 3:1 contrast ratio for large text (18pt+) - Touch targets: 44×44pt (iOS) / 48×48dp (Android) - Support for Dynamic Type / Font Scaling - VoiceOver (iOS) / TalkBack (Android) compatibility - Clear focus indicators for keyboard navigation
**Follow platform-specific design guidelines. Do not mix iOS and Android patterns.**
❌ FORBIDDEN: - Using Android-style FAB on iOS - Using iOS-style bottom sheets on Android without adaptation - Mixing platform navigation patterns - Ignoring platform typography (SF Pro vs Roboto) ✅ REQUIRED: iOS (Human Interface Guidelines): - Use SF Pro font family - Tab bar at bottom for primary navigation - Push navigation with back chevron - Standard iOS controls (UIKit/SwiftUI) Android (Material Design 3): - Use Roboto font family - Bottom navigation bar or navigation drawer - Material components with ripple effects - Follow Material You dynamic theming
**Every app must have a documented design system with tokens.**
❌ FORBIDDEN: - Ad-hoc colors and spacing values - Inconsistent button styles across screens - Multiple unnamed font sizes - Components without defined states ✅ REQUIRED: Design System Must Include: ├── Color Tokens (primary, secondary, surface, error, etc.) ├── Typography Scale (heading1-6, body, caption, etc.) ├── Spacing Scale (4, 8, 12, 16, 24, 32, 48px) ├── Border Radius Tokens (none, sm, md, lg, full) ├── Shadow/Elevation Tokens (elevation1-5) └── Component Library (button, input, card, etc.)
**All interactive elements must be optimized for touch interaction.**
❌ FORBIDDEN: - Touch targets smaller than minimum size - Interactive elements too close together (<8px gap) - Important actions outside thumb reach zone - Hover-dependent interactions ✅ REQUIRED: - Minimum touch target: 44×44pt (iOS) / 48×48dp (Android) - Minimum spacing between targets: 8px - Primary actions in thumb-friendly zone (bottom 2/3) - Clear tap feedback (ripple, highlight, scale)
---
| Scenario | Approach | Key Considerations | |----------|----------|-------------------| | New app design | Start with design system | Define tokens before screens | | iOS-only app | Human Interface Guidelines | SF Pro, standard iOS patterns | | Android-only app | Material Design 3 | Roboto, Material components | | Cross-platform app | Adaptive design | Platform-specific navigation | | Redesign existing app | Audit first | Maintain mental models | | Accessibility review | WCAG 2.2 AA checklist | Contrast, touch targets, labels |
---
## Color Token Structure ### Semantic Colors primary → Main brand color, CTAs primary-variant → Darker/lighter primary for states secondary → Secondary actions, accents background → App background surface → Card backgrounds, elevated surfaces error → Error states, destructive actions on-primary → Text/icons on primary color on-background → Text/icons on background on-surface → Text/icons on surface ### Color Palette (60-30-10 Rule) 60% → Neutral/background colors 30% → Secondary/supporting colors 10% → Accent/primary colors ### Dark Mode Considerations - Don't just invert colors - Use desaturated colors for dark surfaces - Reduce contrast slightly (avoid pure white on black) - Maintain color meaning across modes
## Mobile Typography Guidelines ### iOS Typography (SF Pro) Large Title → 34pt, Bold Title 1 → 28pt, Bold Title 2 → 22pt, Bold Title 3 → 20pt, Semibold Headline → 17pt, Semibold Body → 17pt, Regular Callout → 16pt, Regular Subhead → 15pt, Regular Footnote → 13pt, Regular Caption 1 → 12pt, Regular Caption 2 → 11pt, Regular ### Android Typography (Roboto / Material 3) Display Large → 57sp Display Medium → 45sp Display Small → 36sp Headline Large → 32sp Headline Medium→ 28sp Headline Small → 24sp Title Large → 22sp Title Medium → 16sp, Medium Title Small → 14sp, Medium Body Large → 16sp Body Medium → 14sp Body Small → 12sp Label Large → 14sp, Medium Label Medium → 12sp, Medium Label Small → 11sp, Medium ### Best Practices - Maximum 2-3 font families per app - Minimum body text: 16px (14px absolute minimum) - Line height: 1.4-1.6× font size for body text - Support Dynamic Type (iOS) / Font Scalin
Cross-runtime skills for Claude Code, Codex, and multi-agent workflows.
Repo: majiayu000/spellbook
想法群聊室 — 类比者角色。被 idea-team 主编排器调用,或用户单独说"类比一下"、"别的行业有没有"、"yes-and 扩展"、"X 让你想到什么"、"跨界启示"时触发。**专门做跨界类比 + yes-and 扩展——不评判、不挑刺、不要求事实证据**。Do NOT use when 用户要数据(用…
想法群聊室 — 反方角色。被 idea-team 主编排器调用,或用户单独说"反方意见"、"挑这个想法的刺"、"为什么会失败"、"找漏洞 / 反例"、"devil's advocate"时触发。**专门挑漏洞、找隐藏假设、给反例——不安慰、不"也许可以这样"、不全盘否定**。Do NOT use when…
想法群聊室 — 调研员角色。被 idea-team 主编排器调用,或用户单独说"调研一下 X"、"X 的现状/竞品/数据"、"找 2026 数据"、"事实底"时触发。**用 WebSearch 拉真实 2026 数据、列竞品、引来源——只给事实,不评判,不建议**。Do NOT use when…
想法群聊室主持人 — 把一句话想法丢给多角色 AI 团队(调研员/反方/类比者)做查漏补缺。每个角色有自己的 voice,他们互相 @ 接话;你随时插话。**这是创意扩展工具,不打分、不否决、不堵路**。Use when 用户说"组个团队聊一下"、"开会讨论这个想法"、"找几个角度看看"、"群聊一下 X"、"team…
端到端产品教练 — 把一句话想法走到 PRD + 可点击 HTML 原型。会顶嘴、强制砍功能、用 Nielsen + Norman 做友好性硬检。Use when user 说"我有一个想法"、"想做一个产品"、"做 MVP"、"写 PRD"、"做用户友好的产品",或调用插件命令…
Use when the user wants to extract Figma designs into production-ready React or Next.js components with TypeScript, Tailwind CSS, and pixel-perfect accuracy.