mobilize-web-to-mobile

Convert a web app repo into a tested React Native Expo mobile app via AgentMarvel.

Updated Jul 23, 2026
One-click install
npx skills add https://github.com/MadhavMareddy/AgentMarvel --skill mobilize-web-to-mobile-madhavmareddy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mobilize-web-to-mobile
Source: https://github.com/MadhavMareddy/AgentMarvel/tree/main/harness/your-project/skills.d/mobilize-web-to-mobile
Command: npx skills add https://github.com/MadhavMareddy/AgentMarvel --skill mobilize-web-to-mobile-madhavmareddy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Porting an existing web application to mobile normally means manually rewriting screens, re-implementing auth, and hoping the result matches the original spec. This Skill drives the AgentMarvel CLI to generate a React Native (Expo) app from a web repo plus a controls document, then independently verifies the result with blind test authoring, a locked test suite, and an automated judge. ## Core Features & Use Cases - Automated web-to-mobile porting: Runs the full AgentMarvel pipeline (ingest, design, plan, generate, build, verify, judge, repair) from a single CLI command. - Independent verification gates: A blind test author, sha256-locked Maestro test suite, and typed verdict contracts ensure the generated app actually matches the controls doc. - Flexible run modes: Supports incremental screen-by-screen builds, supervised self-healing runs, environment pinning for multi-tenant APIs, and focused iteration on cached screens. - Use Case: A developer has a React web dashboard and a controls document describing its screens. They run the Skill with --repo and --controls to produce a verified Expo app on an Android emulator, with failures classified and repaired automatically. ## Quick Start Ask the agent to run AgentMarvel against your web repo and controls document, for example: port the web app in ./my-web-app to mobile using the controls doc at ./controls.md.

Frequently Asked Questions about mobilize-web-to-mobile

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

FAQPage Schema
How do I convert a web app to a React Native mobile app?

Run the AgentMarvel CLI with --repo pointing to your web app and --controls pointing to a document describing its screens and controls. The pipeline generates an Expo app, builds it on an Android emulator, and verifies it against the controls doc.

How do I run AgentMarvel from the command line?

From the AgentMarvel repo root, run npm run agentmarvel -- run --repo <web_repo> --controls <controls_doc>, with optional flags like --out, --reference, and environment pins. An ANTHROPIC_API_KEY in .env is required.

What do I need installed to build and test the generated mobile app?

You need Node.js 20+, an Anthropic API key, and either the provided Docker executor or a local Android SDK with an emulator and Maestro installed. The Docker option bundles the emulator and Maestro together.

Can I iterate on a single screen instead of regenerating the whole app?

Yes, use the --focus flag with specific screen IDs to iterate only on cached screens, or --incremental to build the foundation and login once then proceed screen by screen. Reusing an existing --out directory also reuses dependencies and prebuild.

Why does AgentMarvel lock the generated test files?

The authored Maestro tests are sha256-hashed and made read-only so the repair loop cannot weaken tests to make failures pass. Any tampering aborts the run, and the repair stage must fix the app instead of the tests.

How are test failures classified during verification?

Failures are classified by an independent judge: 4xx or client errors are app bugs, a 5xx that also fails via curl with a valid token is a backend issue, and Metro, emulator, or adb problems are flaky environment issues.