swarm-mobile-ux-agent

Audit gnubok mobile UI for touch targets, safe areas, and navigation patterns.

209|46|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/erp-mafia/gnubok --skill swarm-mobile-ux-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: swarm-mobile-ux-agent
Source: https://github.com/erp-mafia/gnubok/tree/main/.claude/skills/swarm-mobile-ux-agent
Command: npx skills add https://github.com/erp-mafia/gnubok --skill swarm-mobile-ux-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a read-only audit of gnubok's mobile UX quality, scanning for touch targets, safe-area usage, responsive breakpoints, navigation patterns, input modes, and viewport configuration to ensure accessibility and usability on mobile devices.

Core Features & Use Cases

  • Touch-target and tap-area validation: ensures targets meet WCAG AA guidance (≥44×44 CSS px) and adequate spacing.
  • Safe-area and notch handling: verifies padding with env(safe-area-inset-*) to prevent content overlap.
  • Viewport and responsive checks: validates meta viewport settings and mobile-first breakpoints in app layouts.
  • Navigation patterns audit: ensures mobile navigation uses bottom tabs or hamburger with clear current-page indicators.
  • Input mode recommendations: checks for appropriate input types and inputMode attributes for numeric amounts and dates.

Quick Start

Inspect the gnubok mobile UI by scanning app/, components/, and app/layout.tsx to surface mobile UX issues.

Frequently Asked Questions about swarm-mobile-ux-agent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit mobile UX for touch targets and safe-area handling?

To audit mobile UX, scan your app and components directories to validate touch targets meet WCAG AA guidance and verify safe-area insets prevent content overlap. This static analysis surfaces actionable accessibility gaps in your layout configurations.

What is mobile UX static analysis and how does it validate responsive breakpoints?

Mobile UX static analysis inspects codebase files like layout.tsx to validate meta viewport settings and mobile-first breakpoints. It checks the code directly without running the app to identify responsive configuration issues.

Does this mobile UX audit work with both iOS and Android configurations?

Yes, the mobile UX audit is applicable across iOS and Android. It evaluates responsive layouts, safe areas, touch targets, and navigation patterns to ensure accessibility and usability on both mobile platforms.

How do I check inputMode attributes for numeric amounts and dates in a mobile app?

To check inputMode attributes, scan your components for appropriate input types on numeric amounts and dates. The audit verifies these configurations to ensure correct mobile keyboard modes are triggered for user inputs.

What are the limitations of static analysis for mobile navigation pattern audits?

Static analysis for mobile navigation audits is limited to reading source code in your app directory, meaning it cannot detect runtime visual bugs. It only verifies that bottom tabs or hamburger menus include clear current-page indicators.