@salesforce/webapp-template-feature-react-file-upload-experimental 1.106.2 → 1.107.0

package/dist/.a4drules/skills/{salesforce-data-access → accessing-data}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: salesforce-data-access
+name: accessing-data
 description: Salesforce data access patterns. Use when adding or modifying any code that fetches data from Salesforce (records, Chatter, Connect API, etc.).
 paths:
   - "**/*.ts"
@@ -42,7 +42,7 @@ For GraphQL, if `sdk.graphql` is undefined, the call returns `undefined` — han
 - Creating, updating, or deleting records (when GraphQL supports the operation)
 - Fetching related data, filters, sorting, pagination
 
-**Use `sdk.fetch` only when GraphQL is not sufficient.** For REST API usage, invoke the `salesforce-rest-api-fetch` skill, which documents:
+**Use `sdk.fetch` only when GraphQL is not sufficient.** For REST API usage, invoke the `fetching-rest-api` skill, which documents:
 
 - Chatter API (e.g., `/services/data/v65.0/chatter/users/me`)
 - Connect REST API (e.g., `/services/data/v65.0/connect/file/upload/config`)
@@ -64,7 +64,7 @@ const sdk = await createDataSDK();
 
 ## Example 1: GraphQL (Preferred)
 
-For record queries and mutations, use GraphQL via the Data SDK. Invoke the `salesforce-graphql` skill for the full workflow (schema exploration, query authoring, codegen, lint validate).
+For record queries and mutations, use GraphQL via the Data SDK. Invoke the `using-graphql` skill for the full workflow (schema exploration, query authoring, codegen, lint validate).
 
 ```typescript
 import { createDataSDK, gql } from "@salesforce/sdk-data";
@@ -103,7 +103,7 @@ export async function getAccounts() {
 
 ## Example 2: Fetch (When GraphQL Is Not Sufficient)
 
-For REST endpoints that have no GraphQL equivalent, use `sdk.fetch`. **Invoke the `salesforce-rest-api-fetch` skill** for full documentation of Chatter, Connect REST, Apex REST, UI API REST, and Einstein LLM endpoints.
+For REST endpoints that have no GraphQL equivalent, use `sdk.fetch`. **Invoke the `fetching-rest-api` skill** for full documentation of Chatter, Connect REST, Apex REST, UI API REST, and Einstein LLM endpoints.
 
 ```typescript
 import { createDataSDK } from "@salesforce/sdk-data";
@@ -151,15 +151,15 @@ const res = await sdk.fetch?.("/services/data/v65.0/chatter/users/me");
 
 ## Decision Flow
 
-1. **Need to query or mutate Salesforce records?** → Use GraphQL via the Data SDK. Invoke the `salesforce-graphql` skill.
-2. **Need Chatter, Connect REST, Apex REST, UI API REST, or Einstein LLM?** → Use `sdk.fetch`. Invoke the `salesforce-rest-api-fetch` skill.
+1. **Need to query or mutate Salesforce records?** → Use GraphQL via the Data SDK. Invoke the `using-graphql` skill.
+2. **Need Chatter, Connect REST, Apex REST, UI API REST, or Einstein LLM?** → Use `sdk.fetch`. Invoke the `fetching-rest-api` skill.
 3. **Never** use `fetch`, `axios`, or similar directly for Salesforce API calls.
 
 ---
 
 ## Reference
 
-- GraphQL workflow: invoke the `salesforce-graphql` skill (`.a4drules/skills/salesforce-graphql/`)
-- REST API via fetch: invoke the `salesforce-rest-api-fetch` skill (`.a4drules/skills/salesforce-rest-api-fetch/`)
+- GraphQL workflow: invoke the `using-graphql` skill (`.a4drules/skills/using-graphql/`)
+- REST API via fetch: invoke the `fetching-rest-api` skill (`.a4drules/skills/fetching-rest-api/`)
 - Data SDK package: `@salesforce/sdk-data` (`createDataSDK`, `gql`, `NodeOfConnection`)
 - `createRecord` for UI API record creation: `@salesforce/webapp-experimental/api` (uses Data SDK internally)

package/dist/.a4drules/skills/{webapp-metadata-and-config → configuring-webapp-metadata}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: webapp-metadata-and-config
+name: configuring-webapp-metadata
 description: Rules for web application metadata structure, webapplication.json configuration, and bundle organization
 ---
 

package/dist/.a4drules/skills/{webapp-creation → creating-webapp}/SKILL.md

@@ -1,4 +1,5 @@
 ---
+name: creating-webapp
 description: Core web application rules for SFDX React apps
 paths:
   - "**/webapplications/**/*"
@@ -81,7 +82,7 @@ Agents consistently miss these. **You must not leave them default.**
 
 # Shell Command Safety (MUST FOLLOW)
 
-**Never use complex `node -e` one-liners** for file edits or multi-line transforms. They break in Zsh due to `!` history expansion and backtick interpolation. Use a temporary `.js` file, `sed`/`awk`, `jq`, or IDE file-editing tools instead. See **webapp-cli-commands.md** for full details and approved alternatives.
+**Never use complex `node -e` one-liners** for file edits or multi-line transforms. They break in Zsh due to `!` history expansion and backtick interpolation. Use a temporary `.js` file, `sed`/`awk`, `jq`, or IDE file-editing tools instead.
 
 # Development Cycle
 

package/dist/.a4drules/skills/{salesforce-graphql-explore-schema → exploring-graphql-schema}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: salesforce-graphql-explore-schema
+name: exploring-graphql-schema
 description: Explore the Salesforce GraphQL schema via grep-only lookups. Use before generating any GraphQL query — schema exploration must complete first.
 paths:
   - "**/*.ts"
@@ -125,7 +125,7 @@ Salesforce GraphQL returns field values wrapped in typed objects:
 2. **Run the "Find Available Fields" grep command** for your object (copy only the field names visible in the grep output; do not open the file)
 3. **Run the "Find Filter Options" grep command** (`<Object>_Filter`) to understand filtering options
 4. **Run the "Find OrderBy Options" grep command** (`<Object>_OrderBy`) for sorting capabilities
-5. **Build the query** following the patterns in the `salesforce-graphql-read-query` or `salesforce-graphql-mutation-query` skill using only values returned by grep
+5. **Build the query** following the patterns in the `generating-graphql-read-query` or `generating-graphql-mutation-query` skill using only values returned by grep
 6. **Validate field names** using grep matches (case-sensitive). Do not open or parse the file beyond grep.
 
 ## Tips for Agents
@@ -156,5 +156,5 @@ If any of the above occurs, stop and replace the action with one of the Allowed
 
 ## Related Skills
 
-- For generating read queries, invoke the `salesforce-graphql-read-query` skill
-- For generating mutation queries, invoke the `salesforce-graphql-mutation-query` skill
+- For generating read queries, invoke the `generating-graphql-read-query` skill
+- For generating mutation queries, invoke the `generating-graphql-mutation-query` skill

package/dist/.a4drules/skills/{salesforce-rest-api-fetch → fetching-rest-api}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: salesforce-rest-api-fetch
+name: fetching-rest-api
 description: REST API usage via the Data SDK fetch method. Use when implementing Chatter, Connect REST, Apex REST, UI API REST, or Einstein LLM calls — only when GraphQL is not sufficient.
 paths:
   - "**/*.ts"
@@ -162,6 +162,6 @@ const data = await response.json();
 
 ## Reference
 
-- Parent: `salesforce-data-access` — enforces Data SDK usage for all Salesforce data fetches
-- GraphQL: `salesforce-graphql` — use for record queries and mutations when possible
+- Parent: `accessing-data` — enforces Data SDK usage for all Salesforce data fetches
+- GraphQL: `using-graphql` — use for record queries and mutations when possible
 - `createRecord` from `@salesforce/webapp-experimental/api` for UI API record creation (uses SDK internally)

package/dist/.a4drules/skills/{salesforce-graphql-mutation-query → generating-graphql-mutation-query}/SKILL.md

@@ -1,6 +1,6 @@
 ---
-name: salesforce-graphql-mutation-query
-description: Generate Salesforce GraphQL mutation queries. Use when the query to generate is a mutation query. Schema exploration must complete first — invoke salesforce-graphql-explore-schema first.
+name: generating-graphql-mutation-query
+description: Generate Salesforce GraphQL mutation queries. Use when the query to generate is a mutation query. Schema exploration must complete first — invoke exploring-graphql-schema first.
 paths:
   - "**/*.ts"
   - "**/*.tsx"
@@ -11,16 +11,16 @@ paths:
 
 **Triggering conditions**
 
-1. Only if the schema exploration phase completed successfully (invoke `salesforce-graphql-explore-schema` first)
+1. Only if the schema exploration phase completed successfully (invoke `exploring-graphql-schema` first)
 2. Only if the query to generate is a mutation query
 
 ## Schema Access Policy
 
-> ⚠️ **GREP ONLY** — During mutation generation you may need to verify field names, input types, or representations. All schema lookups **MUST** use the grep-only commands defined in the `salesforce-graphql-explore-schema` skill. Do NOT open, read, stream, or parse `./schema.graphql` with any tool other than grep.
+> ⚠️ **GREP ONLY** — During mutation generation you may need to verify field names, input types, or representations. All schema lookups **MUST** use the grep-only commands defined in the `exploring-graphql-schema` skill. Do NOT open, read, stream, or parse `./schema.graphql` with any tool other than grep.
 
 ## Your Role
 
-You are a GraphQL expert. Generate Salesforce-compatible mutation queries. Schema exploration must complete first. If the schema exploration has not been executed yet, you **MUST** run the full exploration workflow from the `salesforce-graphql-explore-schema` skill first, then return here for mutation query generation.
+You are a GraphQL expert. Generate Salesforce-compatible mutation queries. Schema exploration must complete first. If the schema exploration has not been executed yet, you **MUST** run the full exploration workflow from the `exploring-graphql-schema` skill first, then return here for mutation query generation.
 
 ## Mutation Queries General Information
 
@@ -186,7 +186,7 @@ npx eslint <path-to-file-containing-mutation>
 
 **On failure:** Fix the reported issues, re-run `npx eslint <file>` until clean, then proceed to testing.
 
-> ⚠️ **Prerequisites**: The `schema.graphql` file must exist (invoke `salesforce-graphql-explore-schema` first) and project dependencies must be installed (`npm install`).
+> ⚠️ **Prerequisites**: The `schema.graphql` file must exist (invoke `exploring-graphql-schema` first) and project dependencies must be installed (`npm install`).
 
 ## Generated Mutation Query Testing
 
@@ -234,12 +234,12 @@ The query is invalid:
 3. **Targeted Resolution** - Depending on the root cause categorization
    - **Execution** - You're trying to update or delete an unknown/no longer available entity: either create an entity first, if you have generated the related query, or ask for a valid entity id to use. **STOP and WAIT** for the user to provide a valid Id
    - **Syntax** - Update the query using the error message information to fix the syntax errors
-   - **Validation** - The field name is most probably invalid. Re-run the relevant grep command from the `salesforce-graphql-explore-schema` skill to verify the correct field name. If still unclear, ask the user for clarification and **STOP and WAIT** for their answer
+   - **Validation** - The field name is most probably invalid. Re-run the relevant grep command from the `exploring-graphql-schema` skill to verify the correct field name. If still unclear, ask the user for clarification and **STOP and WAIT** for their answer
    - **Type** - Use the error details and re-verify the type via grep lookup in the schema. Correct the argument type and adjust variables accordingly
    - **Navigation** - Use the [`PARTIAL` status handling workflow](#partial-status-handling-workflow) below
    - **API Version** - `Record` selection is only available with API version 64 and higher, **report** the issue, and try again with API version 64
 4. **Test Again** - Resume the [query testing workflow](#generated-mutation-query-testing) with the updated query (increment and track attempt counter)
-5. **Escalation Path** - If targeted resolution fails after 2 attempts, ask for additional details and restart the entire GraphQL workflow from the `salesforce-graphql-explore-schema` skill
+5. **Escalation Path** - If targeted resolution fails after 2 attempts, ask for additional details and restart the entire GraphQL workflow from the `exploring-graphql-schema` skill
 
 ### `PARTIAL` Status Handling Workflow
 
@@ -254,5 +254,5 @@ The query can be improved:
 
 ## Related Skills
 
-- Schema exploration: `salesforce-graphql-explore-schema` (must complete first)
-- Read query generation: `salesforce-graphql-read-query`
+- Schema exploration: `exploring-graphql-schema` (must complete first)
+- Read query generation: `generating-graphql-read-query`

package/dist/.a4drules/skills/{salesforce-graphql-read-query → generating-graphql-read-query}/SKILL.md

@@ -1,6 +1,6 @@
 ---
-name: salesforce-graphql-read-query
-description: Generate Salesforce GraphQL read queries. Use when the query to generate is a read query. Schema exploration must complete first — invoke salesforce-graphql-explore-schema first.
+name: generating-graphql-read-query
+description: Generate Salesforce GraphQL read queries. Use when the query to generate is a read query. Schema exploration must complete first — invoke exploring-graphql-schema first.
 paths:
   - "**/*.ts"
   - "**/*.tsx"
@@ -11,12 +11,12 @@ paths:
 
 **Triggering conditions**
 
-1. Only if the schema exploration phase completed successfully (invoke `salesforce-graphql-explore-schema` first)
+1. Only if the schema exploration phase completed successfully (invoke `exploring-graphql-schema` first)
 2. Only if the query to generate is a read query
 
 ## Schema Access Policy
 
-> ⚠️ **GREP ONLY** — During query generation you may need to verify field names, types, or relationships. All schema lookups **MUST** use the grep-only commands defined in the `salesforce-graphql-explore-schema` skill. Do NOT open, read, stream, or parse `./schema.graphql` with any tool other than grep.
+> ⚠️ **GREP ONLY** — During query generation you may need to verify field names, types, or relationships. All schema lookups **MUST** use the grep-only commands defined in the `exploring-graphql-schema` skill. Do NOT open, read, stream, or parse `./schema.graphql` with any tool other than grep.
 
 ## Field-Level Security and @optional
 
@@ -35,7 +35,7 @@ const name = node.Name.value;
 
 ## Your Role
 
-You are a GraphQL expert. Generate Salesforce-compatible read queries. Schema exploration must complete first. If the schema exploration has not been executed yet, you **MUST** run the full exploration workflow from the `salesforce-graphql-explore-schema` skill first, then return here for read query generation.
+You are a GraphQL expert. Generate Salesforce-compatible read queries. Schema exploration must complete first. If the schema exploration has not been executed yet, you **MUST** run the full exploration workflow from the `exploring-graphql-schema` skill first, then return here for read query generation.
 
 ## Read Query Generation Workflow
 
@@ -202,7 +202,7 @@ npx eslint <path-to-file-containing-query>
 
 **On failure:** Fix the reported issues, re-run `npx eslint <file>` until clean, then proceed to testing.
 
-> ⚠️ **Prerequisites**: The `schema.graphql` file must exist (invoke `salesforce-graphql-explore-schema` first) and project dependencies must be installed (`npm install`).
+> ⚠️ **Prerequisites**: The `schema.graphql` file must exist (invoke `exploring-graphql-schema` first) and project dependencies must be installed (`npm install`).
 
 ## Generated Read Query Testing
 
@@ -242,12 +242,12 @@ The query is invalid:
    - **Type** - Error contains `VariableTypeMismatch` or `UnknownType`
 3. **Targeted Resolution** - Depending on the root cause categorization
    - **Syntax** - Update the query using the error message information to fix the syntax errors
-   - **Validation** - The field name is most probably invalid. Re-run the relevant grep command from the `salesforce-graphql-explore-schema` skill to verify the correct field name. If still unclear, ask the user for clarification and **STOP and WAIT** for their answer
+   - **Validation** - The field name is most probably invalid. Re-run the relevant grep command from the `exploring-graphql-schema` skill to verify the correct field name. If still unclear, ask the user for clarification and **STOP and WAIT** for their answer
    - **Type** - Use the error details and re-verify the type via grep lookup in the schema. Correct the argument type and adjust variables accordingly
 4. **Test Again** - Resume the [query testing workflow](#generated-read-query-testing) with the updated query (increment and track attempt counter)
-5. **Escalation Path** - If targeted resolution fails after 2 attempts, ask for additional details and restart the entire GraphQL workflow from the `salesforce-graphql-explore-schema` skill
+5. **Escalation Path** - If targeted resolution fails after 2 attempts, ask for additional details and restart the entire GraphQL workflow from the `exploring-graphql-schema` skill
 
 ## Related Skills
 
-- Schema exploration: `salesforce-graphql-explore-schema` (must complete first)
-- Mutation generation: `salesforce-graphql-mutation-query`
+- Schema exploration: `exploring-graphql-schema` (must complete first)
+- Mutation generation: `generating-graphql-mutation-query`

package/dist/.a4drules/skills/{salesforce-graphql → using-graphql}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: salesforce-graphql
+name: using-graphql
 description: Salesforce GraphQL data access. Use when the user asks to fetch, query, or mutate Salesforce data, or add a GraphQL operation for an object like Account, Contact, or Opportunity.
 paths:
   - "**/*.ts"
@@ -20,7 +20,7 @@ Guidance for querying and mutating Salesforce data via the Salesforce GraphQL AP
 
 ## Schema Access Policy (GREP ONLY)
 
-> **GREP ONLY** — The `schema.graphql` file is very large (~265,000+ lines). All schema lookups **MUST** use the grep-only commands defined in the `salesforce-graphql-explore-schema` skill. Do NOT open, read, stream, or parse `./schema.graphql` with any tool other than grep.
+> **GREP ONLY** — The `schema.graphql` file is very large (~265,000+ lines). All schema lookups **MUST** use the grep-only commands defined in the `exploring-graphql-schema` skill. Do NOT open, read, stream, or parse `./schema.graphql` with any tool other than grep.
 
 ## Directory Context
 
@@ -80,9 +80,9 @@ Ensure `schema.graphql` exists at the project root. If missing, run `npm run gra
 
 Before writing any query, verify the target object and its fields exist in the schema.
 
-**Invoke the `salesforce-graphql-explore-schema` skill** for the full exploration workflow and **mandatory grep-only access policy**.
+**Invoke the `exploring-graphql-schema` skill** for the full exploration workflow and **mandatory grep-only access policy**.
 
-> **GREP ONLY** — All schema lookups MUST use the grep commands defined in the `salesforce-graphql-explore-schema` skill. Do NOT open, read, stream, or parse `./schema.graphql` with any tool other than grep.
+> **GREP ONLY** — All schema lookups MUST use the grep commands defined in the `exploring-graphql-schema` skill. Do NOT open, read, stream, or parse `./schema.graphql` with any tool other than grep.
 
 Key actions (all via grep):
 
@@ -113,8 +113,8 @@ For **Pattern 1**:
 
 1. Create a `.graphql` file under `src/api/utils/query/`
 2. Follow UIAPI structure: `query { uiapi { query { ObjectName(...) { edges { node { ... } } } } } }`
-3. For mutations, invoke the `salesforce-graphql-mutation-query` skill
-4. For read queries, invoke the `salesforce-graphql-read-query` skill
+3. For mutations, invoke the `generating-graphql-mutation-query` skill
+4. For read queries, invoke the `generating-graphql-read-query` skill
 
 For **Pattern 2**:
 
@@ -123,7 +123,7 @@ For **Pattern 2**:
 
 ### Step 5: Test Queries Against Live Org
 
-Use the testing workflows in the `salesforce-graphql-read-query` and `salesforce-graphql-mutation-query` skills to validate queries against the connected org before integrating into the app.
+Use the testing workflows in the `generating-graphql-read-query` and `generating-graphql-mutation-query` skills to validate queries against the connected org before integrating into the app.
 
 ### Step 6: Generate Types
 
@@ -284,7 +284,7 @@ Before completing GraphQL data access code:
 
 ### For Pattern 1 (.graphql files):
 
-1. [ ] All field names verified via grep against `schema.graphql` (invoke `salesforce-graphql-explore-schema`)
+1. [ ] All field names verified via grep against `schema.graphql` (invoke `exploring-graphql-schema`)
 2. [ ] Create `.graphql` file for the query/mutation
 3. [ ] Run `npm run graphql:codegen` to generate types
 4. [ ] Import query with `?raw` suffix
@@ -315,9 +315,9 @@ Before completing GraphQL data access code:
 
 ## Reference
 
-- Schema exploration: invoke the `salesforce-graphql-explore-schema` skill
-- Read query generation: invoke the `salesforce-graphql-read-query` skill
-- Mutation query generation: invoke the `salesforce-graphql-mutation-query` skill
+- Schema exploration: invoke the `exploring-graphql-schema` skill
+- Read query generation: invoke the `generating-graphql-read-query` skill
+- Mutation query generation: invoke the `generating-graphql-mutation-query` skill
 - Shared GraphQL schema types: `shared-schema.graphqls` (in this skill directory)
 - Schema download: `npm run graphql:schema` (run from webapp dir)
 - Type generation: `npm run graphql:codegen` (run from webapp dir)

package/dist/.a4drules/webapp-code-quality.md

@@ -15,7 +15,7 @@ Enforces ESLint, TypeScript, and build validation for consistent, maintainable c
 ```bash
 npm run lint   # MUST result in 0 errors
 npm run build  # MUST succeed (includes TypeScript check)
-npm run graphql:coden # MUST succeed (verifies graphql queries)
+npm run graphql:codegen # MUST succeed (verifies graphql queries)
 ```
 
 **Must Pass:**

package/dist/.a4drules/webapp-react.md

@@ -23,12 +23,12 @@ React apps must NOT import Salesforce platform modules like `lightning/*` or `@w
 
 ## Data Access (CRITICAL)
 
-All Salesforce API calls **must** go through the DataSDK (`@salesforce/sdk-data`). Do NOT use `axios` or raw `fetch` — the SDK handles authentication and CSRF.
+For all Salesforce data access (GraphQL, REST, Chatter, Connect, Apex REST, UI API, Einstein LLM), invoke the **`accessing-data`** skill (`.a4drules/skills/accessing-data/`). It enforces Data SDK usage, GraphQL-first preference, optional chaining, and documents when to use `sdk.fetch` via the `fetching-rest-api` skill.
 
 ### GraphQL (Preferred)
 
-For queries and mutations, follow the **`salesforce-data-access`** skill. It covers schema exploration, query patterns, codegen, type generation, and guardrails.
+For queries and mutations, invoke the **`using-graphql`** skill (`.a4drules/skills/using-graphql/`). It covers schema exploration, query patterns, codegen, type generation, and guardrails.
 
 ### UI API (Fallback)
 
-When GraphQL cannot cover the use case, use `sdk.fetch!(/services/data/v62.0/ui-api/records/<recordId>)` for UI API endpoints:
+When GraphQL cannot cover the use case, use `sdk.fetch?.()` for UI API endpoints. See the **`fetching-rest-api`** skill (`.a4drules/skills/fetching-rest-api/`) for full REST API documentation.

package/dist/AGENT.md

@@ -58,9 +58,9 @@ cd <sfdx-source>/webapplications/<appName>
 
 This project includes **.a4drules/** at the project root. Follow them when generating or editing code.
 
-- **Salesforce Data Access** (`.a4drules/skills/salesforce-data-access/`): Use for all Salesforce data fetches. Enforces Data SDK usage (`createDataSDK()` + `sdk.graphql` or `sdk.fetch`); GraphQL preferred, fetch when GraphQL is not sufficient.
-- **Salesforce REST API Fetch** (`.a4drules/skills/salesforce-rest-api-fetch/`): Use when implementing Chatter, Connect REST, Apex REST, UI API REST, or Einstein LLM calls via `sdk.fetch`.
-- **Salesforce GraphQL** (`.a4drules/skills/salesforce-graphql/`): Use when implementing Salesforce GraphQL queries or mutations. Sub-skills: `salesforce-graphql-explore-schema`, `salesforce-graphql-read-query`, `salesforce-graphql-mutation-query`.
+- **Accessing Data** (`.a4drules/skills/accessing-data/`): Use for all Salesforce data fetches. Enforces Data SDK usage (`createDataSDK()` + `sdk.graphql` or `sdk.fetch`); GraphQL preferred, fetch when GraphQL is not sufficient.
+- **Fetching REST API** (`.a4drules/skills/fetching-rest-api/`): Use when implementing Chatter, Connect REST, Apex REST, UI API REST, or Einstein LLM calls via `sdk.fetch`.
+- **Using GraphQL** (`.a4drules/skills/using-graphql/`): Use when implementing Salesforce GraphQL queries or mutations. Sub-skills: `exploring-graphql-schema`, `generating-graphql-read-query`, `generating-graphql-mutation-query`.
 
 When rules refer to "web app directory" or `<sfdx-source>/webapplications/<appName>/`, resolve `<sfdx-source>` from `sfdx-project.json` and use the **actual app folder name** for this project.
 
@@ -83,4 +83,4 @@ sf project deploy start --source-dir <packageDir> --target-org <alias>
 
 - **UI**: shadcn/ui + Tailwind. Import from `@/components/ui/...`.
 - **Entry**: Keep `App.tsx` and routes in `src/`; add features as new routes or sections, don't replace the app shell but you may modify it to match the requested design.
-- **Data (Salesforce)**: Invoke the `salesforce-data-access` skill for all Salesforce data fetches. The skill enforces use of the Data SDK (`createDataSDK()` + `sdk.graphql` or `sdk.fetch`) — never use `fetch` or `axios` directly. GraphQL is preferred; use `sdk.fetch` when GraphQL is not sufficient (e.g., Chatter, Connect REST). For GraphQL implementation, invoke the `salesforce-graphql` skill.
+- **Data (Salesforce)**: Invoke the `accessing-data` skill for all Salesforce data fetches. The skill enforces use of the Data SDK (`createDataSDK()` + `sdk.graphql` or `sdk.fetch`) — never use `fetch` or `axios` directly. GraphQL is preferred; use `sdk.fetch` when GraphQL is not sufficient (e.g., Chatter, Connect REST). For GraphQL implementation, invoke the `using-graphql` skill.

package/dist/CHANGELOG.md

@@ -3,6 +3,17 @@
 All notable changes to this project will be documented in this file.
 See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
 
+# [1.107.0](https://github.com/salesforce-experience-platform-emu/webapps/compare/v1.106.2...v1.107.0) (2026-03-17)
+
+
+### Features
+
+* **template:** add sf-project-setup command at SFDX project root ([#301](https://github.com/salesforce-experience-platform-emu/webapps/issues/301)) ([5a187cd](https://github.com/salesforce-experience-platform-emu/webapps/commit/5a187cd2faeadcab6c8f206d8c110c29763983ec))
+
+
+
+
+
 ## [1.106.2](https://github.com/salesforce-experience-platform-emu/webapps/compare/v1.106.1...v1.106.2) (2026-03-17)
 
 

package/dist/README.md

@@ -2,6 +2,16 @@
 
 Now that you’ve created a Salesforce DX project, what’s next? Here are some documentation resources to get you started.
 
+## Web app: install, build, and dev server
+
+From the **SFDX project root** (this directory), run:
+
+```bash
+npm run sf-project-setup
+```
+
+This installs dependencies in the web app, builds it, and starts the Vite dev server. Use this after cloning or extracting the project.
+
 ## How Do You Plan to Deploy Your Changes?
 
 Do you want to deploy a set of changes, or create a self-contained application? Choose a [development model](https://developer.salesforce.com/tools/vscode/en/user-guide/development-models).

package/dist/package.json

@@ -1,12 +1,13 @@
 {
   "name": "@salesforce/webapp-template-base-sfdx-project-experimental",
-  "version": "1.106.2",
+  "version": "1.107.0",
   "description": "Base SFDX project template",
   "license": "SEE LICENSE IN LICENSE.txt",
   "publishConfig": {
     "access": "public"
   },
   "scripts": {
+    "sf-project-setup": "node scripts/sf-project-setup.mjs",
     "build": "echo 'No build required for base-sfdx-project'",
     "clean": "echo 'No clean required for base-sfdx-project'",
     "lint": "eslint **/{aura,lwc}/**/*.js",

package/dist/scripts/sf-project-setup.mjs

@@ -0,0 +1,66 @@
+#!/usr/bin/env node
+/**
+ * Run from SFDX project root: install dependencies, build, and launch the dev server
+ * for the web app in force-app/main/default/webapplications/.
+ *
+ * Usage: npm run sf-project-setup
+ * (from the directory that contains force-app/ and sfdx-project.json)
+ */
+
+import { spawnSync } from 'node:child_process';
+import { resolve, dirname } from 'node:path';
+import { fileURLToPath } from 'node:url';
+import { readdirSync, existsSync, readFileSync } from 'node:fs';
+
+const __dirname = dirname(fileURLToPath(import.meta.url));
+const ROOT = resolve(__dirname, '..');
+
+function resolveWebapplicationsDir() {
+  const sfdxPath = resolve(ROOT, 'sfdx-project.json');
+  if (!existsSync(sfdxPath)) {
+    console.error('Error: sfdx-project.json not found at project root.');
+    process.exit(1);
+  }
+  const sfdxProject = JSON.parse(readFileSync(sfdxPath, 'utf8'));
+  const pkgDir = sfdxProject?.packageDirectories?.[0]?.path;
+  if (!pkgDir) {
+    console.error('Error: No packageDirectories[].path found in sfdx-project.json.');
+    process.exit(1);
+  }
+  return resolve(ROOT, pkgDir, 'main', 'default', 'webapplications');
+}
+
+function discoverWebappDir() {
+  const webapplicationsDir = resolveWebapplicationsDir();
+  if (!existsSync(webapplicationsDir)) {
+    console.error(`Error: webapplications directory not found: ${webapplicationsDir}`);
+    process.exit(1);
+  }
+  const entries = readdirSync(webapplicationsDir, { withFileTypes: true });
+  const dirs = entries.filter((e) => e.isDirectory() && !e.name.startsWith('.'));
+  if (dirs.length === 0) {
+    console.error(`Error: No web app folder found under ${webapplicationsDir}`);
+    process.exit(1);
+  }
+  if (dirs.length > 1) {
+    console.log(`Multiple web apps found; using first: ${dirs[0].name}`);
+  }
+  return resolve(webapplicationsDir, dirs[0].name);
+}
+
+function run(label, cmd, args, opts) {
+  console.log(`\n--- ${label} ---\n`);
+  const result = spawnSync(cmd, args, { stdio: 'inherit', ...opts });
+  if (result.status !== 0) {
+    process.exit(result.status ?? 1);
+  }
+}
+
+const webappDir = discoverWebappDir();
+console.log('SFDX project root:', ROOT);
+console.log('Web app directory:', webappDir);
+
+run('npm install', 'npm', ['install'], { cwd: webappDir });
+run('npm run build', 'npm', ['run', 'build'], { cwd: webappDir });
+console.log('\n--- Launching dev server (Ctrl+C to stop) ---\n');
+run('npm run dev', 'npm', ['run', 'dev'], { cwd: webappDir });

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@salesforce/webapp-template-feature-react-file-upload-experimental",
-  "version": "1.106.2",
+  "version": "1.107.0",
   "description": "File upload feature with a component to upload files to core",
   "license": "SEE LICENSE IN LICENSE.txt",
   "author": "",
@@ -41,7 +41,7 @@
     }
   },
   "devDependencies": {
-    "@salesforce/webapp-experimental": "^1.106.2",
+    "@salesforce/webapp-experimental": "^1.107.0",
     "@types/react": "^19.2.7",
     "@types/react-dom": "^19.2.3",
     "nodemon": "^3.1.0",