heyoub

@batpak/canonical

Canonical named-field MessagePack codec matching rmp-serde 1.3.1, plus hex helpers for NETBAT framing.

@batpak/client

NETBAT/1 frame client. Phase 0: TCP only.

@batpak/generated

Auto-generated bindings from batpak.manifest.json. FULLY OVERWRITTEN on each pnpm generate.

@batpak/schema

Effect 4 Schema bridge for the BatPAK canonical wire. Runtime parse/encode + bank.event() authoring API.

@batpak/sdk

One-install BatPAK TypeScript SDK: NETBAT/1 client, canonical codec, Effect schema bridge, and manifest-generated types.

@cellstate/convex

Convex component for CELLSTATE — hierarchical memory for AI agents with trajectories, scopes, artifacts, notes, and multi-agent coordination

@cellstate/sdk

TypeScript SDK for CELLSTATE — persistent agent memory and multi-agent coordination

create-liteship

Scaffold a new LiteShip project: run `npm create liteship` to get a minimal Astro app wired to the framework in one step.

@czap/assets

Manage media assets for LiteShip: declare audio, video, and image assets and read cached analysis such as waveforms, beat markers, and onsets.

@czap/astro

The Astro integration for LiteShip: render adaptive UI as islands with the `client:satellite` directive and resolve device tiers on the server for first paint.

@czap/audit

Audit a LiteShip project's structure, integrity, and public surface: a downstream-installable engine that builds a model of the repository and runs configurable checks over it.

@czap/canonical

The content-addressing kernel for LiteShip: canonical CBOR encoding and stable digests so the same definition always hashes to the same address.

@czap/cli

The `czap` command-line tool for LiteShip: JSON-in, JSON-out verbs built for AI agents, with a human-friendly terminal mode.

@czap/cloudflare

Run LiteShip on Cloudflare Workers: a site adapter with a KV-backed edge cache and the Astro middleware glue that caches boundaries at the edge.

@czap/command

The shared command registry behind LiteShip's tooling: one source of command definitions that both the `czap` CLI and the MCP server project from.

@czap/compiler

Compile one LiteShip boundary definition into many outputs at once — CSS, GLSL, WGSL, ARIA, AI descriptions, and Tailwind — so every target stays in sync.

@czap/core

The heart of LiteShip: define UI boundaries, tokens, themes, and signals once as a content-addressed graph, then drive the engine that keeps every rendered output in sync.

@czap/detect

Detect device capabilities for LiteShip: probe GPU tier, CPU, memory, motion preference, and network, then map them to the tiers that select which UI state renders.

@czap/edge

Choose the right UI state at the CDN edge for LiteShip: read Client Hints into a device tier, serve a content-addressed boundary cache, and compile the theme for first paint.

@czap/error

The one error algebra for LiteShip: build tagged error values that work both as thrown Errors and as Effect failures, and compose your own variants on top with zero dependencies.

@czap/gauntlet

The rigor engine behind LiteShip's release gates: define quality gates that report findings and earn blocking power only by proving themselves against their own fixtures.

@czap/genui

Render AI-generated UI safely in LiteShip: validate a model's proposed component tree against a host-owned catalog and draw only trusted, whitelisted components.

@czap/mcp-server

The Model Context Protocol server for LiteShip: exposes the `czap` commands and capsule catalog as MCP tools that AI assistants can call.

@czap/quantizer

Turn continuous signals into a few named UI states for LiteShip: evaluate boundaries, animate the transitions between states, and gate motion by device tier.

@czap/remotion

Use LiteShip inside Remotion: React hooks and composition helpers that drive video frames and shader surfaces from the same boundary state used everywhere else.