File format spec
§11
Imports and libraries
Status
Stable (format version
1.0.0, frozen 2026-10). Backward compatible within 1.x (§16.4). Supersedes the draft v0.1, kept as a historical record; 0.1 files open through the 0.1 → 1.0 migration (§16.2).Schema
https://getkimo.design/schema/kimo-1.0.json (JSON Schema draft 2020-12), generated into packages/core-schema/schema/kimo-1.0.schema.json . The 0.1 schema stays published at …/kimo-0.1.json (schema/kimo-0.1.schema.json, frozen).Reference
@kimo/core-schema (packages/core-schema). Where this document and the implementation disagree, that is a bug in one of them; file an issue.Plan of record
docs/teardown.md §10. Every place where this spec resolves an ambiguity in, or deviates from, that section is listed in §20.License
MIT
imports maps an alias to a relative path of a library .kimo file. Library node ids, variables and axes are referenced with the alias prefix everywhere (of, override path segments, at, bindings, theme pins, when, slot.suggested, instance prop defaults); consumer-owned ids are never prefixed. An alias used anywhere MUST be declared (ALIAS_UNKNOWN). Libraries are linked read-only and loaded when the consumer is opened; validators check references into a library only when the library is supplied (otherwise LIBRARY_NOT_LOADED, a warning).
Keywords:
MUST
MUST NOT
SHOULD
MAY
set in small mono caps wherever they are normative