Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

rn-expo-router

Étoiles3

Forks0

Mis à jour26 mai 2026 à 22:04

Use when working with navigation in an Expo + React Native app: adding routes, building tab/stack/drawer layouts, modal routes, dynamic segments (e.g. /profile/[id]), typed routes, deep linking, search params. Triggers on: "add a route", "wire up tabs", "open as modal", "set up deep linking", "configure navigation", or whenever an agent is about to touch a file under app/. Not for: styling navigation chrome (rn-styling), animating transitions (rn-animations-gestures, Wave 3), or non-RN web routing.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

lukedj78

lukedj78/dev-flow

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

Explorateur de fichiers

9 fichiers

SKILL.md

readonly

name

rn-expo-router

description

rn-expo-router — guardrail for navigation in Expo + RN

The 4 rules (non-negotiable)

Expo Router only. Never import from @react-navigation/* directly — Expo Router wraps and owns it.
File-based: routes live in app/. The filename IS the URL. _layout.tsx files define the layout for their directory.
Typed routes ON. In app.json: "expo": { "experiments": { "typedRoutes": true } }. Use Href type for navigation, never raw strings.
Layouts contain navigators. Screen files contain only the screen UI. Tab bar / stack header config goes in _layout.tsx.

Quick decision tree

"Tabs / Stack / Drawer — which?" → references/decision-tree.md
"How do I structure routes for an auth-gated section?" → references/patterns.md (Auth groups)
"Deep linking from notification or URL?" → references/deep-linking-setup.md
"Show me a real layout" → references/examples/

Common anti-patterns (NEVER do)

❌ import { useNavigation } from '@react-navigation/native' → use useRouter() from expo-router.
❌ router.push('/profile/123') as raw string → typed routes: router.push({ pathname: '/profile/[id]', params: { id: '123' } }).
❌ Defining a <Tabs.Screen> in a screen file — it goes in the parent _layout.tsx.
❌ Hardcoded route strings scattered everywhere → use typed routes (expo-router/typed-routes provides static checking).

Sources

Course: codewithbeto.dev/rnCourse — lesson 11 "Navigation Basics" (free) + 1 free Expo Router lesson.
Official: https://docs.expo.dev/router/introduction/
Official: https://docs.expo.dev/router/reference/typed-routes/

Plus depuis ce dépôt

même dépôt

design-md-to-app

lukedj78/dev-flow

Generate or customize a frontend application from a DESIGN.md (Google design.md spec). Reads the YAML tokens + markdown rationale and produces a working React app whose theme, typography, spacing, radii, and components are pre-styled to match. **Canonical target: Next.js 16 + App Router** (Pages Router or pre-16 explicitly refused). Supports three UI libraries: shadcn/ui (Tailwind + copy-pasted source), Base UI (Tailwind + headless library, no CLI overhead), and MUI (runtime themed, Material-flavored). Supports two form libraries: **TanStack Form + Zod (default, recommended)** or react-hook-form (opt-in). Integrates with the dev-flow contract: when a `.workflow/` exists, reads `meta.json#stack`, writes the app at the project root (alongside `.workflow/`), and bumps phase to `scaffolded`. Use whenever the user has a DESIGN.md and wants to scaffold an app, set up a theme, customize shadcn/Base UI/MUI from these tokens, or "use this DESIGN.md to start an app". Trigger on "DESIGN.md → app", "scaffold from design.

2026-07-183

module-add

lukedj78/dev-flow

Wire a backend or infrastructure module (auth, database, payments, email, file storage, deploy config) into an already-scaffolded app. Reads `.workflow/meta.json#stack` for the chosen tech (better-auth, drizzle+neon, stripe, resend, vercel, etc.) and modifies the codebase at the project root to install + configure the module end-to-end. Always idempotent — running twice does not duplicate config. Use when the user says "add auth", "wire up the database", "set up Stripe", "add file uploads", "configure deploy", "module aggiungi auth", or the orchestrator routes here from phase `scaffolded` / `page_generated`. Not for: scaffolding the app (`design-md-to-app`) or building UI (`screenshot-to-page`).

2026-07-173

eve-agent

lukedj78/dev-flow

Scaffold and manage an eve agent (Vercel's filesystem-first agent framework) inside a monorepo, as the engine behind a Next.js app. Use this skill whenever the user wants to create, set up, or initialize an eve agent; add a tool, skill, channel, connection, schedule, subagent, or hook to an eve agent; wire a Next.js (or any) frontend to consume an eve agent; or evolve the `apps/agent` part of a project. Trigger this for ANY mention of "eve", "the agent engine", "agent tools", "agent backend", or building the agentic core of an app — even if the user does not say the word "skill". This is the eve counterpart to dev-flow's Next.js skills (design-md-to-app / module-add); use it for the agent the same way you'd use those for the web app. Not for: building the Next.js app itself or its pages/forms (use design-md-to-app / screenshot-to-page / module-add), scaffolding the monorepo (use monorepo-bootstrap), or React Native (eve is a server-side engine, not an RN concern).

2026-07-173

screenshot-to-page

lukedj78/dev-flow

Generate a real, working page (route + components) inside an already-scaffolded app from a single UI screenshot, applying the project's DESIGN.md tokens and the existing UI library (shadcn or MUI). Reads a screenshot from `.workflow/screenshots/`, plus `.workflow/DESIGN.md` and `.workflow/meta.json` for tokens and stack, then writes the route into the codebase at the project root. Use when the user says "fai questa pagina dallo screenshot", "build the home page from this image", "/journal route from this PNG", "convert this mockup to code", or the orchestrator routes here from phase `scaffolded` with unmapped screenshots present. Not for: scaffolding the app from scratch (use `design-md-to-app`), extracting tokens from Figma (use `figma-to-design-md`), or wiring backend modules (use `module-add`).

2026-07-173

monorepo-bootstrap

lukedj78/dev-flow

Scaffold a turborepo monorepo containing both a Next.js web app AND an Expo + RN mobile app, with shared packages (types, design tokens, backend client). Uses pnpm workspaces + turborepo. Reads .workflow/meta.json with stack.framework="monorepo" and phase in {prd_drafted, design_extracted}. Produces: root package.json + pnpm-workspace.yaml + turbo.json + packages/typescript-config + packages/eslint-config; apps/web/ scaffolded via design-md-to-app; apps/mobile/ scaffolded via rn-bootstrap; packages/shared/ + packages/design/ + packages/api/ skeletons. Always idempotent. Use when dev-flow routes here from prd_drafted+monorepo, or the user says "scaffolda il monorepo", "create a turborepo with web + mobile", "bootstrap il monorepo da PRD + DESIGN.md". Not for: scaffolding only web (use design-md-to-app), scaffolding only mobile (use rn-bootstrap), adding modules after scaffold (use module-add or rn-module-add).

2026-06-303

dev-flow

lukedj78/dev-flow

Orchestrate an end-to-end product-development workflow built on atomic skills. Reads `.workflow/meta.json` in a project directory, figures out what phase the user is in (idea → PRD → tasks → design → scaffolded → pages → modules → tests), and delegates to the right specialist skill: `prd-from-idea`, `prd-to-tasks`, `figma-to-design-md`, `image-to-design-md`, `design-md-to-app`, `screenshot-to-page`, `module-add`, `write-tests`, `forms`, `data-fetching`, `state-discipline`, `eve-agent` (the eve agent engine behind the app). Use when the user wants to "start a new project end-to-end", "advance my project to the next stage", "what should I do next on this project", or pastes a brand-new product idea / Figma URL / inspiration images with a request to "build the app". Not for: deeply-specialized work inside one stage (in that case, invoke the specialist skill directly).

2026-06-293

name

rn-expo-router

description

rn-expo-router — guardrail for navigation in Expo + RN

The 4 rules (non-negotiable)

Expo Router only. Never import from @react-navigation/* directly — Expo Router wraps and owns it.
File-based: routes live in app/. The filename IS the URL. _layout.tsx files define the layout for their directory.
Typed routes ON. In app.json: "expo": { "experiments": { "typedRoutes": true } }. Use Href type for navigation, never raw strings.
Layouts contain navigators. Screen files contain only the screen UI. Tab bar / stack header config goes in _layout.tsx.

Quick decision tree

"Tabs / Stack / Drawer — which?" → references/decision-tree.md
"How do I structure routes for an auth-gated section?" → references/patterns.md (Auth groups)
"Deep linking from notification or URL?" → references/deep-linking-setup.md
"Show me a real layout" → references/examples/

Common anti-patterns (NEVER do)

❌ import { useNavigation } from '@react-navigation/native' → use useRouter() from expo-router.
❌ router.push('/profile/123') as raw string → typed routes: router.push({ pathname: '/profile/[id]', params: { id: '123' } }).
❌ Defining a <Tabs.Screen> in a screen file — it goes in the parent _layout.tsx.
❌ Hardcoded route strings scattered everywhere → use typed routes (expo-router/typed-routes provides static checking).

Sources

Course: codewithbeto.dev/rnCourse — lesson 11 "Navigation Basics" (free) + 1 free Expo Router lesson.
Official: https://docs.expo.dev/router/introduction/
Official: https://docs.expo.dev/router/reference/typed-routes/