ワンクリックでManusで任意のスキルを実行

rn-publishing-payments

スター3

フォーク0

更新日2026年5月26日 22:05

Use when preparing an Expo + RN app for store submission (metadata, screenshots, localized listings, privacy nutrition label, age rating) and integrating monetization (In-App Purchases via RevenueCat for digital goods/subscriptions; Stripe via WebView ONLY for non-digital services). Triggers on: "submit to App Store", "Play Store listing", "screenshot sizes", "RevenueCat setup", "Stripe payment in app", "subscription", "IAP", "privacy nutrition label", "App Store review reject". Not for: building / submitting (rn-eas-build-submit-update), backend setup (rn-backend).

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

lukedj78

lukedj78/dev-flow

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

rn-publishing-payments — guardrail for store publishing + payments

The 5 rules (non-negotiable)

Apple's 30% rule: ANY digital good/service consumed inside the app MUST go through IAP. Subscriptions, premium tiers, in-app currency, unlock-feature one-shots — all IAP. Bypassing this = banishment from the App Store (guideline 3.1.1).
Stripe / external payment only for NON-digital: physical goods (shipped), services rendered outside the app (ride, food delivery, classroom), B2B (consultant invoice). Even then, Apple's "anti-steering" rules apply — careful what you link.
Use RevenueCat for IAP, not raw react-native-iap. RevenueCat handles receipt validation, cross-platform subscriptions, restore-purchases, sandbox testing, and analytics in one SDK with a generous free tier. Raw IAP works but you'll write 10x the code.
Screenshots must be REAL screenshots of the running app, not marketing illustrations (guideline 2.3.10). 3 sizes per platform required (see references/store-assets.md).
Privacy nutrition label (iOS) + Data safety (Android) MUST match reality. Lying about data collection = ban. Audit the SDKs you use (analytics, push, crash reporting) — each declares what it collects.

Quick decision tree

"IAP, Stripe, or external link?" → references/decision-tree.md
"What assets do I need for the store?" → references/store-assets.md
"How do I integrate RevenueCat?" → references/revenuecat.md
"What about App Store review?" → references/review-guidelines.md

Common anti-patterns (NEVER do)

❌ "Buy premium" button that opens Stripe Checkout in a WebView for an in-app subscription → rejection.
❌ "Already paid on the web? Sign in to unlock" → tolerated under specific conditions (reader app exemption, multi-platform service), but read the rules first.
❌ Hardcoded "€4.99/month" in the UI — use product.priceString from RevenueCat / StoreKit (localized currency, tax-included for EU).
❌ Skipping Sign in with Apple when offering Google sign-in (iOS) → 4.8 reject.
❌ Marketing screenshots with fake content or device frames not provided by Apple → 2.3 reject.
❌ Privacy nutrition label that says "no data collected" while you ship Firebase Analytics → ban risk.
❌ Asking for IDFA (ATT prompt) before showing app value → bad practice + low opt-in rate.

Sources

Course: codewithbeto.dev/rnCourse — "Publishing, Payments, Native Modules" module (paid).
Official Apple: https://developer.apple.com/app-store/review/guidelines/
Official Google: https://support.google.com/googleplay/android-developer/topic/9858052
Official RevenueCat: https://www.revenuecat.com/docs/getting-started
Official Stripe RN: https://stripe.com/docs/payments/accept-a-payment?platform=react-native

このリポジトリの他の Skills

同じリポジトリ

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-publishing-payments

description

rn-publishing-payments — guardrail for store publishing + payments

The 5 rules (non-negotiable)

Apple's 30% rule: ANY digital good/service consumed inside the app MUST go through IAP. Subscriptions, premium tiers, in-app currency, unlock-feature one-shots — all IAP. Bypassing this = banishment from the App Store (guideline 3.1.1).
Stripe / external payment only for NON-digital: physical goods (shipped), services rendered outside the app (ride, food delivery, classroom), B2B (consultant invoice). Even then, Apple's "anti-steering" rules apply — careful what you link.
Use RevenueCat for IAP, not raw react-native-iap. RevenueCat handles receipt validation, cross-platform subscriptions, restore-purchases, sandbox testing, and analytics in one SDK with a generous free tier. Raw IAP works but you'll write 10x the code.
Screenshots must be REAL screenshots of the running app, not marketing illustrations (guideline 2.3.10). 3 sizes per platform required (see references/store-assets.md).
Privacy nutrition label (iOS) + Data safety (Android) MUST match reality. Lying about data collection = ban. Audit the SDKs you use (analytics, push, crash reporting) — each declares what it collects.

Quick decision tree

"IAP, Stripe, or external link?" → references/decision-tree.md
"What assets do I need for the store?" → references/store-assets.md
"How do I integrate RevenueCat?" → references/revenuecat.md
"What about App Store review?" → references/review-guidelines.md

Common anti-patterns (NEVER do)

❌ "Buy premium" button that opens Stripe Checkout in a WebView for an in-app subscription → rejection.
❌ "Already paid on the web? Sign in to unlock" → tolerated under specific conditions (reader app exemption, multi-platform service), but read the rules first.
❌ Hardcoded "€4.99/month" in the UI — use product.priceString from RevenueCat / StoreKit (localized currency, tax-included for EU).
❌ Skipping Sign in with Apple when offering Google sign-in (iOS) → 4.8 reject.
❌ Marketing screenshots with fake content or device frames not provided by Apple → 2.3 reject.
❌ Privacy nutrition label that says "no data collected" while you ship Firebase Analytics → ban risk.
❌ Asking for IDFA (ATT prompt) before showing app value → bad practice + low opt-in rate.

Sources

Course: codewithbeto.dev/rnCourse — "Publishing, Payments, Native Modules" module (paid).
Official Apple: https://developer.apple.com/app-store/review/guidelines/
Official Google: https://support.google.com/googleplay/android-developer/topic/9858052
Official RevenueCat: https://www.revenuecat.com/docs/getting-started
Official Stripe RN: https://stripe.com/docs/payments/accept-a-payment?platform=react-native