@calimero-network/agent-skills 0.3.0 → 0.4.0

package/README.md

@@ -8,16 +8,20 @@ hallucinating APIs that don't exist.
 
 ## Skills
 
-| Skill | When to use |
-| --- | --- |
-| [`calimero-rust-sdk`](#calimero-rust-sdk) | Building Rust WASM applications |
-| [`calimero-client-js`](#calimero-client-js) | Frontend / Node.js clients connecting to a node |
-| [`calimero-registry`](#calimero-registry) | Signing and publishing apps to the registry |
-| [`calimero-desktop`](#calimero-desktop) | Integrating apps with Calimero Desktop SSO |
-| [`calimero-node`](#calimero-node) | Node operators and meroctl scripting |
-| [`calimero-merobox`](#calimero-merobox) | Local multi-node dev environments and CI |
-| [`calimero-client-py`](#calimero-client-py) | Python client for node automation and backend services |
-| [`calimero-abi-codegen`](#calimero-abi-codegen) | Generate TypeScript clients from WASM ABI manifests |
+| Skill                                           | When to use                                               |
+| ----------------------------------------------- | --------------------------------------------------------- |
+| [`calimero-core`](#calimero-core)               | Understanding the runtime model, protocol, and CRDT types |
+| [`calimero-rust-sdk`](#calimero-rust-sdk)       | Building Rust WASM applications                           |
+| [`calimero-sdk-js`](#calimero-sdk-js)           | Building TypeScript WASM applications                     |
+| [`calimero-client-js`](#calimero-client-js)     | Frontend / Node.js clients connecting to a node           |
+| [`calimero-client-py`](#calimero-client-py)     | Python client for node automation and backend services    |
+| [`calimero-desktop`](#calimero-desktop)         | Integrating apps with Calimero Desktop SSO                |
+| [`calimero-node`](#calimero-node)               | Node operator quick-start (merod + meroctl overview)      |
+| [`calimero-merod`](#calimero-merod)             | merod daemon deep-dive — init, config, health             |
+| [`calimero-meroctl`](#calimero-meroctl)         | Complete meroctl CLI reference and scripting              |
+| [`calimero-merobox`](#calimero-merobox)         | Local multi-node dev environments and CI                  |
+| [`calimero-registry`](#calimero-registry)       | Signing and publishing apps to the registry               |
+| [`calimero-abi-codegen`](#calimero-abi-codegen) | Generate TypeScript clients from WASM ABI manifests       |
 
 ## Install
 
@@ -35,10 +39,10 @@ npx @calimero-network/agent-skills --list
 
 ### Where skill files are written
 
-| Flag | File |
-| --- | --- |
-| (default) | `CLAUDE.md` |
-| `--cursor` | `.cursorrules` |
+| Flag        | File                              |
+| ----------- | --------------------------------- |
+| (default)   | `CLAUDE.md`                       |
+| `--cursor`  | `.cursorrules`                    |
 | `--copilot` | `.github/copilot-instructions.md` |
 
 Running the install again updates the existing block without duplicating it.
@@ -47,11 +51,37 @@ Running the install again updates the existing block without duplicating it.
 
 ## Skill reference
 
+### calimero-core
+
+The foundational skill for **any Calimero development**. Install this alongside a language-specific
+skill to give the AI full-stack context.
+
+Covers:
+
+- Context / Application / Identity mental model
+- Full JSON-RPC protocol and endpoint list (`/api/v0/context/{id}/execute`, etc.)
+- WebSocket event schema (`ExecutionEvent`, `StateMutation`) with decoding examples
+- CRDT storage type taxonomy (`UnorderedMap`, `Vector`, `LwwRegister`, `Counter`, etc.)
+- Namespace and group model for multi-node participation
+- Authentication flow (login, refresh, JWT lifespan)
+
+Key rules included:
+
+- Application ≠ Context — installing an app does not create a context
+- CRDT types only for shared state — no `std::collections`, no plain `Map`/`Array`
+
+```bash
+npx @calimero-network/agent-skills calimero-core
+```
+
+---
+
 ### calimero-rust-sdk
 
 For developers building **Calimero WASM applications** in Rust.
 
 Covers:
+
 - App skeleton with `#[app]` macros
 - CRDT state collections (`UnorderedMap`, `Vector`, `Set`)
 - Event emission with `app::emit!()`
@@ -60,6 +90,7 @@ Covers:
 - Reference examples (kv-store, collaborative-editor)
 
 Key rules included:
+
 - Never use `std::collections` for state — CRDT collections only
 - `#[app]` macro goes on the `impl` block, not the struct
 - No `println!` — use `env::log()`
@@ -70,17 +101,44 @@ npx @calimero-network/agent-skills calimero-rust-sdk
 
 ---
 
+### calimero-sdk-js
+
+For developers building **Calimero WASM applications in TypeScript**.
+
+Covers:
+
+- `@State` class with CRDT collection fields
+- `@Logic(StateClass)` class with callable methods
+- `@Init` static method for seeding initial state
+- `@View()` annotation for read-only query methods
+- `calimero-cli-js` build tool (`pnpm build`, `pnpm deploy`)
+- WASM runtime constraints (no async in state methods, CRDT types only)
+
+Key rules included:
+
+- State fields must be CRDT types — do not use plain `Map`, `Set`, or arrays for persistent state
+- `@Logic` class must extend the `@State` class
+- `@Init` must be a `static` method returning the state class
+
+```bash
+npx @calimero-network/agent-skills calimero-sdk-js
+```
+
+---
+
 ### calimero-client-js
 
 For developers building **frontends or Node.js services** that connect to a Calimero node.
 
 Covers:
+
 - Authentication and token storage
 - JSON-RPC calls (mutations and views)
 - WebSocket event subscriptions
 - SSO token reading from URL hash
 
 Key rules included:
+
 - `mero-js` v2 uses camelCase (`contextId`, not `context_id`)
 - Always handle 401 with token refresh before surfacing errors
 
@@ -95,6 +153,7 @@ npx @calimero-network/agent-skills calimero-client-js
 For developers **publishing apps** to the Calimero App Registry.
 
 Covers:
+
 - `mero-sign` installation (crates.io and from source)
 - Key generation and security
 - `manifest.json` format and required fields
@@ -103,6 +162,7 @@ Covers:
 - Team / org signing patterns
 
 Key rules included:
+
 - Sign the manifest **before** bundling — not after
 - Never commit `key.json` to version control
 
@@ -117,11 +177,13 @@ npx @calimero-network/agent-skills calimero-registry
 For developers **integrating their app frontend** with Calimero Desktop SSO.
 
 Covers:
+
 - Hash params passed by Desktop (`access_token`, `refresh_token`, `node_url`, `application_id`)
 - Full startup integration pattern (React and vanilla JS)
 - How Desktop discovers the app's frontend URL (`manifest.json` `links.frontend`)
 
 Key rules included:
+
 - Always fall back to manual login when hash params are absent
 
 ```bash
@@ -135,11 +197,13 @@ npx @calimero-network/agent-skills calimero-desktop
 For **node operators** and developers scripting against a live node.
 
 Covers:
+
 - `merod` startup and configuration
 - Full `meroctl` command reference (app, context, identity, call)
 - Context lifecycle (app install → context create → invite → join → sync)
 
 Key rules included:
+
 - Application and context are different — installing an app does not create a context
 
 ```bash
@@ -148,17 +212,68 @@ npx @calimero-network/agent-skills calimero-node
 
 ---
 
+### calimero-merod
+
+For developers and operators who need deep knowledge of the **`merod` daemon** — init options,
+configuration, health checking, and Docker deployment.
+
+Covers:
+
+- `merod init` — all flags, data directory layout
+- `merod run` — startup flags and background execution
+- Config file schema (`config.toml`) and defaults
+- Health endpoint (`GET /health` returns `{ "status": "alive" }`)
+- Docker and Docker Compose health check patterns
+- Multiple nodes on one machine (port management)
+
+Key rules included:
+
+- Always run `merod init` before `merod run` on a new home directory
+- Never re-init a production node — it destroys the keypair and breaks existing contexts
+- Ports are set at init time; server-port and swarm-port have different consumers
+
+```bash
+npx @calimero-network/agent-skills calimero-merod
+```
+
+---
+
+### calimero-meroctl
+
+Complete **`meroctl` CLI reference** for developers and operators scripting against a running node.
+
+Covers:
+
+- All subcommand groups: `node`, `app`, `context`, `call`, `identity`, `namespace`, `group`
+- Every flag for each command
+- Scripting patterns for CI/CD pipelines
+- Multi-node setup with namespace invite + group join-context
+- Dev-mode hot reload (`context create --watch`)
+
+Key rules included:
+
+- Register a node once with `meroctl node add` + `meroctl node use`; omit `--node` after
+- Always pass `--view` for read-only method calls
+
+```bash
+npx @calimero-network/agent-skills calimero-meroctl
+```
+
+---
+
 ### calimero-merobox
 
 For developers setting up **local multi-node environments** or CI pipelines.
 
 Covers:
+
 - Merobox installation
 - Workflow YAML format
 - Multi-node setup with app deployment and context creation
 - GitHub Actions integration template
 
 Key rules included:
+
 - Docker must be running before any merobox command
 
 ```bash
@@ -172,11 +287,13 @@ npx @calimero-network/agent-skills calimero-merobox
 For developers using the **Python client** to automate or script against a Calimero node.
 
 Covers:
+
 - Full async API (contexts, apps, identities, blobs, aliases, proposals)
 - Authentication and token caching (`~/.merobox/auth_cache/`)
 - First-time token seeding and CI/CD patterns
 
 Key rules included:
+
 - `node_name` must be stable and unique per node — changing it loses cached tokens
 - All client methods are async and must be awaited
 
@@ -191,6 +308,7 @@ npx @calimero-network/agent-skills calimero-client-py
 For developers **generating typed TypeScript clients** from a Calimero app's ABI manifest.
 
 Covers:
+
 - CLI usage (`npx calimero-abi-codegen -i abi.json -o src/generated`)
 - ABI manifest format (`wasm-abi/1` schema, types, methods, events)
 - Generated output shape (`types.ts` + `{ClientName}.ts`)
@@ -198,6 +316,7 @@ Covers:
 - Integrating codegen into your build script
 
 Key rules included:
+
 - ABI must have `"schema_version": "wasm-abi/1"` — other values are rejected
 - Method, event, and type names must all be unique; map keys must be string
 
@@ -211,21 +330,22 @@ npx @calimero-network/agent-skills calimero-abi-codegen
 
 Each skill follows this layout:
 
-```
+```text
 skills/<skill-name>/
 ├── SKILL.md          # Agent instructions: what to know, what to avoid
 ├── references/       # Detailed API guides with real code examples
 └── rules/            # Hard rules: one file per rule, named after the rule
 ```
 
-The install script appends skill content to your editor's context file, wrapped in
-markers so re-running updates the block cleanly.
+The install script appends skill content to your editor's context file, wrapped in markers so
+re-running updates the block cleanly.
 
 ## Contributing
 
 See [CONTRIBUTING.md](CONTRIBUTING.md) for how to add or update a skill.
 
 Skills should be:
+
 - Based on real API surfaces, not pseudocode
 - Focused on code examples over prose
 - Kept up to date with library releases

package/SKILL.md

@@ -4,45 +4,48 @@ This package provides AI agent skills for building on the Calimero Network stack
 
 ## Available Skills
 
-| Skill | Install command | When to use |
-| --- | --- | --- |
-| `calimero-rust-sdk` | `npx @calimero-network/agent-skills calimero-rust-sdk` | Building Rust WASM applications that run on a node |
-| `calimero-sdk-js` | `npx @calimero-network/agent-skills calimero-sdk-js` | Building TypeScript/JS WASM applications that run on a node |
-| `calimero-client-js` | `npx @calimero-network/agent-skills calimero-client-js` | Browser/Node.js frontends connecting to a node (not building apps) |
-| `calimero-registry` | `npx @calimero-network/agent-skills calimero-registry` | Signing and publishing apps to the registry |
-| `calimero-desktop` | `npx @calimero-network/agent-skills calimero-desktop` | Integrating apps with Calimero Desktop SSO |
-| `calimero-node` | `npx @calimero-network/agent-skills calimero-node` | Node operators and meroctl scripting |
-| `calimero-merobox` | `npx @calimero-network/agent-skills calimero-merobox` | Local multi-node dev environments and CI |
-| `calimero-client-py` | `npx @calimero-network/agent-skills calimero-client-py` | Python client for node automation and backend services |
-| `calimero-abi-codegen` | `npx @calimero-network/agent-skills calimero-abi-codegen` | Generate TypeScript clients from WASM ABI manifests |
+| Skill                  | Install command                                           | When to use                                                        |
+| ---------------------- | --------------------------------------------------------- | ------------------------------------------------------------------ |
+| `calimero-rust-sdk`    | `npx @calimero-network/agent-skills calimero-rust-sdk`    | Building Rust WASM applications that run on a node                 |
+| `calimero-sdk-js`      | `npx @calimero-network/agent-skills calimero-sdk-js`      | Building TypeScript/JS WASM applications that run on a node        |
+| `calimero-client-js`   | `npx @calimero-network/agent-skills calimero-client-js`   | Browser/Node.js frontends connecting to a node (not building apps) |
+| `calimero-registry`    | `npx @calimero-network/agent-skills calimero-registry`    | Signing and publishing apps to the registry                        |
+| `calimero-desktop`     | `npx @calimero-network/agent-skills calimero-desktop`     | Integrating apps with Calimero Desktop SSO                         |
+| `calimero-node`        | `npx @calimero-network/agent-skills calimero-node`        | Node operators and meroctl scripting                               |
+| `calimero-merobox`     | `npx @calimero-network/agent-skills calimero-merobox`     | Local multi-node dev environments and CI                           |
+| `calimero-client-py`   | `npx @calimero-network/agent-skills calimero-client-py`   | Python client for node automation and backend services             |
+| `calimero-abi-codegen` | `npx @calimero-network/agent-skills calimero-abi-codegen` | Generate TypeScript clients from WASM ABI manifests                |
 
 ## Auto-Detection
 
 Skills should be loaded when the following are detected in the project:
 
-| Signal | Load skill |
-| --- | --- |
-| `calimero-sdk` in `Cargo.toml` | `calimero-rust-sdk` |
-| `@calimero-network/calimero-sdk-js` in `package.json` | `calimero-sdk-js` |
-| `@State` / `@Logic` decorators in TypeScript source | `calimero-sdk-js` |
-| `calimero-sdk build` in any script | `calimero-sdk-js` |
-| `@calimero-network/calimero-client` in `package.json` | `calimero-client-js` |
-| `@calimero-network/mero-js` in `package.json` | `calimero-client-js` |
-| `mero-sign` in any script or Makefile | `calimero-registry` |
-| `calimero-registry` CLI usage | `calimero-registry` |
-| `access_token` read from `window.location.hash` | `calimero-desktop` |
-| `readDesktopSSO` / `hash.get('access_token')` pattern in frontend code | `calimero-desktop` |
-| `merobox` in `package.json` or `requirements.txt` | `calimero-merobox` |
-| `calimero-client-py` in `requirements.txt` or `pyproject.toml` | `calimero-client-py` |
-| `calimero-abi-codegen` or `abi.json` in project | `calimero-abi-codegen` |
+| Signal                                                                 | Load skill             |
+| ---------------------------------------------------------------------- | ---------------------- |
+| `calimero-sdk` in `Cargo.toml`                                         | `calimero-rust-sdk`    |
+| `@calimero-network/calimero-sdk-js` in `package.json`                  | `calimero-sdk-js`      |
+| `@State` / `@Logic` decorators in TypeScript source                    | `calimero-sdk-js`      |
+| `calimero-sdk build` in any script                                     | `calimero-sdk-js`      |
+| `@calimero-network/calimero-client` in `package.json`                  | `calimero-client-js`   |
+| `@calimero-network/mero-js` in `package.json`                          | `calimero-client-js`   |
+| `mero-sign` in any script or Makefile                                  | `calimero-registry`    |
+| `calimero-registry` CLI usage                                          | `calimero-registry`    |
+| `access_token` read from `window.location.hash`                        | `calimero-desktop`     |
+| `readDesktopSSO` / `hash.get('access_token')` pattern in frontend code | `calimero-desktop`     |
+| `merobox` in `package.json` or `requirements.txt`                      | `calimero-merobox`     |
+| `calimero-client-py` in `requirements.txt` or `pyproject.toml`         | `calimero-client-py`   |
+| `calimero-abi-codegen` or `abi.json` in project                        | `calimero-abi-codegen` |
 
 ## About Calimero
 
-Calimero is a framework for distributed, peer-to-peer applications with automatic CRDT-based data synchronization, user-owned data, and verifiable off-chain computing.
+Calimero is a framework for distributed, peer-to-peer applications with automatic CRDT-based data
+synchronization, user-owned data, and verifiable off-chain computing.
 
 Core concepts:
+
 - **Context** — an isolated application instance with its own state, members, and storage
 - **Application** — WASM code deployed to a node; each context runs one application
 - **Node** (`merod`) — the runtime that hosts apps, syncs state, and exposes JSON-RPC/WebSocket
 - **Identity** — root key → client keys per device; JWT tokens for API auth
-- **CRDT state** — conflict-free replicated data; state lives on node storage, synced across context members
+- **CRDT state** — conflict-free replicated data; state lives on node storage, synced across context
+  members

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@calimero-network/agent-skills",
-  "version": "0.3.0",
+  "version": "0.4.0",
   "description": "AI agent skills for Calimero Network development — Rust SDK, JS SDK, JS client, registry publishing, desktop SSO, and more.",
   "keywords": [
     "calimero",

package/scripts/install.js

@@ -5,9 +5,9 @@ const fs = require('fs');
 const path = require('path');
 
 const SKILLS_DIR = path.join(__dirname, '..', 'skills');
-const VALID_SKILLS = fs.readdirSync(SKILLS_DIR).filter((f) =>
-  fs.statSync(path.join(SKILLS_DIR, f)).isDirectory()
-);
+const VALID_SKILLS = fs
+  .readdirSync(SKILLS_DIR)
+  .filter((f) => fs.statSync(path.join(SKILLS_DIR, f)).isDirectory());
 
 const TARGETS = {
   claude: 'CLAUDE.md',

package/scripts/test.js

@@ -18,9 +18,9 @@ function assert(condition, message) {
   }
 }
 
-const skills = fs.readdirSync(SKILLS_DIR).filter((f) =>
-  fs.statSync(path.join(SKILLS_DIR, f)).isDirectory()
-);
+const skills = fs
+  .readdirSync(SKILLS_DIR)
+  .filter((f) => fs.statSync(path.join(SKILLS_DIR, f)).isDirectory());
 
 console.log(`\nChecking ${skills.length} skills...\n`);
 
@@ -28,18 +28,9 @@ for (const skill of skills) {
   console.log(`[${skill}]`);
   const skillDir = path.join(SKILLS_DIR, skill);
 
-  assert(
-    fs.existsSync(path.join(skillDir, 'SKILL.md')),
-    'SKILL.md exists'
-  );
-  assert(
-    fs.existsSync(path.join(skillDir, 'references')),
-    'references/ directory exists'
-  );
-  assert(
-    fs.existsSync(path.join(skillDir, 'rules')),
-    'rules/ directory exists'
-  );
+  assert(fs.existsSync(path.join(skillDir, 'SKILL.md')), 'SKILL.md exists');
+  assert(fs.existsSync(path.join(skillDir, 'references')), 'references/ directory exists');
+  assert(fs.existsSync(path.join(skillDir, 'rules')), 'rules/ directory exists');
 
   const skillMd = path.join(skillDir, 'SKILL.md');
   if (fs.existsSync(skillMd)) {

package/skills/calimero-abi-codegen/SKILL.md

@@ -1,16 +1,18 @@
 # calimero-abi-codegen — Agent Instructions
 
-You are helping a developer use **`calimero-abi-codegen`** to generate typed TypeScript
-clients from a Calimero WASM application's ABI manifest.
+You are helping a developer use **`calimero-abi-codegen`** to generate typed TypeScript clients from
+a Calimero WASM application's ABI manifest.
 
 ## What it does
 
-Takes an `abi.json` file (exported by the Calimero Rust SDK) and generates two files:
-- `types.ts` — all TypeScript type definitions matching the app's Rust types
-- `{ClientName}.ts` — a typed client class with methods for every app function
+Takes an `abi.json` file (exported by `calimero-wasm-abi` during the Rust build) and generates:
 
-After codegen, frontend developers call app methods with full TypeScript type safety
-instead of constructing raw JSON-RPC calls by hand.
+- TypeScript type definitions matching all Rust types (structs, enums)
+- A typed client class with methods for every app function
+- A `CalimeroBytes` class for handling `Vec<u8>` / byte array types
+- An `AbiEvent` union type listing all events
+
+Generated client imports from `@calimero-network/mero-react` by default.
 
 ## Install & run
 
@@ -25,14 +27,14 @@ calimero-abi-codegen -i abi.json -o src/generated
 
 ## CLI flags
 
-| Flag | Default | Description |
-| --- | --- | --- |
-| `-i, --input <file>` | `abi.json` | Input ABI JSON file |
-| `-o, --outDir <dir>` | `src` | Output directory |
-| `--client-name <Name>` | `Client` | Class name for generated client |
-| `--name-from <path>` | — | Derive class name from a file path (e.g. WASM file) |
-| `--import-path <path>` | `@calimero-network/calimero-client` | Import path for base types |
-| `--validate` | — | Validate ABI only, no code generation |
+| Flag                   | Default                        | Description                            |
+| ---------------------- | ------------------------------ | -------------------------------------- |
+| `-i, --input <file>`   | `abi.json`                     | Input ABI JSON file                    |
+| `-o, --outDir <dir>`   | `src`                          | Output directory                       |
+| `--client-name <Name>` | `Client`                       | Class name for generated client        |
+| `--name-from <path>`   | —                              | Derive class name from a WASM filename |
+| `--import-path <path>` | `@calimero-network/mero-react` | Import for `MeroJs`                    |
+| `--validate`           | —                              | Validate ABI only, no code generation  |
 
 ## Quick examples
 
@@ -43,19 +45,116 @@ npx calimero-abi-codegen -i abi.json -o src/generated
 # Custom class name
 npx calimero-abi-codegen -i abi.json -o src/generated --client-name KvStoreClient
 
-# Derive class name from WASM filename
+# Derive from WASM filename (kv_store.wasm → KvStore)
 npx calimero-abi-codegen -i abi.json -o src/generated --name-from kv_store.wasm
-# → generates class KvStore
 
-# Just validate the ABI (CI check)
+# Just validate
 npx calimero-abi-codegen --validate -i abi.json
 ```
 
-## Critical: ABI schema version must be `wasm-abi/1`
+## Generated output shape
+
+```typescript
+/** @generated by @calimero/abi-codegen — DO NOT EDIT. */
+import { MeroJs } from '@calimero-network/mero-react';
+
+// Rust structs → TS interfaces
+export interface Post {
+  id: number;
+  title: string;
+}
+
+// Rust enums → discriminated unions
+export type StatusPayload = { name: 'Active' } | { name: 'Archived' };
+export const Status = {
+  Active: (): StatusPayload => ({ name: 'Active' }),
+  Archived: (): StatusPayload => ({ name: 'Archived' }),
+} as const;
+
+// AbiEvent union (all events the app emits)
+export type AbiEvent =
+  | { name: 'Inserted'; payload: Event_Inserted }
+  | { name: 'Removed'; payload: Event_Removed };
+
+// The generated client class
+export class KvClient {
+  constructor(
+    private mero: MeroJs,
+    private contextId: string,
+    private executorPublicKey: string
+  ) {}
+
+  async set(params: { key: string; value: string }): Promise<void> {
+    const response = await this.mero.rpc.execute({
+      contextId: this.contextId,
+      method: 'set',
+      argsJson: params,
+      executorPublicKey: this.executorPublicKey,
+    });
+    return response as void;
+  }
+
+  async get(params: { key: string }): Promise<string | null> {
+    const response = await this.mero.rpc.execute({
+      contextId: this.contextId,
+      method: 'get',
+      argsJson: params,
+      executorPublicKey: this.executorPublicKey,
+    });
+    return response as string | null;
+  }
+}
+```
+
+## Using the generated client in React
+
+```typescript
+import { useMeroJs } from '@calimero-network/mero-react';
+import { KvClient } from './generated/KvClient';
+
+function MyComponent({ contextId, executorKey }) {
+  const mero = useMeroJs();
+  const client = useMemo(
+    () => new KvClient(mero, contextId, executorKey),
+    [mero, contextId, executorKey]
+  );
+
+  const handleSet = async () => {
+    await client.set({ key: 'hello', value: 'world' });
+  };
+}
+```
+
+## CalimeroBytes
+
+When a Rust method uses `Vec<u8>` or `[u8; N]`, the generator emits `CalimeroBytes`. The class
+handles hex strings, number arrays, and Uint8Array transparently:
+
+```typescript
+// WASM returns byte arrays as number[] — convertWasmResultToCalimeroBytes handles this
+const board = await client.getOwnBoard({ match_id: id });
+// board.board is CalimeroBytes
+const bytes: Uint8Array = board.board.toUint8Array();
+```
+
+## ABI schema version
+
+The input JSON must have `"schema_version": "wasm-abi/1"`. This is produced automatically by the
+`calimero-wasm-abi` build dependency — just add it to `build.rs`:
+
+```rust
+fn main() {
+    calimero_wasm_abi::export().unwrap();
+}
+```
+
+## Related skills
 
-The input JSON must have `"schema_version": "wasm-abi/1"`. Other versions are rejected.
+- **`calimero-rust-sdk`** — building the WASM app that produces the `abi.json` file
+- **`calimero-client-js`** — using the generated TypeScript client in a browser/React frontend
+- **`calimero-core`** — JSON-RPC protocol that generated clients call underneath
 
 ## References
 
-See `references/` for ABI format, generated output shape, and programmatic API.
-See `rules/` for schema version and unique name requirements.
+See `references/` for ABI format, generated output shape, and programmatic API. See `rules/` for
+schema version and unique name requirements.

package/skills/calimero-abi-codegen/references/abi-format.md

@@ -22,7 +22,7 @@ The input `abi.json` follows the `wasm-abi/1` schema.
     "Entry": {
       "kind": "record",
       "fields": [
-        { "name": "key",   "type": { "kind": "string" } },
+        { "name": "key", "type": { "kind": "string" } },
         { "name": "value", "type": { "kind": "string" } }
       ]
     }
@@ -31,15 +31,13 @@ The input `abi.json` follows the `wasm-abi/1` schema.
     {
       "name": "set",
       "params": [
-        { "name": "key",   "type": { "kind": "string" } },
+        { "name": "key", "type": { "kind": "string" } },
         { "name": "value", "type": { "kind": "string" } }
       ]
     },
     {
       "name": "get",
-      "params": [
-        { "name": "key", "type": { "kind": "string" } }
-      ],
+      "params": [{ "name": "key", "type": { "kind": "string" } }],
       "returns": { "kind": "string" },
       "returns_nullable": true
     },