Ship

code-with-beto/ship

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.

487 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

130

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/Code-with-Beto/skills --skill ship

The instruction itself

8 sections, as written by the author

@codewithbeto/ship

Ship a revenue-ready AI image app this weekend.

Built by Code with Beto — Platano landing page

Quick start

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

Clone the template repo (shallow, then remove .git)
Configure app name, bundle ID, slug, and payment keys
Run bun install
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

cd <project-name>
npx expo start

How to use it

Copy the folder

Take code-with-beto/ship from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.

Install what it needs

The instructions reference npx. Without those the skill loads but fails at the first command.