How do I install the Mobile skill?

Run npx skillmds@latest add envoydev/mobile in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Mobile safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Mobile?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Mobile free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Mobile?

envoydev (@envoydev) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Mobile by envoydev — Agent Skill

Name: Mobile
Author: envoydev

Mobile

Router and index for Ionic / Capacitor mobile + hybrid app work - maps a mobile area (Ionic Angular UI, the Capacitor native layer, native plugins, the store/release/signing pipeline, mobile security hardening) to the focused leaf skill via the body's routing table. Load when starting mobile work and unsure which area applies - 'add a camera feature', 'why does the back button close the app', 'get this build into TestFlight' - or when orienting in a codebase with ionic.config.json or capacitor.config.*; go straight to the leaf skill when the area is known. Companions: angular-conventions, typescript. For plain web frontend see frontend; for .NET backend see dotnet.

envoydev 498dd1f 3.1 KB Updated Sep 17, 2026

File contents

mobile (Ionic / Capacitor router)

Index mapping an Ionic/Capacitor mobile work area to the skill to load. Routes, does not restate. An Ionic/Capacitor app is an Angular + TypeScript app in a native shell - angular-conventions and typescript still apply underneath; this router adds the mobile-specific layer. Most day-to-day feature work lands on ionic - this router earns its load only when the area is genuinely unclear (conventions vs release vs hardening).

Area -> skill

Availability. Every row below is per-project: load a skill only when it is in your skill list, and a name that is not there means this workspace has no such surface - work from this router and skip the row.

You are about to...	Load
follow house Ionic/Capacitor conventions - structure, lifecycle, permissions, plugin sourcing + wrapping	`ionic`
build Ionic navigation or page lifecycle	`ionic` (its `references/navigation-and-lifecycle.md`); component APIs / theming fetched live
wire the Angular+Capacitor bridge - lifecycle listeners, zone glue, back button, deep links	`ionic`
install / configure a Capacitor plugin (official, Capawesome, community, CapGo)	`ionic` for sourcing + wrapping; per-plugin config fetched live (context7 / plugin README)
build / sign / submit a release, wire OTA + the release CI pipeline	`capacitor-release`
harden or security-review an Ionic/Capacitor feature - secret storage, deep-link input, native permissions, cleartext + WebView hardening	`ionic-security`
write the Angular framework code underneath	`angular-conventions`
write or review the unit-test layer (the native seams' testing stays in `ionic`)	`angular-testing`
write the TypeScript / JavaScript baseline	`typescript`
build plain (non-mobile) web frontend	`frontend`

Example

'The app shows a blank screen after resuming on Android.' -> resume is lifecycle + bridge territory, not release or hardening: load ionic (its references/navigation-and-lifecycle.md owns resume/lifecycle listeners). Only if the trail ends at a backgrounding-snapshot or WebView-hardening flag does it cross to ionic-security.

Notes

Native Swift / Kotlin platform code and custom-plugin authoring are deliberately out of scope here - Capacitor generates the native shell, so reach for the platform native docs for that, not this router.
Backend / .NET work routes through dotnet.

---name: mobiledescription: Router and index for Ionic / Capacitor mobile + hybrid app work - maps a mobile area (Ionic Angular UI, the Capacitor native layer, native plugins, the store/release/signing pipeline, mobile security hardening) to the focused leaf skill via the body's routing table. Load when starting mobile work and unsure which area applies - 'add a camera feature', 'why does the back button close the app', 'get this build into TestFlight' - or when orienting in a codebase with ionic.config.json or capacitor.config.*; go straight to the leaf skill when the area is known. Companions: angular-conventions, typescript. For plain web frontend see frontend; for .NET backend see dotnet.---# mobile (Ionic / Capacitor router)Index mapping an Ionic/Capacitor mobile work area to the skill to load. Routes, does not restate. An Ionic/Capacitor app is an Angular + TypeScript app in a native shell - `angular-conventions` and `typescript` still apply underneath; this router adds the mobile-specific layer. Most day-to-day feature work lands on `ionic` - this router earns its load only when the area is genuinely unclear (conventions vs release vs hardening).## Area -> skill**Availability.** Every row below is per-project: load a skill only when it is in your skill list, and a name that is not there means this workspace has no such surface - work from this router and skip the row.| You are about to... | Load ||---|---|| follow house Ionic/Capacitor conventions - structure, lifecycle, permissions, plugin sourcing + wrapping | `ionic` || build Ionic navigation or page lifecycle | `ionic` (its `references/navigation-and-lifecycle.md`); component APIs / theming fetched live || wire the Angular+Capacitor bridge - lifecycle listeners, zone glue, back button, deep links | `ionic` || install / configure a Capacitor plugin (official, Capawesome, community, CapGo) | `ionic` for sourcing + wrapping; per-plugin config fetched live (context7 / plugin README) || build / sign / submit a release, wire OTA + the release CI pipeline | `capacitor-release` || harden or security-review an Ionic/Capacitor feature - secret storage, deep-link input, native permissions, cleartext + WebView hardening | `ionic-security` || write the Angular framework code underneath | `angular-conventions` || write or review the unit-test layer (the native seams' testing stays in `ionic`) | `angular-testing` || write the TypeScript / JavaScript baseline | `typescript` || build plain (non-mobile) web frontend | `frontend` |## Example'The app shows a blank screen after resuming on Android.' -> resume is lifecycle + bridge territory, not release or hardening: load `ionic` (its `references/navigation-and-lifecycle.md` owns resume/lifecycle listeners). Only if the trail ends at a backgrounding-snapshot or WebView-hardening flag does it cross to `ionic-security`.## Notes- Native Swift / Kotlin platform code and custom-plugin authoring are deliberately out of scope here - Capacitor generates the native shell, so reach for the platform native docs for that, not this router.- Backend / .NET work routes through `dotnet`.

Frequently asked questions