@chill-sharp/chill-cli

Chill CLI

Create a ChillSharp workspace that is ready for your preferred coding agent.

npm install -g @chill-sharp/chill-cli
chill new my-data-project
cd my-data-project

chill new asks whether to create an ASP.NET Core API, an Angular UI, or both. It creates the project directory, installs the maintained ChillSharp agent skills in .agents/skills, and adds AGENTS.md with instructions that agent tools can follow while developing the project.

The API is generated with dotnet new webapi and adds ChillSharp from NuGet. The UI is generated by @chill-sharp/create-app and installs its dependencies from npm. No local NuGet packages or .tgz archives are copied into the generated workspace.

For a normal application request, that guidance requires the coding agent to deliver a connected system:

• an ASP.NET Core backend using ChillSharp and EF Core;
• an authenticated management UI that changes real backend data; and
• a user-facing frontend that reads and writes the same API.

The agent should only omit one of those layers when the request explicitly asks for an API-only, UI-only, or static prototype. A visual-only frontend, mock data, and browser-only persistence do not satisfy a full application request.

Use a concrete prompt that names the user roles and first workflow. For example:

Create a blog with an ASP.NET Core ChillSharp backend and middleware. Authors must be able to sign in and manage posts and categories in an admin UI. Visitors must be able to browse published posts in a separate frontend. Both UIs must use the same API and database.

The command uses only Node.js standard-library APIs, so it works on Linux, macOS, and Windows with Node.js 20 or later.

Command

chill new <project-name> [--api|--ui|--both]

Without an option, the command displays this menu:

1. API (ASP.NET Core + ChillSharp)
2. UI (Angular + ChillSharp UI)
3. API and UI

Use --api, --ui, or --both for a non-interactive run. Project names use lowercase letters, digits, and hyphens. The command refuses to overwrite an existing directory. Creating an API requires the .NET SDK; creating a UI requires npm and internet access to the public package registries.

Install a client package

From the target project directory, run:

chill install

The menu can install one published dependency at a time:

• @chill-sharp/ng-client, @chill-sharp/vue-client, @chill-sharp/react-client, or @chill-sharp/ts-client with npm;
• ChillSharp or ChillSharp.Client with dotnet add package; or
• chill-sharp-py-client with python -m pip install.

Use a non-interactive option such as chill install --vue-client. For .NET packages, run the command from the directory containing the target .csproj file.