a-at-ui

Use when an AI agent/SDK needs to emit A@UI render/update/destroy commands to drive frontend widgets. Covers command shapes, structured JSON output, optional SSE transport, and validation constraints. Backend-only: no frontend runtime setup.

Use when a component library author needs to create, validate, or maintain the a-at-ui.manifest.json file that declares components to the A@UI runtime. Covers manifest schema, component registration, params design, event definitions, and lifecycle declarations. Targets component library maintainers integrating with A@UI.

Use when setting up A@UI in a project: installing the npm package, wiring the frontend runtime, integrating framework adapters, or configuring the component manifest. Targets AI coding tools like Claude Code, Codex, and VS Code. Do NOT use for emitting A@UI commands from a backend agent — use a-at-ui-protocol for that.