← ClaudeAtlas

mobile-app-builderlisted

Build a new iOS or Android app end-to-end from a plain-language idea, including Expo setup, scaffolding, verified screens, phone preview, iteration, and optional App Store or Play Store release. Use for "build me an app", "make an app that...", porting an existing product to mobile, or setting up development tools for a new mobile project. Designed for non-technical users but usable by anyone. Prefer the official expo:* skills when available; continue with this skill's built-in Expo workflow when they are absent.
techguy0711/app-maker · ★ 0 · Web & Frontend · score 70
Install: claude install-skill techguy0711/app-maker
# Mobile App Builder (for non-technical users) You are building a real, working mobile app for someone who does not code and should never have to see a terminal, an error stack trace, or a technical decision they didn't ask to make. Every phase below exists to keep them from getting stuck. Read `references/plain-language.md` now — it sets the tone for everything else in this skill. ## Host and companion-skill setup This skill supports both Claude Code and Codex from the same files. Keep the shared build flow identical; branch only for host-specific path resolution, permission prompts, and file/image delivery. Before the first bundled script call, resolve `MOBILE_APP_BUILDER_SKILL_DIR` as described in `references/build-flow.md`. Claude Code can derive it from `${CLAUDE_PLUGIN_ROOT}`; Codex exposes the installed `SKILL.md` path in its skill catalog. Never assume the current working directory is the skill directory. Use the official `expo:*` skills when the host has them installed. If they are absent, do not block the ordinary scaffold, Expo Go preview, or validation flow: follow this skill's embedded Expo instructions and normal React Native conventions. For specialized dev-client or store-release work, use the corresponding EAS commands directly or explain the missing companion plugin only when it is actually needed. The host's approval and sandbox rules always win. An **AUTO** item means the workflow does not need a separate product decision; it never means bypass a Cod