CLI reference

The launchswift CLI (implemented in cli/src/) provides four commands:

• new
• add
• deploy
• greenlight

Installation

The currently reproducible installation flow is from source:

git clone https://github.com/cardotrejos/launchswift.git
cd launchswift
cd cli
npm install
npm run build
npm link
launchswift --help

Commands

launchswift new

Scaffold a new SwiftLaunch project.

launchswift new <name> [--template <github|embedded|local-path>]

Options:

Flag	Description	Default
--template	Template source (github, embedded, or local path)	github

What it does:

1. Prompts for:
   • project name
   • bundle ID
   • deployment path (appleNative or fullStack)
   • optional feature list
2. Scaffolds from the Pro GitHub template (or embedded/local template source)
   • github: attempts to clone the LaunchSwift Pro Template
   • on access-denied: falls back to the embedded Free Starter Template
   • embedded: always uses the Free Starter Template
3. Applies substitutions (bundle ID, project name, deployment path, feature flags)
4. Initializes git unless LAUNCHSWIFT_SKIP_GIT is set
5. Runs npm install for backend/ on Full Stack projects unless LAUNCHSWIFT_SKIP_INSTALL is set
6. Applies selected feature templates via the same mechanism as launchswift add

Free Starter vs Pro output

• Free Starter Template: app shell + backend /healthz + starter feature files
• LaunchSwift Pro Template: fully wired auth, AI chat, payments, analytics, i18n, Liquid Glass, and full backend/API surface

Example:

launchswift new MyApp --template embedded

launchswift add

Add a feature module to an existing project.

launchswift add [feature]

Available features:

Feature	Description
auth-apple	Apple auth feature templates
auth-betterauth	Full-stack auth templates
ai-chat	AI chat with SSE streaming
analytics	TelemetryDeck integration
i18n	Localization feature templates
payments	StoreKit 2 paywall templates
revenuecat	RevenueCat integration templates
feedback	In-app feedback form
liquid-glass	iOS 26+ Liquid Glass components

What it does:

1. Copies files from cli/templates/features/<feature>/ into your project (without overwriting existing files)
2. Applies feature-specific mutations:
   • analytics / revenuecat: updates ios/project.yml package dependencies
   • auth-betterauth / feedback: updates backend/src/index.ts route mounts
3. Regenerates Xcode project with xcodegen on a best-effort basis

Example:

launchswift add payments

launchswift deploy

Deploy the Path B backend to Cloudflare Workers.

launchswift deploy [--wrangler]

Options:

Flag	Description	Default
--wrangler	Backwards-compatible alias (currently a no-op)	false

What it does:

1. Verifies backend/package.json exists and contains a deploy script
2. Runs npm run deploy inside backend/

Example:

launchswift deploy

launchswift greenlight

Run the App Store compliance scanner (Greenlight) on your iOS project.

launchswift greenlight [--path <target-directory>]

Options:

Flag	Description	Default
--path	Path to scan	ios

What it does:

1. Executes scripts/greenlight-scan.sh <targetPath>
2. Writes reports to:
   • .artifacts/greenlight/greenlight.txt
   • .artifacts/greenlight/greenlight.md

Example:

launchswift greenlight

Local scripts

These scripts are available in the repo but not part of the CLI:

scripts/ci-local.sh

Full local CI pipeline — builds, lints, and typechecks everything.

./scripts/ci-local.sh

scripts/greenlight-scan.sh

Direct wrapper for the Greenlight scanner:

./scripts/greenlight-scan.sh ios