Agent skill

Mobile Parity Check

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

Verify design and functional parity between the implemented mobile app and its web source.

MITAuto-check passedMobile

Install Mobile Parity Check

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

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

GitHub CLI
$ gh skill install suntay44/web-to-mobile-magic-plugin mobile-parity-check --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-parity-check .claude/skills/mobile-parity-check && 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-parity-check
GitHub stars
107
Token cost
~515 tokens
SKILL.md length
247 words
Files
1
Skills in repo
11
Repo updated
First seen
Licence
MIT

At a glance

Verify design and functional parity between the implemented mobile app and its web source.

  • Tasks that involve Cross-platform mobile apps
  • SKILL.md covers Required Input, Functional Parity, Design Parity and Human Review Required, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Tasks that involve UX design

What it does

Mobile Parity Check is an agent skill from suntay44/web-to-mobile-magic-plugin. Verify design and functional parity between the implemented mobile app and its web source. Use after expo-react-native-build in the web-to-mobile workflow to check feature completeness, visual alignment, and key user flows.

Its SKILL.md is about 520 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Mobile, covering Cross-platform mobile apps and UX design. It works with Expo and React Native. 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 UX design

Example prompts

  • “/mobile-parity-check”

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 Parity Check loads about 515 tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 247 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~61
When it runs · the whole SKILL.md, loaded when a task matches
~515

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). 247 words, ~515 tokens.

Download SKILL.mdSave it as .claude/skills/mobile-parity-check/SKILL.md (or your agent's skills folder).
name
mobile-parity-check
description
Verify design and functional parity between the implemented mobile app and its web source. Use after expo-react-native-build in the web-to-mobile workflow to check feature completeness, visual alignment, and key user flows.
license
MIT

Mobile Parity Check

Verify that the mobile implementation faithfully matches the web source before QA.

Required Input

Use the approved plan under docs/web-to-mobile/ — specifically the Route To Mobile Navigation Map, Reusable Code, and Acceptance Criteria sections. If no plan exists, stop and return to mobile-migration-plan.

Functional Parity

For each route in the Route To Mobile Navigation Map:

  • Confirm the mapped mobile screen exists and is implemented.
  • Confirm all interactions from the web route (forms, buttons, links, data display) are present in the mobile screen.
  • Note any web feature that was deferred — it must appear in the plan as an explicit deferral, not a silent omission.

Design Parity

Check what the agent can verify in code:

  • Colors: confirm design tokens or hardcoded values match the web source palette.
  • Typography: confirm font family, size scale, and weight usage aligns with the web source.
  • Spacing and layout: confirm component hierarchy and padding constants are consistent.
  • Icons and assets: confirm correct assets are used, not placeholders.

Flag deviations with the specific file and line where the mismatch occurs.

Human Review Required

Mark the following for explicit human visual sign-off — the agent cannot verify these in code:

  • Pixel-level layout accuracy on device.
  • Animation and transition feel.
  • Brand color rendering on screen.
  • Accessibility contrast ratios in the rendered UI.

See Human Sign-Off Required in ../mobile-migration-plan/references/output-contracts.md.

Plan Update

Add a "Parity Review" section to the plan listing: agent-verified items, agent-flagged deviations, and items requiring human visual sign-off.

Handoff

End by handing off to mobile-qa-release.

© 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

Just SKILL.md in skills/mobile-parity-check of suntay44/web-to-mobile-magic-plugin.

Open the folder on GitHubat commit e6eb780

Compare with similar skills

Mobile Parity Check 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 Parity Check compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Mobile Parity Check this skillsuntay44/web-to-mobile-magic-plugin107—~515Automated safety check: PassMIT
React Native Best Practicesvercel-labs/openreview1.7k17 repos~1.1kAutomated safety check: PassMIT
Appllama App Design SkillAppllama/appllama-skills2.5k1 repos~5kAutomated safety check: PassMIT
Appllama UsageAppllama/appllama-skills2.5k1 repos~1.6kAutomated safety check: PassMIT
Release Sample SweepAtmosphere/atmosphere3.8k—~4.2kAutomated safety check: PassApache-2.0
App Store Reviewsafaiyeh/app-store-review-skill3681 repos~3.4kAutomated 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
  • 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
  • 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
  • Release Sample Sweep

    Atmosphere/atmosphere

    Run the pre-release end-to-end sweep of every user-facing surface — the 33 samples under samples/ (booted from their packaged artifacts and driven in a real browser via chrome-devtools MCP), the…

    3.8k GitHub stars~4.2k tokensUpdated 2 days ago
    MobileAuto-check passed
  • App Store Review

    safaiyeh/app-store-review-skill

    Evaluates code against Apple's App Store Review Guidelines. An agent skill from safaiyeh/app-store-review-skill.

    368 GitHub starsUsed in 1 repo~3.4k tokens
    MobileAuto-check passed
  • Cali

    callstackincubator/cali

    Official

    A skill your agent uses when working in the Cali repository or when you need to run, extend, or debug the Cali CLI for mobile React Native and Expo workflows.

    991 GitHub stars~731 tokensUpdated 3 mo ago
    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.

    107 GitHub stars~871 tokensUpdated 27 days ago
    Auto-check passed
  • Web To Mobile

    suntay44/web-to-mobile-magic-plugin

    Orchestrate website or web app conversion into a mobile app.

    107 GitHub stars~781 tokensUpdated 27 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.

    107 GitHub stars~811 tokensUpdated 27 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.

    107 GitHub stars~692 tokensUpdated 27 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.

    107 GitHub stars~793 tokensUpdated 27 days ago
    Auto-check passed
  • Mobile Migration Plan

    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.

    107 GitHub stars~712 tokensUpdated 27 days ago
    Auto-check passed

Categories

Questions about Mobile Parity Check

What does Mobile Parity Check do?

Verify design and functional parity between the implemented mobile app and its web source. Mobile Parity Check is an agent skill from suntay44/web-to-mobile-magic-plugin. Verify design and functional parity between the implemented mobile app and its web source.

When should I use Mobile Parity Check?

Mobile Parity Check fits situations like: tasks that involve Cross-platform mobile apps; tasks that involve UX design.

How do I install Mobile Parity Check in Claude Code?

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

How do I install Mobile Parity Check in Codex?

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

Can I use Mobile Parity Check 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-parity-check -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-parity-check, .gemini/skills/mobile-parity-check, .github/skills/mobile-parity-check and .opencode/skills/mobile-parity-check in your project.

What does Mobile Parity Check need to run?

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

Does Mobile Parity Check 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 Parity Check 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 Parity Check use?

Mobile Parity Check 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 Parity Check use?

About 515 tokens (SKILL.md is roughly 2.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Mobile Parity Check?

Skills that share tags, products or a category with Mobile Parity Check: React Native Best Practices (vercel-labs/openreview, 1.7k stars), Appllama App Design Skill (Appllama/appllama-skills, 2.5k stars), Appllama Usage (Appllama/appllama-skills, 2.5k stars) and Release Sample Sweep (Atmosphere/atmosphere, 3.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Mobile Parity Check?

suntay44 (a GitHub user) maintains it in suntay44/web-to-mobile-magic-plugin, which has 107 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.