---
name: a2ui-implement-new-sdks-for-client-language
description: Step-by-step phased instructions for building new A2UI Core SDKs, Framework Adapters, and Inference SDKs from scratch in any client language.
metadata:
  internal: true
title: a2ui-implement-new-sdks-for-client-language
canonical_url: https://skilld.dev/gh/a2ui-project/a2ui/a2ui-implement-new-sdks-for-client-language
last_updated: 2026-11-13T20:07:16.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install a2ui-project/a2ui/a2ui-implement-new-sdks-for-client-language`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/a2ui-implement-new-sdks-for-client-language`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/a2ui-project/a2ui/a2ui-implement-new-sdks-for-client-language) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/a2ui-implement-new-sdks-for-client-language`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/a2ui-implement-new-sdks-for-client-language --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/a2ui-implement-new-sdks-for-client-language --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# A2UI SDK Implementation Guide (Phased Execution)

This skill provides expert instructions and sequences for AI agents or contributors tasked with implementing A2UI Core SDKs, Framework Adapters, or Agent/Inference SDKs in a new programming language or UI framework.

---

## **1. Core State SDK Phases**

If you are building a new **Core SDK** (e.g., in Rust, Swift, Go, or C++), you must follow this sequence of phases:

### **Phase 1: Context & Schemas Ingestion**

Thoroughly review:

- `blueprints/modules/a2ui_core.blueprint.md` (for state and message structures).
- `specification/v1_0/json/common_types.json` (dynamic binding schemas).
- `specification/v1_0/json/server_to_client.json` (message envelopes).
- `catalogs/basic/v1/catalog.json` (target components catalog).

### **Phase 2: Technical Architecture Planning**

Create a detailed, local architectural proposal detailing:

- **Dependencies**: Which Schema library and Observable/Reactive library will you use? Note that the reactive library must support both discrete event subscription and stateful, signal-like data streams (e.g., BehaviorSubject/Signal).
- **Component APIs**: How will you define the `ComponentApi` interface in this language?
- **Binding Strategy**: How will you structure the abstract Core Binder Layer?
- _STOP and obtain human reviewer approval on this plan before writing code._

### **Phase 3: Core Model Layer**

Implement the framework-agnostic data and processor layers:

1.  **Observables & Signals**: Implement multi-cast reactive streams with clear unsubscribe mechanism to prevent leaks.
2.  **Protocol Structures**: Create strictly-typed native classes/structs representing `A2uiMessage` envelopes and client capabilities with serialization/deserialization.
3.  **DataModel & JSON Pointers**: Implement relative/absolute path resolution, auto-vivification (auto-typing intermediate segments), and bubble/cascade path change notifications.
4.  **Core State Models**: Implement `ComponentModel`, `SurfaceComponentsModel`, `SurfaceModel`, and `SurfaceGroupModel`.
5.  **Context Mapping**: Implement `DataContext` and `ComponentContext`.
6.  **MessageProcessor**: Ingest incoming messages and mutate the state models. Generate `inlineCatalogs` client capabilities.
7.  **Verification**: Write comprehensive unit tests for pointer cascading, JSON deserialization/validation, and message dispatching.

### **Phase 4: Foundational Basic Catalog Support**

Bootstrap support for the Basic Catalog:

- **Foundational Components**: Define the pure API schemas and Binders for: `Text`, `Row`, `Column`, `Button`, and `TextField`.
- **Foundational Functions**: Implement `formatString` to interpret `${expression}` syntaxes, supporting recursive token evaluations and reactive coercion.
- **Verification**: Ensure properties update reactively when underlying data paths emit notifications.

### **Phase 5: Complete Basic Catalog Support**

- **Full Components & Binders**: Define core binders for all other components in `basic/catalog.json`.
- **Full Functions**: Implement remaining basic mathematical, logical, and array operations.
- **Validation**: Ensure strict type coercion rules are satisfied and memory disposals work flawlessly.

---

## **2. Framework Adapter SDK Phases**

If you are building a new **UI Framework Adapter / Renderer** (e.g., in Flutter/Dart, SwiftUI, Jetpack Compose, Vue, or Svelte), follow this sequence:

### **Phase 1: Ingestion & Core Integration**

Review:

- `blueprints/modules/a2ui_framework_adapter.blueprint.md` (View and rendering architecture).
- `catalogs/basic/v1/basic_catalog_implementation_guide.md` (spacing, alignment, and typography specifications).

### **Phase 2: Architectural Plan**

Draft a plan specifying:

- **Component Registry**: How components are dynamically resolved and instantiated.
- **Surface Widget**: How the root canvas mounts and recurses through the layout tree starting at `root`.
- **Observer/State Bridge**: Which Strategy (Direct, Predefined Binders, or Automated wrappers) will connect core signals to native views.
- _STOP and obtain human reviewer approval on this plan._

### **Phase 3: Adapter & Lifecycle Layer**

- Implement `ComponentImplementation` base traits/classes.
- Implement the framework-native `Surface` entrypoint widget.
- Implement subscription management: lazy-subscribing only on mount, handling path stability updates, and strictly calling `dispose()` on unmount.

### **Phase 4: Bootstrapping Basic Catalog Rendering**

- Build native visual elements for: `Text`, `Row`, `Column`, `Button`, and `TextField`.
- Bundle these elements into the first framework catalog adapter.
- Verify reactive layout properties dynamically.

### **Phase 5: Gallery Application Milestone**

Build the **Gallery App** as a testing playground with:

- Left Column: Sample navigation.
- Center Column: Surface preview, JSON message stream, and step-by-step interactive message stepper.
- Right Column: Live data model inspect pane and action logger.
- Load the 5 foundational verification examples: `scaffold-simple-text.json`, `scaffold-row-layout.json`, `scaffold-complex-layout.json`, `scaffold-interactive-button.json`, and `scaffold-simple-login-form.json`.
- _STOP and obtain human reviewer approval of the UI and visual rendering performance._

### **Phase 6: Full Catalog Support**

- Implement all remaining widgets (e.g. Card, Image, List, etc.) and validation traits like `Checkable`.
- Update the Gallery App to support all official examples in `catalogs/basic/v1/examples/`.
- Run visual parity and event action tests to verify correctness.
