mobile-expert

Route mobile development requests between design and Capacitor implementation skills.

8|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/SufficientDaikon/omniskill --skill mobile-expert
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mobile-expert
Source: https://github.com/SufficientDaikon/omniskill/tree/main/bundles/mobile-kit/meta-skill
Command: npx skills add https://github.com/SufficientDaikon/omniskill --skill mobile-expert

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines mobile development by intelligently routing requests between the distinct domains of mobile-first design/UX and technical implementation using Capacitor.

Core Features & Use Cases

  • Design Routing: Directs requests related to UI/UX, touch interactions, and platform conventions to the mobile-design skill.
  • Implementation Routing: Routes requests concerning Capacitor project setup, plugin integration, and native API access to the capacitor-best-practices skill.
  • Use Case: When a user asks to "Design a mobile-first UI and then implement the camera feature," this meta-skill ensures the design aspects are handled by mobile-design and the technical implementation by capacitor-best-practices.

Quick Start

Use the mobile-expert skill to design a mobile navigation menu and then implement the camera plugin.

Frequently Asked Questions about mobile-expert

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

FAQPage Schema
How do I design a mobile-first UI and implement native features in one workflow?

Mobile app development workflows can be coordinated by routing design requests to mobile-first UX skills and implementation requests to Capacitor best practices. This ensures touch interactions and native API access are handled sequentially.

What is the best way to structure a Capacitor project for mobile app development?

Capacitor project setup is streamlined by routing implementation requests to specialized best practices. This handles plugin integration and native functionality access, ensuring technical execution follows mobile-first design principles.

Can I use this to handle both UI design and touch interaction implementation?

Yes, mobile design and touch interaction implementation are handled by routing UI/UX requests to dedicated design skills. Platform conventions and mobile-first design principles are applied before technical implementation begins.

Does this workflow support integrating native device plugins like a camera?

Native device plugins like the camera are fully supported through Capacitor integration. Implementation requests are routed to handle plugin integration and native API access after the mobile-first UI design is finalized.

How does routing between mobile design and Capacitor implementation actually work?

Routing separates mobile development requests by domain: UI/UX and touch interactions go to mobile design skills, while Capacitor setup and plugin integration go to implementation skills, supporting sequential multi-skill scenarios.