@testspectra/skills 1.1.8-rc.5 → 1.1.8-rc.6

package/LICENSE.md

@@ -1,48 +1,48 @@
-# TestSpectra Commercial Software License Agreement
-
-Copyright (c) 2026 TestSpectra. All rights reserved.
-
-IMPORTANT NOTICE: This software is NOT open-source. Although distribution archives,
-npm packages, and editor extensions are publicly downloadable, installation,
-execution, and use of the Software are strictly conditioned upon obtaining a valid
-Commercial License or an authorized Evaluation/Trial License from TestSpectra.
-
-1. GRANT OF LICENSE
-   Subject to payment of applicable license fees or an active authorized evaluation
-   period, TestSpectra grants you a non-exclusive, non-transferable, revocable license
-   to install and execute the Software solely for authoring, debugging, and executing
-   automated software tests.
-
-2. LICENSE ACTIVATION & ENFORCEMENT
-   - Use of the Software requires activation via a valid License Key, authorized CI token,
-     or active TestSpectra Cloud account.
-   - Any attempt to circumvent, disable, modify, reverse engineer, or tamper with the
-     license verification mechanisms, cryptographic signatures, or binary checks is
-     a material breach of this Agreement and automatically terminates your license.
-
-3. RESTRICTIONS
-   You shall not, and shall not permit any third party to:
-   - Decompile, disassemble, reverse engineer, or derive source code from the binaries,
-     compiled scripts, or libraries of the Software.
-   - Sublicense, sell, rent, lease, distribute, or host the Software as a service for third parties.
-   - Re-brand, white-label, or package the Software or any of its components as part of a
-     competing commercial QA, testing, or developer tooling product.
-   - Modify, alter, or remove any proprietary notices, copyright labels, or license headers.
-
-4. INTELLECTUAL PROPERTY
-   The Software, including its source code, architecture, Rust core engine, algorithms,
-   matchers, extensions, interfaces, and documentation, represents valuable intellectual
-   property and trade secrets of TestSpectra.
-
-5. TERMINATION
-   This license is effective until terminated. Your rights under this license will terminate
-   automatically without notice if you fail to comply with any of its terms, or upon expiration
-   of your active subscription or trial term. Upon termination, you must cease all use of
-   the Software and delete all copies in your possession.
-
-6. DISCLAIMER OF WARRANTY & LIMITATION OF LIABILITY
-   THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
-   INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
-   PURPOSE, AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE
-   FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
-   ARISING FROM THE USE OF OR INABILITY TO USE THE SOFTWARE.
+# TestSpectra Commercial Software License Agreement
+
+Copyright (c) 2026 TestSpectra. All rights reserved.
+
+IMPORTANT NOTICE: This software is NOT open-source. Although distribution archives,
+npm packages, and editor extensions are publicly downloadable, installation,
+execution, and use of the Software are strictly conditioned upon obtaining a valid
+Commercial License or an authorized Evaluation/Trial License from TestSpectra.
+
+1. GRANT OF LICENSE
+   Subject to payment of applicable license fees or an active authorized evaluation
+   period, TestSpectra grants you a non-exclusive, non-transferable, revocable license
+   to install and execute the Software solely for authoring, debugging, and executing
+   automated software tests.
+
+2. LICENSE ACTIVATION & ENFORCEMENT
+   - Use of the Software requires activation via a valid License Key, authorized CI token,
+     or active TestSpectra Cloud account.
+   - Any attempt to circumvent, disable, modify, reverse engineer, or tamper with the
+     license verification mechanisms, cryptographic signatures, or binary checks is
+     a material breach of this Agreement and automatically terminates your license.
+
+3. RESTRICTIONS
+   You shall not, and shall not permit any third party to:
+   - Decompile, disassemble, reverse engineer, or derive source code from the binaries,
+     compiled scripts, or libraries of the Software.
+   - Sublicense, sell, rent, lease, distribute, or host the Software as a service for third parties.
+   - Re-brand, white-label, or package the Software or any of its components as part of a
+     competing commercial QA, testing, or developer tooling product.
+   - Modify, alter, or remove any proprietary notices, copyright labels, or license headers.
+
+4. INTELLECTUAL PROPERTY
+   The Software, including its source code, architecture, Rust core engine, algorithms,
+   matchers, extensions, interfaces, and documentation, represents valuable intellectual
+   property and trade secrets of TestSpectra.
+
+5. TERMINATION
+   This license is effective until terminated. Your rights under this license will terminate
+   automatically without notice if you fail to comply with any of its terms, or upon expiration
+   of your active subscription or trial term. Upon termination, you must cease all use of
+   the Software and delete all copies in your possession.
+
+6. DISCLAIMER OF WARRANTY & LIMITATION OF LIABILITY
+   THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
+   INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
+   PURPOSE, AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE
+   FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+   ARISING FROM THE USE OF OR INABILITY TO USE THE SOFTWARE.

package/README.md

@@ -1,78 +1,78 @@
-# @testspectra/skills
-
-Modular AI agent skills installer & manager for standardizing **TestSpectra** script authoring —
-specs, Page Objects, shared steps, custom actions, lifecycle hooks, fixtures, and the matcher
-vocabulary.
-
-Distributed the same way as [`@testspectra/matchers`](../matchers): as a standalone npm package
-with its own CLI, installable independently of the main `@testspectra/cli`. When `@testspectra/cli`
-is already installed in a workspace, the exact same commands are also available unified under
-`spectra skills` — no separate install required.
-
----
-
-## Quick Start
-
-```bash
-# 1. One-time setup: pick agent(s) + which skills to install, in one guided flow
-npx @testspectra/skills init          # or: spectra skills init
-
-# 2. Standalone binary (works with zero other TestSpectra packages installed)
-npx @testspectra/skills list
-npx @testspectra/skills add
-npx @testspectra/skills add workspace-structure spec-and-suite-authoring matchers-and-assertions
-npx @testspectra/skills update
-npx @testspectra/skills remove network-interception
-
-# Unified under the main CLI (equivalent — use whichever is already installed)
-spectra skills list
-spectra skills add
-spectra skills add workspace-structure spec-and-suite-authoring matchers-and-assertions
-spectra skills update
-spectra skills remove network-interception
-```
-
-`init` is a two-step guided flow:
-
-1. **Pick agent(s)** — which AI agent(s) the project uses (Claude Code, OpenCode, Kilo, Universal
-   `.agents`, or the global Gemini CLI). Saved to `.spectra-skills.json` at the workspace root, so
-   every later `list`/`add`/`update`/`remove` call reads it automatically — no need to re-detect or
-   re-specify agents each time. Without `init`, commands fall back to auto-detecting only agent
-   directories that already exist in the target workspace.
-2. **Pick skills** — a multiselect (all 8 pre-checked) of which skills to install right away for
-   the agent(s) just selected. Deselect what you don't want, or submit empty to skip installing
-   anything yet (you can always run `add` later).
-
-A one-off `--agent <ids>` (or `-a` on `spectra skills`) flag on `list`/`add`/`update`/`remove`
-overrides the saved selection for a single invocation.
-
----
-
-## Available Skills
-
-| Skill | Covers |
-| :--- | :--- |
-| `workspace-structure` | Directory layout, zero-import architecture, file suffixes, `spectra.config.ts`, core CLI commands |
-| `spec-and-suite-authoring` | `suite.md` / `spec.md` frontmatter, the paired `*.test.ts` script, every `spectra lint` rule |
-| `page-objects-and-selectors` | Page Object pattern (`Spectra.get`/`getAll`), the `~`/`#` selector contract |
-| `matchers-and-assertions` | Full element action/assertion/collection matcher and global `Spectra.*` command reference |
-| `shared-steps-and-actions` | `Step.*` business workflows vs `support/actions/*` technical utilities |
-| `lifecycle-hooks` | `global-hooks/` vs `specs/<suite>/hooks/`, execution order, failure cascade |
-| `fixtures-data` | `fixtures/*.json` and the ambient `Fixture.*` namespace |
-| `network-interception` | `Spectra.intercept()` mocking, polling, and failure-simulation patterns |
-
-Each skill is grounded in `docs/v2/` and the reference workspace at `cli/templates/default`, so an
-AI coding agent scaffolding TestSpectra scripts produces code that already passes `spectra lint`.
-
----
-
-## Features
-
-- **Multi-Agent, Cross-Platform**: Installs into `.claude/skills`, `.agents/skills`,
-  `.opencode/skills`, `.kilo/skills`, and the Gemini CLI's global skills directory. `init` lets you
-  pick explicitly; otherwise it auto-detects whichever the target project/agent already uses.
-- **Independent Usage**: Works in any TestSpectra workspace (default or Nx/monorepo template)
-  without requiring the main `@testspectra/cli` to be installed first.
-- **Update-in-Place**: `update` re-installs every currently-installed skill from the package's
-  current registry, so bumping `@testspectra/skills` and re-running `update` refreshes local
-  copies.
+# @testspectra/skills
+
+Modular AI agent skills installer & manager for standardizing **TestSpectra** script authoring —
+specs, Page Objects, shared steps, custom actions, lifecycle hooks, fixtures, and the matcher
+vocabulary.
+
+Distributed the same way as [`@testspectra/matchers`](../matchers): as a standalone npm package
+with its own CLI, installable independently of the main `@testspectra/cli`. When `@testspectra/cli`
+is already installed in a workspace, the exact same commands are also available unified under
+`spectra skills` — no separate install required.
+
+---
+
+## Quick Start
+
+```bash
+# 1. One-time setup: pick agent(s) + which skills to install, in one guided flow
+npx @testspectra/skills init          # or: spectra skills init
+
+# 2. Standalone binary (works with zero other TestSpectra packages installed)
+npx @testspectra/skills list
+npx @testspectra/skills add
+npx @testspectra/skills add workspace-structure spec-and-suite-authoring matchers-and-assertions
+npx @testspectra/skills update
+npx @testspectra/skills remove network-interception
+
+# Unified under the main CLI (equivalent — use whichever is already installed)
+spectra skills list
+spectra skills add
+spectra skills add workspace-structure spec-and-suite-authoring matchers-and-assertions
+spectra skills update
+spectra skills remove network-interception
+```
+
+`init` is a two-step guided flow:
+
+1. **Pick agent(s)** — which AI agent(s) the project uses (Claude Code, OpenCode, Kilo, Universal
+   `.agents`, or the global Gemini CLI). Saved to `.spectra-skills.json` at the workspace root, so
+   every later `list`/`add`/`update`/`remove` call reads it automatically — no need to re-detect or
+   re-specify agents each time. Without `init`, commands fall back to auto-detecting only agent
+   directories that already exist in the target workspace.
+2. **Pick skills** — a multiselect (all 8 pre-checked) of which skills to install right away for
+   the agent(s) just selected. Deselect what you don't want, or submit empty to skip installing
+   anything yet (you can always run `add` later).
+
+A one-off `--agent <ids>` (or `-a` on `spectra skills`) flag on `list`/`add`/`update`/`remove`
+overrides the saved selection for a single invocation.
+
+---
+
+## Available Skills
+
+| Skill | Covers |
+| :--- | :--- |
+| `workspace-structure` | Directory layout, zero-import architecture, file suffixes, `spectra.config.ts`, core CLI commands |
+| `spec-and-suite-authoring` | `suite.md` / `spec.md` frontmatter, the paired `*.test.ts` script, every `spectra lint` rule |
+| `page-objects-and-selectors` | Page Object pattern (`Spectra.get`/`getAll`), the `~`/`#` selector contract |
+| `matchers-and-assertions` | Full element action/assertion/collection matcher and global `Spectra.*` command reference |
+| `shared-steps-and-actions` | `Step.*` business workflows vs `support/actions/*` technical utilities |
+| `lifecycle-hooks` | `global-hooks/` vs `specs/<suite>/hooks/`, execution order, failure cascade |
+| `fixtures-data` | `fixtures/*.json` and the ambient `Fixture.*` namespace |
+| `network-interception` | `Spectra.intercept()` mocking, polling, and failure-simulation patterns |
+
+Each skill is grounded in `docs/v2/` and the reference workspace at `cli/templates/default`, so an
+AI coding agent scaffolding TestSpectra scripts produces code that already passes `spectra lint`.
+
+---
+
+## Features
+
+- **Multi-Agent, Cross-Platform**: Installs into `.claude/skills`, `.agents/skills`,
+  `.opencode/skills`, `.kilo/skills`, and the Gemini CLI's global skills directory. `init` lets you
+  pick explicitly; otherwise it auto-detects whichever the target project/agent already uses.
+- **Independent Usage**: Works in any TestSpectra workspace (default or Nx/monorepo template)
+  without requiring the main `@testspectra/cli` to be installed first.
+- **Update-in-Place**: `update` re-installs every currently-installed skill from the package's
+  current registry, so bumping `@testspectra/skills` and re-running `update` refreshes local
+  copies.

package/bin/spectra-skills.js

@@ -1,7 +1,7 @@
-#!/usr/bin/env node
-import { runCli } from '../dist/index.js';
-
-runCli().catch((err) => {
-  console.error(err);
-  process.exit(1);
-});
+#!/usr/bin/env node
+import { runCli } from '../dist/index.js';
+
+runCli().catch((err) => {
+  console.error(err);
+  process.exit(1);
+});

package/dist/index.js

@@ -27,35 +27,35 @@ function getPackageVersion() {
         return '0.0.0';
     }
 }
-const HELP_TEXT = `
-\x1b[1m\x1b[36m🚀 TestSpectra Skills CLI\x1b[0m
-Install, update, and manage modular AI agent skills that standardize TestSpectra script authoring.
-
-\x1b[1mUsage:\x1b[0m
-  npx @testspectra/skills [command] [options]
-  spectra-skills [command] [options]
-
-\x1b[1mCommands:\x1b[0m
-  \x1b[36minit\x1b[0m                      Prompt which AI agent(s) you use and save the choice for future commands
-  \x1b[36mlist\x1b[0m                      List all available and installed skills
-  \x1b[36madd\x1b[0m [skills...]           Install specified skills (interactive if none provided)
-  \x1b[36mupdate\x1b[0m [skills...]        Update installed skills to latest versions
-  \x1b[36mremove\x1b[0m <skills...>        Remove specified skills from agent environment
-
-\x1b[1mOptions:\x1b[0m
-  --target <dir>             Target directory (default: current working directory)
-  --agent <ids>               One-off override: comma-separated agent(s) to target, bypassing the
-                               saved "init" selection and auto-detection. Known ids: ${getKnownAgentIds().join(', ')}
-  -h, --help                  Show help message
-  -v, --version                Show version
-
-\x1b[1mExamples:\x1b[0m
-  npx @testspectra/skills init
-  npx @testspectra/skills list
-  npx @testspectra/skills add workspace-structure
-  npx @testspectra/skills add spec-and-suite-authoring matchers-and-assertions
-  npx @testspectra/skills update
-  npx @testspectra/skills remove network-interception
+const HELP_TEXT = `
+\x1b[1m\x1b[36m🚀 TestSpectra Skills CLI\x1b[0m
+Install, update, and manage modular AI agent skills that standardize TestSpectra script authoring.
+
+\x1b[1mUsage:\x1b[0m
+  npx @testspectra/skills [command] [options]
+  spectra-skills [command] [options]
+
+\x1b[1mCommands:\x1b[0m
+  \x1b[36minit\x1b[0m                      Prompt which AI agent(s) you use and save the choice for future commands
+  \x1b[36mlist\x1b[0m                      List all available and installed skills
+  \x1b[36madd\x1b[0m [skills...]           Install specified skills (interactive if none provided)
+  \x1b[36mupdate\x1b[0m [skills...]        Update installed skills to latest versions
+  \x1b[36mremove\x1b[0m <skills...>        Remove specified skills from agent environment
+
+\x1b[1mOptions:\x1b[0m
+  --target <dir>             Target directory (default: current working directory)
+  --agent <ids>               One-off override: comma-separated agent(s) to target, bypassing the
+                               saved "init" selection and auto-detection. Known ids: ${getKnownAgentIds().join(', ')}
+  -h, --help                  Show help message
+  -v, --version                Show version
+
+\x1b[1mExamples:\x1b[0m
+  npx @testspectra/skills init
+  npx @testspectra/skills list
+  npx @testspectra/skills add workspace-structure
+  npx @testspectra/skills add spec-and-suite-authoring matchers-and-assertions
+  npx @testspectra/skills update
+  npx @testspectra/skills remove network-interception
 `;
 export async function runCli() {
     const args = process.argv.slice(2);

package/dist/skills/fixtures-data/SKILL.md

@@ -1,109 +1,109 @@
----
-name: fixtures-data
-description: TestSpectra test data fixtures — JSON files under fixtures/, auto-typed globally under Fixture.* with zero imports, and how to reference/refactor them from test scripts, steps, and hooks. Use whenever a test needs static mock data (credentials, catalog items, payloads, locales).
----
-
-# Skill: Fixture & Test Data Management
-
-Use this skill whenever a test case, shared step, or hook needs static data — user credentials,
-product catalogs, mock API payloads, localization strings.
-
----
-
-## 1. Directory & Storage
-
-```
-workspace-root/
-└── fixtures/
-    ├── users.json             # User roles & credential sets
-    ├── products.json          # Catalog items & SKU metadata
-    ├── api-payloads.json      # Mock response payloads
-    └── locales.json           # Localization dictionaries
-```
-
-```json
-// fixtures/users.json
-{
-  "admin": {
-    "id": "usr-admin-01",
-    "name": "System Administrator",
-    "email": "admin@testspectra.dev",
-    "password": "Password123!",
-    "role": "admin"
-  },
-  "standardUser": {
-    "id": "usr-std-02",
-    "name": "Jane Doe",
-    "email": "jane.doe@testspectra.dev",
-    "password": "Password123!",
-    "role": "member"
-  }
-}
-```
-
----
-
-## 2. Ambient Typing (Zero Import)
-
-The `TypeGenerator` watches `fixtures/` and emits `.testspectra/types/fixtures.d.ts` automatically
-whenever a fixture file is created/updated:
-
-```typescript
-declare global {
-  namespace Fixture {
-    const users: typeof import('../../fixtures/users.json');
-    const products: typeof import('../../fixtures/products.json');
-  }
-}
-```
-
-Never hand-write this file, and never `import` a fixture JSON file directly — always access it via
-the global `Fixture.<fileBaseName>` namespace, exactly like Page Objects and `Step.*`.
-
----
-
-## 3. Usage
-
-### In test scripts
-
-```typescript
-it('should login with admin credentials from fixture', async () => {
-  await Spectra.navigate('/auth/login');
-  await LoginPage.emailInput.type(Fixture.users.admin.email, { clearFirst: true });
-  await LoginPage.passwordInput.type(Fixture.users.admin.password);
-  await LoginPage.submitButton.click();
-
-  await DashboardPage.welcomeMsg.shouldContainText(Fixture.users.admin.name);
-});
-```
-
-### In shared steps
-
-```typescript
-// support/steps/loginUser/web.step.ts
-export default async function (userType: 'admin' | 'standardUser' = 'standardUser') {
-  const user = Fixture.users[userType];
-  await Spectra.navigate('/auth/login');
-  await LoginPage.emailInput.type(user.email, { clearFirst: true });
-  await LoginPage.passwordInput.type(user.password);
-  await LoginPage.submitButton.click();
-}
-```
-
-Fixtures are freely usable inside hooks too (e.g. `global-hooks/before` seeding a DB via `fetch`
-with `Fixture.apiPayloads.seedUser`).
-
----
-
-## 4. Renaming a Fixture
-
-Never rename a fixture file by hand. Use:
-
-```
-spectra refactor fixture users accounts
-```
-
-This renames `fixtures/users.json` → `fixtures/accounts.json`, rewrites every `Fixture.users`
-reference across `specs/**/*.test.ts`, `support/steps/**/*.step.ts`, and `hooks/**` to
-`Fixture.accounts`, and regenerates `.testspectra/types/fixtures.d.ts` immediately with 0
-TypeScript errors.
+---
+name: fixtures-data
+description: TestSpectra test data fixtures — JSON files under fixtures/, auto-typed globally under Fixture.* with zero imports, and how to reference/refactor them from test scripts, steps, and hooks. Use whenever a test needs static mock data (credentials, catalog items, payloads, locales).
+---
+
+# Skill: Fixture & Test Data Management
+
+Use this skill whenever a test case, shared step, or hook needs static data — user credentials,
+product catalogs, mock API payloads, localization strings.
+
+---
+
+## 1. Directory & Storage
+
+```
+workspace-root/
+└── fixtures/
+    ├── users.json             # User roles & credential sets
+    ├── products.json          # Catalog items & SKU metadata
+    ├── api-payloads.json      # Mock response payloads
+    └── locales.json           # Localization dictionaries
+```
+
+```json
+// fixtures/users.json
+{
+  "admin": {
+    "id": "usr-admin-01",
+    "name": "System Administrator",
+    "email": "admin@testspectra.dev",
+    "password": "Password123!",
+    "role": "admin"
+  },
+  "standardUser": {
+    "id": "usr-std-02",
+    "name": "Jane Doe",
+    "email": "jane.doe@testspectra.dev",
+    "password": "Password123!",
+    "role": "member"
+  }
+}
+```
+
+---
+
+## 2. Ambient Typing (Zero Import)
+
+The `TypeGenerator` watches `fixtures/` and emits `.testspectra/types/fixtures.d.ts` automatically
+whenever a fixture file is created/updated:
+
+```typescript
+declare global {
+  namespace Fixture {
+    const users: typeof import('../../fixtures/users.json');
+    const products: typeof import('../../fixtures/products.json');
+  }
+}
+```
+
+Never hand-write this file, and never `import` a fixture JSON file directly — always access it via
+the global `Fixture.<fileBaseName>` namespace, exactly like Page Objects and `Step.*`.
+
+---
+
+## 3. Usage
+
+### In test scripts
+
+```typescript
+it('should login with admin credentials from fixture', async () => {
+  await Spectra.navigate('/auth/login');
+  await LoginPage.emailInput.type(Fixture.users.admin.email, { clearFirst: true });
+  await LoginPage.passwordInput.type(Fixture.users.admin.password);
+  await LoginPage.submitButton.click();
+
+  await DashboardPage.welcomeMsg.shouldContainText(Fixture.users.admin.name);
+});
+```
+
+### In shared steps
+
+```typescript
+// support/steps/loginUser/web.step.ts
+export default async function (userType: 'admin' | 'standardUser' = 'standardUser') {
+  const user = Fixture.users[userType];
+  await Spectra.navigate('/auth/login');
+  await LoginPage.emailInput.type(user.email, { clearFirst: true });
+  await LoginPage.passwordInput.type(user.password);
+  await LoginPage.submitButton.click();
+}
+```
+
+Fixtures are freely usable inside hooks too (e.g. `global-hooks/before` seeding a DB via `fetch`
+with `Fixture.apiPayloads.seedUser`).
+
+---
+
+## 4. Renaming a Fixture
+
+Never rename a fixture file by hand. Use:
+
+```
+spectra refactor fixture users accounts
+```
+
+This renames `fixtures/users.json` → `fixtures/accounts.json`, rewrites every `Fixture.users`
+reference across `specs/**/*.test.ts`, `support/steps/**/*.step.ts`, and `hooks/**` to
+`Fixture.accounts`, and regenerates `.testspectra/types/fixtures.d.ts` immediately with 0
+TypeScript errors.