xl1-patterns
XL1 Design Patterns
This skill provides prescriptive, recipe-style patterns for building common application features on XL1. Where the lower layers document what XL1 is, this layer documents how to build things on it.
Rule ownership. Entries below summarize rules that are stated in full in the linked file. The linked file is canonical: if a summary here and its file ever disagree, follow the file and flag the drift rather than reconciling silently.
Skill identity. This skill's version is exposed in this file's frontmatter under metadata.version. Whenever you present a plan, an acknowledgement, or a completion summary, state which skills informed it, formatted as <skill-name> v<version> — read the version from this file's frontmatter, never from an example. When multiple skills from this plugin are active, each may be listed.
Skill layers
This is Layer 5 of the XYO skill stack: xy-development (1) → xy-toolchain (2) → xyo-knowledge (3) → xl1-knowledge (4) → xl1-patterns (5) → xl1-dapp-kit (6) → xl1-testing (7) → xl1-scaffold (8) → xl1-build (9).
- Builds on: xl1-knowledge (4) — chain data model, datalakes, gateway (generic, browser, and Node); xyo-knowledge (3) — payloads, bound witnesses, modules, identity;
xy-toolchainandxy-developmentfrom ariestools-skills (1–2) — build tooling, ESLint, TypeScript config, Vitest; coding conventions, Git, testing, workflow - Hands off to: xl1-dapp-kit (6) — when adopting
@xyo-network/dapp-kit*(headless runtime, application ports, effect journals and recovery, hosting); xl1-testing (7) — to verify the work (headless testnet, local chain, browser mode) and to walk the dApp Definition of Done before reporting it complete; xl1-scaffold (8) — when starting a new XL1 project; xl1-build (9) — when the build request is still vague
Payload schema and hash prerequisites
Before adapting a recipe, read Payload Schema Evolution and Identity: stable ASCII schema names, explicit version/shape support, frozen definitions with deliberate closure, and root hashes for new application references/commitments. Existing protocol-specific data-hash algorithms remain contracts; their documented exceptions do not make data hashes the default for new applications.