_____ _ _ _ __ __ _ _
|_ _| |__ ___ | | __ _ ___| |_ | \/ (_) | ___
| | | '_ \ / _ \ | | / _` / __| __| | |\/| | | |/ _ \
| | | | | | __/ | |__| (_| \__ \ |_ | | | | | | __/
|_| |_| |_|\___| |_____\__,_|___/\__| |_| |_|_|_|\___|
Build it with AI. Ship it with one command.
/ship takes your app from your laptop to the App Store and Google Play. Any
stack.
Building it was the fun part. Then comes the last mile: developer accounts,
certificates, build numbers, screenshots in five sizes, privacy questionnaires, and
a reviewer who rejects you for saying "Google Play" on your paywall. It's where most
AI built apps quietly stall.
Your app doesn't need to be perfect. It needs to be in the store, because that's
the only place it can get a user, and a user is the only person who can ever pay
you for it.
/ship handles the last mile. Getting real users and paying users comes next, and
that's where this repo is going.
/plugin marketplace add namedtoaster/the-last-mile
/plugin install the-last-mile@the-last-mile
Then, in your app's folder:
/ship
What /ship does
- Works out what you have. Expo, React Native, Flutter, Swift, Kotlin,
Capacitor, .NET MAUI, Kotlin Multiplatform, or a web app from Lovable, Bolt or v0
that needs wrapping first. iOS, Android or both. First release or an update.
- Finds what will get you rejected, before a reviewer does. It checks your code
against a list of traps that actually caught real apps, each with the official
rule it comes from and the date someone last checked it.
- Fixes what it can. Version and build numbers, permissions you don't need, text
that names the other store, missing account deletion, and so on.
- Builds the release version and has you test it, because some bugs only exist
there.
- Writes your store listing. Name, subtitle, keywords, description, review notes,
and a draft of the privacy answers based on the SDKs your app actually uses.
- Uploads and submits from the command line where the stores allow it, after you
say yes.
- Tells you exactly what only you can do, like paying for the developer account or
signing the agreements, then picks up where it left off.
- Shows where you stand.
/ship status puts every item on a board, on your
phone or your desktop, with what only you can do at the top.
To see what it finds without starting a release, run /ship sweep. It checks the app,
fixes what you agree to, and stops before the version bump. Nothing is built,
uploaded or submitted.
It looks up the current store rules every time instead of trusting its memory, because
Apple and Google change them.
[!NOTE]
Early release. The shipping process comes from a real app live on the App Store and
Google Play. The paths for other stacks follow each framework's official docs and
have had less real-world use. Tell us what breaks.
What it won't do
- Judge your idea. It gets you through review. Whether people want the app is still up to you.
- Click "Submit for review" without asking you.
- Make up store rules. Every rule it checks has a link to Apple's or Google's own
page. If it can't check one, it says so.
- Guarantee approval. Every rule it checks is one someone read and dated against
Apple's or Google's own page. A reviewer is still a person, and one can say no for a
reason nobody has written down. That's what the next section is for.
Got rejected anyway?
Run /ship with the rejection message. It fixes only what the reviewer asked for,
drafts a short reply, and resubmits.
Then tell us what caught you.
Every rejection someone reports becomes a check for everyone after them.
Want a second look before you submit?
I'll run the checks on your app myself and send you what I find, each with the file
and line. Free for now. Ask here
with your stack and when you plan to submit.
Then: users. Then: money.
Being in the store gets you zero users on its own. Nobody searches for your app.
Next up in this repo, from what actually worked (and didn't) for a real app:
| Next skill | What it does |
|---|
| analytics | Tracks the few things that matter: who opened it, who came back, who paid |
| store-listing | A name, subtitle, keywords and screenshots someone might actually tap |
| creator-codes | Free premium codes for a creator's audience, with tracking. Cost so far: nothing |
| ugc-brief | Finding small creators and paying them to make videos. The best move so far |
| release-notes | Turns your commit log into notes people want to read |
Fair warning: the author has a handful of paying users, not a growth machine. These
skills will say what worked, what didn't, and how sure anyone is.
Other agents
Cursor, Codex, Gemini CLI and other agents that read skills:
npx skills add namedtoaster/the-last-mile
I only use Claude Code, so these are untested anywhere else. If something breaks in
your agent, tell me
or send the fix.
Cloud sessions (Claude Code on the web and the Claude app on your phone) do not
load plugins. Keep a synced copy of the skills in your project instead, which works
on every device. sync/README.md covers setting it up (one prompt),
staying current with /sync, and fixing a skill from your own fork.
The rest of the kit
/ship stands on its own. These are for the days between releases. Most are
written for any stack; see-it-work is still Expo first.
여기까지가 README 앞부분입니다. 나머지는 원문에서 읽을 수 있습니다. README 전문 보기 ↗
