I’ve been experimenting with AI coding agents on a common request: “Turn this website/web app into a native mobile app.” The biggest failure mode I kept seeing was not that Claude/Codex/Cursor could not write React Native code. The failure was that they started coding too early. They skipped the audit, missed browser-only APIs, ignored auth/session differences, failed to map routes to mobile screens, and often produced a polished but incomplete mobile app. So I built a small open-source plugin/skills workflow around a different pattern: Audit -> Markdown plan -> approval checkpoint -> implementation -> parity check -> QA The main lesson: the Markdown plan is not just documentation. It becomes durable project memory. Future agent runs can inspect the checklist instead of re-deriving intent from chat history. The audit checks for things like:
- web framework and routes
- package scripts
- auth/session libraries
- API/data libraries
- styling libraries
- browser-only APIs like window, document, localStorage, and cookies
- reusable code vs rewrite-required code
- mobile-native gaps like storage, auth redirects, push, camera, files, maps
- unknowns/blockers before implementation The goal is not to replace Expo CLI, Capacitor, or PWAs. If someone only needs a web shell or installable website, those are better options. This is for cases where the team actually wants a native Expo React Native migration and needs the agent to work from a structured checklist instead of a vague prompt. Curious if others are using similar “agent work order” patterns: durable Markdown plans, approval gates, route-to-screen maps, or audit-first workflows before allowing code changes. For context, the repo is here if anyone wants to inspect the structure: https://github.com/suntay44/web-to-mobile-magic-plugin submitted by /u/suntay44
Originally posted by u/suntay44 on r/ArtificialInteligence