CLI reference

• directory is required and must not already contain a product.
• marketing is the default and currently implemented preset.
• Repeat --module to select multiple optional modules as they become available.
• --recipe selects a predefined page composition. The default is marketing-classic.
• Repeat --block to replace the recipe with an exact ordered block selection.
• --plan resolves and prints the operation without writing files.
• --json emits machine-readable output where supported.

pnpm stackiln create <directory> \
  --preset marketing \
  --name "Product name" \
  [--description "..."] \
  [--module accounts] \
  [--recipe saas-launch] \
  [--block hero.centered] \
  [--plan] [--json]

Starts the local visual builder for a new marketing product. The directory is the eventual export destination. Studio saves a validated local draft while you arrange blocks and edit design and content, then exports through the standard planner and staged creation path.

pnpm stackiln studio <directory> [--port 4173]

Reports the preset, installed modules, Stackiln version, deployment target, and changed managed files. The directory defaults to the current working directory.

pnpm stackiln inspect [directory] [--json]

Checks state readability, managed-file hashes, DATABASE_URL, and APP_URL. It exits with code 1 when managed files have changed and code 2 for invalid commands or arguments.

pnpm stackiln doctor [directory] [--json]

Prints a concise map of the product for maintainers and coding agents. --write saves the same snapshot as AGENT_CONTEXT.md.

pnpm stackiln context [directory]
pnpm stackiln context [directory] --write

Runs the framework repository's canonical verification gate. It requires Docker and is distinct from pnpm verify inside a generated product.

pnpm stackiln verify