| name | ujg-tr-2026-06-modeling |
| description | Generate, review, correct, and reason about User Journey Graph JSON-LD for the Technical Report 2026.06. Use when modeling UJG documents, checking vocabulary discipline, selecting modules, or correcting Graph/Runtime/Experience/Localization/module separation. |
UJG TR 2026.06 Modeling
Skill tree context
Target: Technical Report 2026.06
Public spec URL: https://ujg.specs.openuji.org/tr/2026.06
Scope: whole UJG document modeling across Core, Graph, Runtime, Experience, Localization, and optional modules
Module scope: whole target
Related generated skills:
- ujg-tr-2026-06-design-system-modeling: Design System module semantics and its relationship to Graph and Surface
When the task crosses module boundaries, read references/related-skills.md and references/skill-tree.json before continuing.
UJG TR 2026.06 Modeling Skill
Use this skill when generating, reviewing, correcting, or reasoning about User Journey Graph JSON-LD for the UJG Technical Report 2026.06 snapshot.
Source of truth
Use the dated Technical Report snapshot:
https://ujg.specs.openuji.org/tr/2026.06
Do not silently use active ED terms when the user asks for TR 2026.06. Generate only terms defined by the 2026.06 contexts unless the user explicitly requests an extension or an ED comparison.
Module selection
Select only required modules.
Core: document container and top-level nodes.
Graph: journeys, states, transitions, composition, exits, outgoing navigation, indexes.
Runtime: observed events, values, clicks, URLs, timestamps, payloads.
Experience: journey-map annotations such as phases, touchpoints, steps, pain points.
Localization: locale metadata, localized copy references, locale switch affordance metadata.
Core is required for UJG documents. Include Graph when modeling topology. Include Runtime only for observed behavior or traces. Include Experience only for journey-map annotations. Include Localization only when using l10n terms such as l10n:targetLocale, copyRef, defaultLocale, fallbackLocales, or locales.
Modeling discipline
Default to the shallowest valid graph. Start flat and add nesting only when nesting preserves meaning that a flatter model would lose.
Keep Graph, Runtime, Experience, Localization, Surface, and Design System roles separate. Do not repair missing topology with annotations or private extensions.
When evidence is insufficient, say so instead of inventing structure.
Cross-skill awareness
Use the generated related-skills reference when a task is mostly about Graph or Design System. Use sibling skills for module-specific vocabulary discipline and return to this root skill for whole-document integration.
