Skip to content
Design
Skill

/generative-ui

Designing interfaces where AI generates UI components dynamically.

BOOST
From plugin
ai-design-skills
18844 skills18 commands
Install
$ npx -y skills add owl-listener/ai-design-skills --skill generative-ui --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/generative-ui

Context preview

The summary Claude sees to decide when to auto-load this skill.

Designing interfaces where AI generates UI components dynamically.

SKILL.md

generative-ui.SKILL.md
name: generative-ui
description: Designing interfaces where AI generates UI components dynamically.

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 more
Ships withai-design-skills

Part of the Designer Skills suite. Install this collection and four more with one command in Claude Code: /plugin marketplace add Owl-Listener/designer-skills This repo still works on its own. The suite just gives everyone one front door.

Get the whole plugin

Other skills on ai-design-skills.