More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Expo Project Structure: Where Every File Lives

    1

    Lay out a new Expo Router app so a file's location answers what it is: routes only in app/, reusable UI in components/, screen bodies in screens/, server code fenced off.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Expo Project Structure: Where Every File Lives

    Expo Project Structure: Where Every File Lives

    Example session with this skill installed

    Lay out a new Expo app for me: a habit tracker with a home list, habit detail, a settings screen, and a server route that syncs habits to the cloud. iOS, Android, and web.

    • Read your context and instructions
    • Compiled the expo project structure

    Habit tracker — layout produced with the skill

    Skeleton (client-only folders kept, server fenced):

    • src/app/_layout.tsx, index.tsx (habit list route), habits/[id].tsx (detail route), settings/index.tsx — routes only, each under 60 lines, reading params and rendering a screen body.
    • src/app/api/sync+api.ts — the only server route, grouped under api/; its auth helper lives in src/server/auth.ts, never imported by client code.
    • src/screens/home/ — list body plus private habit-row.tsx and streak-chip.tsx; src/screens/habit-detail/ — detail body plus private progress-ring.tsx. Neither is promoted yet: only one screen uses each.
    • src/components/ — empty on day one except button.tsx and card.tsx, the two pieces two screens already share.
    • src/utils/format-date.ts + format-date.test.ts beside it; src/hooks/use-habits.ts; src/theme.ts for tokens.

    Platform call: the progress ring is one file with Platform.select for a web hover tooltip — a style-level difference, not a split. No server/ logic leaks: the sync helper the client calls is a plain fetch in utils/, and the secret stays in server/auth.ts. Rubric score: 9/10 — one point held back because utils/ has no grouping yet; it gets utils/format/ once it passes ten files.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    A new project is the one moment when the folder layout is cheap to get right. This skill lays out an Expo Router skeleton where every file's location answers what it is: routes only in src/app/, reusable UI in components/, screen bodies and their private parts in screens/, server routes grouped under app/api/ with helpers fenced in server/. It enforces the thin-route rule (params, layout, render — under 60 lines), promotes components to shared only on second use, and splits platform variants only when behavior genuinely differs, with identical props and always a default file.

    You get the full skeleton with a one-line job per folder, a decision table for the seven signals that say "move this file now," a layout checklist, and a scoring rubric with a ship threshold of 8/10. Edge cases cover the utils junk drawer, the alias that lets screens import routes, the web-only file with no default, and server logic hiding in a shared hook. A worked example walks the first week of a recipes app — filter chips staying private until a second screen needs them, the shopping-list API fenced in server/, a web-only hover variant — so the rules are concrete, not abstract.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Mobile Development.

    • It is for new projects only — restructuring an existing app is a migration with its own risks, not a skeleton.
    • It does not decide navigation structure, state management, or backend architecture; those are separate decisions.
    • The 60-line route rule and the ten-file utils grouping are judgment thresholds, not laws — a team can tune them, but should write the tuned numbers down.
    • It assumes Expo Router with src/app/; the classic app/-at-root layout needs the paths adjusted.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 3 days ago

    Permissions

    No special permissions declared or detected

    Listed3 days ago

    What's inside

    Frequently Asked Questions

    No — that is the skill's explicit boundary. A starting skeleton is not a migration plan. For an existing app, use the rules as a review lens (find the helpers hiding in app/, the premature promotions) and move files one at a time with tests, not as a big-bang restructure.

    On second use, by a second screen — not before. Reuse is a fact, not a forecast. The move itself is cheap: move the file, update the two imports, delete the old location.

    Because a parallel styles tree makes every rename cost two edits, and the second edit gets forgotten. Styles at the bottom of the component file keep one source of truth for one component.

    New in Mobile Development