ship

Included with Lifetime

$97 forever

Scaffold production-ready React Native apps using the @codewithbeto/ship CLI. Use when the user wants to create a new app from a Code with Beto template, scaffold a project with Platano, or run `bunx @codewithbeto/ship`. Always use flag-based (non-interactive) mode — the interactive TUI requires a terminal.

Web Dev

What this skill does


# @codewithbeto/ship

Ship a revenue-ready AI image app this weekend.
Built by [Code with Beto](https://codewithbeto.dev) — [Platano landing page](https://cwb.sh/platano)

## Quick start

```bash
bunx @codewithbeto/ship --name my-app
```

## Flags

| Flag | Required | Default |
|------|----------|---------|
| `--name <dir>` | Yes | — |
| `--template <name>` | No | `platano` |
| `--app-name <name>` | No | title-cased `--name` |
| `--bundle-id <id>` | No | `com.<user>.<slug>` |
| `--payments` / `--no-payments` | No | `--payments` |
| `--rc-key-ios <key>` | No | — |
| `--rc-key-android <key>` | No | same as iOS key |
| `--dry-run` | No | — |

## What it does

1. Clone the template repo (shallow, then remove `.git`)
2. Configure app name, bundle ID, slug, and payment keys
3. Run `bun install`
4. Initialize a fresh git repo with baseline commit

## Output

- **stderr** — progress logs (checking access, cloning, configuring)
- **stdout** — structured result on success:

```
name: my-app
app_name: My App
bundle_id: com.beto.my-app
slug: my-app
payments: true
template: platano
directory: my-app
```

## Error handling

Errors go to stderr and exit with code 1. Common failures:

- **Access denied** — user needs Pro access at https://cwb.sh/platano
- **Directory exists** — pick a different `--name`
- **Install failed** — ensure `bun` is available

## After scaffolding

```bash
cd <project-name>
npx expo start
```

## Links

- Course & Pro access: https://cwb.sh/rn
- YouTube: https://cwb.sh/youtube
- Discord: https://cwb.sh/discord
- Newsletter: https://cwb.sh/newsletter

Files: 1

Size: 1.9 KB

Complexity: 7/100

Category: Web Dev

Source: https://github.com/code-with-beto/skills/tree/main/plugins/cwb-ship/skills/ship

Related in Web Dev

generating-lwc-components

Included

Lightning Web Components with PICKLES methodology and 165-point scoring. Use this skill when the user creates or edits LWC components, builds wire service patterns, or writes Jest tests for LWC. TRIGGER when: user creates/edits LWC components, touches lwc/**/*.js, .html, .css, .js-meta.xml files, or asks about wire service, SLDS, or Jest LWC tests. DO NOT TRIGGER when: Apex classes (use generating-apex), Aura components, or Visualforce.

Web Devscripts

tanstack-query

Included

Manage server state in React with TanStack Query v5. Set up queries with useQuery, mutations with useMutation, configure QueryClient caching strategies, implement optimistic updates, and handle infinite scroll with useInfiniteQuery. Use when: setting up data fetching in React projects, migrating from v4 to v5, or fixing object syntax required errors, query callbacks removed issues, cacheTime renamed to gcTime, isPending vs isLoading confusion, keepPreviousData removed problems.

Web Devscripts

document-processor-api

Included

Process documents with Nutrient DWS. Use when the user wants to generate PDFs from HTML or URLs, convert Office/images/PDFs, assemble or split packets, OCR scans, extract text/tables/key-value pairs, redact PII, watermark, sign, fill forms, optimize PDFs, or produce compliance outputs like PDF/A or PDF/UA. Triggers include convert to PDF, merge these PDFs, OCR this scan, extract tables, redact PII, sign this PDF, make this PDF/A, or linearize for web delivery.

Web Devscripts

nutrient-document-processing

Included

Web Devscripts

tanstack-query

Included

Manage server state in React with TanStack Query v5. Covers useMutationState, simplified optimistic updates, throwOnError, network mode (offline/PWA), and infiniteQueryOptions. Use when setting up data fetching, fixing v4→v5 migration errors (object syntax, gcTime, isPending, keepPreviousData), or debugging SSR/hydration issues with streaming server components.

Web Devscripts

accelint-nextjs-best-practices

Included

Next.js performance optimization and best practices. Use when writing Next.js code (App Router or Pages Router); implementing Server Components, Server Actions, or API routes; optimizing RSC serialization, data fetching, or server-side rendering; reviewing Next.js code for performance issues; fixing authentication in Server Actions; or implementing Suspense boundaries, parallel data fetching, or request deduplication.

Web Devscripts