@eventmodelers/cli 0.0.12 → 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.12",
+  "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
 }
 ```
 

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

@@ -21,7 +21,7 @@ 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, e.g. `"A2"` | none |
+| `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`.
@@ -30,6 +30,8 @@ Use `BOARD_ID` and `BASE_URL` from the `connect` skill. If a `boardId` argument
 
 **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