ag-ui-a2ui-integration

# AG-UI + A2UI Integration Skill ## Overview Use this skill to add A2UI rendering to an AG-UI application. Treat AG-UI as the transport and agent integration layer, `@ag-ui/a2ui-middleware` as the server-side bridge that detects and paints A2UI operations, and A2UI as the UI payload format that the client renderer displays. This is a developer-facing skill artifact. It is meant to be loaded by coding agents and used against a real app or repo, not published as a docs page. ## When to Use - Adding A2UI rendering to an existing AG-UI app. - Creating an AG-UI quickstart that should display A2UI surfaces. - Connecting any AG-UI-supported framework or custom AG-UI agent to an A2UI-capable frontend. - Adding or extending an A2UI component catalog. - Debugging why an A2UI surface does not render or why a user action does not flow back to the agent. ## When NOT to Use - For AG-UI protocol event semantics only, use the AG-UI protocol skill or protocol docs. - For A2UI renderer internals outside an AG-UI app, use the A2UI renderer docs or renderer-specific skills. - For generic CopilotKit frontend work without A2UI, use CopilotKit-specific setup and React skills. ## Workflow 1. Inspect the app shape: framework adapter, AG-UI agent endpoint, runtime host, frontend shell, and any existing A2UI renderer/catalog. 2. Decide the A2UI mode before editing code: - Fixed schema: backend tools return an `a2ui_operations` envelope with `createSurface`, `updateComponen...