CLI reference — Frontfriend

The CLI is included in @frontfriend/tailwind. Run each command’s --help for the options supported by your installed version.

Tokens and diagnostics

npx frontfriend init
npx frontfriend init --force
npx frontfriend status
npx frontfriend check
npx frontfriend clean

init fetches and prepares tokens. status inspects configuration and cache state. check validates token configuration. clean clears the token cache. Regenerate after cleaning before relying on cached builds.

Component downloads

npx frontfriend download button accordion -f react --primitive base --registry v4

Option	Meaning
`-f, --framework`	`react` or `vue`
`-p, --primitive`	`radix`, `base`, `aria`, or `reka`
`--registry`	`v4` or `legacy`
`-o, --output`	Destination directory
`--overwrite`	Replace existing files deliberately

all requests the complete applicable catalogue. Start with named components and review changes before choosing a broad download. The target must be a supported framework/primitive pair and your project needs an ff-id.

Migration and recovery

npx frontfriend migrate --help
npx frontfriend migrate --component button --no-push
npx frontfriend upgrade-config --help
npx frontfriend restore --help
npx frontfriend codemod v4 --help

Migration can change component configuration; restore can change remote state. Inspect snapshots, output and the exact installed CLI behavior before accepting a write. See Adopt Frontfriend and v3 migration.

Authentication and agents

npx frontfriend login
npx frontfriend logout
npx frontfriend mcp --help
npx frontfriend agents install
npx frontfriend design sync

Complete login through the device flow. mcp starts the local authenticated stdio proxy. Skill installation and design sync write project-local context; inspect those changes before committing.

Command availability

Run npx frontfriend --help to inspect the commands provided by your installed version. Use Versions & releases to understand how component adoption relates to your Design System.