Design IR Schema

The Design IR is the universal intermediate format that sits between source-code extractors and design-tool writers. Every extractor produces IR; every writer consumes it. This document is the single source of truth for the format.

Non-negotiable Rules

1. IR is always minified JSON — no pretty-printing, no comments, no trailing commas.
2. Short keys only — use the key map below. Never use full property names.
3. Two-layer format — every IR file has exactly two top-level keys: tk (token table) and nd (node tree).
4. Style by reference — nodes reference tokens by ID, never by raw value (no inline #ff0000).
5. IR lives on disk — stored in .ui-convert/ir/, never passed through chat context.
6. One file per artifact — each component/page/view gets its own IR file.

Key Map

Top-level keys