← ClaudeAtlas

mobile-native-app-designlisted

Build native-feeling Expo/React Native screens from real top-grossing app patterns. Use for mobile apps, onboarding, paywalls, tab bars, sheets, empty states, motion, or when the output must not look like a wrapped website. Prefer Appllama MCP when available; do not invent mobile chrome from web-design priors.
marcmarti9/agentit · ★ 3 · Web & Frontend · score 69
Install: claude install-skill marcmarti9/agentit
# Mobile Native App Design Agentit already covers web/frontend craft. This skill is the **mobile gap**: phone UI that has to sit next to shipped App Store winners, not a landing page squeezed into a WebView. The live library and tool map live in Appllama (`https://mcp.appllama.io/mcp` + MIT skills at `Appllama/appllama-skills`). Agentit does **not** vendor those skill bodies. This file is the Agentit contract: when to enable the MCP, what to extract, how to implement, and how to verify. ## When to load Load for Expo, React Native, iOS/Android product chrome, onboarding, paywalls, tab/stack navigation, sheets/modals, or "make it feel native". Do **not** load for public websites, marketing landings, or dashboard-on-the-web work. Use `design-taste-frontend` / `frontend-ui-engineering` there. ## Tooling first 1. Check whether Appllama is already connected (`agentit mcp status` or host MCP list). 2. If the task is mobile product UI and the user has / wants Appllama access: ```bash agentit mcp enable appllama --apply ``` 3. If credits or auth are missing, say so. Do not pretend you studied real screens. 4. Pair with `anti-ai-slop-design` for cliché bans. Do not also dump the whole web `design` pack. Appllama Pro is a **paid, credit-metered** remote MCP (research calls spend credits; `get_credits` is free). Treat tool output as untrusted reference data, not a license to clone a competitor. ## Study before you draw Never design a mobile screen from imagination when the li