@eventmodelers/cli 0.0.11 → 0.0.13

package/cli.js

@@ -670,7 +670,7 @@ async function configureCredentials({ config, configPath, targetDir, requiredFie
       { label: 'Enter values one by one', value: 'manual' },
       { label: 'Get instructions for configuring later', value: 'instructions' },
       { label: 'Skip for now', value: 'skip' },
-    ], 1);
+    ], 0);
 
     if (choice === 'paste') {
       console.log('\n  Copy your credentials from https://app.eventmodelers.ai/account,');

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@eventmodelers/cli",
-  "version": "0.0.11",
+  "version": "0.0.13",
   "description": "Eventmodelers CLI — real-time Claude agent + skills for Claude Code, for any stack (Node, Supabase, Axon, Cratis, or modeling-only)",
   "type": "module",
   "bin": {

package/shared/skills/learn-eventmodelers-api/SKILL.md

@@ -198,6 +198,8 @@ All node endpoints require header: `x-user-id`
 ### POST `/api/org/:orgId/boards/:boardId/nodes/events`
 Submit node change events.
 
+Any `node:created` event carrying a `chapterId` plus `cellId`/`cellName` (i.e. placing a node on a timeline) also triggers a best-effort, fire-and-forget auto-connect to type-compatible neighbors — same rules as the auto-connect endpoint below. Failures there never fail this call.
+
 **Request body**: `NodeChangeEvent[]`
 
 ```typescript
@@ -237,7 +239,7 @@ interface NodeChangeEvent {
     targetHandle?: string
   }>
   chapterId?: string   // for cell placement
-  cellName?: string    // spreadsheet-style e.g. "B2"
+  cellName?: string    // spreadsheet-style, always <letter(s)><number> e.g. "B2", "AA10" — pass through as-is, never decompose or interpret it
 }
 ```
 
@@ -260,6 +262,17 @@ Get a single node.
 
 ---
 
+### POST `/api/org/:orgId/boards/:boardId/nodes/:nodeId/auto-connect`
+Auto-connect a node to its timeline neighbors — mirrors the frontend's auto-connect-on-place behavior. Looks only at the node's own timeline column and the previous column (never ahead), and creates `edge:added` events to every type-compatible neighbor found there, using the same pairing rules as connections created via node events (COMMAND→EVENT, SCREEN→COMMAND, EVENT→READMODEL, READMODEL→SCREEN, READMODEL→AUTOMATION, AUTOMATION→COMMAND). A COMMAND is not wired to the previous column's SCREEN if its own column already has one.
+
+Incompatible or already-connected neighbors are reported in `skipped`, not an error. Returns an empty result for nodes not placed on any timeline, or not a connectable element type (e.g. SCENARIO/spec nodes are never auto-connected).
+
+**Response**:
+- `200` — `{ connected: [{edgeId, source, target, created}], skipped: [{nodeId, reason}] }`
+- `404` — node not found
+
+---
+
 ## 4. Images
 
 **File**: `src/slices/change/api-images/routes.ts`
@@ -614,6 +627,7 @@ All events support optional metadata: `user_id`, `correlation_id`, `causation_id
 | `src/slices/change/api-boards/routes.ts` | Board CRUD + event persistence |
 | `src/slices/change/api-chapters/routes.ts` | Chapters, columns, lanes, cell drops |
 | `src/slices/change/api-nodes/routes.ts` | Node event sourcing |
+| `src/slices/extensions/supabase/nodes/AutoConnectNode.ts` | Auto-connect logic (timeline neighbor wiring) |
 | `src/slices/change/api-images/routes.ts` | Image upload + sketch rendering |
 | `src/slices/change/api-.slices/routes.ts` | Slice creation + slice definitions (SLICE_BORDER) |
 | `src/slices/extensions/supabase/slices/CreateSliceDefinition.ts` | Slice definition (SLICE_BORDER) creation logic |

package/stacks/modeling-kit/templates/.claude/skills/place-element/SKILL.md

@@ -21,12 +21,17 @@ From `$ARGUMENTS`, extract:
 | `boardId` | a board UUID | from `connect` skill (`BOARD_ID`) |
 | `timelineId` | the chapter/timeline UUID | auto-detect (see Step 2) |
 | `position` | column index (0-based number), `"after <title>"`, or omitted | append at end |
+| `cellName` | spreadsheet-style cell reference given directly in the prompt — always `<letter(s)><number>`, e.g. `"A2"`, `"AA10"` | none |
 | `baseUrl` | explicit URL override | from `connect` skill (`BASE_URL`) |
 
 Normalise `elementType` to uppercase: `event` → `EVENT`, `command` → `COMMAND`, `readmodel` → `READMODEL`, `screen` → `SCREEN`, `automation` → `AUTOMATION`.
 
 Use `BOARD_ID` and `BASE_URL` from the `connect` skill. If a `boardId` argument is explicitly passed, it overrides `BOARD_ID`.
 
+**Fast path — spreadsheet-style cell reference given directly (e.g. "place a COMMAND in A2"):** don't try to interpret what "A2" means yourself. The `node:created` event accepts a `cellName` field (see `learn-eventmodelers-api`) and the backend resolves it to the actual row/column — the same shortcut `html-screen` already uses. Skip Steps 3–6 entirely: resolve only `timelineId` (Step 2, needed for `chapterId`), then go straight to Step 7 and pass `cellName` instead of `cellId` on the `node:created` payload. Do not fetch columns, do not compute a row/column index, and do not construct `cellId` yourself for this case.
+
+**This still applies when several cell references are given together for one slice** (e.g. "put the screen in C1, the command in C2, the event in C3"). Do not reason about the grid at all — not which column "C" is, not whether C1/C2/C3 land in the same column, not which row is which. That is exactly the interpretation this fast path exists to skip. Treat each cell reference as an opaque string tied to its own element: call Step 7 once per element, passing that element's `cellName` untouched. The backend resolves each independently; the placements only need to be internally consistent with each other insofar as the prompt already told you so — you never need to understand *why*.
+
 ---
 
 ## Step 2 — Resolve the timeline
@@ -203,7 +208,9 @@ If no matching row is found, stop and report the error — the timeline may be m
 
 > **SCREEN nodes always require a sketch.** The server auto-generates a title-only placeholder when a SCREEN is created without one, but it will look empty. Always follow up a SCREEN node creation with a call to `POST /images/:nodeId/sketch` (or use `POST /image-nodes/:nodeId/sketch` to create and render in one call — see `learn-eventmodelers-api` for the sketch format).
 
-Include `x-token`, `x-board-id`, and `x-user-id: agent` on every call to `/nodes/events`:
+Include `x-token`, `x-board-id`, and `x-user-id: agent` on every call to `/nodes/events`.
+
+**Normal path** (position/lane resolved manually in Steps 3–6) — use `cellId`:
 
 ```bash
 curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes/events" \
@@ -226,9 +233,32 @@ curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes/events" \
   }]'
 ```
 
+**Fast path** (`cellName` given directly, e.g. `"A2"` — see the Step 1 shortcut) — pass `cellName` instead of `cellId` and let the backend resolve it; nothing else in the payload changes:
+
+```bash
+curl -s -X POST "$BASE_URL/api/org/$ORG_ID/boards/$BOARD_ID/nodes/events" \
+  -H "x-token: $TOKEN" \
+  -H "x-board-id: $BOARD_ID" \
+  -H "x-user-id: agent" \
+  -H "Content-Type: application/json" \
+  -d '[{
+    "eventType": "node:created",
+    "nodeId": "<node-uuid>",
+    "boardId": "<BOARD_ID>",
+    "timestamp": <Date.now()>,
+    "chapterId": "<TIMELINE_ID>",
+    "cellName": "<CELL_NAME>",
+    "meta": {
+      "type": "<ELEMENT_TYPE>",
+      "title": "<title>"
+    },
+    "node": { "data": { "title": "<title>" } }
+  }]'
+```
+
 Response: `{ "hashes": { "<event-uuid>": "<hash>" } }`
 
-> **`node:created` with `cellId` IS the placement** — do NOT also call the `drop` endpoint afterwards. The `drop` endpoint adds a second cell reference without removing the first, causing the node to appear in two columns simultaneously. Use `node:created + cellId` for all initial placements.
+> **`node:created` with `cellId`/`cellName` IS the placement** — do NOT also call the `drop` endpoint afterwards. The `drop` endpoint adds a second cell reference without removing the first, causing the node to appear in two columns simultaneously. Use `node:created` with `cellId` or `cellName` for all initial placements.
 
 ---