@webship.co/workspace-ai-commands 0.0.0-stage → 1.0.0-alpha1

package/README.md

@@ -1,3 +1,26 @@
-# Temporary Holding Version
+# @webship.co/workspace-ai-commands
 
-This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
+The **AI Commands** workspace of the [Webship Workspace](https://github.com/webship/workspace) dashboard:
+the `ai-commands/` folder (type `ai-items`), its settings file (`core/config/workspace.ai-commands.settings.yml`),
+its commands and its docs, as a plugin.
+
+## Use it
+
+```bash
+cd ~/workspace
+bash core/scripts/plugins.sh --require github:webship/workspace-ai-commands
+bash core/scripts/plugins.sh --activate ai-commands     # puts `ai-commands` on the workspaces list of settings.yml
+bash core/scripts/plugins.sh --install ai-commands      # 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.
+
+## The commands
+
+| Command |
+| --- |
+| `cmd-tool-backup-command.sh` |
+| `cmd-tools-ai-items.sh` |
+
+The bash functions these commands call live in the dashboard's `core/scripts/functions`.

package/commands/cmd-tool-backup-command.sh

@@ -0,0 +1,20 @@
+#!/usr/bin/env bash
+
+# Bootstrap.
+# Find the workspace tooling from this script, so a fresh clone needs no setup.
+WORKSPACE_SCRIPTS="${WORKSPACE_SCRIPTS:-$(cd "$(dirname "${BASH_SOURCE[0]}")/../core/scripts" && pwd)}";
+source ${WORKSPACE_SCRIPTS}/bootstrap.sh || exit 1 ;
+
+# Load workspace settings and extra lists.
+eval $(parse_yaml ${WORKSPACE_CONFIG}/workspace.ai-commands.settings.yml);
+
+ARGPARSE_DESCRIPTION="Backup a command"
+argparse "$@" <<ARGEOF || exit 1
+parser.add_argument('PROJECT_NAME',
+                    help='The name of the project.')
+ARGEOF
+
+shift $#;
+trim_project_name ;   # "v11x00b1/" -> "v11x00b1" — see functions/fun-project-name.sh
+
+backup_workspace_item "${PROJECT_NAME}" || exit 1 ;

package/commands/cmd-tools-ai-items.sh

@@ -0,0 +1,45 @@
+#!/usr/bin/env bash
+
+# Move commands between the three places they live: this workspace folder,
+# the Claude Code CLI (~/.claude/commands), and the shared repository
+# github.com/webship/ai-agents.
+
+# Bootstrap.
+# Find the workspace tooling from this script, so a fresh clone needs no setup.
+WORKSPACE_SCRIPTS="${WORKSPACE_SCRIPTS:-$(cd "$(dirname "${BASH_SOURCE[0]}")/../core/scripts" && pwd)}";
+source ${WORKSPACE_SCRIPTS}/bootstrap.sh || exit 1 ;
+
+# Load workspace settings and extra lists.
+eval $(parse_yaml ${WORKSPACE_CONFIG}/workspace.ai-commands.settings.yml);
+
+ARGPARSE_DESCRIPTION="Show, fetch, pull, install or clone commands (workspace | ~/.claude | webship/ai-agents)"
+source ${WORKSPACE_SCRIPTS}/args/arg-ai-items.sh || exit 1 ;
+
+shift $#;
+
+if [ "${PROPOSE}" == 'yes' ] ; then
+  ai_items_propose "ai-commands" "${NAME}" "${SUMMARY}" "$([ "${CONFIRM}" == 'yes' ] && echo yes || echo no)" ;
+elif [ ! "${CLONE_TO}" == '_none_' ] ; then
+  clone_ai_item "ai-commands" "${NAME}" "${CLONE_TO}" || exit 1 ;
+  tailor_ai_item "ai-commands" "${CLONED_AI_ITEM}" "${CLONE_TO}" "${PURPOSE}" ;
+elif [ "${LIST_REMOTE}" == 'yes' ] ; then
+  ai_items_list_remote "ai-commands" ;
+elif [ "${FETCH}" == 'yes' ] ; then
+  ai_items_fetch "ai-commands" "${NAME}" claude ;
+elif [ "${PULL}" == 'yes' ] ; then
+  if [ "${SOURCE}" == 'claude' ] ; then
+    ai_items_from_claude "ai-commands" "${NAME}" "${FILTER}" ;
+  else
+    ai_items_fetch "ai-commands" "${NAME}" workspace ;
+  fi
+elif [ "${INSTALL}" == 'yes' ] ; then
+  install_ai_item "ai-commands" "${NAME}" "${TO}" ;
+elif [ ! "${ADD}" == '_none_' ] ; then
+  ai_items_add "ai-commands" "${NAME}" "${ADD}" "${TO}" ;
+elif [ "${UPDATE}" == 'yes' ] ; then
+  ai_items_update "ai-commands" "${NAME}" "${TO}" ;
+elif [ "${CHECK}" == 'yes' ] ; then
+  ai_items_check "ai-commands" "${NAME}" "${TO}" ;
+else
+  ai_items_status "ai-commands" ;
+fi

package/config/workspace.ai-commands.settings.yml

@@ -0,0 +1,13 @@
+doc:
+  name: ai-commands
+
+# What this folder's projects are, and which actions their rows offer:
+# sites | code | files | media | ai-items — see core/workspace-app/WORKSPACES.md.
+type: ai-items
+
+# What the assistant is called on THIS workspace's page, and what its composer says when empty.
+# `default` in either means "whatever settings.yml says" — the global value, so a rename there
+# still reaches this page. Set a value here to override it for this workspace alone.
+assistant:
+  name: default
+  placeholder: default

package/dist/src/index.d.ts

@@ -0,0 +1,11 @@
+/**
+ * The AI Commands workspace for Webship Workspace: the `ai-commands/` 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
+ * 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 = "ai-commands";
+export declare function register(api: PluginApi): void;

package/dist/src/index.js

@@ -0,0 +1,17 @@
+"use strict";
+/**
+ * The AI Commands workspace for Webship Workspace: the `ai-commands/` 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
+ * 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.register = register;
+exports.WORKSPACE_KEY = 'ai-commands';
+function register(api) {
+    api.addAssistantContext(() => `The ai-commands/ workspace is the AI Commands workspace (a plugin, @webship.co/workspace-ai-commands); its commands are the cmd-*.sh scripts in that folder.`);
+}
+//# sourceMappingURL=index.js.map

package/dist/src/index.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../src/index.ts"],"names":[],"mappings":";AAAA;;;;;;;GAOG;;;AAMH,4BAEC;AAJY,QAAA,aAAa,GAAG,aAAa,CAAC;AAE3C,SAAgB,QAAQ,CAAC,GAAc;IACrC,GAAG,CAAC,mBAAmB,CAAC,GAAG,EAAE,CAAC,8JAA8J,CAAC,CAAC;AAChM,CAAC"}

package/docs/AGENTS.md

@@ -0,0 +1,24 @@
+# Prompts
+
+Reusable AI prompts. Run them from the dashboard or clone one to adapt; they are not
+installed as slash commands, because a prompt with placeholders is meant to be filled in.
+
+Part of the **Webship Workspace** (`~/workspace`), a DDEV-only harness. The rules in the root
+`CLAUDE.md` apply here too; what follows is what is specific to this folder.
+
+## What an item is here
+
+One markdown file per prompt. They are run — handed to the assistant with the placeholders still
+in them, to fill in — or cloned and adapted. They are deliberately NOT installed as slash
+commands: a prompt nobody has filled in is not a command.
+
+## Commands here
+
+```bash
+bash cmd-tool-backup-prompt.sh                        # Bootstrap.
+bash cmd-tool-git-change-filemode-to-false.sh         # Bootstrap.
+bash cmd-tool-propose-prompts.sh                      # Propose one prompt back to the shared repository — webship/ai-agents by default, or whatever
+```
+
+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.

package/docs/CLAUDE.md

@@ -0,0 +1,7 @@
+# Prompts — workspace context
+
+You are inside the **prompts** workspace of the Webship Workspace (`~/workspace`).
+
+@AGENTS.md
+
+The rules in it apply to everything under this folder, however deep.

package/docs/README.md

@@ -0,0 +1,41 @@
+# AI Commands
+
+Claude Code **slash commands**: one `<name>.md` per command, installed into
+`~/.claude/commands/` where it becomes `/<name>`.
+
+Three places hold them, and this folder is one of them:
+
+| Where | What it is |
+|---|---|
+| `~/workspace/ai-commands/` | this folder — drafts, and what you edit |
+| `~/.claude/commands/` | what a Claude Code session actually loads |
+| `webship/ai-agents` `.claude/commands/` | what the team has |
+
+## Why it is `ai-commands` and not `commands`
+
+`~/workspace/commands` is already taken: it is the Settings view over every `cmd-*.sh` shell
+script in the workspace, and it is deliberately not a registered workspace. Two different things
+called "commands" in one tree would collide on the folder name, so this one is `ai-commands`.
+Its label in the dashboard is **AI Commands**.
+
+## Use it
+
+```bash
+bash cmd-tools-ai-items.sh                     # what is here, installed, and in the repo
+bash cmd-tools-ai-items.sh --list-remote       # what the shared repo has
+bash cmd-tools-ai-items.sh review --pull       # repo  -> this folder, to read or edit
+bash cmd-tools-ai-items.sh review --fetch      # repo  -> ~/.claude, usable next session
+bash cmd-tools-ai-items.sh review --install    # here  -> ~/.claude
+bash cmd-tools-ai-items.sh review --clone-to my-review --purpose "..."
+bash cmd-tool-backup-command.sh review         # tar it into ~/workspace/backups/
+```
+
+Omit the name and every command is meant.
+
+## Commands and prompts both land in `~/.claude/commands/`
+
+A command is a markdown spec with `$ARGUMENTS`, typed mid-session. A **prompt**
+(`~/workspace/ai-prompts/`) is a whole `claude …` launch command that opens a new screen session in
+a folder or project. Six names exist in both — `drupal-patch`, `explain`, `phpcs-fix`, `review`,
+`say`, `test` — and installing one writes over the other. Pick the kind you want before you run
+`--install`.

package/features/ai-commands.feature

@@ -0,0 +1,12 @@
+Feature: The AI Commands workspace plugin
+  Once the plugin is activated and installed, the ai-commands workspace is on the dashboard, and the
+  Plugins page lists the plugin with its four steps.
+
+  Scenario: The workspace page is there
+    Given I am on "/ai-commands"
+     Then I should see "AI Commands"
+
+  Scenario: The plugin is listed on the Plugins page
+    Given I am on "/settings/plugins"
+     Then I should see "AI Commands"
+      And I should see "@webship.co/workspace-ai-commands"

package/package.json

@@ -1,6 +1,54 @@
 {
   "name": "@webship.co/workspace-ai-commands",
-  "version": "0.0.0-stage",
-  "stub": true,
-  "description": "Temporary package placeholder for staged publishing"
-}
+  "version": "1.0.0-alpha1",
+  "description": "The AI Commands workspace for Webship Workspace: the `ai-commands/` folder (type ai-items), its settings file, its 2 commands and its docs, activated as a plugin.",
+  "main": "dist/src/index.js",
+  "types": "dist/src/index.d.ts",
+  "license": "ISC",
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/webship/workspace-ai-commands.git"
+  },
+  "files": [
+    "dist/src",
+    "commands",
+    "config",
+    "docs",
+    "features",
+    "README.md"
+  ],
+  "scripts": {
+    "build": "tsc -p tsconfig.json",
+    "prepare": "npm run build",
+    "test": "npm run build && node --test dist/tests/*.test.js",
+    "lint": "tsc -p tsconfig.json --noEmit"
+  },
+  "workspacePlugin": {
+    "name": "ai-commands",
+    "label": "AI Commands",
+    "workspace": {
+      "key": "ai-commands",
+      "settingsTemplate": "config/workspace.ai-commands.settings.yml",
+      "files": [
+        "commands/cmd-tool-backup-command.sh",
+        "commands/cmd-tools-ai-items.sh"
+      ],
+      "docs": [
+        "docs/AGENTS.md",
+        "docs/CLAUDE.md",
+        "docs/README.md"
+      ]
+    },
+    "features": [
+      "features/ai-commands.feature"
+    ]
+  },
+  "devDependencies": {
+    "@types/node": "^24.0.0",
+    "@webship.co/workspace-plugin-api": "^1.0.0-alpha1",
+    "typescript": "^5.9.0"
+  },
+  "publishConfig": {
+    "access": "public"
+  }
+}