@rubytech/create-maxy-code 0.1.185 → 0.1.186

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rubytech/create-maxy-code",
-  "version": "0.1.185",
+  "version": "0.1.186",
   "description": "Install Maxy — AI for Productive People",
   "bin": {
     "create-maxy-code": "./dist/index.js"

package/payload/platform/plugins/admin/hooks/__tests__/prompt-optimiser-directive.test.sh

@@ -0,0 +1,70 @@
+#!/usr/bin/env bash
+# Regression test for prompt-optimiser-directive.sh.
+#
+# Covers:
+#   1. Valid UserPromptSubmit stdin  -> exit 0, stdout is valid JSON,
+#      hookEventName == "UserPromptSubmit", additionalContext non-empty.
+#   2. Empty / garbage stdin         -> exit 0, still valid JSON (the hook
+#      ignores the prompt text; the directive is standing).
+#   3. python3 unavailable on PATH   -> exit 0, empty stdout (fail-open).
+
+set -u
+
+HOOK="$(cd "$(dirname "$0")/.." && pwd)/prompt-optimiser-directive.sh"
+if [[ ! -x "$HOOK" ]]; then
+  echo "FAIL: $HOOK not executable" >&2
+  exit 1
+fi
+
+PASS=0
+FAIL=0
+
+# Assert: hook on $1 (stdin) exits 0 and stdout is JSON with a non-empty
+# additionalContext and the correct hookEventName.
+assert_valid_injection() {
+  local name="$1" stdin="$2" out actual_exit
+  out=$(printf '%s' "$stdin" | bash "$HOOK" 2>/dev/null)
+  actual_exit=$?
+  if [[ "$actual_exit" -ne 0 ]]; then
+    echo "FAIL: $name (expected exit=0, got=$actual_exit)" >&2; FAIL=$((FAIL+1)); return
+  fi
+  if printf '%s' "$out" | python3 -c '
+import json, sys
+d = json.load(sys.stdin)
+h = d["hookSpecificOutput"]
+assert h["hookEventName"] == "UserPromptSubmit", "wrong hookEventName"
+assert isinstance(h["additionalContext"], str) and len(h["additionalContext"]) > 0, "empty additionalContext"
+' 2>/dev/null; then
+    echo "PASS: $name"; PASS=$((PASS+1))
+  else
+    echo "FAIL: $name (stdout not valid directive JSON: $out)" >&2; FAIL=$((FAIL+1))
+  fi
+}
+
+# Case 1 — valid UserPromptSubmit envelope.
+assert_valid_injection "valid UserPromptSubmit stdin -> directive JSON" \
+  '{"hook_event_name":"UserPromptSubmit","prompt":"fix the thing","session_id":"abc"}'
+
+# Case 2 — garbage stdin still yields the standing directive.
+assert_valid_injection "garbage stdin -> still directive JSON" \
+  'not json at all'
+
+# Case 3 — fail-open when python3 is absent from PATH.
+FAKEBIN=$(mktemp -d)
+# A minimal PATH containing the core utils the hook needs (cat, printf, env,
+# command) but NOT python3. Resolve their real dir(s) and symlink them in.
+for util in cat printf env bash; do
+  src=$(command -v "$util" 2>/dev/null) && ln -sf "$src" "$FAKEBIN/$util" 2>/dev/null
+done
+nopy_out=$(printf '%s' '{"prompt":"x"}' | PATH="$FAKEBIN" bash "$HOOK" 2>/dev/null)
+nopy_exit=$?
+if [[ "$nopy_exit" -eq 0 && -z "$nopy_out" ]]; then
+  echo "PASS: python3 absent -> exit 0, empty stdout (fail-open)"; PASS=$((PASS+1))
+else
+  echo "FAIL: python3 absent (expected exit=0 + empty stdout, got exit=$nopy_exit stdout=$nopy_out)" >&2; FAIL=$((FAIL+1))
+fi
+rm -rf "$FAKEBIN"
+
+echo "----"
+echo "PASS=$PASS FAIL=$FAIL"
+[[ "$FAIL" -eq 0 ]]

package/payload/platform/plugins/admin/hooks/prompt-optimiser-directive.sh

@@ -0,0 +1,52 @@
+#!/usr/bin/env bash
+# UserPromptSubmit hook: inject the standing prompt-optimiser directive as
+# additionalContext on every turn, so the agent restates each non-trivial
+# prompt via the prompt-optimiser skill before acting on it. Mirrors
+# doctrine.sh: emit hookSpecificOutput.additionalContext via python3,
+# fail-open with exit 0.
+#
+# Compliance is behavioural, not deterministic. A hook cannot force a skill
+# call; the directive steers the agent, it does not gate the turn. The raw
+# prompt always still reaches the model (UserPromptSubmit output is ADDED to
+# the prompt, never substituted), so "the restatement governs" is an
+# instruction to the agent, not a removal of the original text.
+#
+# Input  (stdin, UserPromptSubmit contract): { "prompt": "...", ... } — drained
+#         and ignored; the directive is standing and prompt-independent.
+# Output (stdout JSON):
+#   { "hookSpecificOutput": { "hookEventName": "UserPromptSubmit",
+#                             "additionalContext": "<directive>" } }
+#
+# Fail-open: if python3 is unavailable or JSON encoding fails, exit 0 with no
+# stdout. The hook must never block or corrupt a turn.
+
+set -uo pipefail
+
+# Drain stdin; the directive does not depend on the prompt text.
+cat >/dev/null 2>&1 || true
+
+# Fail-open if the JSON encoder is unavailable.
+command -v python3 >/dev/null 2>&1 || exit 0
+
+DIRECTIVE=$(cat <<'DIRECTIVE_EOF'
+PROMPT-OPTIMISER DIRECTIVE (standing)
+Before acting on this turn's request, run the prompt-optimiser skill on the user's raw prompt in its in-session restatement mode, then treat the restated task as the authoritative statement of what was asked and proceed from it. Set aside your own first reading of the raw wording; the restatement governs. The raw prompt stays in context for reference only.
+Skip the restatement when the prompt is a one-word confirmation, a slash-command invocation, or a direct continuation of the immediately preceding turn; restatement adds nothing in those cases.
+DIRECTIVE_EOF
+)
+
+OUT=$(printf '%s' "$DIRECTIVE" | python3 -c '
+import json, sys
+ctx = sys.stdin.read()
+print(json.dumps({
+    "hookSpecificOutput": {
+        "hookEventName": "UserPromptSubmit",
+        "additionalContext": ctx,
+    }
+}))
+' 2>/dev/null) || exit 0
+
+[ -n "$OUT" ] || exit 0
+printf '%s\n' "$OUT"
+echo "[prompt-optimiser-directive] injected len=${#DIRECTIVE}" >&2
+exit 0

package/payload/platform/plugins/docs/references/plugins-guide.md

@@ -24,7 +24,7 @@ These are part of {{productName}}'s foundation and cannot be disabled:
 | `tasks` | Task lifecycle — create, update, list, relate, complete |
 | `workflows` | Persistent named workflows — reusable instruction sets |
 | `contacts` | CRM contact management — create, lookup, update, list |
-| `prompt-optimiser` | Prompt optimiser — turns a rough draft or task description into a single finished, copy-pasteable prompt tuned for Opus 4.7 adaptive thinking in the chat app (claude.ai, Mac, iOS) |
+| `prompt-optimiser` | Prompt optimiser — two modes. Chat-app mode turns a rough draft or task description into a single finished, copy-pasteable prompt tuned for Opus 4.7 adaptive thinking (claude.ai, Mac, iOS). In-session mode is applied automatically: a standing `UserPromptSubmit` directive hook (`admin/hooks/prompt-optimiser-directive.sh`) injects context every turn telling the admin agent to restate each non-trivial prompt through this skill and act on the restatement, skipped for one-word confirmations, slash-commands, and direct continuations. Compliance is behavioural — the hook steers the agent, it cannot force the skill call. |
 | `url-get` | Faithful page retrieval — fetches a server-rendered page, writes a verbatim markdown copy to an account-scoped reference file (no model in the path, so no copyright refusal), and returns a transformative summary plus the file path. Use instead of WebFetch when a faithful copy is needed (e.g. ingesting your own published writing). |
 
 ### {{productName}} Plugins (user-selectable)

package/payload/platform/plugins/prompt-optimiser/skills/prompt-optimiser/SKILL.md

@@ -9,6 +9,21 @@ You turn whatever the user gives you — a rough draft, a vague idea, a task des
 
 This is for the **chat app** (claude.ai, Mac, iOS), not the API. The user is going to paste a single message into chat. There is no system prompt, no `effort` parameter, no tool config to tune. The prompt itself has to do all the work.
 
+## Which mode are you in? (read this first)
+
+This skill is invoked two ways, and they want opposite outputs. Decide which one applies before doing anything else.
+
+**In-session restatement mode.** You are invoking this skill on the current turn's own user prompt — triggered by the standing prompt-optimiser directive — so that you can act on a sharper reading of what was just asked. The output is for *you*, the working agent, not for a human to paste anywhere. Produce a plain restated task and nothing else:
+
+- Restate what the user is actually asking for: the goal, the constraints they stated, and the format or scope if they gave one. Turn vague wording into concrete intent, grounded only in what they wrote plus the conversation context you already hold.
+- Write it as plain prose or a short bulleted brief. No fenced code block. No role line, no XML tags, no length-cap ceremony unless the user asked for one.
+- Do not end with "Think before answering". Do not ask the user to paste anything — you already have the content and the context.
+- Do not invent requirements or add scope the user did not ask for. If the prompt was already clear, say so in one line and restate it tightly.
+
+Then do the work from the restated task. Everything below this section is for the other mode and does not apply — stop reading here.
+
+**Chat-app prompt mode.** The user explicitly asked you to write, rewrite, or optimise a prompt they will paste into the chat app. That is the rest of this document: a single finished, copy-pasteable prompt in a code block ending in "Think before answering". Read on.
+
 ## Two hard rules
 
 These two rules override everything else in this skill. Read them, then re-read them.

package/payload/platform/scripts/setup-account.sh

@@ -143,7 +143,8 @@ cat > "$ACCOUNT_SETTINGS" << SETTINGS_EOF
     "UserPromptSubmit": [
       {
         "hooks": [
-          { "type": "command", "command": "bash $HOOKS_PATH/archive-ingest-surface-gate.sh" }
+          { "type": "command", "command": "bash $HOOKS_PATH/archive-ingest-surface-gate.sh" },
+          { "type": "command", "command": "bash $HOOKS_PATH/prompt-optimiser-directive.sh" }
         ]
       }
     ],