@eltonssouza/development-utility-kit 0.10.1 → 0.11.0

package/README.md

@@ -14,6 +14,15 @@
 
 CLI binary: `duk` · Node `>=18` · License: MIT
 
+**Install as a Claude Code plugin** (recommended — global, works in every project):
+
+```
+/plugin marketplace add eltonssouza/development-utility-kit
+/plugin install development-utility-kit
+```
+
+**Or inject per-project via npx** (writes `.claude/` + `CLAUDE.md` into the current project):
+
 ```bash
 npx @eltonssouza/development-utility-kit install
 ```
@@ -138,6 +147,20 @@ Polling every 5s. Click a project → **Processes panel** shows recent orchestra
 
 ## Quickstart
 
+### Two ways to install
+
+| | **Plugin** (recommended) | **npx injection** |
+|---|---|---|
+| Command | `/plugin marketplace add eltonssouza/development-utility-kit` then `/plugin install development-utility-kit` | `npx @eltonssouza/development-utility-kit install` |
+| Scope | Global — every project, every session | Per-project (writes `.claude/` + `CLAUDE.md`) |
+| Lands in | `~/.claude/plugins/` | the project directory |
+| Updates | `/plugin update` (or auto on version bump) | re-run `npx … install` |
+| Per-project stack | declare in a small `CLAUDE.md` `## Project Identity` (or let agents auto-detect) | written into the injected `CLAUDE.md` |
+
+Both deliver the same 19 skills + 21 agents + stack packs. The plugin keeps them global and out of your repo; the npx path injects them into the project (and self-installs `duk` globally). Skills, agents and the flow-governance hook load identically either way.
+
+> **Note on `## Project Identity`:** Claude Code plugins cannot ship a project `CLAUDE.md` (plugin context arrives via skills/agents/hooks, not CLAUDE.md). When you install via the plugin, declare your stack in a short per-project `CLAUDE.md` block so `stack-resolver` picks the right pack — or rely on `detect-stack.js` auto-detection. The npx path still writes the full `CLAUDE.md` for you.
+
 ### Brand-new project
 
 ```bash

package/bin/cli.js

@@ -304,12 +304,27 @@ function adoptProject(opts) {
   const destClaude = path.join(subDir, '.claude');
   const destClaudeMd = path.join(subDir, 'CLAUDE.md');
 
+  // Drive-root / system-directory guard.
+  // Prevents EPERM crashes when the user accidentally runs from C:\, D:\, etc.
+  const targetResolved = path.resolve(subDir);
+  const parsed = path.parse(targetResolved);
+  const isDriveRoot = parsed.root === targetResolved + path.sep || parsed.root === targetResolved;
+  const WIN_SYSTEM_PREFIXES = ['\\Windows', '\\Program Files', '\\Program Files (x86)', '\\Users\\Default'];
+  const isSystemDir = process.platform === 'win32' &&
+    WIN_SYSTEM_PREFIXES.some((p) => targetResolved.toLowerCase().startsWith((parsed.root + p.slice(1)).toLowerCase()));
+  if (isDriveRoot || isSystemDir) {
+    process.stderr.write('Error: unsafe install target — cannot install into a drive root or system directory.\n');
+    process.stderr.write(`Target: ${targetResolved}\n`);
+    process.stderr.write('cd into your project folder first, then run:\n');
+    process.stderr.write('  npx @eltonssouza/development-utility-kit install\n');
+    process.exit(1);
+  }
+
   // Item 21 — self-destruction guard.
   // If install runs inside the harness source tree, the backup step would
   // `mv srcClaude → srcClaude.bak`, removing the very source about to be
   // copied. Abort early with a clear message before any destructive op.
   const pkgRootResolved = path.resolve(pkgRoot);
-  const targetResolved = path.resolve(subDir);
   if (targetResolved === pkgRootResolved) {
     process.stderr.write('Error: cannot install harness into its own source tree.\n');
     process.stderr.write(`Target directory equals the harness package root:\n  ${pkgRootResolved}\n`);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@eltonssouza/development-utility-kit",
-  "version": "0.10.1",
+  "version": "0.11.0",
   "description": "npx installer for the development-utility-kit harness",
   "bin": {
     "duk": "bin/cli.js"