| name | ujg-tr-2026-06-design-system-modeling |
| description | Generate, review, correct, and reason about Design System Modeling in User Journey Graph JSON-LD for the Technical Report 2026.06. Use when the task is scoped to Design System module semantics and its relationship to Graph and Surface or when whole-document modeling crosses this module boundary. |
UJG TR 2026.06 Design System Modeling
Skill tree context
Target: Technical Report 2026.06
Public spec URL: https://ujg.specs.openuji.org/tr/2026.06
Scope: Design System module semantics and its relationship to Graph and Surface
Module scope: modules/design-system
Related generated skills:
- ujg-tr-2026-06-modeling: whole UJG document modeling across Core, Graph, Runtime, Experience, Localization, and optional modules
When the task crosses module boundaries, read references/related-skills.md and references/skill-tree.json before continuing.
UJG TR 2026.06 Design System Modeling Skill
Use this skill when modeling or reviewing Design System module terms for the UJG Technical Report 2026.06 snapshot.
Source of truth
Use the dated Technical Report Design System module:
https://ujg.specs.openuji.org/tr/2026.06/modules/design-system
Do not silently use active ED Design System terms when the user asks for TR 2026.06.
Scope
Design System guidance is module-specific. It depends on Graph and bridges through Surface.
Use this skill for token and theme references, design-system vocabulary discipline, semantic recipes, modes, and design binding expressed by TR 2026.06 terms.
Boundaries
Do not put traversal, journey ownership, exits, target resolution, or runtime observations into Design System terms.
Use Graph for topology. Use Surface for structural surface contracts. Use Design System when the concept is genuinely about design-system semantics or design binding.
Cross-skill awareness
Consult the Graph skill when a design-system decision changes topology or traversal. Consult the root modeling skill when the task spans multiple modules.
