https://docs.strapi.io/cms/cli

Day-to-day development

npm run develop      # Start with auto-reload (use this while building)
npm run start        # Start without auto-reload (production mode)
npm run build        # Build the admin panel
npm run strapi console  # Interactive REPL with full Strapi context

Content type & schema generation

strapi generate      # Interactive generator (content-type, component, policy, middleware, service, controller)
strapi content-types:list   # List all registered content types

• includes plugin:: + admin:: types

Database

strapi export        # Export data + schema to an encrypted .tar.gz
strapi import        # Import a previously exported archive
strapi transfer      # Live transfer data between two Strapi instances (e.g. local → production)

TypeScript

strapi ts:generate-types   # Regenerate backend/types/generated/contentTypes.d.ts

This is the one you should run after adding or editing a schema — it's what keeps your TypeScript types in sync.

Deployment / cloud

strapi deploy        # Push to Strapi Cloud (if using their hosting)

Upgrade

npx @strapi/upgrade minor   # Upgrade to latest minor version
npx @strapi/upgrade major   # Upgrade to latest major version
npx @strapi/upgrade latest  # Upgrade to absolute latest
npx @strapi/upgrade latest --dry  # Preview what would change without applying it

The two you'll use most when working on schema: npm run develop to run locally, and strapi ts:generate-types after any schema change before committing.