generative-ui

generative-ui is a skill for Claude Code from Owl-Listener/ai-design-skills. It costs 14 tokens per session (441 once invoked), scanned A, original, MIT.

A guide to designing interfaces that an AI creates during a conversation, such as forms, cards, charts, or layouts, instead of showing only prebuilt screens or text.

In plain words
What is it for?
Use it when designing AI products whose interface changes based on each request. It helps define component libraries, layout rules, style boundaries, interaction patterns, and accessibility constraints.
Why use it?
It explains the rules needed to keep AI-created interfaces consistent and usable. These include allowed components, layout, visual style, interactions, and accessibility requirements.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the model-interaction-design plugin — 8 skills, 3 commands shipped together

Good fit Use it when designing AI products whose interface changes based on each request. It helps define component libraries, layout rules, style boundaries, interaction patterns, and accessibility constraints.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/owl-listener/ai-design-skills/generative-ui
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add Owl-Listener/ai-design-skills --skill generative-ui
Clone the repo
git clone --depth 1 https://github.com/Owl-Listener/ai-design-skills

Made for: Claude Code.

Or install model-interaction-design, the plugin that ships this one along with the rest of its 8 skills, 3 commands.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for generative-ui

README.md
[![agentmods](https://agentmods.dev/badge/skills/owl-listener/ai-design-skills/generative-ui/github.svg)](https://agentmods.dev/skills/owl-listener/ai-design-skills/generative-ui)
Your own site
<a href="https://agentmods.dev/skills/owl-listener/ai-design-skills/generative-ui"><img src="https://agentmods.dev/badge/skills/owl-listener/ai-design-skills/generative-ui/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for generative-ui

Your own site · 80×15
<a href="https://agentmods.dev/skills/owl-listener/ai-design-skills/generative-ui"><img src="https://agentmods.dev/badge/skills/owl-listener/ai-design-skills/generative-ui.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 14 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 441 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00014 $0.00441
Opus 5.5 $0.00006 $0.00176
Sonnet 5.5 $0.00003 $0.00088
Haiku 4.5 $0.00001 $0.00044

Measured 1mo ago against content hash f7bf39e92952, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

generative-ui scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

claude-plugin/model-interaction-design/skills/generative-ui/SKILL.md · 35 lines

How it starts

The opening of the file, as written. The whole thing — 35 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Generative UI

Generative UI is when the AI creates interface elements on the fly — forms, cards, charts, layouts — rather than responding with plain text. The interface itself becomes a model output.

What Generative UI Changes

Traditional UI is designed ahead of time. Generative UI is created in the moment:

  • Static UI: Designer creates all possible screens. Developer builds them. User navigates between them.
  • Generative UI: The AI creates interface elements in response to user needs. No screen was pre-designed. This shifts the designer's role from designing screens to designing the rules, constraints, and patterns the AI uses to generate screens.

Design Constraints for Generated UI

The AI needs guardrails for what it generates:

  • Component library: A defined set of components the AI can compose (cards, tables, forms, charts, buttons)
  • Layout rules: Grid systems, spacing, hierarchy rules the AI must follow
  • Style boundaries: Colour, typography, and visual style the AI must stay within
  • Interaction patterns: How generated elements behave (clickable, editable, dismissible)
  • Accessibility requirements: Generated UI must meet accessibility standards automatically

When to Use Generative UI

Generative UI is powerful when:

  • The output is structured data that benefits from visual presentation (tables, charts, comparisons)
  • The user's request implies an interface (e.g., "show me a dashboard of...")
  • Interactive elements would be more useful than text (e.g., forms, selectors, toggles)
  • The content is highly variable and can't be pre-designed for every case

When Not to Use It

  • When plain text is clearer and simpler
  • When the generated UI could be confusing or inconsistent
  • When accessibility cannot be guaranteed
  • When the user expects a predictable, stable interface

Design Artefacts

  • Generative UI component libraries (what the AI can use)
  • Generation rules and constraints specification
  • Quality criteria for generated interfaces
  • Fallback designs for when generation fails

Read the full file on GitHub · 35 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 35 lines · 14 tokens per session scan A f7bf39e92952

Subscribe to this mod's changes

generative-ui is a skill published in the GitHub repository Owl-Listener/ai-design-skills (189 stars, last pushed 4mo ago), licensed MIT. It adds 14 tokens to every session and 441 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens