@webship.co/workspace-gatsby 1.0.9 → 1.0.11

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: gatsby-tester
3
- description: Use this agent to test a Gatsby site of the Webship Workspace with webship-js and the Gatsby step pack (`@webship-js/gatsby-steps`) — set the testing stack up with `cmd-tools-testing.sh`, look at the built site in the Playwright MCP browser first, write Gherkin scenarios from the pack's own steps (the production build, hydration, client-side routing, images, page data, the 404 page), run them in the project's container and read the report. The site is static: there are no accounts, and it never writes a platform name into a step phrase. Invoke for "test this Gatsby site", "write scenarios for the navigation", "why does this scenario fail", or "run the suite on <site>". For building or changing the site itself, hand over to `gatsby-site-builder`.
3
+ description: Use this agent to test a Gatsby site of the Webship Workspace with webship-js and the Gatsby step pack (`@webship-js/gatsby-steps`) — set the testing stack up with `cmd-tools-testing.sh`, look at the built site in the Playwright MCP browser first, write Gherkin scenarios from the pack's own steps (the production build, hydration, client-side routing, images, page data, the 404 page), run them in the project's container and read the report. The site is static — there are no accounts, and it never writes a platform name into a step phrase. Invoke for "test this Gatsby site", "write scenarios for the navigation", "why does this scenario fail", or "run the suite on <site>". For building or changing the site itself, hand over to `gatsby-site-builder`.
4
4
  model: fable
5
5
  tools:
6
6
  - Bash
@@ -3,28 +3,31 @@ Feature: The Gatsby plugin on the dashboard
3
3
  AI folder lists the items of its kind the plugin ships, and the Plugins page lists the plugin
4
4
  with its steps.
5
5
 
6
- Scenario: The plugin is listed on the Plugins page
6
+ # The Plugins page names each plugin; the package is on the plugin's own page (the row shows it on hover only).
7
+ Scenario: The plugin is listed on the Plugins page, and its own page names its package
7
8
  Given I am on "/settings/plugins"
8
9
  Then I should see "Gatsby"
9
- And I should see "@webship.co/workspace-gatsby"
10
+ When I go to "/settings/plugin/gatsby"
11
+ Then I should see "@webship.co/workspace-gatsby"
10
12
 
11
13
  Scenario: A sites folder offers the Gatsby builder
12
14
  Given I am on "/dev"
13
15
  Then "option[value='cmd-gatsby-project.sh']" should be attached
14
16
 
17
+ # The AI folders are searched by name: with every plugin on, a folder lists more than one page of items.
15
18
  Scenario: The AI Agents folder lists the agents the plugin ships
16
- Given I am on "/ai-agents"
19
+ Given I am on "/ai-agents?q=gatsby-"
17
20
  Then I should see "gatsby-site-builder"
18
21
  And I should see "gatsby-tester"
19
22
 
20
23
  Scenario: The AI Skills folder lists the skill the plugin ships
21
- Given I am on "/ai-skills"
24
+ Given I am on "/ai-skills?q=gatsby-scenarios"
22
25
  Then I should see "gatsby-scenarios"
23
26
 
24
27
  Scenario: The AI Commands folder lists the command the plugin ships
25
- Given I am on "/ai-commands"
28
+ Given I am on "/ai-commands?q=gatsby-test"
26
29
  Then I should see "gatsby-test"
27
30
 
28
31
  Scenario: The AI Prompts folder lists the prompt the plugin ships
29
- Given I am on "/ai-prompts"
32
+ Given I am on "/ai-prompts?q=gatsby-build-and-test"
30
33
  Then I should see "gatsby-build-and-test"
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@webship.co/workspace-gatsby",
3
- "version": "1.0.9",
3
+ "version": "1.0.11",
4
4
  "description": "Gatsby for Webship Workspace: the builder (`cmd-gatsby-project.sh`) and the Gatsby CLI tool in every sites folder, a starter built to a production build and served in a container, the Gatsby step pack wired into the testing setup, and its AI items in their folders: two agents, a skill, a command and a prompt.",
5
5
  "main": "dist/src/index.js",
6
6
  "types": "dist/src/index.d.ts",