@chill-sharp/chill-cli 1.1.16 → 1.1.19

package/README.md

@@ -10,6 +10,18 @@ cd my-data-project
 
 `chill new` creates the project directory and installs the maintained ChillSharp agent skills in `.agents/skills`. It also adds `AGENTS.md` with instructions that agent tools can follow while developing the project.
 
+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

package/bin/chill.mjs

@@ -53,11 +53,11 @@ function createProject(name) {
 }
 
 function projectInstructions(name) {
-  return `# ${name}\n\nThis project is prepared for ChillSharp development with a coding agent.\n\nBefore changing ChillSharp code, inspect the relevant skill in \`.agents/skills\`. Use the project\'s existing conventions and keep implementation work focused on the requested outcome.\n\nFor a new ChillSharp backend, start by describing the users, data, and first workflow. The agent can then use the included model, registration, permissions, i18n, menu, plugin, and MCP guidance as needed.\n`;
+  return `# ${name}\n\nThis project is prepared for ChillSharp development with a coding agent.\n\nBefore changing ChillSharp code, inspect the relevant skill in \`.agents/skills\`. Use the project\'s existing conventions and keep implementation work focused on the requested outcome.\n\nWhen asked to build a new site or application, use \`.agents/skills/chillsharp-full-stack-application/SKILL.md\`. Unless the user explicitly asks for an API-only, UI-only, or static prototype, deliver a connected ASP.NET Core ChillSharp API, an authenticated management UI for real data, and a user-facing frontend that uses the same API. Do not replace those components with mock data, browser-only storage, or a standalone visual site.\n\nFor a new application, start by describing the users, data, and first workflow. The agent can then use the included full-stack, model, registration, permissions, i18n, menu, plugin, and MCP guidance as needed.\n`;
 }
 
 function projectReadme(name) {
-  return `# ${name}\n\nA ChillSharp project workspace prepared for coding agents.\n\n## Start building\n\nOpen this folder with your coding agent and describe the first outcome you want to deliver. The agent guidance lives in [\`.agents/skills\`](.agents/skills).\n\nFor example:\n\n> Build a service directory for our nonprofit. Visitors should be able to find local support services, while staff can securely manage the underlying data.\n\n## Included guidance\n\nThe workspace contains ChillSharp skills for model preparation, registration, permissions, localized text, menus, client plugins, current-user preferences, documentation, and MCP.\n`;
+  return `# ${name}\n\nA ChillSharp project workspace prepared for coding agents.\n\n## Start building\n\nOpen this folder with your coding agent and describe the first outcome you want to deliver. The agent guidance lives in [\`.agents/skills\`](.agents/skills).\n\nA request to build an application produces a connected system by default: an ASP.NET Core ChillSharp API, an authenticated management UI, and a user-facing frontend using that API. Ask for an API-only, UI-only, or static prototype only when that is genuinely the desired scope.\n\nFor example:\n\n> Build a blog. Authors sign in to manage posts and categories in an admin UI; visitors can browse published posts in a separate public frontend. Use the same ChillSharp API and database for both.\n\n## Included guidance\n\nThe workspace contains skills for full-stack application delivery, model preparation, registration, permissions, localized text, menus, client plugins, current-user preferences, documentation, and MCP.\n`;
 }
 
 function printUsage() {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@chill-sharp/chill-cli",
-  "version": "1.1.16",
+  "version": "1.1.19",
   "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

@@ -0,0 +1,24 @@
+---
+name: chillsharp-full-stack-application
+description: Build a connected ChillSharp application with an ASP.NET Core API, a data-management UI, and a user-facing frontend. Use when a request is to build a site, product, or application rather than only an API or only a client.
+---
+
+# ChillSharp Full-Stack Application
+
+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.
+
+## 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.
+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.
+
+Keep the frontend(s), API URL, CORS or development proxy, authentication flow, and database configuration coherent so they can be started locally together. For a deliberately unsecured demo, say that choice explicitly; otherwise protect staff data and management routes with ChillSharp authentication and authorization.
+
+## Before declaring the work complete
+
+Verify the backend builds and starts, a ChillSharp endpoint responds, the management UI can complete a representative create or update against the API, and the user-facing frontend can read that persisted data. Record the local start commands and URLs in the project README.
+
+Do not stop after creating only a visual frontend, only a data model, or only a list of proposed next steps. If an existing project already supplies one of the three components, preserve it and implement the missing connected components.