@inizioevoke/veeva-astroclm-core 1.0.6 → 1.0.8

package/agents/claude/veeva-config-manager/SKILL.md

@@ -6,6 +6,7 @@ description: >
   presentation, or run the veeva-config-manager. Also trigger when the user says things like
   "set up the config", "create the config file", "initialize the presentation config",
   "sync the config", "check the config", or "update the slides in the config".
+allowed-tools: AskUserQuestion
 ---
 
 # Veeva Config Manager

package/agents/claude/veeva-config-manager/create.md

@@ -4,13 +4,30 @@ Interactively collect presentation metadata from the user and write a
 `veeva-config.ts` file to the project root, replicating the flow in
 `src/apps/veeva-config-manager/create.ts`.
 
+## Before you start
+
+Check whether `veeva-config.ts` already exists in the project root. If it does, ask the user how to proceed:
+- **Overwrite** — discard the existing file and continue with this skill
+- **Update instead** — stop this skill and run the manage skill (`manage.md`) to sync slides with `src/pages/`
+- **Abort** — stop without making changes
+
+Do not proceed with collecting input until the user confirms overwrite.
+
+## Clean input rule
+
+Before using any free-text value (product name, presentation name, presentation ID) in the output: `.trim()` and replace runs of two or more spaces with a single space. Do not otherwise transform user input. This rule is referenced from the input-collection and ID-generation steps below.
+
 ## What you need from the user
 
-Tell the user that some information is required to generate the config file. Gather **all** of the following before writing any files. Ask each one at a time, do not batch together.
+Tell the user that some information is required to generate the config file. Gather **all** of the following before writing any files.
+
+Ask the free-text questions one at a time (steps 1–2). The predefined-option questions in step 3 are batched into a single `AskUserQuestion` call — that's intentional, since `AskUserQuestion` natively supports multiple questions per call.
+
+Apply the [Clean input rule](#clean-input-rule) to every free-text value as you receive it.
 
-1. Ask for the `Product name` and `Presentation name`
-2. Ask for the `Presention ID`. Suggest a value of `Presentation name` lowercased, non-alphanumeric → `_`. Ask user to confirm or enter a new value.
-3. Call `AskUserQuestion` with a multi-tab payload with the following tabs in order:
+1. Ask for the `Product name` and `Presentation name` (one at a time).
+2. Ask for the `Presentation ID`. Suggest a value derived from the cleaned `Presentation name`: lowercased, with any non-alphanumeric character replaced by `_`. Ask the user to confirm or enter a new value.
+3. Call `AskUserQuestion` with one call containing the following questions in order. Set `multiSelect: true` only on **Disable**; the other three are single-select.
   - **Dimensions**
     - Question: Select the IVA dimensions
     - Options: `1024 × 768`, `1366 × 1024` *(default)*, `1376 × 1032`
@@ -18,31 +35,34 @@ Tell the user that some information is required to generate the config file. Gat
     - Question: Select the iOS resolution
     - Options: `Default For Device` *(default)*, `Scale To Fit`, `Scale To 1024x768`
   - **Disable**
-    - Question: Select any Veeva features to disable
-    - Options: multi-select: `History Buttons`, `Navigation Bar`, `Reactions`, `Swipe`
+    - Question: Select any Veeva features to disable globally (multi-select)
+    - Options: `History Buttons`, `Navigation Bar`, `Reactions`, `Swipe`
   - **Platform**
     - Question: Select the target Veeva platform
     - Options: `Salesforce` *(default)*, `Vault`
 
+For the **Dimensions** answer, split the selected option on `×` and trim each side to get the numeric width and height (e.g. `1366 × 1024` → width `1366`, height `1024`).
+
 ### Preferred collection strategy
 
 1. **Try `AskUserQuestion` first** for all fields with predefined options.
 
 2. **Fall back to conversational** for any field if `AskUserQuestion` is
-   unavailable or the call fails. List the options in an numbered list to allow the user to enter a number rather than the full option text.
+   unavailable or the call fails. List the options in a numbered list so the user can reply with a number rather than the full option text.
 
 ### Exceptions
 
-If `Other` is selected for `IVA dimensions`, `iOS resolution`, or `CRM target`, reject the response and re-prompt the user asking them to choose only from the defined vaules.
+If `Other` is selected for `Dimensions`, `Resolution`, or `Platform`, reject the response and re-prompt the user asking them to choose only from the defined values.
 
-If `Other` is selected for `Disabled actions`, reject the response and re-prompt, informing the user that the only other allowed values are following: `Pinch to Exit`, `Rotation Lock`, `Zoom`.
+If `Other` is selected for `Disable`, ask the user which additional actions they want to disable. The only accepted values beyond the listed four are: `Pinch to Exit`, `Rotation Lock`, `Zoom`. Accept any combination of these. If the user enters anything else, reject and re-prompt with this list.
 
 ## Generating IDs
 
 You will need two kinds of random IDs. Implement them inline with JavaScript/TypeScript logic or generate them yourself:
 
-- **External ID prefix**: First 3 chars of `product` (uppercased) + `_` + an 8-char alphanumeric random string (uppercase A–Z, 0–9).
+- **External ID prefix**: First 3 chars of `product` (uppercased) + `_` + an 8-char alphanumeric random string (uppercase A–Z, 0–9). If the cleaned product name is shorter than 3 chars, right-pad with `_` to reach 3 chars before uppercasing.
   Example: product `Velorixin` → `VEL_3K9BW12X`
+  Example: product `Ox` → `OX__3K9BW12X`
 - **Per-slide ID**: An independent 8-char alphanumeric random string for each slide, unique within the set.
 
 To generate an 8-char random-ish ID in a bash snippet you can run:
@@ -53,11 +73,7 @@ Or generate them yourself — just make them look like `3K9BW12X` (8 uppercase a
 
 ## Discovering slides
 
-Read all `.astro` files in `src/pages/`:
-
-```bash
-ls src/pages/*.astro 2>/dev/null
-```
+Use the Glob tool with the pattern `src/pages/*.astro` to list all slide pages. (Glob is platform-agnostic — prefer it over `ls`, which is unreliable on Windows.)
 
 For each file `some-page-name.astro`:
 - `path` = filename without `.astro` extension (e.g. `some-page-name`)
@@ -66,8 +82,7 @@ For each file `some-page-name.astro`:
 
 ## Output format
 
-Write `veeva-config.ts` to the **project root** using exactly this template
-(replace all `##...##` tokens with the collected/generated values):
+Write `veeva-config.ts` to the **project root** using exactly this template. Replace every `##...##` token with the collected/generated value, but **leave all `${...}` template-literal expressions exactly as written** — those are TypeScript that runs at runtime, not placeholders for you to substitute. Do not modify the imports, the function signature, or the `binderFields` block.
 
 ```ts
 import type { IVeevaClmBinderFields, IVeevaConfig, VeevaEnv } from "@inizioevoke/veeva-astroclm-core/types";
@@ -160,11 +175,6 @@ export default function ({ veevaEnv = 'client', isTraining = false }: IVeevaConf
 }]
 ```
 
-## "Clean input" rule
-
-Before using any free-text value in the output: `.trim()` and replace runs of
-two or more spaces with a single space. Do not otherwise transform user input.
-
 ## After writing the file
 
 Tell the user where the file was written (`veeva-config.ts` in the project

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@inizioevoke/veeva-astroclm-core",
-  "version": "1.0.6",
+  "version": "1.0.8",
   "description": "",
   "license": "ISC",
   "author": "",