Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
pproenca avatar

Expo Ios Screen Scaffolder

  • 69 installs
  • 191 repo stars
  • Updated July 24, 2026
  • pproenca/dot-skills

expo-ios-screen-scaffolder is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted coding.

Key points

  • expo-ios-screen-scaffolder
  • AI & Agent Building
  • AI-coding skill

Expo Ios Screen Scaffolder by the numbers

  • 69 all-time installs (skills.sh)
  • +7 installs in the week ending Aug 4, 2026 (Skillselion tracking)
  • Ranked #5,786 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
  • Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/pproenca/dot-skills --skill expo-ios-screen-scaffolder

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs69
repo stars191
Last updatedJuly 24, 2026
Repositorypproenca/dot-skills

How do I helps with ai & agent building tasks during ai-assisted development?

Helps with ai & agent building tasks during AI-assisted development.

Who is it for?

Best when you're working on ai & agent building and need structured help with expo-ios-screen-scaffolder.

Skip if: Teams with no ai & agent building needs, or anyone wanting a generic chat assistant without this specific workflow.

When should I use this skill?

When you need to helps with ai & agent building tasks during ai-assisted development, or when expo-ios-screen-scaffolder is a claude code skill for ai & agent building. it helps solo builders move faster with ai-assiste

What you get

Structured output aligned to expo-ios-screen-scaffolder: expo-ios-screen-scaffolder; AI & Agent Building; AI-coding skill.

Files

SKILL.mdMarkdownGitHub ↗

Expo iOS Screen Scaffolder

Parameterized templates that generate HIG-compliant Expo Router screens. Every template produces a screen that is native-by-construction — native navigation, virtualized lists, safe areas, semantic colors, SF Symbols, haptics, and honest empty states — so new screens start correct instead of being retrofitted. Each generated file cites the expo-ios-hig rules it satisfies.

When to Apply

Use this skill when the user wants to:

  • Create or add a new screen, route, or layout in an Expo app for iOS
  • Scaffold a list, detail, form, modal sheet, tab bar, or settings screen
  • Start a new Expo feature and want the screens to feel native from the first commit
  • Bring an existing screen up to the conventions in references/conventions.md

Available Templates

To scaffold: read the template, substitute the placeholders, and write the result to its route path under app/. Placeholders use single braces (e.g., {ScreenName}); the literal TSX braces stay as-is.

TemplateGeneratesPlaceholders
`list-screen.tsx.template`Large-title list: FlashList + RefreshControl + empty state + bottom safe-area inset{ScreenName} {Entity} {entity_plural} {Title} {route_path} {sf_symbol}
`detail-screen.tsx.template`Pushed detail: edge-to-edge scroll, semantic colors, system share button{ScreenName} {Entity} {entity} {entityId}
`form-screen.tsx.template`Create form: keyboard avoidance, configured input, optimistic save + haptics{ScreenName} {Entity} {entity}
`modal-sheet.tsx.template`formSheet route with detents + grabber and Cancel/Done{ScreenName} {Title} {route_name}
`native-tabs-layout.tsx.template`Root NativeTabs layout with SF Symbol icons (repeat per tab){tab_name} {Tab_label} {tab_sf_symbol}
`settings-screen.tsx.template`Grouped settings: SectionList + platform Switch rows{ScreenName} {Title}

Common placeholders:

  • {ScreenName} — PascalCase component with a Screen suffix, e.g. TrailsScreen
  • {Entity} / {entity} / {entity_plural} — PascalCase, camelCase, and plural forms, e.g. Trail / trail / trails
  • {entityId} — dynamic route param name, matching the file ([trailId].tsxtrailId)
  • {Title} — navigation bar title text, e.g. Trails
  • {route_path} / {route_name} — route segment(s) used for navigation
  • {sf_symbol} / {tab_sf_symbol} — SF Symbol name from Apple's SF Symbols app
  • {file_path} — the destination path, written into the header comment

How to Use

1. Pick the template for the screen type. 2. Choose values for its placeholders (see the table above and the header comment inside each template). 3. Substitute and write to the route path, e.g. app/(trails)/index.tsx, app/(trails)/[trailId].tsx. 4. Implement the imported companion (use{Entity}List, create{Entity}, …) — the scaffold owns the view, you own the data layer. 5. Read references/conventions.md for the rules each template enforces and when to deviate.

Setup

config.json is optional. Override on first use if your project differs:

  • app_dir — Expo Router routes directory (default app)
  • components_dir — shared components directory (default components)
  • list_componentFlashList (default) or FlatList for the list template

Related Skills

  • `expo-ios-hig` — the rules these templates follow; each generated file cites them.
  • `expo-ios-hig-verify` — run it after scaffolding to confirm the screen stays native.

Related skills

FAQ

What does expo-ios-screen-scaffolder do?

expo-ios-screen-scaffolder is a Claude Code skill for ai & agent building. It helps developers move faster with AI-assisted coding.

When should I use expo-ios-screen-scaffolder?

When you need to helps with ai & agent building tasks during ai-assisted development, or when expo-ios-screen-scaffolder is a claude code skill for ai & agent building. it helps developers move faster with ai-assisted coding.

What are the main capabilities?

expo-ios-screen-scaffolder; AI & Agent Building; AI-coding skill.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.