# OpenUISpec — Full Reference > OpenUISpec is a semantic UI specification format for AI-native, platform-native app development. It replaces cross-platform frameworks by sharing intent (YAML spec) instead of runtime code — AI generates native SwiftUI, Jetpack Compose, and React from the same source of truth. This document contains the complete OpenUISpec v0.1 specification followed by all JSON Schema definitions for validation. ## Quick file format reference Every file type has a root key and a JSON Schema. Read the schema before creating files. | File | Schema | Root key | |------|--------|----------| | \`openuispec.yaml\` | \`openuispec.schema.json\` | \`spec_version\` | | \`screens/*.yaml\` | \`screen.schema.json\` | \`\` | | \`flows/*.yaml\` | \`flow.schema.json\` | \`\` | | \`platform/*.yaml\` | \`platform.schema.json\` | \`platform\` | | \`locales/*.json\` | \`locale.schema.json\` | (object) | | \`contracts/x_*.yaml\` | \`custom-contract.schema.json\` | \`contract\` | | \`tokens/color.yaml\` | \`tokens/color.schema.json\` | \`color\` | | \`tokens/typography.yaml\` | \`tokens/typography.schema.json\` | \`typography\` | | \`tokens/spacing.yaml\` | \`tokens/spacing.schema.json\` | \`spacing\` | | \`tokens/elevation.yaml\` | \`tokens/elevation.schema.json\` | \`elevation\` | | \`tokens/motion.yaml\` | \`tokens/motion.schema.json\` | \`motion\` | | \`tokens/layout.yaml\` | \`tokens/layout.schema.json\` | \`layout\` | | \`tokens/themes.yaml\` | \`tokens/themes.schema.json\` | \`themes\` | | \`tokens/icons.yaml\` | \`tokens/icons.schema.json\` | \`icons\` | **Important:** Every token file requires a root wrapper key matching its type (e.g. \`tokens/color.yaml\` must start with \`color:\`). --- ## Specification # OpenUISpec v0.1 > A single source of truth design language for AI-native, platform-native app development. **Status:** Draft **Version:** 0.1 **Authors:** Rustam Samandarov **Last updated:** 2026-03-13 --- ## 1. Philosophy OpenUISpec is not a cross-platform framework. It is a **semantic design language specification** from which AI generates native platform code. The spec describes *what* UI does and *how it should feel* — never *which widget to use*. ### Core principles 1. **Semantic over visual.** The spec defines behavioral intent, not pixel layouts. A "primary action trigger" maps to `Button` in SwiftUI, `Button` in Compose, and `