@eventmodelers/cli 1.0.4 → 1.0.6

package/README.md

@@ -101,6 +101,7 @@ Which skills install depends on the chosen stack — see `stacks/<name>/template
 
 ```bash
 npx @eventmodelers/cli init --stack <name>          # scaffold a stack + install + configure (alias: install)
+npx @eventmodelers/cli re-init                      # refresh an already-installed kit's scripts/skills only — never touches the root scaffold
 npx @eventmodelers/cli run                          # start the agent loop (ralph-claude.js) from the installed kit dir
 npx @eventmodelers/cli run --ollama                 # same, via local Ollama (ralph-ollama.js)
 npx @eventmodelers/cli run --bash                   # bash-only loop, no realtime (ralph.sh)
@@ -306,6 +307,19 @@ npx @eventmodelers/cli listen --port 4000            # same, on a different port
 
 `listen` is a dispatcher for `<kit-dir>/code-export.mjs` — a local HTTP server (port 3001 by default) that the eventmodelers board UI posts slice/screen data to, which then gets written under `<kit-dir>/.slices/`. Unlike `fetch`, it does receive screen images, since the board UI pushes them directly.
 
+### Re-init — refresh scripts/skills without touching your app
+
+```bash
+npx @eventmodelers/cli re-init                      # refresh the installed build kit (.build-kit/) + its skills
+npx @eventmodelers/cli re-init --modeling            # refresh the modeling kit (.agent-modeling-kit/) + its skills
+```
+
+`re-init` re-runs `init` against whichever stack `install-manifest.json` says was installed (no need to pass `--stack` again), but skips step 2 of `init` entirely — the root project scaffold (`package.json`, `src/`, `server.ts`, `docker-compose.yml`, etc.) and the root `CLAUDE.md` router are never touched. Use it after upgrading the CLI to pick up fixes to `ralph.js`/`ralph.sh`/skills without re-scaffolding a project you've since built on top of.
+
+Credentials are left alone unless you pass `--force` — same rule `init` already follows when everything required is already configured. `--global` defaults to however skills were originally installed; pass it explicitly to move them.
+
+If the kit dir predates install-manifest.json tracking, or was installed via `init --git <url>` (a community/custom stack, not one of the built-in `STACKS` keys), `re-init` can't tell what to re-copy and tells you to re-run the original `init` command by hand instead.
+
 ### Uninstall
 
 Every `init`/`init-modeling` run writes an install manifest into `<kit-dir>/.eventmodelers/install-manifest.json` recording exactly what it put down. `uninstall` reads that manifest back and removes only:

package/cli.js

@@ -754,6 +754,10 @@ async function installStack(stackKey, stackCfg, options = {}) {
     }
 
     // --- 2. Spread stack scaffold files into the project root ---
+    // Skipped entirely by `re-init` (options.skipRootScaffold) — that command only
+    // refreshes an already-scaffolded project's kit dir + skills, and must never
+    // re-touch root/ files the user has since built on top of, nor the root
+    // CLAUDE.md router below.
     const rootSrc = join(templatesSource, 'root');
     // root/CLAUDE.md is never copied to the project root directly (see step 3 below) —
     // built-in stacks no longer ship one at all, and an outdated community/--git stack
@@ -761,7 +765,7 @@ async function installStack(stackKey, stackCfg, options = {}) {
     // copy must never let it slip through to root and clobber the shared router there.
     const stackRootClaudeSrc = join(rootSrc, 'CLAUDE.md');
     const stackShipsOwnRootClaude = existsSync(stackRootClaudeSrc);
-    if (existsSync(rootSrc)) {
+    if (!options.skipRootScaffold && existsSync(rootSrc)) {
       console.log('📦 Installing project files...');
       // .gitignore is the one file every stack's root/ ships that can collide with
       // another already-installed kit's own .gitignore (e.g. modeling-kit + a build-kit
@@ -796,7 +800,7 @@ async function installStack(stackKey, stackCfg, options = {}) {
     // instead of silently guessing either way.
     const rootClaudeDest = join(targetDir, 'CLAUDE.md');
     const sharedRootClaude = join(__dirname, 'shared', 'root-claude', 'CLAUDE.md');
-    const routerContent = existsSync(sharedRootClaude) ? readFileSync(sharedRootClaude, 'utf-8') : null;
+    const routerContent = options.skipRootScaffold ? null : (existsSync(sharedRootClaude) ? readFileSync(sharedRootClaude, 'utf-8') : null);
     if (routerContent !== null) {
       if (!existsSync(rootClaudeDest)) {
         writeFileSync(rootClaudeDest, routerContent);
@@ -1620,6 +1624,49 @@ credentialFlags(program
     });
   });
 
+// Every kit config `re-init` can refresh, keyed the same way install-manifest.json's
+// `stack` field is — looked up after reading that manifest so re-init knows exactly
+// which templates to re-copy without the user having to pass --stack again.
+const REINITIABLE_STACKS = { ...STACKS, [MODELING_KIT.key]: MODELING_KIT, [BLANK_BUILD_KIT.key]: BLANK_BUILD_KIT };
+
+credentialFlags(program
+  .command('re-init')
+  .description('Refresh an already-installed kit from the current CLI version — re-copies skills and the kit dir (.build-kit or .agent-modeling-kit) so you pick up script/skill updates after upgrading. Unlike `init`, never touches the project root scaffold or the root CLAUDE.md router, and leaves existing credentials alone unless --force is passed.')
+  .option('--modeling', 'Refresh the modeling kit (.agent-modeling-kit) instead of a build kit')
+  .option('--global', 'Re-install skills into ~/.claude/skills/ instead of the project — defaults to however they were originally installed')
+  .option('-f, --force', 'Re-prompt for credentials even if a config already has everything required — overwrites the existing config.json'))
+  .action(async (opts, command) => {
+    const globalOpts = command.optsWithGlobals();
+    const targetDir = process.cwd();
+
+    const kitDirName = opts.modeling ? MODELING_KIT.kitDirName : STACKS.node.kitDirName;
+    const kitDir = join(targetDir, kitDirName);
+
+    if (!existsSync(kitDir)) {
+      console.error(`❌ No ${kitDirName}/ found in ${targetDir} — run \`init${opts.modeling ? ' --modeling' : ''}\` first.`);
+      process.exit(1);
+    }
+
+    const manifest = readJsonSafe(join(kitDir, '.eventmodelers', 'install-manifest.json'));
+    const stackKey = opts.modeling ? MODELING_KIT.key : manifest.stack;
+    const stackCfg = stackKey ? REINITIABLE_STACKS[stackKey] : null;
+
+    if (!stackCfg) {
+      console.error(`❌ Can't tell which stack ${relative(targetDir, kitDir)} was installed from (${manifest.stack ? `"${manifest.stack}" isn't one re-init recognizes — likely a --git community stack` : 'its install manifest predates this tracking, or is missing'}).`);
+      console.error('   Re-run the original `init --git <url> --stack <name>` command by hand instead.');
+      process.exit(1);
+    }
+
+    await installStack(stackKey, stackCfg, {
+      configPath: globalOpts.config,
+      print: globalOpts.print,
+      global: opts.global !== undefined ? opts.global : !!manifest.global,
+      force: opts.force,
+      credentialOverrides: credentialOverridesFromOpts(opts),
+      skipRootScaffold: true,
+    });
+  });
+
 program
   .command('init-mcp')
   .description('Register the eventmodelers MCP server in .claude/settings.json (and optionally another harness)')

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@eventmodelers/cli",
-  "version": "1.0.4",
+  "version": "1.0.6",
   "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/stacks/modeling-kit/templates/.claude/skills/html-screen/SKILL.md

@@ -66,6 +66,17 @@ Guidelines:
 - Don't add `<html>`/`<head>`/`<body>` tags to a page — every page is a body-only fragment. The canvas wraps each page in its own `<html><head>` (stylesheet + resize script) `<body>...</body></html>` at render time, so anything sent is placed inside that generated `<body>`.
 - Bulma CSS (0.9.4) is loaded by default in that `<head>` — classes like `title`, `button`, `is-primary`, `field`/`control`/`input` etc. all work out of the box, no need to write custom CSS for standard form/layout components. Note headings need a size modifier too, e.g. `class="title is-1"` — a bare `title` class alone is always 2rem regardless of the tag (`h1` vs `h2` etc.).
 
+### Marks — only when the user explicitly asks for one
+
+The canvas has a native "Marks" feature (outline highlight, optional blur-outside spotlight) for calling out part of a screen. **Do not add marks by default.** Only apply one of the two effects below when the request explicitly asks to highlight/mark/call out/circle/spotlight or blur/obscure part of the screen (e.g. "highlight the submit button", "blur everything except the email field"). An ordinary "design a screen" request gets no marks.
+
+Since this skill only has a `pages`/`backgroundColor` field to send (no separate marks API), reproduce the same visual language directly as inline CSS on the target element(s) — self-contained in the page HTML, same as any other styling in Step 3:
+
+- **Mark / highlight an area** — add to the target element's `style`: `outline:4px solid <color> !important;outline-offset:1px;`. Default color `#e74c3c` (red) unless the user names one; other options mirror the app's mark picker: `#1e293b` (dark slate), `#2ecc71` (green), `#3b82f6` (blue), `#f1c40f` (yellow), `#ffffff` (white).
+- **Blur outside / spotlight an area** — add `style="filter:blur(6px) !important;"` to every other top-level sibling/section on the page so only the called-out element stays sharp. Combine with the outline above if the user asked to both mark and blur.
+
+Apply these only to the specific element(s) the request describes — don't guess at additional areas to call out.
+
 ## Step 4 — Render the pages
 
 **Updating an existing node** (`nodeId` was given) — always sends the **complete** pages array, not just the changed/new entry: