@futurethesislab/cli

Add FTLAB Venture Kit components, elements, pages and the design system into any Next.js app — the way shadcn does, for the @futurethesislab registry.

Requirements

ftlab init needs only an empty folder — it scaffolds a complete Next.js app. ftlab add layers into an existing Next.js (App Router) project using Tailwind CSS v4 and the @/* → ./src/* path alias.

Usage

# Scaffold a complete, runnable venture site into an empty folder (then: pnpm install && pnpm dev)
npx @futurethesislab/cli init

# Add individual pieces
npx @futurethesislab/cli add @futurethesislab/hero-band @futurethesislab/pricing-table @futurethesislab/header-pill

# Add a whole page template…
npx @futurethesislab/cli add @futurethesislab/page-docs @futurethesislab/app-dashboard

# …or the entire marketing site
npx @futurethesislab/cli add @futurethesislab/website

# Browse everything
npx @futurethesislab/cli list

Every item declares @futurethesislab/base as a dependency, so the CLI installs the foundation automatically the first time.

Options

| Flag | Meaning | |---|---| | --registry <url\|path> | Registry base (default: the jsDelivr CDN; use a local path to test). | | --overwrite | Overwrite files that already exist. | | --no-install | Don't run the package manager; print the deps instead. | | --cwd <dir> | Target a different project directory. |

The package manager is detected from your lockfile (pnpm / npm / yarn / bun).

How it works

add fetches the item JSON from the registry, recursively resolves its @futurethesislab/* registryDependencies, writes the files into your project (source files under src/, brands/ + content/ at the root), and installs the union of npm dependencies.