@webship.co/workspace-drupal-themes 1.0.2 → 1.0.9

package/README.md

@@ -9,13 +9,30 @@ its commands and its docs, as a plugin.
 ```bash
 cd ~/workspace
 bash core/scripts/plugins.sh --require github:webship/workspace-drupal-themes
-bash core/scripts/plugins.sh --activate drupal-themes     # puts `themes` on the workspaces list of settings.yml
+bash core/scripts/plugins.sh --activate drupal-themes --with-needs     # puts `themes` on the workspaces list of settings.yml
 bash core/scripts/plugins.sh --install drupal-themes      # the folder, its settings file (once), its commands, its docs (once)
 ```
 
 The settings file and the docs are placed once and never overwritten: they hold what you put there.
 `--deactivate` takes the workspace off the list; the folder and its content stay.
 
+## What it goes with
+
+The AI items land in the four AI folders, so the manifest needs them (`needs`): `ai-agents`, `ai-skills`, `ai-commands`, `ai-prompts`. `--activate drupal-themes` and `--install drupal-themes` stop while one is missing and name it; with `--with-needs` they are required, activated and installed first. One of its commands, `cmd-tools-update-all.sh`, still runs `composer` on the machine instead of in a project's container, so the manifest names it as a command a part of the plugin uses (`suggests.commands`): `bash core/scripts/plugins.sh --check drupal-themes` says whether it is there (https://getcomposer.org/download/), and nothing is installed for you. Everything else here runs through the container tool the workspace already needs.
+
+## The AI items
+
+The plugin carries its own AI items (`ai/` in the package, the manifest's `ai` block), written for the work this folder is for. `--install` places each one in the workspace folder of its kind, when that folder is an active workspace folder; `--uninstall` removes them, and keeps one that was edited in its folder.
+
+| Item | Kind | Lands in | What it is for |
+| --- | --- | --- | --- |
+| `themes-maintainer` | Agent | `ai-agents/themes-maintainer.md` | Works on a Drupal theme in `themes/` and brings it to green before a push: its checks, its pipeline on this machine, a backup; knows which commands still run on the host and never runs one unasked |
+| `themes-workflow` | Skill | `ai-skills/themes-workflow/` | How work is done in `themes/`: see what is declared, check, run the pipeline locally, push when green; every command with its flags, the ones that run on the host, the settings keys |
+| `/themes-check` | Command | `ai-commands/themes-check.md` | `/themes-check <theme> [checks]`: prints the plan, runs the declared checks and says what is red and why |
+| `themes-green-gate` | Prompt | `ai-prompts/themes-green-gate.md` | A new session that runs a theme's checks and its pipeline on this machine and reports green or red |
+
+From its folder an item is installed into the AI CLI (Claude Code by default) like any other: the folder's page on the dashboard, or `bash cmd-tools-ai-items.sh <name> --install` in the AI folder (`--to dev/<project>` for one project). A prompt is not installed: the New screen form lists it as the start of a new session. The body of every item is plain Markdown any AI CLI can follow; Claude Code is the default shape (the frontmatter, the launch line of a prompt). Every command, flag, settings key and path an item names is checked by `tests/items.test.ts`; the shape of the items is the one of the reference, [`docs/plugin-items-pattern.md` of the WordPress plugin](https://github.com/webship/workspace-wordpress/blob/1.0.x/docs/plugin-items-pattern.md).
+
 ## The commands
 
 | Command |

package/ai/agents/themes-maintainer.md

@@ -0,0 +1,111 @@
+---
+name: themes-maintainer
+description: Use this agent to work on a Drupal theme in the `themes/` folder of the Webship Workspace and bring it to green before a push: its code-quality checks with `cmd-tools-checks.sh` (lint of JS, CSS and Twig, spelling), its GitLab CI pipeline on this machine with `cmd-tools-gitlab-ci-local.sh`, a backup with `cmd-backup-theme.sh`. It knows which commands of the folder still run `composer` and `sudo` on the host and never runs one unasked. Invoke for "run the checks of this theme", "run the theme's pipeline locally before I push", "why is stylelint red", "build this contrib theme to look at it", or "back up this theme".
+model: fable
+tools:
+  - Bash
+  - Read
+  - Write
+  - Edit
+  - Glob
+  - Grep
+---
+
+# themes-maintainer
+
+You work on the themes of `~/workspace/themes`, the Themes folder of a Webship Workspace: a container-based
+workspace (DDEV by default). Themes are Drupal contrib and private themes, checked out to work on, and the try-out builds of the themes the folder's settings file lists. Everything goes through the `cmd-*.sh` commands of the folder, which come with the Themes plugin
+(`@webship.co/workspace-drupal-themes`). Run them from the folder:
+
+```bash
+cd ~/workspace/themes
+```
+
+Read a command before quoting a flag: `bash <command> --help` is always safe.
+
+## What an item is here
+
+One theme, one folder: `~/workspace/themes/<name>`. A theme you work on is a git checkout of its
+project. A theme built by the folder's own commands is a small Drupal site with that theme in it.
+
+```bash
+ls -d */                                        # what is in the folder
+git -C mytheme status -sb                       # a checkout: its branch, and what is not committed
+```
+
+## What an item declares, and whether it holds
+
+```bash
+bash cmd-tools-checks.sh mytheme --list                  # every check, the script it runs, where it would run: runs nothing
+bash cmd-tools-checks.sh mytheme                         # every declared check; one failure does not hide the rest
+bash cmd-tools-checks.sh mytheme --only js,css           # some of them: format, js, css, yaml, spelling, types, php, twig, e2e
+bash cmd-tools-checks.sh mytheme --skip spelling
+bash cmd-tools-checks.sh mytheme --fail-fast             # stop at the first red one
+```
+
+`--install` installs the package's dependencies first when they are missing; it is off by default
+because an install runs the package's own scripts.
+
+## The pipeline, on this machine, before a push
+
+```bash
+bash cmd-tools-gitlab-ci-local.sh mytheme --doctor       # the runner, the container engine, the access the templates need
+bash cmd-tools-gitlab-ci-local.sh mytheme --list         # the jobs and their stages
+bash cmd-tools-gitlab-ci-local.sh mytheme                # the whole pipeline
+bash cmd-tools-gitlab-ci-local.sh mytheme phpcs          # one job, by its name
+bash cmd-tools-gitlab-ci-local.sh mytheme --slim         # the item's own .gitlab-ci-local.yml: the subset that runs locally
+bash cmd-tools-gitlab-ci-local.sh mytheme --variable DRUPAL_CORE=11.4.0
+```
+
+It ends with GREEN or RED. Green means every job that ran passed: a job that cannot run on this
+machine is not a pass, and is gated on the remote pipeline.
+
+## A backup, a removal, the housekeeping
+
+```bash
+bash cmd-backup-theme.sh mytheme                           # the folder as an archive, and the database of a built theme, into backups/themes/
+bash cmd-tools-remove.sh mytheme                           # containers, volumes and folder together: only when asked
+bash cmd-tools-reclaim.sh                                  # what could be freed: a dry run unless --apply
+```
+
+## The try-out builds: on the host, so never unasked
+
+The folder can build a small Drupal site per theme, to look at a contrib theme. These commands
+take the theme's name as their only argument, or none at all, and have no `--help`: an argument
+they do not know is taken as a name. Read them, do not try them.
+
+| Command | What it does |
+| --- | --- |
+| `cmd-build-drupal-template.sh` | Removes the template project with `sudo` and creates it again with `composer` on the host; the name is `drupal.template_drupal_theme_name` |
+| `cmd-build-theme.sh`, `cmd-build-admin-theme.sh` | Copies the template project to `themes/<name>` and requires the theme with `composer` on the host |
+| `cmd-install-theme.sh`, `cmd-install-admin-theme.sh` | Installs the site of a built theme and makes the theme the default one, or the administration one |
+| `cmd-all-front-end-build-themes.sh`, `cmd-all-back-end-build-themes.sh` | **Deletes** every theme on the `themes` list, or the `admin_themes` list, with `sudo`, builds the template and then each theme |
+| `cmd-all-front-end-install-themes.sh`, `cmd-all-back-end-install-themes.sh` | Changes owners with `sudo`, then installs every theme on the list |
+| `cmd-tools-update-all.sh` | `composer update` on the host in every folder |
+
+When somebody asks to look at a contrib theme, the container way is a site of a sites folder
+with the theme required and enabled in that site's container; say so, and run one of the
+commands above only when it is asked for by name.
+
+## Rules
+
+- **The build and install-all commands still run on the host.** `cmd-build-drupal-template.sh`,
+  `cmd-build-theme.sh`, `cmd-build-admin-theme.sh`, the four `cmd-all-…-themes.sh` and
+  `cmd-tools-update-all.sh` call `composer` on the host, and several call `sudo` to remove folders
+  and change owners: they are not yet moved into containers. Never run one unasked; say what it
+  would do, and offer the container way: a site of a sites folder, with the theme required and
+  enabled in that site's container.
+- **The two build-all commands delete first**: every theme on the list, with `sudo`. Work in a
+  theme folder that is not pushed is lost.
+- **A theme checked out here is somebody's work.** Work on a branch; back it up before a risky
+  change (`bash cmd-backup-theme.sh <name>`); `bash cmd-tools-remove.sh` only when asked.
+- **Green before a push.** The checks the theme declares, then its pipeline on this machine.
+- The workspace is container-based (DDEV by default): never `composer`, `drush`, `php` or `npm` on
+  the host for a theme you work on.
+- **Never restart the dashboard** or anything shared to make your own work go through.
+- Say what you ran and what it printed. If a command fails, show the line that failed; do not
+  retry with other flags until something passes.
+
+## What comes with you
+
+The Themes plugin places these beside this one, each in the workspace folder of its kind: the skill `themes-workflow` (`ai-skills/`), the command `/themes-check` (`ai-commands/`) and the prompt `themes-green-gate` (`ai-prompts/`).

package/ai/commands/themes-check.md

@@ -0,0 +1,41 @@
+---
+description: Run the code-quality checks a theme of the themes/ folder of the Webship Workspace declares, and say what is red and why, before anything is pushed.
+argument-hint: '<theme> [checks, comma separated]'
+---
+
+# /themes-check
+
+Check the theme of `~/workspace/themes` named in: `$ARGUMENTS`
+
+The arguments are the text typed after the command: the first word is the theme (its folder
+name in `themes/`), and a second word is a comma separated list of checks to run instead of all of
+them (`format`, `js`, `css`, `yaml`, `spelling`, `types`, `php`, `twig`, `e2e`). With no theme,
+stop and ask for one: `ls ~/workspace/themes` lists the candidates. The workspace is container-based
+(DDEV by default); nothing is installed on the host for a check.
+
+## 1. The plan
+
+```bash
+cd ~/workspace/themes
+bash cmd-tools-checks.sh <theme> --list
+```
+
+It prints every check, the script the package declares for it and where it would run, and runs
+nothing. A check that is "not declared" is not a failure: say which are declared.
+
+## 2. Run
+
+```bash
+bash cmd-tools-checks.sh <theme>
+bash cmd-tools-checks.sh <theme> --only <checks>
+```
+
+Use the second form when checks were named. If the plan says the dependencies are not installed,
+say so and ask before adding `--install`: an install runs the package's own scripts.
+
+## 3. Report
+
+For each check: passed, failed or not declared; for a failed one the first lines of what it
+printed and the file it points at. Do not fix anything unasked, and never skip a check to make
+the run pass. For the pipeline (`cmd-tools-gitlab-ci-local.sh`), hand over to the `themes-maintainer` agent; the
+`themes-workflow` skill lists every command of the folder.

package/ai/prompts/themes-green-gate.md

@@ -0,0 +1,27 @@
+Bring a Drupal theme to green before a push: the checks it declares, then its pipeline on this machine.
+
+The launch line is for Claude Code, the default; the text between the triple quotes can be given to another AI CLI as it is.
+
+```
+claude --permission-mode bypassPermissions """
+Bring the theme <theme> of the themes folder to green before it is pushed
+# ~/workspace/themes/<theme> · a git checkout · container-based (DDEV by default)
+# nothing is pushed, merged, reset, deleted or built in this session
+# the build and install-all commands of the folder run composer and sudo on the host: do not run them
+
+1. git -C <theme> status -sb
+   tell me the branch and what is not committed
+2. bash cmd-tools-checks.sh <theme> --list
+   tell me which checks the theme declares
+3. bash cmd-tools-checks.sh <theme>
+   every declared check; tell me which are red, with the first lines of each
+4. bash cmd-tools-gitlab-ci-local.sh <theme> --doctor
+   stop and tell me if the runner or the container engine is missing
+5. bash cmd-tools-gitlab-ci-local.sh <theme>
+   if the whole pipeline cannot run here, say why and run: bash cmd-tools-gitlab-ci-local.sh <theme> --slim
+
+Report: the checks (passed, failed, not declared), the pipeline (GREEN or RED, which jobs ran,
+which could not run here). A red job is a result: do not hide it, do not allow it to fail.
+Then ask me whether to fix what is red.
+"""
+```

package/ai/skills/themes-workflow/SKILL.md

@@ -0,0 +1,72 @@
+---
+name: themes-workflow
+description: How work is done in the `themes/` folder of the Webship Workspace — what a theme is there (a git checkout to work on, or a try-out build), how its code-quality checks and its GitLab CI pipeline are run before a push, how it is backed up, which commands of the folder still run `composer` and `sudo` on the host and are never run unasked, with the flags of each command and the settings keys of the folder. Use when asked to "run the checks of this theme", "run the pipeline locally", "build this theme", "which themes does the folder list", or when a command of `themes/` is about to be run.
+argument-hint: '[what you are about to do in themes]'
+---
+
+# themes-workflow
+
+`~/workspace/themes` is the Themes folder of a Webship Workspace (container-based, DDEV by default).
+Themes are Drupal contrib and private themes, checked out to work on, and the try-out builds of the themes the folder's settings file lists. It comes with the Themes plugin (`@webship.co/workspace-drupal-themes`), which places the commands below in the folder. Every command finds the workspace from its own path; run it from the folder, and read `bash <command> --help` before quoting a flag.
+
+## The order of work
+
+1. **See what the theme declares**: `bash cmd-tools-checks.sh mytheme --list`. It runs nothing.
+2. **Work on a branch** of the checkout, `~/workspace/themes/mytheme`.
+3. **Run the checks**: `bash cmd-tools-checks.sh mytheme`, or some with `--only`.
+4. **Run the pipeline on this machine**: `bash cmd-tools-gitlab-ci-local.sh mytheme --doctor`
+   once, then `bash cmd-tools-gitlab-ci-local.sh mytheme` (or `--slim`).
+5. **Push when it is green**, and gate on the remote pipeline what could not run here.
+
+The build and install-all commands are not part of this order: they run on the host.
+
+## Commands
+
+| Command | What it does | Flags |
+| --- | --- | --- |
+| `cmd-all-back-end-build-themes.sh` | **On the host.** The same for the `admin_themes` list | none |
+| `cmd-all-back-end-install-themes.sh` | **On the host.** The same for the `admin_themes` list | none |
+| `cmd-all-front-end-build-themes.sh` | **On the host.** Deletes every theme on the `themes` list with `sudo`, then builds the template and each theme | none |
+| `cmd-all-front-end-install-themes.sh` | **On the host.** Changes owners with `sudo`, then installs every theme on the `themes` list | none |
+| `cmd-backup-theme.sh` | The folder of a theme as an archive, and the database of a built theme as a dump, into `backups/themes/`: `<theme>` | none |
+| `cmd-build-admin-theme.sh` | **On the host.** The same for an administration theme: `<theme>` | none |
+| `cmd-build-drupal-template.sh` | **On the host.** Removes the template project with `sudo` and creates it again with `composer` | none |
+| `cmd-build-theme.sh` | **On the host.** Copies the template project to `themes/<name>` and requires the theme with `composer`: `<theme>` | none |
+| `cmd-install-admin-theme.sh` | Installs the site of a built theme and makes the theme the administration one: `<theme>` | none |
+| `cmd-install-theme.sh` | Installs the site of a built theme and makes the theme the default one: `<theme>` | none |
+| `cmd-tools-checks.sh` | Runs the code-quality checks an item's `package.json` declares; `--list` prints the plan and runs nothing | `--browser` `--e2e` `--fail-fast` `--install` `--list` `--only` `--runner` `--skip` |
+| `cmd-tools-gitlab-ci-local.sh` | Runs an item's GitLab CI pipeline on this machine, before a push | `--doctor` `--list` `--slim` `--variable` |
+| `cmd-tools-reclaim.sh` | Disk held by projects whose folder is gone: a dry run unless `--apply` | `--apply` `--keep-days` `--list-protected` `--only` |
+| `cmd-tools-remove.sh` | Containers, volumes and folder together; refuses work that is on no remote unless `--force` | `--force` `--orphans` |
+| `cmd-tools-update-all.sh` | **On the host.** `composer update` in every folder. Do not run it unasked | none |
+
+## Settings
+
+| Key | File | What it says |
+| --- | --- | --- |
+| `doc.name` | `core/config/workspace.themes.settings.yml` | The folder under the workspace root: `themes` |
+| `type` | `core/config/workspace.themes.settings.yml` | `code`: the rows of the page are packages and repositories, with the Build, Backup, Remove and Checks actions |
+| `composer` | `core/config/workspace.themes.settings.yml` | `manifest`: the COMPOSER menu only adds to `composer.json` here, and never installs |
+| `themes` | `core/config/workspace.themes.settings.yml` | The front-end themes the build-all and install-all commands go through, by project name |
+| `admin_themes` | `core/config/workspace.themes.settings.yml` | The administration themes, for the back-end commands |
+| `drupal.template_drupal_theme_name` | `core/config/workspace.themes.settings.yml` | The name of the template project the builds are copied from; the commands refuse to run when it is empty |
+| `assistant.name`, `assistant.placeholder` | `core/config/workspace.themes.settings.yml` | What the assistant is called on this page; `default` takes the workspace's |
+| `workspaces` | `core/config/settings.yml` | The active folders; `themes` is on it once the plugin is activated |
+
+## Rules
+
+- **The build and install-all commands still run on the host.** `cmd-build-drupal-template.sh`,
+  `cmd-build-theme.sh`, `cmd-build-admin-theme.sh`, the four `cmd-all-…-themes.sh` and
+  `cmd-tools-update-all.sh` call `composer` on the host, and several call `sudo` to remove folders
+  and change owners: they are not yet moved into containers. Never run one unasked; say what it
+  would do, and offer the container way: a site of a sites folder, with the theme required and
+  enabled in that site's container.
+- **The two build-all commands delete first**: every theme on the list, with `sudo`. Work in a
+  theme folder that is not pushed is lost.
+- **A theme checked out here is somebody's work.** Work on a branch; back it up before a risky
+  change (`bash cmd-backup-theme.sh <name>`); `bash cmd-tools-remove.sh` only when asked.
+- **Green before a push.** The checks the theme declares, then its pipeline on this machine.
+- The workspace is container-based (DDEV by default): never `composer`, `drush`, `php` or `npm` on
+  the host for a theme you work on.
+
+The Themes plugin places these beside this one, each in the workspace folder of its kind: the agent `themes-maintainer` (`ai-agents/`), the command `/themes-check` (`ai-commands/`) and the prompt `themes-green-gate` (`ai-prompts/`).

package/dist/src/index.d.ts

@@ -2,10 +2,15 @@
  * The Drupal themes workspace for Webship Workspace: the `themes/` folder as a plugin.
  *
  * What the package carries is placed by the installer from the manifest (the folder's settings file,
- * its commands and its docs) and listed by --activate; the dashboard draws the workspace from the
+ * its commands, its docs and its AI items, each in the folder of its kind) and listed by --activate; the dashboard draws the workspace from the
  * settings file like any other. Nothing to register at run time yet: this is where the folder's own
  * rail buttons, row menus or assistant context would go.
  */
 import type { PluginApi } from '@webship.co/workspace-plugin-api';
 export declare const WORKSPACE_KEY = "themes";
+/** The AI items the installer places, each in the workspace folder of its kind (ai/ in this package). */
+export declare const AGENTS: string[];
+export declare const SKILLS: string[];
+export declare const AI_COMMANDS: string[];
+export declare const PROMPTS: string[];
 export declare function register(api: PluginApi): void;

package/dist/src/index.js

@@ -3,15 +3,20 @@
  * The Drupal themes workspace for Webship Workspace: the `themes/` folder as a plugin.
  *
  * What the package carries is placed by the installer from the manifest (the folder's settings file,
- * its commands and its docs) and listed by --activate; the dashboard draws the workspace from the
+ * its commands, its docs and its AI items, each in the folder of its kind) and listed by --activate; the dashboard draws the workspace from the
  * settings file like any other. Nothing to register at run time yet: this is where the folder's own
  * rail buttons, row menus or assistant context would go.
  */
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.WORKSPACE_KEY = void 0;
+exports.PROMPTS = exports.AI_COMMANDS = exports.SKILLS = exports.AGENTS = exports.WORKSPACE_KEY = void 0;
 exports.register = register;
 exports.WORKSPACE_KEY = 'themes';
+/** The AI items the installer places, each in the workspace folder of its kind (ai/ in this package). */
+exports.AGENTS = ['themes-maintainer'];
+exports.SKILLS = ['themes-workflow'];
+exports.AI_COMMANDS = ['themes-check'];
+exports.PROMPTS = ['themes-green-gate'];
 function register(api) {
-    api.addAssistantContext(() => `The themes/ workspace is the Drupal themes workspace (a plugin, @webship.co/workspace-drupal-themes); its commands are the cmd-*.sh scripts in that folder.`);
+    api.addAssistantContext(() => `The themes/ workspace is the Drupal themes workspace (a plugin, @webship.co/workspace-drupal-themes); its commands are the cmd-*.sh scripts in that folder. It comes with AI items for work in this folder: the agent \`themes-maintainer\` (ai-agents/), the skill \`themes-workflow\` (ai-skills/), the command \`/themes-check\` (ai-commands/) and the prompt \`themes-green-gate\` (ai-prompts/).`);
 }
 //# sourceMappingURL=index.js.map

package/dist/src/index.js.map

@@ -1 +1 @@
-{"version":3,"file":"index.js","sourceRoot":"","sources":["../../src/index.ts"],"names":[],"mappings":";AAAA;;;;;;;GAOG;;;AAMH,4BAEC;AAJY,QAAA,aAAa,GAAG,QAAQ,CAAC;AAEtC,SAAgB,QAAQ,CAAC,GAAc;IACrC,GAAG,CAAC,mBAAmB,CAAC,GAAG,EAAE,CAAC,6JAA6J,CAAC,CAAC;AAC/L,CAAC"}
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../src/index.ts"],"names":[],"mappings":";AAAA;;;;;;;GAOG;;;AAYH,4BAEC;AAVY,QAAA,aAAa,GAAG,QAAQ,CAAC;AAEtC,yGAAyG;AAC5F,QAAA,MAAM,GAAG,CAAC,mBAAmB,CAAC,CAAC;AAC/B,QAAA,MAAM,GAAG,CAAC,iBAAiB,CAAC,CAAC;AAC7B,QAAA,WAAW,GAAG,CAAC,cAAc,CAAC,CAAC;AAC/B,QAAA,OAAO,GAAG,CAAC,mBAAmB,CAAC,CAAC;AAE7C,SAAgB,QAAQ,CAAC,GAAc;IACrC,GAAG,CAAC,mBAAmB,CAAC,GAAG,EAAE,CAAC,wYAAwY,CAAC,CAAC;AAC1a,CAAC"}

package/docs/AGENTS.md

@@ -2,7 +2,7 @@
 
 Contrib and private themes, checked out to work on.
 
-Part of the **Webship Workspace** (`~/workspace`), a DDEV-only harness. The rules in the root
+Part of the **Webship Workspace** (`~/workspace`), a container-based harness (DDEV by default). The rules in the root
 `CLAUDE.md` apply here too; what follows is what is specific to this folder.
 
 ## The rule that matters here
@@ -41,3 +41,13 @@ bash cmd-tools-update-all.sh                          # Find the workspace tooli
 
 Every one locates the workspace from its own path, so there is nothing to export and nothing to
 install. `--help` on any of them lists its arguments.
+
+## AI items for this folder
+
+The plugin of this folder (`@webship.co/workspace-drupal-themes`) places its own AI items in the AI folders of the
+workspace, when they are active:
+
+- `themes-maintainer` (`ai-agents/`): Works on a Drupal theme in `themes/` and brings it to green before a push: its checks, its pipeline on this machine, a backup; knows which commands still run on the host and never runs one unasked
+- `themes-workflow` (`ai-skills/`): How work is done in `themes/`: see what is declared, check, run the pipeline locally, push when green; every command with its flags, the ones that run on the host, the settings keys
+- `/themes-check` (`ai-commands/`): `/themes-check <theme> [checks]`: prints the plan, runs the declared checks and says what is red and why
+- `themes-green-gate` (`ai-prompts/`): A new session that runs a theme's checks and its pipeline on this machine and reports green or red

package/features/drupal-themes.feature

@@ -11,3 +11,19 @@ Feature: The Drupal themes workspace plugin
     Given I am on "/settings/plugins"
      Then I should see "Drupal themes"
       And I should see "@webship.co/workspace-drupal-themes"
+
+  Scenario: The AI Agents folder lists the agent the plugin ships
+    Given I am on "/ai-agents"
+     Then I should see "themes-maintainer"
+
+  Scenario: The AI Skills folder lists the skill the plugin ships
+    Given I am on "/ai-skills"
+     Then I should see "themes-workflow"
+
+  Scenario: The AI Commands folder lists the command the plugin ships
+    Given I am on "/ai-commands"
+     Then I should see "themes-check"
+
+  Scenario: The AI Prompts folder lists the prompt the plugin ships
+    Given I am on "/ai-prompts"
+     Then I should see "themes-green-gate"

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@webship.co/workspace-drupal-themes",
-  "version": "1.0.2",
-  "description": "The Drupal themes workspace for Webship Workspace: the `themes/` folder (type code), its settings file, its 15 commands and its docs, activated as a plugin.",
+  "version": "1.0.9",
+  "description": "The Drupal themes workspace for Webship Workspace: the `themes/` folder (type code), its settings file, its 15 commands, its docs and its AI items (an agent, a skill, a command and a prompt, each in the folder of its kind), activated as a plugin.",
   "main": "dist/src/index.js",
   "types": "dist/src/index.d.ts",
   "license": "ISC",
@@ -11,6 +11,7 @@
   },
   "files": [
     "dist/src",
+    "ai",
     "commands",
     "config",
     "docs",
@@ -26,6 +27,20 @@
   "workspacePlugin": {
     "name": "drupal-themes",
     "label": "Drupal themes",
+    "needs": [
+      "ai-agents",
+      "ai-skills",
+      "ai-commands",
+      "ai-prompts"
+    ],
+    "suggests": {
+      "commands": [
+        {
+          "command": "composer",
+          "hint": "https://getcomposer.org/download/"
+        }
+      ]
+    },
     "workspace": {
       "key": "themes",
       "settingsTemplate": "config/workspace.themes.settings.yml",
@@ -52,6 +67,20 @@
         "docs/README.md"
       ]
     },
+    "ai": {
+      "agents": [
+        "ai/agents/themes-maintainer.md"
+      ],
+      "skills": [
+        "ai/skills/themes-workflow"
+      ],
+      "commands": [
+        "ai/commands/themes-check.md"
+      ],
+      "prompts": [
+        "ai/prompts/themes-green-gate.md"
+      ]
+    },
     "features": [
       "features/drupal-themes.feature"
     ]