@assertrx/dino 1.0.9 → 1.0.10

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@assertrx/dino",
-  "version": "1.0.9",
+  "version": "1.0.10",
   "description": "A friendly purple dinosaur pi package with a custom TUI header, theme, and Playwright skills.",
   "keywords": [
     "pi-package"

package/prompts/generate-bdd-from-url.md

@@ -1,8 +1,10 @@
 ---
 description: Generate exhaustive Gherkin BDD scenarios for a single page using the bdd-gherkin skill
-argument-hint: "<URL> [output-dir] [auth-env-file]"
+argument-hint: "<URL> [output-dir] [auth-env-file] [tester-roles]"
 ---
 
+Selected tester roles (may be empty): ${4:-}
+
 Use the `bdd-gherkin` skill and `playwright-cli` commands to inspect the page at $1 and generate exhaustive Gherkin BDD scenarios for **that page only**. Fall back to the Playwright MCP bridge (`browser_*` tools) only if `playwright-cli` is unavailable or fails.
 
 ## Preferred tooling
@@ -43,6 +45,8 @@ Use the `bdd-gherkin` skill and `playwright-cli` commands to inspect the page at
    - **UI / interaction cases** — toggles, show/hide password, dropdown dependencies, disabled fields, cancel/reset actions.
    - **Accessibility / usability cases** — keyboard focus, visible labels, error announcement (if inferable from the page).
 
+   Additionally, if the "Selected tester roles" value at the top of this prompt is **not empty**, adopt the perspective of each listed tester role (e.g. accessibility tester, security tester, performance tester, functional tester) and generate additional scenarios that role would write for this page. Examples: an accessibility tester produces scenarios for screen-reader labels, focus order, and color-contrast issues; a security tester produces scenarios for injection attempts, unauthorized access, and data exposure; a performance tester produces scenarios for large payloads and slow-network handling. Keep these role-specific scenarios business-readable and in the same Gherkin style as the rest — tag them with a role tag such as `@accessibility`, `@security`, or `@performance`. If no tester roles are listed, skip this and produce only the default coverage above.
+
 5. **Follow Gherkin best practices**.
    - Use a single-focused Scenario for each behavior.
    - Use **exactly one `When` action per scenario**; move setup details into `Given` or `Background`.

package/scripts/api-server.mjs

@@ -58,6 +58,7 @@ const PROMPT_REGISTRY = {
       { name: "url", required: true, description: "Target website URL" },
       { name: "outputDir", required: false, description: "Output directory (default: tests/features/)" },
       { name: "authEnvFile", required: false, description: "Auth env file for login credentials" },
+      { name: "testerRoles", required: false, description: "Comma-separated tester roles (e.g. accessibility, security) whose perspectives to include when generating scenarios" },
     ],
     description: "Generate Gherkin BDD scenarios for a page by inspecting it with playwright-cli",
   },
@@ -108,8 +109,14 @@ async function loadPrompt(name, params = {}) {
 
   let content = await readFile(filePath, "utf-8");
 
-  // Build positional arg array from ordered entry.params
-  const positional = entry.params.map((p) => params[p.name] ?? "");
+  // Build positional arg array from ordered entry.params. Array values
+  // (e.g. testerRoles sent as a list from the desktop app) are joined into
+  // a comma-separated string so the prompt template can substitute them.
+  const positional = entry.params.map((p) => {
+    const v = params[p.name];
+    if (Array.isArray(v)) return v.filter(Boolean).join(", ");
+    return v ?? "";
+  });
   // Substitute $1, $2, $3, $4, ${1:-default}, ${2:-default}, etc.
   content = content.replace(
     /\$\{?(\d+)(?:\s*:-\s*([^}]*))?\}?/g,