@salesforce/templates 66.13.4 → 66.13.6

package/lib/templates/project/reactinternalapp/PRD.md

@@ -0,0 +1,35 @@
+# Internal User App (B2E)
+
+## Overview
+
+A ready-to-use starter for building internal, employee-facing apps on the Salesforce platform. It comes with a clean, modern interface, page navigation, and a built-in Agentforce chat assistant. It ships with no data of its own — a clean slate — but includes one working example (an Account search with filtering, sorting, and a detail view) that shows how the app reads Salesforce data, so teams can point it at their own information.
+
+## Problem
+
+Teams building internal tools on Salesforce keep re-solving the same setup: standing up a new app, choosing how it looks, connecting it to Salesforce data, and adding an Agentforce assistant. Starting from a prebuilt demo means ripping out someone else's data before any real work begins; starting from scratch means rebuilding the same foundation every time. There has been no simple, opinionated starting point that gives just the essentials and one correct example of showing Salesforce data.
+
+## Solution
+
+A minimal internal starter with the essentials already in place: the app framework, page navigation, a built-in Agentforce chat assistant, and a single example feature — Account search — that shows how the app displays Salesforce data. Everything is structured so the Account example works as a template: point it at your own information, adjust the fields, and remove the example once your own feature is working.
+
+### Core Features
+
+- **App framework and navigation** — A ready-made layout with a Home page, a "page not found" screen, and a navigation menu, prepared for adding new screens.
+- **Consistent design system** — A preinstalled set of interface building blocks so new screens look consistent from the start.
+- **Account search example** — A complete example with a search bar, filters, sorting, and paging, plus a search results screen and a detail view. This is the template for showing Salesforce data.
+- **Agentforce chat assistant** — A built-in chat surface an Agentforce agent can drive, giving the app in-app assistance.
+- **Add-on features** — Tooling to browse and add additional prebuilt features into the app.
+
+### Non-Goals
+
+- Shipping a prebuilt data model — this starter deliberately includes none; teams bring their own.
+- External-facing use, sign-in, or public site hosting — use the External User App (B2X) starter for that.
+- A finished application — the Account example is meant to be copied and then removed, not kept.
+
+## Target Users
+
+Salesforce teams building employee-facing tools (support consoles, ops dashboards, internal admin apps) who want a clean, minimal starting point rather than a demo they have to dismantle first.
+
+## Org prerequisites
+
+- The in-app Agentforce chat assistant requires Agentforce to be set up in the org, with an agent configured for it.

package/lib/templates/project/reactinternalapp/README.md

@@ -71,9 +71,12 @@ Two npm scripts at the project root streamline getting started and deployment.
 
 **`npm run sf-project-setup`** — installs the UI Bundle dependencies, builds the app, and starts the dev server (see [Getting started](#getting-started)).
 
-**`npm run setup`** — runs the full deployment setup in one command: org login (if needed), UI Bundle build, deploy the UI Bundle, fetch GraphQL schema, run codegen, and optionally start the dev server:
+**`npm run setup`** — runs the full deployment setup in one command: org login (a required precondition, auto-skipped if already connected), UI Bundle build, deploy the UI Bundle, fetch GraphQL schema, and run codegen. It no longer starts the dev server — run `npm run dev:preview` for that:
 
 ```bash
+# Install project dependencies first (required before running setup)
+npm install
+
 npm run setup -- --target-org <alias>
 ```
 
@@ -85,15 +88,16 @@ npm run setup -- --target-org <alias> --yes
 
 Common options:
 
-| Option                    | Description                                    |
-| ------------------------- | ---------------------------------------------- |
-| `--skip-login`            | Skip browser login (org already authenticated) |
-| `--skip-deploy`           | Do not deploy metadata                         |
-| `--skip-graphql`          | Skip GraphQL schema fetch and codegen          |
-| `--skip-ui-bundle-build`  | Skip `npm install` and UI Bundle build         |
-| `--skip-dev`              | Do not start the dev server at the end         |
-| `--ui-bundle-name <name>` | UI Bundle folder name when multiple exist      |
-| `-y, --yes`               | Skip interactive step picker; run all steps    |
+| Option                    | Description                                     |
+| ------------------------- | ----------------------------------------------- |
+| `--target-org <alias>`    | Target org. If omitted, uses default org/prompt |
+| `--skip-deploy`           | Do not deploy metadata                          |
+| `--skip-graphql`          | Skip GraphQL schema fetch and codegen           |
+| `--skip-ui-bundle-build`  | Skip `npm install` and UI Bundle build          |
+| `--ui-bundle-name <name>` | UI Bundle folder name when multiple exist       |
+| `-y, --yes`               | Skip interactive step picker; run all steps     |
+
+> Login is a required precondition (no `--skip-login`), and the dev server is no longer part of setup (no `--skip-dev`); both flags are accepted but ignored. To start the dev server after setup, run `npm run dev:preview`.
 
 For all options: `npm run setup -- --help`.