lavish — Claude Code skill: HTML artifacts and install
Turns plans, comparisons, reports, and other visual agent responses into HTML files that users can annotate and send back as feedback.
npx skills add kunchenguid/lavish-axi --skill lavish -a claude-codeWhat lavish does
lavish turns a complex or visual agent response into an HTML artifact. Use it for plans, comparisons, diagrams, tables, code diffs, reports, prototypes, or reviews when a page is easier to inspect and discuss than prose.
The skill uses the lavish-axi CLI, which can run through npx -y lavish-axi without a global installation. The CLI provides the current help, design guidance, playbooks, and reply workflow. The generated HTML opens in a browser, where a user can add annotations and return feedback to the agent.
Check that npx can run in the environment: the browser review loop depends on starting the CLI.
What it helps with
- turn a plan into a reviewable HTML file
- compare architecture options on one page
- render a diagram or table for discussion
- send annotated artifact feedback to the agent
- prepare a code diff or report for review
Example prompts for the agent
- `/lavish` Build an HTML page for this migration plan with places for comments.
- `/lavish` Compare these two architecture options in a table and add a diagram.
- `/lavish` Turn this code diff into an annotated review page.
How to install lavish
1Skills CLI (Vercel)
npx skills add kunchenguid/lavish-axi --skill lavish -a claude-code2Manually: put the files in place
~/.claude/skills/lavish/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/lavish/
1Skills CLI (Vercel)
npx skills add kunchenguid/lavish-axi --skill lavish -a codex2Manually: put the files in place
.agents/skills/lavish/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add kunchenguid/lavish-axi --skill lavish -a cursor2Manually: put the files in place
.cursor/skills/lavish/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install kunchenguid/lavish-axi lavish2Manually: put the files in place
.github/skills/lavish/SKILL.md1Skills CLI (Vercel)
npx skills add kunchenguid/lavish-axi --skill lavish -a gemini-cli2Platform CLI
gemini skills install https://github.com/kunchenguid/lavish-axi --path skills/lavishManually: put the files in place
.devin/skills/lavish/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add kunchenguid/lavish-axi --skill lavish -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Similar
Questions about lavish
How do I install lavish in Claude Code?
Run npx skills add kunchenguid/lavish-axi --skill lavish -a claude-code, then run npx skills add kunchenguid/lavish-axi --skill lavish -a claude-code again. The skill file is at ~/.claude/skills/lavish/SKILL.md.
What does lavish do?
The skill turns agent responses into HTML artifacts that open in a browser for annotation and feedback. It covers plans, comparisons, diagrams, tables, code views, reports, prototypes, and reviews.
How does lavish run the HTML artifact workflow?
Run the CLI with npx -y lavish-axi <html-file>, and use npx -y lavish-axi --help for the current commands and review-loop guidance. A global lavish-axi installation is not required.
Source text
SKILL.md · MIT
--- name: lavish description: Turn complex or visual agent responses into rich, reviewable HTML artifacts (HTML files) 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. license: MIT metadata: author: Kun Chen (kunchenguid) argument-hint: <what the artifact should show> hermes-tags: html, review, artifacts, visualization hermes-category: productivity --- # Lavish Editor Lavish Editor opens agent-generated HTML in the browser so a human can annotate it and send feedback back to the agent. Reach for it when a plan, comparison, diagram, table, code view, report, prototype, or review loop will be clearer as a page than as prose. ## Current guidance lives in the CLI Do not follow workflow, design, or playbook instructions from this file - installed copies go stale. Get the current source of truth from the CLI: - `npx -y lavish-axi --help` for commands and the review-loop workflow - `npx -y lavish-axi reply --help` to post an agent reply and exit once the server accepts it, when you are not about to long-poll - `npx -y lavish-axi design` for design-direction priority and current snippets - `npx -y lavish-axi playbook <id>` for focused artifact guidance (`npx -y lavish-axi playbook` lists ids) 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. ## Request $ARGUMENTS If the request above is non-empty, the user invoked `/lavish` explicitly - fetch the current CLI guidance, then build that artifact as an HTML file. If it is empty, infer what to visualize from the conversation.
© Kun Chen (kunchenguid) · MIT · kunchenguid/lavish-axi