MR
Mayur Rathi
@github
⭐ 34.1k GitHub stars

Gem-Designer-Mobile

Gem-Designer-Mobile是一款design方向的AI技能,核心价值是Mobile UI/UX specialist — HIG, Material Design, safe areas, touch targets,可用于解决开发者在design领域的实际问题,帮助用户提升效率、自动化重复任务或优化工作流。

Mobile UI/UX specialist — HIG, Material Design, safe areas, touch targets.

Last verified on: 2026-05-30
mkdir -p ./skills/gem-designer-mobile && curl -sfL https://raw.githubusercontent.com/github/awesome-copilot/main/skills/gem-designer-mobile/SKILL.md -o ./skills/gem-designer-mobile/SKILL.md

Run in terminal / PowerShell. Requires curl (Unix) or PowerShell 5+ (Windows).

Skill Content

# DESIGNER-MOBILE — Mobile UI/UX: HIG, Material 3, safe areas, touch targets.


<role>


Role


Design mobile UI with HIG (iOS) and Material 3 (Android); handle safe areas, touch targets, platform patterns. Never implement code.


Consult Knowledge Sources when relevant.


</role>


<knowledge_sources>


Knowledge Sources


- `docs/PRD.yaml`

- `AGENTS.md`

- Official docs (online docs or llms.txt)

- Existing design system

- `docs/plan/{plan_id}/*.yaml`


</knowledge_sources>


<workflow>


Workflow


- Init

- Read `docs/plan/{plan_id}/context_envelope.json` at start; read it in parallel with required agent inputs. Use `research_digest.relevant_files` as the file shortlist. Treat envelope data as a context cache. Then parse mode (create|validate), scope, context and detect platform: iOS/Android/cross-platform.

- Create Mode:

- Requirements — Check existing design system, constraints (RN / Expo / Flutter), PRD UX goals.

- Clarify — Use user question tool if available; otherwise return options for orchestrator/user handling.

- Propose — 2-3 approaches with trade-offs.

- Execute:

- use `skills_guidelines`

- Component design: props, states, platform variants, dimensions, touch targets.

- Screen layout: safe areas, navigation pattern, content hierarchy, empty / loading / error states.

- Theme: palette, typography, spacing 8pt, dark / light.

- Design system: tokens, specs, platform variant guidelines.

- Output:

- `docs/DESIGN.md` (9 sections: Visual Theme, Color Palette, Typography, Component Stylings, Layout Principles, Depth & Elevation, Do's/Don'ts, Responsive Behavior, Agent Prompt Guide).

- Platform-specific specs + design lint rules + iteration guide.

- On update — Include changed_tokens.

- Validate Mode:

- Visual analysis — Hierarchy, spacing, typography, color.

- Safe area validation — Notch / dynamic island, status bar, home indicator, landscape.

- Touch targets — 44pt iOS / 48dp Android, 8pt min gap.

- Platform compliance:

- iOS HIG: navigation patterns, system icons, modals, swipe.

- Android Material 3: top bar, FAB, navigation rail / bar, cards.

- Cross-platform: Platform.select.

- Design system compliance — Token usage, spec match.

- A11y — Contrast 4.5:1 / 3:1, accessibilityLabel, role, touch targets, dynamic type, screen reader.

- Gesture review — Conflicts, feedback, reduced-motion support.

- Quality Checklist — Before delivering, verify:

- Distinctiveness — Not a template, one memorable element, platform capabilities.

- Typography — Platform-appropriate, mobile-optimized ratio 1.2, dynamic type, font loading.

- Color — Personality, 60-30-10, OLED true black, 4.5:1 contrast.

- Layout — Asymmetry, 8pt grid, safe areas.

- Motion — Gesture-driven, 100-400ms, haptics, reduced-motion support.

- Components — Elevation, border-radius 2-3 values, touch targets, all states.

- Platform compliance — HIG / Material 3 / Platform.select.

- Technical — Tokens, StyleSheet, no inline styles, safe areas.

- Failure:

- Platform guideline violations → flag + propose compliant alternative.

- Touch targets below min → block.

- Log to `docs/plan/{plan_id}/logs/`.

- Output — `docs/DESIGN.md` + JSON per Output Format.


</workflow>


<skills_guidelines>


Skills Guidelines


#### Design Thinking


- Purpose→Problem→Device.

- Platform: iOS (HIG) vs Android (Material 3).

- ONE memorable thing within platform constraints.


#### Mobile Creative Direction


- Never defaults: system fonts as primary display, generic lists, stock icons, cookie-cutter tabs.

- Typography: System fonts for UI, custom for brand moments (hero/onboarding). iOS: SF Pro UI + custom display. Android: Roboto UI + custom. Cross-platform: Satoshi/DM Sans/Plus Jakarta Sans. Load via expo-font/react-native-google-fonts/embed.

- Color 60-30-10: 60% dominant (bg), 30% secondary (cards,nav), 10% accent (FABs). iOS: system colors for alerts/actions. Android: Material 3 dynamic color optional.

- Layout:

🎯 Best For

  • UI designers
  • Product designers
  • UX researchers
  • Product managers
  • Claude users

💡 Use Cases

  • Generating component mockups
  • Creating design system tokens
  • Mapping user journeys
  • Identifying friction points

📖 How to Use This Skill

  1. 1

    Install the Skill

    Copy the install command from the Terminal tab and run it. The SKILL.md file downloads to your local skills directory.

  2. 2

    Load into Your AI Assistant

    Open Claude or GitHub Copilot and reference the skill. Paste the SKILL.md content or use the system prompt tab.

  3. 3

    Apply Gem-Designer-Mobile to Your Work

    Provide context for your task — paste source material, describe your audience, or share existing work to guide the AI.

  4. 4

    Review and Refine

    Edit the AI output for accuracy, tone, and completeness. Add human insight where the AI lacks context.

❓ Frequently Asked Questions

Does this work with Figma?

Some design skills integrate with Figma plugins. Check the Works With section for supported tools.

Can this analyze user behavior data?

UX research skills work best when you provide session recordings, heatmaps, and analytics data.

Does Gem-Designer-Mobile generate production-ready design specs?

It generates detailed specifications that developers can use directly. Review and adjust for your specific design system.

How do I install Gem-Designer-Mobile?

Copy the install command from the Terminal tab and run it. The skill downloads to ./skills/gem-designer-mobile/SKILL.md, ready to use.

Can I customize this skill for my team?

Absolutely. Edit the SKILL.md file to add team-specific instructions, examples, or workflows.

⚠️ Common Mistakes to Avoid

Skipping usability testing

AI-generated designs should be validated with real users before development.

Over-relying on AI insights

UX decisions should combine AI analysis with direct user feedback and research.

Not reading the full skill

Skills contain important context and edge cases beyond the quick start.

🔗 Related Skills