| name | xl1-dapp-kit |
| description | Portable headless XL1 dApp architecture via @xyo-network/dapp-kit*. Covers definition/config/plan/incarnation, xl1.dapp.json, application ports, effect journals and crash recovery, durable events vs Event Kit wakes, Node/browser hosts, Vercel/Cloudflare target composition, and conformance evidence. Activates when building or migrating an XL1 dApp toward dapp-kit, writing xl1.dapp.json, hosting a headless runtime, or distinguishing UI clients from the protocol application. Complements xl1-patterns domain recipes and xl1-scaffold React+service apps — does not replace gateway/chain knowledge. |
| metadata | {"version":"1.1.31"} |
XL1 dApp Kit
An XL1 dApp is a portable, headless protocol runtime. UI, CLI, and HTTP surfaces are clients. Indexes and projections are rebuildable. Finalized XL1 is the canonical ordering substrate; side channels may accelerate liveness but must not secretly govern recovery.
This skill teaches the @xyo-network/dapp-kit* application-contract layer. It sits above xl1-knowledge and alongside xl1-patterns (domain recipes still apply). Classic xl1-scaffold React+Express apps remain valid; migrate to dapp-kit when you need definition/plan/ports/recovery/conformance — not merely a Vite UI.
Skill identity. Report as xl1-dapp-kit v<version> from this file's metadata.version.
Maturity: @xyo-network/dapp-kit* is published on npm (1.x line, public access; license may still be UNLICENSED). Local UC-01..03 and adapters exist; credentialed hosted / Sequence / production evidence gates can still be open per consumer — check the deployment's evidence labels. Prefer local conformance via @xyo-network/dapp-kit-vitest-config; do not claim hosted qualification from local tests.
Lower layers
Table of Contents
Definition, configuration, plan, incarnation, host, status dimensions, durability classes — the words agents must not collapse.
xl1.dapp.json, deployment requests, locks, and the xl1-dapp CLI (validate / inspect / plan / dev / test).
Staged XL1 effects, effect journals, prepared sidecars, and SIGKILL-safe recovery.
Typed command/query/status/admin frames over WebSocket / MessagePort — not “REST as the protocol.”
Event Kit wakes vs dapp-kit durable events vs subscription cursors. Detail for JWT/grants: Authenticated Wake Delivery.
Node vs browser hosts, deployable things, Vercel/Cloudflare composition, fail-closed policies.
Evidence labels, what “done” means for a dapp-kit app, and what local tests do not prove.