lavish-axi 0.1.16 → 0.1.17

package/README.md

@@ -35,7 +35,7 @@ Lavish Editor opens agent-generated HTML files in a local browser, lets you pinp
 
 - **Local only** - Work with your local HTML artifacts with a local CLI. Zero cloud dependency.
 - **Human-AI collaboration** - Annotate elements, selected text ranges, and send messages to the agent without leaving Lavish Editor.
-- **Battery included** - Lavish Editor teaches your agent good visualization for common use cases such as technial plans, design explorations and more out of the box.
+- **Battery included** - Lavish Editor teaches your agent good visualization for common use cases such as product or technical plans, design explorations and more out of the box.
 
 Lavish Editor is an [AXI](https://axi.md), which means -
 
@@ -48,7 +48,7 @@ Lavish Editor is an [AXI](https://axi.md), which means -
 Just tell your agent:
 
 ```sh
-Use `npx lavish-axi` to write a technical plan for what we discussed.
+Use `npx lavish-axi` to write a product or technical plan for what we discussed.
 ```
 
 ## Install

package/dist/cli.mjs

@@ -577,31 +577,28 @@ var PLAYBOOKS = [
   },
   {
     id: "plan",
-    use_when: "Explain a technical plan before implementation",
+    use_when: "Explain a product or technical plan before implementation",
     choose: [
       "Use this when the user needs to inspect a feature approach before implementation begins.",
-      "Use it when state, APIs, files, tests, or edge cases are numerous enough to deserve a visual map.",
-      "Use a lighter comparison or diagram playbook when the plan is only a small design choice."
+      "Use it when the user explicitly asked for a PRD, technical design, implementation plan or proposal.",
+      "Use a lighter comparison or diagram playbook when the plan is only a single small design choice."
     ],
     structure: [
-      "Start with the problem, the desired behavior, and what is out of scope.",
-      "Show affected state, commands, functions, files, and user-visible behavior.",
-      "Include edge cases and tests before implementation notes so risk is visible early."
+      "Start with the goal, the current state, and desired behavior.",
+      "Then describe a proposed approach, focusing on high level decisions.",
+      "At the end, list any risks you see, and open questions you have, and follow the 'comparison' playbook to provide options for the user to choose from."
     ],
     design_rules: [
       "Verify each claim against the codebase before presenting it as fact.",
-      "Keep code snippets focused on the pattern or seam, not full-file dumps.",
-      "Make test requirements concrete enough to drive TDD."
+      "When discussing frontend experiences, prefer visually mocking the experience under a consistent design system as the real product over describing it with text.",
+      "The plan needs to be self-contained enough that another developer can read it and fully implement the proposal."
     ],
     pitfalls: [
-      "Do not invent extension points or APIs that are not present in the repo.",
-      "Do not turn a plan into a long prose essay when state and file maps would be clearer.",
+      "Do not leave resolved open questions in the artifact. Update existing content to reflect the decision and remove the open question.",
+      "Do not only focus on ambiguous decisions and omit the actual proposal.",
       "Do not omit failure modes, migration concerns, or backwards compatibility questions."
     ],
-    lavish_notes: [
-      "A Lavish plan should make uncertainties easy to annotate before code exists.",
-      "Use controls for scope choices so the user can queue a precise implementation direction."
-    ]
+    lavish_notes: ["A Lavish plan should make a plan and its uncertainties easy to annotate before code exists."]
   },
   {
     id: "diff",
@@ -1837,7 +1834,7 @@ function normalizePagePath(path5) {
 // src/cli.js
 var COMMANDS = /* @__PURE__ */ new Set(["open", "poll", "end", "server", "playbook", "design", "setup"]);
 var DESCRIPTION = "Lavish Editor helps agents turn rich HTML artifacts into collaborative human review surfaces. Whenever you are about to give user a complex response that will be easier to understand via a rich / interactive page, consider using Lavish Editor. First generate an interactive HTML artifact according to user request, then run `lavish-axi <html-file>` so the user can visually review it, annotate elements or selected text, queue prompts, and send feedback back through `lavish-axi poll`.";
-var VERSION = "0.1.16";
+var VERSION = "0.1.17";
 async function run(argv) {
   await ensureStateDir();
   const normalizedArgv = normalizeArgv(argv);
@@ -1932,7 +1929,7 @@ function createHomeOutput({ bin, sessions, includeSessions = true }) {
       "Run `lavish-axi end <html-file>` to end a session",
       "Run `lavish-axi playbook <playbook_id>` for focused artifact guidance",
       DESIGN_SYSTEM_HINT,
-      "Use lavish-axi when the user asks for a visual artifact, HTML explainer, interactive prototype, review surface, technical plan, comparison, report, or browser-based feedback loop"
+      "Use lavish-axi when the user asks for a visual artifact, HTML explainer, interactive prototype, review surface, product or technical plan, comparison, report, or browser-based feedback loop"
     ]
   };
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "lavish-axi",
-  "version": "0.1.16",
+  "version": "0.1.17",
   "packageManager": "pnpm@11.1.1",
   "description": "HTML is the new markdown. Lavish is the new editor for your HTML artifacts.",
   "type": "module",