Templates

earthling-ui create clones a maintained template repository, replaces project placeholders, and removes the template Git history. It requires network access and an empty destination directory.

bash

npx earthling-ui create <template> <destination>

The destination accepts lowercase letters, numbers, and dashes.

Available templates

Template	Aliases	Kind	Example
`next`	`ssr`, `nextjs`	App	`npx earthling-ui create next customer-portal`
`vite`	`spa`	App	`npx earthling-ui create vite dashboard`
`tauri`	`app`, `desktop`	App	`npx earthling-ui create tauri desktop-client`
`kiosk`	`electron`	App	`npx earthling-ui create kiosk lobby-display`
`db`	`database`, `drizzle`	Package	`npx earthling-ui create db data-access`
`lib`	`library`	Package	`npx earthling-ui create lib shared-utils`
`cli`	—	Package	`npx earthling-ui create cli release-tools`
`monorepo`	`repo`	Repository	`npx earthling-ui create monorepo product-suite`

Aliases select the same canonical repository. For example, spa clones template-vite, and ssr clones template-next.

Destination behavior

Inside a workspace whose root package.json includes apps/*, app templates are placed under apps. Package templates use packages/* in the same way. Repository templates are created at the requested path and initialized as a new Git repository.

Outside a matching workspace, the destination is created under the current directory.

Templates live under the earthling-collective organization. Review the generated package.json and setup notes before adding credentials or deploying.