a2ui-developer-guide

name	a2ui_developer_guide
description	A comprehensive developer guide containing the entire a2ui.org documentation suite. Contains full specs for A2UI v0.9.1, JSON schemas, Agent (Python/ADK) & Renderer (React/Angular/Flutter) SDK guides, concept definitions, quickstarts, and open-source examples. Use this for ANY question or coding task related to Agent-Driven User Interfaces.

A2UI Developer Guide

This skill provides the reference for building applications, agents, and client libraries with the A2UI (Agent-Driven User Interfaces) Protocol.

A2UI is a streaming protocol that lets agents emit interactive UI components directly into a chat stream.

Core Mandates

When using A2UI, consult the reference documentation in the references/ directory. Do not guess the structure of the JSON payload, client data models, or component formats. Always verify against the specification.

Reference Material

All references are taken from the official A2UI.org documentation. They are located in the references/ directory.

Use the view_file tool to read the contents of the relevant reference file before responding:

1. Introduction

• What is A2UI?
• Who is it for?
• How to use it
• Agent UI Ecosystem

2. Core Concepts

• Overview
• Components
• Data Flow
• Data Binding
• Catalogs
• Transports
• Actions
• Glossary

3. Implementation Guides & Tutorials

• Quickstart: The fastest path to getting a basic A2UI application running.
• Client Setup: Consume the A2UI protocol on the frontend (React, Angular, Lit, etc.).
• Agent Development: Build Agents that emit A2UI components using Python/ADK.
• Defining Your Own Catalog: Build custom catalogs matching your design system.
• Authoring Components: Create new interactive UI components for agents to use.
• Theming: Styling and theming A2UI components.
• Renderer Development: Build custom renderers for interpreting A2UI.
• A2UI with Any Agent Framework: Using A2UI with LangChain, LlamaIndex, etc.
• A2UI in MCP Apps & A2UI over MCP: Integrating with the Model Context Protocol.

4. SDKs and Reference

• Messages: Full reference of valid A2UI protocol messages.
• Components: Standard components reference.
• Renderers SDK Reference (React, Angular, Lit, Flutter): Frontend Client Libraries reference.
• Agents SDK Reference (Python/ADK): Server-side agent reference.

5. Specifications & Protocol (v0.9.1)

• v0.9.1 Core Specification: The absolute source of truth for the A2UI v0.9.1 data models, JSON schemas, component states, and messaging.
• v0.9.1 Extension Specification: Details on the A2UI Extension spec.
• v0.9.1 Basic Catalog Implementation: Standard catalog implementation guide.
• v0.9.1 Evolution Guide: Migrating from earlier versions.
• JSON Schemas:
  • Client Data Model
  • Basic Catalog
  • Common Types

6. Ecosystem & Other

• Open Source Examples: Links to official samples, community renderers, and open-source integrations.
• Community Renderers
• Community Projects
• A2UI in the World
• A2UI Composer
• Roadmap

Workflow

1. Identify the User's Goal: What exactly are they trying to do? Are they learning concepts, building an agent, integrating a client, authoring components, or looking up spec details?
2. Read the Relevant Reference: Immediately read the matching file(s) in the references/ directory.
3. Provide Code or Answers: Use the code samples and exact JSON structures defined in the documentation to fulfill the request. If generating code, make sure to strictly adhere to the models and SDK references.