lavish-axi 0.1.26 → 0.1.27
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +5 -2
- package/dist/cli.mjs +4 -3
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -127,7 +127,10 @@ pnpm link
|
|
|
127
127
|
```
|
|
128
128
|
|
|
129
129
|
- **File-path identity** - Sessions are keyed by the canonical HTML file path, so agents do not need opaque IDs.
|
|
130
|
-
- **Portable artifacts** - The artifact runs in an iframe while Lavish injects a small SDK for annotations, snapshots, and feedback controls.
|
|
130
|
+
- **Portable artifacts** - The artifact runs in an iframe while Lavish injects a small SDK for annotations, snapshots, and feedback controls.
|
|
131
|
+
Lavish does not inject any design system, so the saved HTML file renders identically whether you open it through `lavish-axi` or directly in a browser.
|
|
132
|
+
Before writing HTML, choose a design system in strict priority order: follow a user-requested look first; otherwise inspect the current project for a Tailwind or theme config, CSS variables or design tokens, a component library, brand assets, or existing styled pages and match what you find; only when both come up empty, run `lavish-axi design` for a copy-pasteable Tailwind CSS v4 + DaisyUI v5 CDN fallback.
|
|
133
|
+
That fallback guidance recommends DaisyUI's `luxury` theme by default and warns not to `@apply` DaisyUI classes inside Tailwind browser-runtime style blocks.
|
|
131
134
|
- **Local assets** - Copy local images, CSS, fonts, and scripts next to the HTML artifact and reference them with relative paths from that directory; root-prefixed paths such as `/assets/logo.png` will not resolve through Lavish's artifact route.
|
|
132
135
|
- **Live reload** - Lavish watches the HTML artifact file by default and preserves the artifact iframe scroll position across reloads. To also reload on sibling asset changes, add `data-lavish-live-reload-root` to the root element or `<meta name="lavish-live-reload" content="root">`.
|
|
133
136
|
- **Feedback controls** - Native form controls (radios, checkboxes, inputs, selects, buttons, labels, contenteditable) are interactive automatically, so they do not need `data-lavish-action`; wire their handlers to `window.lavish.queuePrompt()` or `window.lavish.sendQueuedPrompts()` to send feedback.
|
|
@@ -151,7 +154,7 @@ pnpm link
|
|
|
151
154
|
| `lavish-axi end <html-file>` | End a session. |
|
|
152
155
|
| `lavish-axi stop` | Shut down the background server. |
|
|
153
156
|
| `lavish-axi playbook [id]` | List focused artifact guidance or show one playbook. |
|
|
154
|
-
| `lavish-axi design` | Show the Tailwind + DaisyUI CDN fallback
|
|
157
|
+
| `lavish-axi design` | Show the Tailwind + DaisyUI CDN fallback, including the `luxury` default theme and DaisyUI `@apply` warning. |
|
|
155
158
|
| `lavish-axi setup hooks` | Install or repair optional SessionStart hooks for Claude Code, Codex, and OpenCode; restart the agent session afterward. |
|
|
156
159
|
| `lavish-axi server` | Run the local Lavish Editor server. |
|
|
157
160
|
|
package/dist/cli.mjs
CHANGED
|
@@ -70,11 +70,12 @@ function createDesignOutput() {
|
|
|
70
70
|
other_design_systems: "If the user asks for a different design system (Bootstrap, custom CSS, plain HTML, etc.), use that instead - Lavish does not require DaisyUI."
|
|
71
71
|
},
|
|
72
72
|
theme_usage: [
|
|
73
|
-
'
|
|
73
|
+
'Default to `<html data-theme="luxury">` - it matches the Lavish look. Pick a different theme from the list below only when the user asked for one or the content clearly calls for it.',
|
|
74
74
|
'Set a nested section theme with `<section data-theme="night">`.',
|
|
75
75
|
"Prefer semantic colors such as `bg-base-100`, `bg-base-200`, `text-base-content`, `bg-primary`, `text-primary-content`, `alert-warning`, and `btn-primary` so themes remain readable.",
|
|
76
76
|
"Avoid hardcoded Tailwind color names for text and surfaces unless the user asked for exact colors.",
|
|
77
|
-
"Use Tailwind responsive prefixes such as `sm:`, `md:`, `lg:`, and `xl:` for layout changes."
|
|
77
|
+
"Use Tailwind responsive prefixes such as `sm:`, `md:`, `lg:`, and `xl:` for layout changes.",
|
|
78
|
+
'Never `@apply` DaisyUI classes (such as `text-base-content/40`, `bg-base-200`, or `btn`) inside `<style type="text/tailwindcss">` - the Tailwind browser runtime does not know them, and one unknown utility aborts the entire compile, leaving the page with no Tailwind styles at all. Put DaisyUI classes directly on elements, or write plain CSS with theme variables such as `var(--color-base-200)`.'
|
|
78
79
|
],
|
|
79
80
|
themes: DAISYUI_THEMES,
|
|
80
81
|
components: {
|
|
@@ -1946,7 +1947,7 @@ function normalizePagePath(path5) {
|
|
|
1946
1947
|
// src/cli.js
|
|
1947
1948
|
var COMMANDS = /* @__PURE__ */ new Set(["open", "poll", "end", "stop", "server", "playbook", "design", "setup"]);
|
|
1948
1949
|
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`.";
|
|
1949
|
-
var VERSION = "0.1.
|
|
1950
|
+
var VERSION = "0.1.27";
|
|
1950
1951
|
async function run(argv) {
|
|
1951
1952
|
await ensureStateDir();
|
|
1952
1953
|
const normalizedArgv = normalizeArgv(argv);
|