Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

rn-eas-build-submit-update

Estrellas3

Forks0

Actualizado26 de mayo de 2026 a las 22:05

Use for cloud builds and OTA updates of an Expo + RN app via EAS: configuring eas.json profiles (development/preview/production), managing credentials (APNs key, Android keystore) without committing them to git, submitting builds to App Store Connect / Google Play via EAS Submit, shipping JS-only fixes via EAS Update with channels/branches, EAS Workflows for CI. Triggers on: "set up EAS Build", "OTA update", "EAS Submit", "configure eas.json", "deploy to Play Store / TestFlight". Not for: store metadata/screenshots/IAP (rn-publishing-payments), scaffolding (rn-bootstrap), or the end-to-end deploy orchestration (rn-eas-deploy).

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

lukedj78

lukedj78/dev-flow

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

Explorador de archivos

6 archivos

SKILL.md

readonly

name

rn-eas-build-submit-update

description

rn-eas-build-submit-update — guardrail for EAS Build / Submit / Update / Workflows

The 5 rules (non-negotiable)

3 profiles in eas.json: development (dev client, internal), preview (TestFlight / Play Internal — test on real devices), production (the store). NEVER ship from a profile not pre-tested in preview.
Credentials server-side via eas credentials. NEVER commit .p12, .p8, *.keystore, *.jks, or google-services.json for production accounts. EAS holds them; local Apple/Google CLI never touches them.
OTA only for JS-only changes. If the diff touches app.json config plugins, native modules, or anything that would change prebuild output → it's a new build, not an Update.
Channels separate environments. preview channel for QA, production channel for end users. Ship updates to preview first, promote to production only after smoke-test.
expo-updates config in app.json is the source of truth for runtime version (runtimeVersion: { policy: "appVersion" } or "sdkVersion"). Mismatched runtime versions = OTAs ignored.

Quick decision tree

"Build, Submit, or Update — which do I need now?" → references/decision-tree.md
"How do I write the eas.json profiles?" → references/eas-json.md
"How do credentials work — where does the cert live?" → references/credentials.md
"How do I set up EAS Workflows for CI?" → references/workflows.md

Common anti-patterns (NEVER do)

❌ Committing certificates / keystores to git.
❌ eas build --profile production without ever having built --profile preview for that commit.
❌ eas update --channel production without --branch <name> and without testing on preview channel first.
❌ Updating app.json config plugins and shipping via OTA — fails silently or crashes on user devices.
❌ Bumping version in app.json without also bumping ios.buildNumber / android.versionCode — store reject.
❌ expo-updates with default runtimeVersion (none) — OTA gets applied to incompatible native builds → crash.

Sources

Course: codewithbeto.dev/rnCourse — EAS Build/Submit/Update/Workflows modules (paid).
Official: https://docs.expo.dev/eas/
Official: https://docs.expo.dev/eas-update/introduction/
Official: https://docs.expo.dev/eas-workflows/get-started/

Más de este repositorio

mismo repositorio

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-eas-build-submit-update

description

rn-eas-build-submit-update — guardrail for EAS Build / Submit / Update / Workflows

The 5 rules (non-negotiable)

3 profiles in eas.json: development (dev client, internal), preview (TestFlight / Play Internal — test on real devices), production (the store). NEVER ship from a profile not pre-tested in preview.
Credentials server-side via eas credentials. NEVER commit .p12, .p8, *.keystore, *.jks, or google-services.json for production accounts. EAS holds them; local Apple/Google CLI never touches them.
OTA only for JS-only changes. If the diff touches app.json config plugins, native modules, or anything that would change prebuild output → it's a new build, not an Update.
Channels separate environments. preview channel for QA, production channel for end users. Ship updates to preview first, promote to production only after smoke-test.
expo-updates config in app.json is the source of truth for runtime version (runtimeVersion: { policy: "appVersion" } or "sdkVersion"). Mismatched runtime versions = OTAs ignored.

Quick decision tree

"Build, Submit, or Update — which do I need now?" → references/decision-tree.md
"How do I write the eas.json profiles?" → references/eas-json.md
"How do credentials work — where does the cert live?" → references/credentials.md
"How do I set up EAS Workflows for CI?" → references/workflows.md

Common anti-patterns (NEVER do)

❌ Committing certificates / keystores to git.
❌ eas build --profile production without ever having built --profile preview for that commit.
❌ eas update --channel production without --branch <name> and without testing on preview channel first.
❌ Updating app.json config plugins and shipping via OTA — fails silently or crashes on user devices.
❌ Bumping version in app.json without also bumping ios.buildNumber / android.versionCode — store reject.
❌ expo-updates with default runtimeVersion (none) — OTA gets applied to incompatible native builds → crash.

Sources

Course: codewithbeto.dev/rnCourse — EAS Build/Submit/Update/Workflows modules (paid).
Official: https://docs.expo.dev/eas/
Official: https://docs.expo.dev/eas-update/introduction/
Official: https://docs.expo.dev/eas-workflows/get-started/