@chill-sharp/chill-cli 1.1.19 → 1.1.20

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@chill-sharp/chill-cli",
-  "version": "1.1.19",
+  "version": "1.1.20",
   "description": "Start a ChillSharp project with agent-ready guidance.",
   "license": "AGPL-3.0-or-later",
   "type": "module",

package/skills/chillsharp-full-stack-application/SKILL.md

@@ -7,11 +7,32 @@ description: Build a connected ChillSharp application with an ASP.NET Core API,
 
 Treat a request to build a new site or application in a ChillSharp workspace as a full-stack request unless the user explicitly limits it to an API, a UI, or a static prototype.
 
+## Public package catalog
+
+Use these published packages directly. Do not search the local filesystem, clone the ChillSharp repository, or recreate a client library to find an implementation that is already available here.
+
+| Registry | Package | Use it for |
+| --- | --- | --- |
+| NuGet | `ChillSharp` | The ASP.NET Core backend, including the core API and bundled auth, schema, i18n, MCP, and attachment modules. |
+| NuGet | `ChillSharp.Client` | A .NET application that consumes a ChillSharp API. |
+| npm | `@chill-sharp/create-app` | Generate an Angular application shell with the standard ChillSharp UI dependencies. |
+| npm | `@chill-sharp/ui-core` | The shared Angular management UI, layouts, CRUD pages, and providers. |
+| npm | `@chill-sharp/ts-client` | A framework-neutral browser or TypeScript client. |
+| npm | `@chill-sharp/ng-client` | Angular client helpers. |
+| npm | `@chill-sharp/react-client` | React providers and hooks. |
+| npm | `@chill-sharp/vue-client` | Vue plugin and composables. |
+| npm | `@chill-sharp/chill-cli` | Create an agent-ready ChillSharp workspace; it is not a runtime dependency. |
+| PyPI | `chill-sharp-py-client` | A Python client for a ChillSharp API. |
+
+For a new Angular management UI, prefer `npm create @chill-sharp/app <app-name>` rather than building a replacement from local source. For another frontend stack, install its matching client package and connect it to the API. Use only the client family needed by the requested application; do not install every package in this table.
+
+For example, add the backend with `dotnet add package ChillSharp`, a browser client with `npm install @chill-sharp/ts-client`, or a Python integration with `pip install chill-sharp-py-client`.
+
 ## Required delivered components
 
 Deliver all of these as working parts of the same application:
 
-1. **ASP.NET Core backend.** Create a runnable backend that uses ChillSharp: an EF Core `DbContext` implementing `IChillContext`, ChillSharp entities and query types for the requested data, `AddChillApi`, and `MapChillApi`. Use the registration and model-preparation skills for the exact setup.
+1. **ASP.NET Core backend.** Create a runnable backend that uses the public `ChillSharp` NuGet package: an EF Core `DbContext` implementing `IChillContext`, ChillSharp entities and query types for the requested data, `AddChillApi`, and `MapChillApi`. Use the registration and model-preparation skills for the exact setup.
 2. **Management UI.** Create an authenticated staff/admin experience that reads and writes the backend's real ChillSharp data. Use the ChillSharp schema/menu and client guidance when a ChillSharp UI client is appropriate. Do not substitute a design mock-up, static page, or local-only data editor.
 3. **User-facing frontend.** Create the requested public/customer-facing experience and connect it to the same backend API. Its displayed and submitted data must come from real API calls, not fixtures, browser storage, or a parallel mock service.