generative-ui
Skill1 starsChanged 6 days agoMITView on GitHub
How to render rich interactive HTML widgets inline in the chat or as standalone artifacts. Use this skill when you want to show the user diagrams, data visualizations, interactive controls, educational walkthroughs, or any rich visual content beyond plain text and markdown.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- BuilderIO/agent-nativetheir own version, first seen Oct 8, 2026
- IngAs8/ClaudeSkilltheir own version, first seen Sep 28, 2026
- lsongdev/skillstheir own version, first seen Sep 10, 2026
- Sapiens-ostracism678/finance-skillstheir own version, first seen Mar 20, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- BuilderIO/agent-native★ 7.6ksame name
- IngAs8/ClaudeSkill★ 0same name
- lsongdev/skills★ 0same name
- Sapiens-ostracism678/finance-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- automationSkill
- code-reviewSkill
- github-workflowSkill
- react-expertSkill
- vlypse-guideSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Create the HTML Artifact: Use write_file to save a self-contained .html file (using Tailwind CSS and inline JavaScript) to the artifact …
- Very specific: line 66
Never size an inline widget with h-screen, min-h-screen, 100vh, or height: 100% on a top-level container.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Generative UI
You can render custom, rich, interactive user interfaces (inline widgets or larger artifacts) directly in the chat or in the side pane. This is a great way to communicate complex information to the user, generate rich visualizations, and even create small interactive experiences for the user.
Workflow
- Create the HTML Artifact: Use
write_fileto save a self-contained.htmlfile (using Tailwind CSS and inline JavaScript) to the artifact directory. SetUserFacing: trueinArtifactMetadata. Embed Inline (optional): Include the iframe embed in your chat response when this html artifact should be rendered inline in the conversation:
<iframe src="file:///<artifact_path>/widget.html" class="w-full border-none rounded-xl" style="height: 480px;"></iframe>
Constraints & Theming
Styling & Tailwind CSS: Style your artifacts cleanly using Tailwind CSS. Include the following script tag in your
<head>to enable Tailwind:<script src="https://cdn.tailwindcss.com"></script>- Use Provided Theme Variables: The host environment injects semantic design-system tokens, so widgets automatically match the host theme and custom colors:
- Surfaces:
--background,--card,--sidebar - Borders:
--border - Text:
--foreground,--muted-foreground,--placeholder - Accents:
--primary,--primary-foreground,--accent - Typography is applied automatically — avoid sub-12px micro-text (
text-[10px],text-[11px], or CSSfont-sizebelow 12px; keeptext-xs/ 12px as minimum floor).
- Surfaces:
HTML Boilerplate Template: Recommended base template:
<!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8"> <meta name="viewport" content="width=device-width, initial-scale=1.0"> <script src="https://cdn.tailwindcss.com"></script> <style> :root { --background: #121316; --card: #1c1d22; --border: #2e3038; --foreground: #f1f2f6; --muted-foreground: #9ca3af; --accent: #8b5cf6; } </style> </head> <body class="bg-transparent text-[var(--foreground)] antialiased p-5"> <div class="bg-[var(--card)] text-[var(--foreground)] border border-[var(--border)] rounded-xl p-5 shadow-sm"> <h2 class="text-[var(--foreground)] font-semibold text-lg">Title</h2> <p class="text-[var(--muted-foreground)] text-sm mb-4">Description of the component</p> <!-- Interactive content and controls go here --> </div> </body> </html>
Sizing Inline Embeds
- Inline embeds look best within a 450px–500px height budget.
- Never size an inline widget with
h-screen,min-h-screen,100vh, orheight: 100%on a top-level container. Use padding for breathing room instead.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

