Skip to content
Beskid Platform specification

Beskid

Jump to a Beskid service

Beskid

Jump to a Beskid service

beskid new command

Platform spec feature

beskid new command

Spec standingStandard

Owner
Piotr Mikstacki
Submitter
Piotr Mikstacki

What this feature specifies

The beskid new command family — list, install, uninstall, and instantiate templates from registry, path, or git with interactive and flag-driven parameters.

Implementation anchors

  • compiler/crates/beskid_cli/src/cli.rs — subcommand tree
  • Planned compiler/crates/beskid_cli/src/commands/new.rs
  • compiler/crates/beskid_pckg — registry download

Contract statement

The Beskid CLI must expose a top-level beskid new command family for template discovery, installation, and instantiation. This is the only normative user entrypoint for scaffolding; beskid pckg remains publish/upload only.

Command taxonomy

CommandObligation
beskid new listList installed and optionally online templates
beskid new install <package|path|git>Cache template for offline use
beskid new uninstall <shortName|package>Remove cached template
beskid new <shortName> [options]Instantiate installed template by short name
beskid new --path ...Instantiate without prior install
beskid new --git ...Instantiate from git source
beskid new --package <id>[@version]Instantiate from registry (install if needed)

Global options documented in contracts and edge cases.

First-party templates

When the registry is reachable, the CLI must resolve beskid.templates.console, beskid.templates.lib, and beskid.templates.project from pckg—not from files shipped inside the CLI binary. Short names console, lib, and template map to those packages when unambiguous.

Decisions

No open decisions. Closed choices: D-TOOL-SCAFF-0001 (beskid new command), 0002 (interactive modes), 0003 (update check on instantiate)—see adr/ and the ADRs tab.

Articles