Zeek.Cli

Zeek.Cli is the recommended entry point for generating modular Zeek Avalonia desktop applications.

dotnet tool install --global Zeek.Cli
zeek new app Acme.Product
cd Acme.Product
zeek add module Orders
zeek doctor

Commands:

• zeek new app <name> installs the matching Zeek.Templates package and creates the fixed zeek-app solution shape.
• zeek add module <name> creates a zeek-module, adds it to the solution, updates Shell/Test project references, and updates the fully-qualified entries inside AppModule.Composition.cs. Re-running it reconciles those deterministic connections without overwriting module files.
• zeek doctor checks the actual dotnet path, selected SDK, any application-owned global.json, NuGet source mapping, template version, generated solution shape, and Native AOT prerequisites. On Windows it checks the active toolchain first, then vswhere, then the default Visual Studio and Windows SDK locations.

The CLI delegates generation to the official dotnet new Template Engine and uses dotnet sln add and .NET 10 dotnet reference add. It does not implement a custom template engine, plugin platform, runtime module scanner, interactive wizard, or Server generator.

The CLI does not create, modify, or enforce global.json. Generated applications target net10.0, while SDK selection and optional patch pinning remain owned by the application and its CI.

The CLI does not choose or replace login-page designs. zeek-app generates one default LoginView; after generation, that view belongs to the application. Alternative designs are development references in samples/Zeek.LoginViewGallery, not CLI or Template Engine options.

Zeek.Cli and Zeek.Templates versions are locked together. For local package acceptance, ZEEK_TEMPLATE_PACKAGE can point to a packed Zeek.Templates nupkg, ZEEK_TEMPLATE_VERSION can override the expected test version, ZEEK_CANDIDATE_FEED can redirect generated applications to a complete local set of candidate Zeek packages, and ZEEK_PUBLIC_PACKAGE_FEED can redirect third-party restore to a complete local NuGet folder source. These variables are test hooks, not normal user configuration.