--- id: gh-lavish name: "lavish" url: https://skills.yangsir.net/skill/gh-lavish author: kunchenguid domain: ai-dev-tools-workflow tags: ["cli-utilities", "html-generation", "feedback-loop", "agent-output"] install_count: 22500 rating: 4.60 (120 reviews) github: https://github.com/kunchenguid/lavish-axi/tree/main/skills/lavish --- # lavish > 此技能将复杂的或视觉化的 AI 智能体响应转化为富文本、可审查的 HTML 页面，用户可在其上进行标注并提供反馈。它通过 lavish-axi CLI 工具，将计划、比较、图表、表格、代码差异或报告等内容以更直观的方式呈现，显著提升人机协作效率和反馈质量。 **Stats**: 22,500 installs · 4.6/5 (120 reviews) ## Before / After 对比 ### 复杂信息审查与反馈效率提升 **Before**: 在没有此技能之前，用户或团队在审查 AI 智能体生成的复杂计划、图表或报告时，往往需要花费大量时间阅读纯文本，难以快速理解关键信息和潜在问题，导致反馈周期长且不够精准。 **After**: 此技能将 AI 智能体响应转化为交互式 HTML 页面，用户可以直接在视觉化内容上进行标注和反馈。这极大地缩短了复杂信息的理解时间，并使反馈更加直观和高效，加速了决策过程。 | Metric | Before | After | Change | |---|---|---|---| | 复杂信息理解时间 | 60分钟 | 10分钟 | -83% | | 反馈准确率 | 50% | 90% | +80% | ## Readme # 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 ` 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 `. If lavish-axi output shows a follow-up command starting with `lavish-axi`, run it as `npx -y lavish-axi ...` instead. ## Request $ARGUMENTS If the request above is non-empty, the user invoked `/lavish` explicitly - build an HTML artifact for that request now, following the workflow below. If it is empty, infer what to visualize from the conversation. ## 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/.html` in the working directory). 2. Run `npx -y lavish-axi ` to open or resume a review session in the browser. 3. Run `npx -y lavish-axi poll ` to long-poll for the user's annotations, queued prompts, and browser-reported `layout_warnings`. The poll stays silent until the user acts or the real browser reports fresh layout warnings - leave it running, never kill it. If your harness limits how long a foreground command may run, run the poll as a background task; if it gets killed or times out anyway, just re-run it - queued feedback is never lost. 4. If poll returns `layout_warnings`, fix overflow, clipped text, or overlapping unreadable content and re-check before involving the human. 5. Apply human feedback, then poll again with `--agent-reply ""` to reply in the browser and keep the loop going. 6. Run `npx -y lavish-axi end ` 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 at every nesting level: nested grid/flex children also need minmax(0, 1fr) tracks and min-width: 0, especially when badges, labels, or status text use wide pixel or monospace fonts; wrap, truncate, or contain long unbreakable text deliberately ## Playbooks Run `npx -y lavish-axi playbook ` for focused, detailed guidance on any of these. One artifact often combines several playbooks (for example a plan that includes a comparison and a diagram), so MUST open each matching playbook before writing HTML. For flows, architecture, state, or sequence diagrams, do not hand-build boxes-and-arrows from div/flexbox; open the diagram playbook and use Mermaid unless SVG is needed for richly annotated nodes. - `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 - `code` - Render source code, code files, patches, PR diffs, and before/after code inside Lavish artifacts - `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 ` 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 ` to wait for user feedback or browser-reported layout_warnings. It long-polls and stays silent until the user sends feedback, ends the session, or the real browser reports fresh layout_warnings, so leave it running - never kill it. Fix layout_warnings before involving the human. If your harness limits how long a foreground command may run, run the poll as a background task; if it gets killed or times out anyway, just re-run it - queued feedback is never lost - Run `npx -y lavish-axi end ` 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 ` for focused artifact guidance. One artifact often combines several playbooks (for example a plan that includes a comparison and a diagram), so MUST open each matching playbook before writing HTML. - Lavish does not auto-inject any design system - artifacts stay portable so they render identically when opened directly without lavish-axi running. Before writing any HTML, decide the design direction in this strict priority order, and only move to the next step when the current one truly yields nothing: (1) if the user asked for a specific look or named design system, use that; (2) otherwise you must first inspect the project the artifact is about - the subject or product whose content or UI it represents, which may differ from your current working directory - and match that project's design system: Tailwind or theme config, shared CSS variables or design tokens, component library, brand assets, or existing styled pages. If the artifact previews, proposes, or mocks a specific app's UI, render it in that app's own design system so it faithfully shows the product, even when you are running in a different repo; (3) only when both steps come up empty, use the Lavish-recommended Tailwind CSS browser runtime v4 + DaisyUI v5, available via CDN - run `npx -y lavish-axi design` for a content-to-playbook router, a copy-pasteable CDN snippet, a Mermaid CDN snippet/init for diagrams, and the DaisyUI component reference, and prefer the Tailwind/DaisyUI CDN snippet over hand-writing styles unless explicitly instructed otherwise by the user. When you deliver the artifact, state which of the three design sources you used and why. - 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 --- *Source: https://skills.yangsir.net/skill/gh-lavish* *Markdown mirror: https://skills.yangsir.net/api/skill/gh-lavish/markdown*