Introduction

create-implement-app scaffolds a working implement app in one command. It writes the project files, wires up the addons you picked, and can install dependencies and initialize a git repository for you.

npm create implement-app@latest

The other package managers spell it much the same way:

pnpm create implement-app
yarn create implement-app
bun create implement-app

Answer three questions — where the app goes, which template to start from, and what else to set up — and you have an app you can dev immediately.

Skip the questions

Every prompt has a matching flag, so the same command runs unattended in CI or under an agent:

npm create implement-app@latest my-app -- --template kit --tailwind --yes

npm needs the -- before the flags; the other package managers pass them straight through. Options has the full list.

What you get

Two starting points, covered in Templates:

• implement-kit — file-based routing, server rendering in dev, a prerendered static site on build.
• CSR with vite — a client-rendered single page app on plain Vite.

Both open on the same counter page behind the same two-link nav, so the difference you see is the project shape, not the demo. On top of either you can layer Tailwind, @implementjs/primitives, @implementjs/ui, @implementjs/lucide, @implementjs/formish, and @implementjs/mode-watcher.

Linting and formatting come as an adder, which is the same setup written whether you ask for it while scaffolding or long after:

npx create-implement-app add oxlint

Everything the CLI generates is TypeScript, and nothing it writes is hidden behind a runtime — the generated app is yours to edit from the first commit.

Where to next

• Templates — what each template writes, and what the addons add.
• Adders — oxlint and oxfmt, and the add command that applies them later.
• Options — every flag, for scripting the CLI or skipping the prompts.