lavish-axi 0.1.19 → 0.1.20

package/README.md

@@ -73,9 +73,13 @@ pnpm run build
 pnpm link
 ```
 
-## Set Up Agent Hooks (recommended)
+## Teach Your Agent About Lavish (recommended)
 
-Lavish does not install agent hooks automatically, which means your agent would not know to use it in a fresh session.
+Lavish does not wire itself into your agent automatically, so in a fresh session your agent would not know to use it.
+There are two ways to fix that - **you only need one.**
+We recommend the hook.
+
+### Option A: Session hook (recommended)
 
 Run this once to opt in:
 
@@ -88,7 +92,22 @@ With the hook installed, your agent learns to turn complex responses into rich,
 
 **Restart your agent session after running this** so the new hook takes effect.
 
-Prefer not to install hooks? Lavish still works fully as a plain CLI - just tell your agent to `npx lavish-axi <file.html>` as shown in the Quick Start.
+### Option B: Install as a skill
+
+Prefer the [Agent Skills](https://agentskills.io) format, or use an agent that supports it?
+Install Lavish as a skill with [`npx skills`](https://github.com/vercel-labs/skills):
+
+```sh
+npx skills add kunchenguid/lavish-axi --skill lavish-axi
+```
+
+This drops a `lavish-axi` skill into your agent's skills directory (`.claude/skills/` for example; add `-g` for `~/.claude/skills/`).
+The skill carries the same guidance the hook delivers, but it loads on demand when the agent recognizes a task that calls for a visual artifact, rather than every session.
+It does not surface your live open sessions - run `lavish-axi setup hooks` if you want that ambient context too.
+
+### No setup at all
+
+Lavish also works fully as a plain CLI - just tell your agent to `npx lavish-axi <file.html>` as shown in the Quick Start.
 
 ## How It Works
 
@@ -157,6 +176,7 @@ Known playbook IDs: `diagram`, `table`, `comparison`, `plan`, `diff`, `input`, `
 ```sh
 pnpm run check          # Run all verification commands
 pnpm run build          # Bundle the publishable CLI, chrome, and design assets
+pnpm run build:skill    # Regenerate the installable lavish-axi skill
 pnpm test               # Run node:test tests
 pnpm run lint           # Run ESLint
 pnpm run format:check   # Check Prettier formatting

package/dist/chrome-client.js

@@ -260,6 +260,12 @@ annotationButton.onclick = () => {
 };
 
 sendButton.onclick = sendQueued;
+chatInput.addEventListener("keydown", (event) => {
+  if (event.key === "Enter" && !event.shiftKey && !event.isComposing) {
+    event.preventDefault();
+    sendQueued();
+  }
+});
 copyPathButton.onclick = copyFilePath;
 endButton.onclick = endSession;
 frame.addEventListener("load", () => {

package/dist/cli.mjs

@@ -942,6 +942,12 @@ function createArtifactSdk() {
       if (prompt) queuePrompt(prompt, c);
       closeCard();
     };
+    textarea.addEventListener("keydown", (event) => {
+      if (event.key === "Enter" && !event.shiftKey && !event.isComposing) {
+        event.preventDefault();
+        sendButton.click();
+      }
+    });
     setTimeout(() => textarea.focus(), 0);
   }
   window.lavish = {
@@ -1899,7 +1905,7 @@ function normalizePagePath(path5) {
 // src/cli.js
 var COMMANDS = /* @__PURE__ */ new Set(["open", "poll", "end", "stop", "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.19";
+var VERSION = "0.1.20";
 async function run(argv) {
   await ensureStateDir();
   const normalizedArgv = normalizeArgv(argv);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "lavish-axi",
-  "version": "0.1.19",
+  "version": "0.1.20",
   "packageManager": "pnpm@11.1.1",
   "description": "HTML is the new markdown. Lavish is the new editor for your HTML artifacts.",
   "type": "module",
@@ -9,13 +9,15 @@
   },
   "files": [
     "dist",
+    "skills/lavish-axi",
     "lavish-editor-marketing/renders/lavish-editor-marketing.gif",
     "LICENSE",
     "README.md"
   ],
   "scripts": {
     "build": "node scripts/build.js",
-    "check": "npm run build && npm run lint && npm run format:check && npm run typecheck && npm test",
+    "build:skill": "node scripts/build-skill.js",
+    "check": "npm run build && npm run lint && npm run format:check && npm run typecheck && npm test && node scripts/build-skill.js --check",
     "start": "node dist/cli.mjs",
     "lint": "eslint bin src test scripts",
     "format": "prettier --write .",

package/skills/lavish-axi/SKILL.md

@@ -0,0 +1,54 @@
+---
+name: lavish-axi
+description: Turn complex or visual agent responses into rich, reviewable HTML artifacts the user can annotate and send feedback on, using the lavish-axi CLI. Use when about to give a plan, comparison, diagram, table, code diff, report, or anything easier to grasp visually than as prose.
+---
+
+# Lavish Editor
+
+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 `npx -y lavish-axi <html-file>` so the user can visually review it, annotate elements or selected text, queue prompts, and send feedback back through `npx -y lavish-axi poll`.
+
+You do not need lavish-axi installed globally - invoke it with `npx -y lavish-axi <html-file>`.
+If lavish-axi output shows a follow-up command starting with `lavish-axi`, run it as `npx -y lavish-axi ...` instead.
+
+## When to use
+
+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
+
+## Workflow
+
+1. Create the HTML artifact (default location `.lavish/<name>.html` in the working directory).
+2. Run `npx -y lavish-axi <html-file>` to open or resume a review session in the browser.
+3. Run `npx -y lavish-axi poll <html-file>` to long-poll for the user's annotations and queued prompts.
+4. Apply the feedback, then poll again with `--agent-reply "<message>"` to reply in the browser and keep the loop going.
+5. Run `npx -y lavish-axi end <html-file>` when the review is finished.
+
+## Visual guidance
+
+- Use visual hierarchy to make the most important decisions, risks, tradeoffs, and next actions obvious at a glance
+- Use visual structure such as sections, cards, tables, diagrams, annotated snippets, and side-by-side comparisons instead of long prose
+- Choose typography, spacing, color, and layout deliberately so the artifact has a clear point of view
+- Prevent horizontal overflow: design narrow layouts intentionally, use minmax(0, 1fr) and min-width: 0 for grid/flex children, and deliberately wrap or truncate long labels/status text
+
+## Playbooks
+
+Run `npx -y lavish-axi playbook <id>` for focused, detailed guidance on any of these:
+
+- `diagram` - Map relationships, flows, state, and architecture
+- `table` - Turn dense records into scan-friendly review surfaces
+- `comparison` - Show options, tradeoffs, and current vs target behavior
+- `plan` - Explain a product or technical plan before implementation
+- `diff` - Present code or PR changes with evidence and findings
+- `input` - Must be used when the agent needs to collect user input on decisions, choices, preferences, triage, scope, or other structured feedback from within the artifact
+- `slides` - Create a deliberate presentation when slides are requested
+
+## Commands & rules
+
+- Run `npx -y lavish-axi <html-file>` to open or resume a Lavish Editor session
+- Unless the user specifies another location, create HTML artifacts in the current working directory under `.lavish/`
+- Lavish serves the html file through a local express.js server. If your html needs to reference other filesystem assets such as images, CSS, fonts, and local scripts, copy them into the same directory as the HTML file, then reference them with relative paths from that directory. Never prepend `/` to those asset paths - root paths won't work
+- Run `npx -y lavish-axi poll <html-file>` to wait for user feedback
+- Run `npx -y lavish-axi end <html-file>` to end a session
+- Run `npx -y lavish-axi stop` to shut down the background server (it also self-stops when idle or after the last session ends with nothing connected)
+- Run `npx -y lavish-axi playbook <playbook_id>` for focused artifact guidance
+- Lavish does not auto-inject any design system - artifacts stay portable so they render identically when opened directly without lavish-axi running. Choose a design system in this priority order: (1) if the user asked for a specific look or named design system, follow that; (2) otherwise, if the current project already has a design system or style conventions, match those so the artifact fits in; (3) otherwise, prefer the Lavish-recommended Tailwind CSS browser runtime v4 + DaisyUI v5, available via CDN - run `npx -y lavish-axi design` for a copy-pasteable CDN snippet plus component reference. Prefer that CDN snippet over hand-writing styles unless explicitly instructed otherwise by the user.
+- 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