@lahat-group/cli 1.0.0

package/package.json

@@ -0,0 +1,32 @@
+{
+  "name": "@lahat-group/cli",
+  "version": "1.0.0",
+  "description": "CLI + Claude Skill to build, validate, price, and save wardrobe designs.",
+  "license": "UNLICENSED",
+  "type": "module",
+  "bin": { "wardrobe": "dist/index.js" },
+  "files": ["dist", "skill"],
+  "engines": { "node": ">=18" },
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/shahar-abra/wardrobe-configurator.git",
+    "directory": "tools/cli"
+  },
+  "publishConfig": { "access": "public" },
+  "scripts": {
+    "build": "tsup",
+    "prepublishOnly": "npm run build",
+    "dev": "tsx src/index.ts",
+    "typecheck": "tsc --noEmit",
+    "test": "vitest run"
+  },
+  "devDependencies": {
+    "@wardrobe/shared": "*",
+    "commander": "^12.0.0",
+    "ky": "^1.14.3",
+    "tsup": "^8.0.0",
+    "tsx": "^4.0.0",
+    "typescript": "^5.5.0",
+    "vitest": "^3.1.1"
+  }
+}

package/skill/SKILL.md

@@ -0,0 +1,80 @@
+---
+name: wardrobe-configurator
+description: Use when the user wants to build, configure, validate, price, or order a wardrobe/closet design from the terminal — phrases like "configure a wardrobe", "price a design", "build a closet layout", "validate my wardrobe config". Drives the `wardrobe` CLI (HTTP client over the configurator API); a WardrobeConfig JSON file on disk is the unit of work.
+---
+
+# Wardrobe Configurator CLI
+
+Build, validate, price, save, and stage wardrobe designs from the terminal via the
+`wardrobe` CLI. A **`WardrobeConfig` JSON file on disk is the unit of work**. The
+agent loop is: **init → edit → validate → price → plan → apply**.
+
+## Prerequisites
+
+- Install the CLI: `npm install -g @lahat-group/cli` (or run ad-hoc via `npx @lahat-group/cli <verb>`).
+  It ships as a self-contained binary — no build step, no extra dependencies.
+- **Authenticate once**: `wardrobe login` runs the OAuth device flow — it prints a
+  user code, opens `/activate` in the browser, and stores a scoped agent key at
+  `~/.config/wardrobe/config.json` (chmod 600). Confirm with `wardrobe whoami`.
+- The CLI targets the **production** API by default. Set `WARDROBE_API_URL` to override
+  (e.g. `http://localhost:3001/api` for a local dev server).
+- Every verb accepts `--json` for machine-readable output. Read those; don't scrape prose.
+
+## The loop
+
+1. **init** — `wardrobe init [--width <cm>] [--height <cm>] [--depth <cm>] > wardrobe.json`
+   emits a fresh, valid `WardrobeConfig` (full-width, split into optimal columns).
+2. **edit** — modify `wardrobe.json` directly (see shape below).
+3. **validate** — `wardrobe validate wardrobe.json` (or `-` for stdin). Runs the
+   **shared constraint pipeline fully offline** — byte-identical to the web app.
+   Exit 0 = valid; exit 1 + structured errors otherwise. Do this after every edit.
+4. **price** — `wardrobe price wardrobe.json` → authoritative total in **NIS** from
+   the API's unified area×rate engine.
+5. **plan** — `wardrobe plan wardrobe.json` → dry-run price **plus a BOM preview**.
+   Mutates nothing. Use this to preview before applying.
+6. **apply** — `wardrobe apply wardrobe.json --project <id> [--name <name>]` → saves
+   the config as a design and prints its `{id}`. **`--project` is required.**
+
+`wardrobe describe <idOrFile>` gives a human-readable summary of a local file/`-`
+or a saved design id.
+
+## Listing context
+
+- `wardrobe projects list` — projects you can access (needed for `--project`).
+- `wardrobe designs list --project <id>` — designs saved in a project.
+
+## WardrobeConfig shape (top-level)
+
+```jsonc
+{
+  "roomPosition": "freestanding",     // placement
+  "width": 100, "height": 240, "depth": 60,   // cm
+  "material": "<externalMaterialId>",
+  "materialInternal": "<internalMaterialId>",
+  "materialExternal": "<externalMaterialId>",
+  "columns": [                        // one or more columns, widths sum to `width`
+    { "id": "<nanoid>", "width": 100, "modules": [ /* rails, shelves, drawers */ ] }
+  ],
+  "ruleVersion": "<current rule version>"
+}
+```
+
+Prefer generating the skeleton with `wardrobe init` rather than hand-writing it —
+`init` fills materials, `ruleVersion`, and a valid column layout for you. Column
+`id`s are `nanoid()` and are not stable across rebuilds.
+
+## Guardrails — orders require a human
+
+- **The CLI cannot place orders.** Ordering is intentionally not an agent verb: the
+  agent key carries only `designs:read`, `designs:write`, `price:read` — **no order or
+  admin scope**. Don't attempt to order, or to run admin/catalog operations.
+- To turn a saved design into an order, direct the **human** to the web app: they
+  open the project, review the design, and complete the **verify-details** flow —
+  which computes the final price, freezes the PDF, and advances the order. Only a
+  human does this. Your job ends at `apply` (a saved design) plus a clear summary.
+
+## Error handling
+
+Zod validation errors from the API return `{ error, issues, fix_hint }`. Read
+`fix_hint` — it names the offending field/path and how to correct it. Re-run
+`validate` locally before retrying a networked verb.