a2ui

Render interactive UI components and route user signals to the backend.

171|4|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/ntygod/ZhiWei --skill a2ui-ntygod
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: a2ui
Source: https://github.com/ntygod/ZhiWei/tree/main/src/main/resources/skills/a2ui
Command: npx skills add https://github.com/ntygod/ZhiWei --skill a2ui-ntygod

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Frontend applications often need to present dynamic interactive components (buttons, forms, lists) that, when interacted with, must communicate back to the Agent backend to continue workflows. A2UI provides a dedicated pathway to render these components and handle user-driven signals, keeping UI logic separate from the Agent core.

Core Features & Use Cases

  • Output an interactive component tree to the frontend using ui_render; user actions emit top-level signals that drive the Agent's next steps.
  • Supports common widgets such as Button, TextField, ListItem, Chip, and Card, enabling rapid creation of guided UI flows without embedding logic in prompts.
  • Useful for scenarios like form submissions, multi-step dialogs, and decision points where backend decisions depend on user input.

Quick Start

Use ui_render to submit a component tree for the current Agent step and respond to the resulting signal to progress the workflow.

Frequently Asked Questions about a2ui

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I render interactive UI components that send user actions back to an Agent backend?

To render interactive UI components that send user actions back to an Agent backend, use ui_render to submit a component tree for the current step and respond to the resulting top-level signal to drive the workflow.

What frontend components can I use for Agent workflow decision points?

For Agent workflow decision points, you can use frontend components such as Button, TextField, ListItem, Chip, and Card to capture user input and emit signals for backend processing.

How do interactive signals work in a dynamic form workflow?

Interactive signals in a dynamic form workflow work by emitting user actions at the top level of the component tree, which routes the interaction back to the Agent backend to trigger the next workflow step.

Does a2ui require embedding UI logic inside the Agent prompt?

No, a2ui does not require embedding UI logic inside the Agent prompt. It provides a dedicated rendering pathway to keep UI component logic separate from the Agent core.

When do I need a dedicated UI rendering pathway for Agent workflows?

You need a dedicated UI rendering pathway for Agent workflows when presenting multi-step dialogs, dynamic forms, or decision points where backend decisions depend on direct user input from the frontend interface.