New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Mobile Migration Plan

by suntay44 in suntay44/web-to-mobile-magic-plugin

Create an approval-gated web-to-mobile plan with a route map, stack verdict, reuse/rewrite split, checklist, tests, and acceptance criteria.

MITAuto-check passedMobile

Install Mobile Migration Plan

skills CLI
$ npx skills add suntay44/web-to-mobile-magic-plugin --skill mobile-migration-plan -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install suntay44/web-to-mobile-magic-plugin mobile-migration-plan --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/suntay44/web-to-mobile-magic-plugin.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/mobile-migration-plan .claude/skills/mobile-migration-plan && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
mobile-migration-plan
GitHub stars
108
Token cost
~712 tokens
SKILL.md length
326 words
Files
5 (incl. references)
Skills in repo
11
Repo updated
First seen
Licence
MIT

At a glance

Create an approval-gated web-to-mobile plan with a route map, stack verdict, reuse/rewrite split, checklist, tests, and acceptance criteria.

  • Tasks that involve Cross-platform mobile apps
  • SKILL.md covers Required Input, Plan File, Required Sections and Approval Gate
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Tasks that involve User stories

What it does

Mobile Migration Plan is an agent skill from suntay44/web-to-mobile-magic-plugin. Create an approval-gated web-to-mobile plan with a route map, stack verdict, reuse/rewrite split, checklist, tests, and acceptance criteria.

Its SKILL.md is about 710 tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/dependency-substitutions.md`, `references/framework-migration-notes.md` and `references/output-contracts.md`).

It sits in Mobile, covering Cross-platform mobile apps and User stories. It works with Expo. The repository describes itself as: Website to React Native mobile app Plugin. Audit, Plan, QA scan, and deep review. Plan-first, approval-gated and Token Efficient. The licence is MIT.

When your agent uses it

  • Tasks that involve Cross-platform mobile apps
  • Tasks that involve User stories

Example prompts

  • “/mobile-migration-plan”

What it can do on your machine

Read from SKILL.md and the folder at commit e6eb780. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Mobile Migration Plan loads about 712 tokens when it runs, and up to ~6.2k if it reads all its reference files. Until then it costs about 41 tokens; SKILL.md has 326 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~41
When it runs · the whole SKILL.md, loaded when a task matches
~712
With references · SKILL.md plus every file in references/, read only if the agent opens them
~6.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from suntay44/web-to-mobile-magic-plugin at commit e6eb780, republished under its MIT licence (© suntay44). 326 words, ~712 tokens.

Download SKILL.mdSave it as .claude/skills/mobile-migration-plan/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
mobile-migration-plan
description
Create an approval-gated web-to-mobile plan with a route map, stack verdict, reuse/rewrite split, checklist, tests, and acceptance criteria.
license
MIT

Mobile Migration Plan

Required Input

Use web-to-mobile-audit findings and recommended stack unless evidence changes. If findings are missing, audit first.

Plan File

Repo/local: docs/web-to-mobile/YYYY-MM-DD-web-to-mobile-plan.md. URL-only: docs/web-to-mobile/YYYY-MM-DD-ui-ux-spec.md; layout, navigation, and visual direction only (see references/output-contracts.md).

Use the current local date for a new run. For the current run, update that file in place, preserving Audit Findings, completed items, and approval history. An audit file marked Plan Status: Audit complete — planning pending is the same run. Add a numeric suffix only for a distinct run whose filename collides.

Required Sections

Follow references/plan-template.md in order, including Capabilities & Limits, Migration Fit Verdict, API Needs, Reusable Code, Rewrite-Required Code, Native Feature Gaps, Unknowns And Blockers, Implementation Checklist, and Human Sign-Off Required.

The Migration Fit Verdict chooses one path. Do not force native when a wrapper or PWA suffices. The verdict controls the next phase:

  • Expo React Native → approval, then expo-react-native-build.
  • Capacitor, PWA/PWABuilder, Stay Web → approval, then explicit web-stack handoff; no Expo build or mobile parity phase.
  • Swift/Native → native-team handoff after approval; no bundled implementation.

Read only the detected framework's section in references/framework-migration-notes.md and relevant packages in references/dependency-substitutions.md for reuse/rewrite decisions, equivalents, and difficulty. Reuse findings already in context.

In the Route To Mobile Navigation Map, use tabs for primary areas, stacks for details, auth flows for login/signup, modals for focused flows, and explicit deferrals.

The Implementation Checklist needs checkboxes, file paths, source → target mappings, an observable done condition, verification commands (or Test Plan IDs), and a confidence label ([from-code], [inferred], [assumption]) per item. Order by dependencies; identify blocked items and the next unblocked action.

Keep required sections compact: record evidence once and reference it elsewhere; use None with a reason for inapplicable sections, and Unknown for unverified areas. Keep reusable, rewrite-required, mobile-native gaps, and unknowns/blockers distinct.

Approval Gate

For unapproved or changed scope, set Plan Status: Planning complete — approval pending, link the plan, summarize scope/blockers, and request approval. Preserve existing approval for unchanged scope. Do not edit app code before approval.

© suntay44, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (references) in skills/mobile-migration-plan of suntay44/web-to-mobile-magic-plugin.

  • SKILL.md
  • references/dependency-substitutions.md
  • references/framework-migration-notes.md
  • references/output-contracts.md
  • references/plan-template.md

Open the folder on GitHubat commit e6eb780

Compare with similar skills

Mobile Migration Plan next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Mobile Migration Plan compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Mobile Migration Plan this skillsuntay44/web-to-mobile-magic-plugin108—~712Automated safety check: PassMIT
React Native Best Practicesvercel-labs/openreview1.7k17 repos~1.1kAutomated safety check: PassMIT
Expo Cicd WorkflowsCherryHQ/cherry-studio-app4k6 repos~870Automated safety check: PassMIT
Expo Modulebbplayer-app/BBPlayer1.2k3 repos~1.4kAutomated safety check: PassMIT
Appllama App Design SkillAppllama/appllama-skills2.5k1 repos~5kAutomated safety check: PassMIT
Building Native UICherryHQ/cherry-studio-app4k8 repos~2.6kAutomated safety check: PassMIT

Similar skills

  • React Native Best Practices

    vercel-labs/openreview

    Official

    A prioritized rule set for React Native and Expo apps covering list performance, animation, navigation, UI patterns, state, rendering, monorepos and configuration.

    1.7k GitHub starsUsed in 17 repos~1.1k tokens
    MobileAuto-check passed

  • Expo Cicd Workflows

    CherryHQ/cherry-studio-app

    Helps understand and write EAS workflow YAML files for Expo projects.

    4k GitHub starsUsed in 6 repos~870 tokens
    MobileAuto-check passed

  • Expo Module

    bbplayer-app/BBPlayer

    Guide for creating and writing Expo native modules and views using the Expo Modules API (Swift, Kotlin, TypeScript).

    1.2k GitHub starsUsed in 3 repos~1.4k tokens
    MobileAuto-check passed

  • Appllama App Design Skill

    Appllama/appllama-skills

    Build native-feeling, benchmark-quality mobile app screens (Expo / React Native).

    2.5k GitHub starsUsed in 1 repo~5k tokens
    MobileAuto-check passed

  • Building Native UI

    CherryHQ/cherry-studio-app

    Complete guide for building beautiful apps with Expo Router.

    4k GitHub starsUsed in 8 repos~2.6k tokens
    MobileAuto-check passed

  • Appllama Usage

    Appllama/appllama-skills

    Use the Appllama MCP (mcp.appllama.io) well — research real top-grossing mobile apps, their screens, flows, and UI elements, then build from what you learn.

    2.5k GitHub starsUsed in 1 repo~1.6k tokens
    MobileAuto-check passed

More from suntay44/web-to-mobile-magic-plugin

All 11 skills in this repo

  • Mobile App Audit

    suntay44/web-to-mobile-magic-plugin

    Audit an existing unfinished Expo React Native or Swift mobile app.

    108 GitHub stars~871 tokensUpdated 26 days ago
    Auto-check passed

  • Web To Mobile

    suntay44/web-to-mobile-magic-plugin

    Orchestrate website or web app conversion into a mobile app.

    108 GitHub stars~781 tokensUpdated 26 days ago
    Auto-check passed

  • Web To Mobile Audit

    suntay44/web-to-mobile-magic-plugin

    Audit a website, GitHub repo, local folder, or workspace before web-to-mobile work.

    108 GitHub stars~811 tokensUpdated 26 days ago
    Auto-check passed

  • Mobile Deep Review

    suntay44/web-to-mobile-magic-plugin

    Senior-level deep review of an existing mobile app. An agent skill from suntay44/web-to-mobile-magic-plugin.

    108 GitHub stars~692 tokensUpdated 26 days ago
    Auto-check passed

  • Mobile QA Scan

    suntay44/web-to-mobile-magic-plugin

    QA scan of an existing mobile app. An agent skill from suntay44/web-to-mobile-magic-plugin.

    108 GitHub stars~793 tokensUpdated 26 days ago
    Auto-check passed

  • Expo React Native Build

    suntay44/web-to-mobile-magic-plugin

    Implement an approved web-to-mobile plan in Expo React Native.

    108 GitHub stars~811 tokensUpdated 26 days ago
    Auto-check passed

Works with

Categories

Questions about Mobile Migration Plan

What does Mobile Migration Plan do?

Create an approval-gated web-to-mobile plan with a route map, stack verdict, reuse/rewrite split, checklist, tests, and acceptance criteria. Mobile Migration Plan is an agent skill from suntay44/web-to-mobile-magic-plugin. Create an approval-gated web-to-mobile plan with a route map, stack verdict, reuse/rewrite split, checklist, tests, and acceptance criteria.

When should I use Mobile Migration Plan?

Mobile Migration Plan fits situations like: tasks that involve Cross-platform mobile apps; tasks that involve User stories.

How do I install Mobile Migration Plan in Claude Code?

Run `npx skills add suntay44/web-to-mobile-magic-plugin --skill mobile-migration-plan -a claude-code`. Or copy the skill folder (skills/mobile-migration-plan in suntay44/web-to-mobile-magic-plugin) into .claude/skills/mobile-migration-plan in your project. Claude Code loads it when a task matches its description.

How do I install Mobile Migration Plan in Codex?

Run `npx skills add suntay44/web-to-mobile-magic-plugin --skill mobile-migration-plan -a codex`. Or copy the skill folder (skills/mobile-migration-plan in suntay44/web-to-mobile-magic-plugin) into .agents/skills/mobile-migration-plan in your project. Codex loads it when a task matches its description.

Can I use Mobile Migration Plan in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add suntay44/web-to-mobile-magic-plugin --skill mobile-migration-plan -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/mobile-migration-plan, .gemini/skills/mobile-migration-plan, .github/skills/mobile-migration-plan and .opencode/skills/mobile-migration-plan in your project.

What does Mobile Migration Plan need to run?

SKILL.md names no scripts, command-line tools or credentials: Mobile Migration Plan is instructions for the agent only.

Does Mobile Migration Plan access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Mobile Migration Plan safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Mobile Migration Plan use?

Mobile Migration Plan is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Mobile Migration Plan use?

About 712 tokens (SKILL.md is roughly 2.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 5.5k tokens, read only when the agent opens those files.

What are the alternatives to Mobile Migration Plan?

Skills that share tags, products or a category with Mobile Migration Plan: React Native Best Practices (vercel-labs/openreview, 1.7k stars), Expo Cicd Workflows (CherryHQ/cherry-studio-app, 4k stars), Expo Module (bbplayer-app/BBPlayer, 1.2k stars) and Appllama App Design Skill (Appllama/appllama-skills, 2.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Mobile Migration Plan?

suntay44 (a GitHub user) maintains it in suntay44/web-to-mobile-magic-plugin, which has 108 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on September 13, 2026.

Source: suntay44/web-to-mobile-magic-plugin on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.