drafted 1.8.0 → 1.8.2

package/install-mcp.sh

@@ -507,34 +507,71 @@ NODE
 install_agent_instructions "$HOME/.claude/CLAUDE.md" "Claude global instructions"
 install_agent_instructions "$HOME/.codex/CODEX.md" "Codex global instructions"
 
-# ── Skills ───────────────────────────────────────────────────────
+# ── Skills & commands ─────────────────────────────────────────────
 
-step "Installing skills"
+step "Installing skills and commands"
 
-# Find the installed package's skills directory
-DRAFTED_PKG_DIR="$(node -e "try { console.log(require.resolve('drafted/package.json').replace('/package.json','')) } catch { process.exit(1) }" 2>/dev/null)" || true
+# Resolve the plugin source: a local checkout when present (e.g. --local from this
+# repo), otherwise the installed npm package's bundled plugin/ directory.
+# require.resolve() misses packages under the custom global prefix
+# ($HOME/.drafted/npm-global) when run from an arbitrary cwd (curl | bash), so
+# prefer the already-computed global node_modules root from the install step.
+if [ -n "${NPM_ROOT:-}" ] && [ -d "$NPM_ROOT/drafted" ]; then
+  DRAFTED_PKG_DIR="$NPM_ROOT/drafted"
+else
+  DRAFTED_PKG_DIR="$(node -e "try { console.log(require.resolve('drafted/package.json').replace('/package.json','')) } catch { process.exit(1) }" 2>/dev/null)" || true
+fi
+if [ -d "$SCRIPT_DIR/plugin/skills" ] || [ -d "$SCRIPT_DIR/plugin/commands" ]; then
+  PLUGIN_SRC="$SCRIPT_DIR/plugin"
+elif [ -n "$DRAFTED_PKG_DIR" ] && [ -d "$DRAFTED_PKG_DIR/plugin" ]; then
+  PLUGIN_SRC="$DRAFTED_PKG_DIR/plugin"
+else
+  PLUGIN_SRC=""
+fi
 
-if [ -n "$DRAFTED_PKG_DIR" ] && [ -d "$DRAFTED_PKG_DIR/skills" ]; then
+# Skills — Claude Code auto-loads these from ~/.claude/skills/<name>/SKILL.md
+if [ -n "$PLUGIN_SRC" ] && [ -d "$PLUGIN_SRC/skills" ]; then
   SKILLS_DIR="$HOME/.claude/skills"
   mkdir -p "$SKILLS_DIR"
-  INSTALLED=0
-  # Copy individual skill files
-  for f in "$DRAFTED_PKG_DIR/skills/"*.md; do
-    [ -f "$f" ] || continue
-    cp "$f" "$SKILLS_DIR/"
-    INSTALLED=$((INSTALLED + 1))
-  done
-  # Copy skill directories
-  for d in "$DRAFTED_PKG_DIR/skills/"*/; do
+  SKILL_COUNT=0
+  for d in "$PLUGIN_SRC/skills/"*/; do
     [ -d "$d" ] || continue
     DIRNAME="$(basename "$d")"
     rm -rf "$SKILLS_DIR/$DIRNAME"
     cp -r "$d" "$SKILLS_DIR/$DIRNAME"
-    INSTALLED=$((INSTALLED + 1))
+    SKILL_COUNT=$((SKILL_COUNT + 1))
   done
-  ok "Installed $INSTALLED skills to $SKILLS_DIR"
+  ok "Installed $SKILL_COUNT skill(s) to $SKILLS_DIR"
+else
+  echo -e "    ${YELLOW}Skill source not found in package — skipping skills.${RESET}"
+fi
+
+# Commands — namespaced under drafted/ so they register as /drafted:<name>,
+# matching the marketplace install and the commands' own cross-references.
+if [ -n "$PLUGIN_SRC" ] && [ -d "$PLUGIN_SRC/commands" ]; then
+  CMD_COUNT=0
+  for f in "$PLUGIN_SRC/commands/"*.md; do
+    [ -f "$f" ] || continue
+    CMD_COUNT=$((CMD_COUNT + 1))
+  done
+
+  if [ "$CLIENT_CLAUDE_CODE" = true ]; then
+    CLAUDE_CMD_DIR="$HOME/.claude/commands/drafted"
+    rm -rf "$CLAUDE_CMD_DIR"
+    mkdir -p "$CLAUDE_CMD_DIR"
+    cp "$PLUGIN_SRC/commands/"*.md "$CLAUDE_CMD_DIR/" 2>/dev/null || true
+    ok "Installed $CMD_COUNT command(s) to $CLAUDE_CMD_DIR"
+  fi
+
+  if [ "$CLIENT_CODEX" = true ]; then
+    CODEX_CMD_DIR="$HOME/.codex/prompts/drafted"
+    rm -rf "$CODEX_CMD_DIR"
+    mkdir -p "$CODEX_CMD_DIR"
+    cp "$PLUGIN_SRC/commands/"*.md "$CODEX_CMD_DIR/" 2>/dev/null || true
+    ok "Installed $CMD_COUNT command(s) to $CODEX_CMD_DIR"
+  fi
 else
-  echo -e "    ${YELLOW}Skills directory not found in package — skipping.${RESET}"
+  echo -e "    ${YELLOW}Command source not found in package — skipping commands.${RESET}"
 fi
 
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "drafted",
-  "version": "1.8.0",
+  "version": "1.8.2",
   "description": "Drafted — visual thinking surface for humans and AI agents. Renders HTML, markdown, images, and code as frames on a zoomable canvas, with MCP tools for AI agents and real-time sync for humans.",
   "type": "module",
   "files": [
@@ -9,6 +9,8 @@
     "server/lib/umami.mjs",
     "src/shared/",
     "agent-instructions/",
+    "plugin/skills/",
+    "plugin/commands/",
     "install-mcp.sh"
   ],
   "bin": {
@@ -30,7 +32,7 @@
     "test:watch": "vitest",
     "version": "node scripts/sync-versions.mjs && git add plugin/.claude-plugin/plugin.json .claude-plugin/marketplace.json web-plugin/.claude-plugin/plugin.json web-plugin/.claude-plugin/marketplace.json",
     "version:check": "node scripts/sync-versions.mjs",
-    "postpublish": "bash scripts/sync-plugin.sh \"chore: sync plugin to v$npm_package_version\"",
+    "postpublish": "bash scripts/sync-plugin.sh \"chore: sync plugin to v$npm_package_version\" && bash scripts/sync-web-plugin.sh \"chore: sync web-plugin to v$npm_package_version\"",
     "deploy:check:google": "node scripts/check-google-drive-deploy.mjs",
     "build:excalidraw": "node scripts/build-excalidraw-editor.mjs",
     "prepublishOnly": "node scripts/check-npm-package.mjs"

package/plugin/commands/create-project.md

@@ -0,0 +1,23 @@
+---
+description: Start a new project — or a reusable template — with proper search of knowledge, skills, and templates first
+argument-hint: <project name and what you want to do>
+---
+
+Spin up a project on the surface, or generalize one into a reusable template. Goal: $ARGUMENTS
+
+First ask: **a new project, or a reusable template?** (This command does both.)
+
+Search before creating (also satisfies the gates):
+1. `wiki(action="search")` for relevant knowledge. [G1]
+2. `skill(action="search")` for procedures that should be attached.
+3. `template(action="list")` for an existing template to fork. [G3 — also enforced on `project(action="create")`.]
+
+Then:
+- If a fitting template exists → `project(action="create", templateSlug=...)` to fork it; otherwise create fresh and define the layers.
+- `project(action="open")` the new project.
+- `frame(action="write")` a real brief at the earliest layer (goal, audience, constraints — 6-12 lines, not a placeholder).
+- `frame(action="anchor")` the brief so downstream work surfaces it.
+- Attach the relevant skills you found with `skill(action="attach")`.
+- `focus` the brief so the user watches it land.
+
+For a **template**: build the layer structure + anchored guidance, then note how to fork it next time. Don't speculatively fill downstream frames — wait for direction.

package/plugin/commands/create-skill.md

@@ -0,0 +1,18 @@
+---
+description: Capture a repeatable procedure as an org skill — with proper knowledge and prior-art search
+argument-hint: <what the procedure is for>
+---
+
+Turn a repeatable way of working into a Drafted skill so every future agent in the org follows it. Procedure: $ARGUMENTS
+
+Do the searches first (they also satisfy the gates):
+1. `wiki(action="search")` for relevant org knowledge the procedure should reference. [G1]
+2. `skill(action="search")` for prior art — an existing skill to improve instead of duplicating. [G2 — also enforced on `skill(action="add")`.] If a close match exists, prefer `/drafted:improve-skill`.
+
+Then define a PROPER procedure, not a vague note:
+- a clear trigger ("when to use this"),
+- ordered, concrete steps,
+- success criteria / what "done right" looks like,
+- written in the second person so any agent can follow it directly. Keep it sharp (~40 lines).
+
+Show the draft to the user with a proposed `name` (Title Case), one-line `description`, `tags` (3-5), and `triggerPatterns`. After approval, `skill(action="add")`. Confirm with the slug and note it will auto-surface on matching tasks.

package/plugin/commands/extract.md

@@ -0,0 +1,16 @@
+---
+description: Deposit what this session produced into the harness — knowledge, a skill, and/or a template
+argument-hint: <optional: what to capture>
+---
+
+Session-end deposit. Harvest what's durable from this conversation back into the harness so the next session starts smarter. Focus: $ARGUMENTS
+
+Review the session, then **present the user options for which store(s) to deposit into** — don't auto-decide. Offer any that apply:
+
+- **Knowledge → wiki** — durable facts, decisions, or findings worth keeping. Search first (`wiki(action="search")`) to avoid fragmenting, then `wiki(action="write")`.
+- **Procedure → skill** — a repeatable way of working that emerged. Follow `/drafted:create-skill`.
+- **Template → surface** — a reusable project structure that emerged. `template(action="create")` from the current project.
+
+Show the user the candidate deposits per store, let them pick which to keep, then write the chosen ones with their approval. Confirm what landed where.
+
+One command, all three stores — because at session end the human shouldn't have to remember which store is which.

package/plugin/commands/improve-project-harness.md

@@ -0,0 +1,16 @@
+---
+description: Turn corrections you made in a project into enforced gates (anchors, attached skills, layer rules)
+argument-hint: <optional: the correction to enforce>
+---
+
+When the user had to correct the work in this project, codify the correction so future work is compelled to comply. This is the nurture → enforce bridge. Correction: $ARGUMENTS
+
+1. Identify the recurring correction(s) or standing rule from this session.
+2. Choose the right Drafted-side gate per correction (each counts toward the project's context budget):
+   - **Project anchor** — a brief, constraint, or style guide that must be in context project-wide: `frame(action="write")` it, then `frame(action="anchor")`. [G5]
+   - **Attached skill** — a procedure that must be loaded before work: `/drafted:create-skill` (or `skill(action="search")` for an existing one), then `skill(action="attach")`. [G4]
+   - **Layer rule** — a standing instruction for one stage: set that layer's rules via `project(action="update", layers=...)`. [G6]
+3. Propose which mechanism for each correction, confirm with the user, then apply.
+4. Confirm what is now enforced — the next session in this project will be gated on it automatically.
+
+Keep within the project's context budget — if a deposit would exceed it, tighten existing gates instead of piling on.

package/plugin/commands/improve-skill.md

@@ -0,0 +1,14 @@
+---
+description: Fix a skill you noticed is inefficient, wrong, or missing a step
+argument-hint: <which skill, and what's off>
+---
+
+Improve an existing org skill when it underperformed in practice. Skill / issue: $ARGUMENTS
+
+1. `skill(action="search")` then `skill(action="load")` the skill in question — read it fully.
+2. Pinpoint the inefficiency: a missing step, a wrong instruction, an ambiguous trigger, or a step that wastes effort.
+3. Propose the specific edit to the user — show before/after of the changed steps.
+4. After approval, `skill(action="update")` (the version bumps automatically).
+5. Confirm what changed so the next agent benefits.
+
+Skills are the org's stable processes — every fix compounds across everyone who uses them.

package/plugin/commands/improve-wiki.md

@@ -0,0 +1,14 @@
+---
+description: Fix the wiki — reconcile stale, wrong, fragmented, or contradictory knowledge
+argument-hint: <what's wrong, or the topic to clean up>
+---
+
+Improve the org wiki when knowledge has drifted. Issue/topic: $ARGUMENTS
+
+1. `wiki(action="search")` (3-5 paraphrased queries) and `wiki(action="read")` the affected pages — don't trust titles, open them.
+2. Diagnose: duplicate pages, a stale fact, a contradiction, or knowledge fragmented across pages.
+3. Propose the fix to the user: consolidate duplicates, correct the fact, reconcile the contradiction, or re-link fragments.
+4. Apply with `wiki(action="edit")` (hashline) or `wiki(action="mv")` (which rewrites inbound links). Check `wiki(action="links")` before moving or deleting.
+5. `wiki(action="log")` what changed.
+
+Leave the wiki more coherent than you found it — fewer, sharper, better-linked pages.

package/plugin/commands/ingest.md

@@ -0,0 +1,20 @@
+---
+description: Bring knowledge into the wiki — from a research output, existing documents, or by interrogating you
+argument-hint: <optional: what to ingest, or a source>
+---
+
+Feed durable knowledge into the org wiki. Source/intent: $ARGUMENTS
+
+First decide WHAT to ingest. If it's obvious from the conversation (a research run just finished, or the user named a source), use that. Otherwise ask which of these three modes fits:
+
+1. **A research producible** — the output of a research run (a provider-native `/deep-research` or similar). Structure it into wiki pages.
+2. **Existing documents** — the user points at local / remote / connected folders. Scour them (spawn sub-agents if there are many) for relevant material, shortlist, confirm, then ingest the right ones. Folder scour needs file access (desktop / Cowork); on web, use connected sources.
+3. **Interrogate the user** (grill-me) — when the knowledge is in their head. Interview relentlessly, walking ONE branch of the decision tree at a time and proposing your recommended answer at each step, until you reach shared understanding. Then structure what you captured.
+
+Then deposit:
+- `wiki(action="search")` first (3-5 paraphrased queries) so you don't fragment existing pages.
+- Propose the page set to the user before writing.
+- Write with `wiki(action="write")`, or `wiki(action="source-register")` + `wiki(action="bulk-write")` for a batch. Cross-link related pages.
+- `wiki(action="log")` a one-line entry for the ingest.
+
+The wiki is the org's durable knowledge — write for the next agent and teammate, not just this session.

package/plugin/commands/onboard-drafted.md

@@ -0,0 +1,17 @@
+---
+description: First-run setup — orient to Drafted and bootstrap the harness (wiki, skills, first project)
+argument-hint: <optional: what you want to start working on>
+---
+
+Onboard the user to Drafted — a producibles harness that compounds across three primitives: knowledge (the wiki), procedures (skills), and the project surface. Goal/context: $ARGUMENTS
+
+This is the over-arching prime command: orient, then seed all three stores so every later session starts smart.
+
+1. **Orient** — in 3-4 lines explain the loop: you *prime* from the harness (the system makes you search the wiki, and auto-loads the project's attached skills, anchors, and layer rules before you work), you *build*, then you *compound* (deposit what you learned). The more it's used, the less searching and the more stable the work.
+2. **Confirm the org** — call `get_org`. Confirm the active organization is the one to build the harness in. If unsure, ask.
+3. **Seed knowledge** — run the `/drafted:ingest` flow: help the user point at existing business materials (folders, docs, past research) or interrogate them for tacit knowledge, and land durable pages in the wiki.
+4. **Seed procedures** — from those materials and the conversation, surface 1-3 candidate SOPs. For the most valuable, run the `/drafted:create-skill` flow.
+5. **Seed the surface** — run the `/drafted:create-project` flow for the user's immediate piece of work (or a reusable template).
+6. Close by showing what now exists (wiki pages, skills, project) and restate the one-line loop: prime → build → compound.
+
+Keep it guided and conversational — one step at a time, confirming before each deposit. Don't dump everything at once.

package/plugin/skills/drafted/SKILL.md

@@ -0,0 +1,84 @@
+---
+name: drafted
+description: Use the Drafted producibles harness — a compounding workspace that uplifts any AI across three primitives: knowledge (the org wiki), procedures (skills), and the project surface (frames on a shared real-time canvas). Prime from the harness before working, build durable artifacts as frames instead of burying output in chat, and deposit what you learned back so the next session starts smarter. When Google Drive is connected, prefer Google Workspace frames for docs, sheets, and slides.
+---
+
+# Drafted — a producibles harness that compounds
+
+Drafted makes any AI more effective by giving it a memory and a workspace that get better with use. It has three primitives that layer:
+
+- **Knowledge — the org wiki.** Durable facts, decisions, conventions. *More knowledge = less searching.*
+- **Procedures — skills.** Reusable SOPs the org has encoded. *Better skills = more stable process.*
+- **Surface — projects.** Reviewable work as frames on a shared zoomable canvas the user watches live at `https://drafted.live`. *Reusable projects + anchors = velocity with accuracy.*
+
+The point is the **compounding loop**: you don't produce in a vacuum, you draw on what the org already knows and leave it richer each pass.
+
+## The loop — prime → build → compound
+
+- **Prime (session start).** Pull accumulated value in. The system *enforces* this: you must search the wiki before working, and a project's attached skills, anchored frames, and layer rules are auto-loaded when you open it. Don't fight the gates — they make you start smart.
+- **Build (the work).** Produce artifacts as frames on the surface.
+- **Compound (session end / when you notice something).** Deposit learning back: capture knowledge, distill or fix a skill, harden the project. This is *your* responsibility — the system can't force it, so do it.
+
+## Mental model
+
+```
+Organization
+└── Project (a bounded piece of work, e.g. "Q4 strategy memo")
+    └── Layer (a stage of thinking, e.g. research → drafts → final)
+        └── Lane (a group of related frames, e.g. one competitor per lane)
+            └── Frame (an HTML / markdown / image file)
+```
+
+**Layers are stages** — they depend on the project's template. `project(action="create")` returns the active layers; always check rather than assume. **Frames have addresses** like `/layer/lane/filename`; the canvas auto-arranges them by layer (vertical) and lane (horizontal).
+
+## The gates you'll encounter (and how to satisfy them)
+
+These reset every session. A gate that blocks you tells you exactly what to call next — do it, don't work around it.
+
+- **G1 — wiki search before work.** Before you read or edit anything, `wiki(action="search")` for relevant org knowledge.
+- **G2 — prior-art before a new skill.** `skill(action="add")` requires a `skill(action="search")` first.
+- **G3 — prior-art before a new project.** `project(action="create")` requires wiki + skill + `template(action="list")` searches first.
+- **G4 — attached skills** are auto-injected when you open a project. Follow them — they're how the org does this work.
+- **G5 — the project's anchored frames** are auto-injected on open. They are required reading (briefs, constraints, style guides).
+- **G6 — a layer's rules** are surfaced when you work in that layer. Honor them.
+
+## The commands (when to reach for each)
+
+These bookend the loop. Prime/feed at the start, deposit at the end.
+
+- `/drafted:onboard-drafted` — first run: orient + bootstrap the harness (seed wiki, starter skills, first project).
+- `/drafted:ingest` — bring knowledge into the wiki (a research output, existing documents, or by interrogating the user).
+- `/drafted:create-skill` — capture a repeatable procedure (with knowledge + prior-art search).
+- `/drafted:create-project` — start a project or a reusable template (with knowledge/skill/template search).
+- `/drafted:improve-wiki` — fix stale / wrong / fragmented knowledge.
+- `/drafted:improve-skill` — fix a skill that underperformed.
+- `/drafted:improve-project-harness` — turn corrections into enforced gates (anchors / attached skills / layer rules).
+- `/drafted:extract` — session-end: deposit knowledge, a skill, and/or a template (the user picks which).
+
+## Tool surface (action-based)
+
+`project(list|open|create|update|move)` · `frame(read|write|edit|anchor|mv|search|…)` · `ls` · `skill(search|load|list|add|update|attach|…)` · `wiki(search|read|write|edit|mv|links|log|…)` · `template(list|create|fork|…)` · `focus` · `get_org` · `asset` · `layer`.
+
+## Sign in
+
+If a tool returns an auth error: on a desktop/CLI agent run the `auth(action="login")` tool (it prints a one-time URL; the user opens it). On the web/Cowork connector, authorization happens via the connector's OAuth — ask the user to re-authorize the Drafted connector in their settings, then retry.
+
+## Working on the surface
+
+- **Always `project(action="open")` first.** Every read/write operates on the active project. Use `project(action="list")` to find one. Every response includes a `project` field — verify it matches your intent before writing.
+- **Default to the surface for substantive artifacts.** When asked to draft, write, plan, analyze, compare, design, document, summarize, report, spec, model, or make a deck/table, create or update frames instead of leaving the durable result only in chat. One visible frame per artifact or section.
+- **Prefer Google Workspace when Drive is connected.** Call `get_org`; if it reports `googleDrive.connected: true`, use `frame(action="write", googleType="google-doc"|"google-sheet"|"google-slide", …)` for docs, sheets, and decks; populate immediately with the native write actions.
+- **Read before editing.** `frame(action="edit")` uses hashline addressing — every line in a `frame(action="read")` response gets a 4-char hash; pass it to edit for surgical changes.
+- **`focus` after writing** so the user watches your work land on their surface.
+
+## Quality conventions
+
+- **Match format to layer intent.** Research/strategy/copy are usually markdown; visual work (wireframes, designs, dashboards) is HTML.
+- **Respect the template's conventions.** Read a `design-system` layer before `/designs/`; read an `audience` layer before `/copy/`.
+- **Wireframes are low-fidelity** (grayscale, placeholders); reserve color and real content for the designs/final layer.
+- **Choose dimensions to fit content** — `autoSize: true` for HTML, or explicit `width`/`height`.
+- **Don't re-read unchanged frames** you already have this conversation.
+
+## Surface URL recognition
+
+Any URL containing `/f/{uuid}` is a Drafted frame link. Use `frame(action="read", path=URL)` to get its content and `focus(target=URL)` to pan the canvas to it. Never `WebFetch` Drafted URLs — the MCP tools authenticate properly.