メニュー
Generate, review, and correct UJG ED Localization JSON-LD. Use when attaching MessageBundle copy metadata or locale-switch metadata through l10n terms without changing Graph topology.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | ujg-ed-l10n-modeling |
| description | Generate, review, and correct UJG ED Localization JSON-LD. Use when attaching MessageBundle copy metadata or locale-switch metadata through l10n terms without changing Graph topology. |
Use this skill together with ujg-ed-modeling. Do not use it as a replacement for the parent modeling skill.
Use the active Editor's Draft unless the user explicitly asks for a dated snapshot:
https://ujg.specs.openuji.org/ed/modules/l10n
Generate only terms defined by the active ED Localization context unless the user explicitly requests an extension.
Localization attaches locale and copy metadata to UJG nodes.
It does not define routes, traversal, locale negotiation, runtime translation loading, ICU behavior, imports, or graph identity.
Graph defines topology. Localization annotates graph or experience resources with copy and locale metadata.
When using Localization terms, include the Localization context:
[
"https://ujg.specs.openuji.org/ed/ns/context.jsonld",
"https://ujg.specs.openuji.org/ed/ns/l10n.context.jsonld"
]
When using locale switches with OutgoingTransition, also include Graph context if it is not already included.
Use only these Localization classes:
MessageBundle
Use only these Localization properties:
copyRef
namespace
messageKey
defaultLocale
fallbackLocales
rtl
locales
targetLocale
l10n:targetLocale
Prefer prefixed l10n:* terms in mixed-module examples when clarity matters.
Do not invent:
locale
currentLocale
selectedLocale
translationKey
translations
messages
language
languageCode
i18n
resourceFile
bundleFormat
loader
routeLocale
localeRoute
Use private extensions only for project-specific runtime hints that are not intended to be interoperable l10n semantics.
Use MessageBundle for reusable copy metadata.
A MessageBundle must have exactly one messageKey.
It may have:
namespace
defaultLocale
fallbackLocales
rtl
locales
Use locales only when embedding locale-specific payloads is useful. Otherwise prefer stable message keys and let implementation load translations externally.
Example:
{
"@type": "l10n:MessageBundle",
"@id": "urn:example:l10n:home-hero-title",
"l10n:namespace": "home.hero",
"l10n:messageKey": "home.hero.title",
"l10n:defaultLocale": "de",
"l10n:fallbackLocales": ["en"],
"l10n:rtl": false
}
Use l10n:copyRef to attach any addressable UJG node to one MessageBundle.
Example:
{
"@type": "State",
"@id": "urn:example:state:home-hero",
"label": "Home hero",
"l10n:copyRef": "urn:example:l10n:home-hero-title"
}
Do not use copyRef to define traversal, visibility, routing, state identity, component props, or runtime loading.
Use Graph OutgoingTransition for locale switch affordances.
If the locale switch keeps the same effective graph state, use:
{
"@type": "OutgoingTransition",
"@id": "urn:example:ot:locale-en",
"label": "English",
"toCurrentState": true,
"l10n:targetLocale": "en"
}
If the locale switch targets a distinct modeled state, use to plus l10n:targetLocale.
Do not create duplicate locale-specific states unless locale changes graph topology, available journeys, states, or affordances.
Keep runtime locale selection out of Localization unless the user explicitly asks for Runtime traces.
Do not model clicked language, selected language, URL locale segment, timestamp, cookie value, browser language, request header, payload, or translation-loader behavior as l10n graph metadata.
Do not use Localization to fix missing Graph structure.
Do not use targetLocale without an OutgoingTransition.
Do not use l10n:copyRef without a referenced MessageBundle.
copyRef point to a MessageBundle?MessageBundle have one messageKey?targetLocale used only on OutgoingTransition?toCurrentState: true?Generate, review, correct, and reason about Core Modeling in User Journey Graph JSON-LD for the Editor's Draft. Use when the task is scoped to Core module document containers, imports, top-level nodes, and extensions or when whole-document modeling crosses this module boundary.
Generate, review, correct, and reason about Design System Modeling in User Journey Graph JSON-LD for the Editor's Draft. 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.
Generate, review, correct, and reason about Graph Modeling in User Journey Graph JSON-LD for the Editor's Draft. Use when the task is scoped to Graph module topology, journeys, states, transitions, exits, outgoing navigation, and indexes or when whole-document modeling crosses this module boundary.
Generate, review, correct, and reason about Localization Modeling in User Journey Graph JSON-LD for the Editor's Draft. Use when the task is scoped to Localization module semantics for MessageBundle copy metadata and locale-switch metadata or when whole-document modeling crosses this module boundary.
Generate, review, correct, and reason about User Journey Graph JSON-LD for the Editor's Draft. Use when modeling UJG documents, checking vocabulary discipline, selecting modules, or correcting Core/Graph/Surface/Runtime/Mapping/Metrics/Experience/Localization/Observability and optional module separation, including Design System, Effect, Condition, Routing, and Artifact.
Generate, review, correct, and reason about Observability Modeling in User Journey Graph JSON-LD for the Editor's Draft. Use when the task is scoped to Observability module semantics for ObservationBinding, ObservationEvent input modality requirements, accessible-object locators, surface recognition contracts, and SurfaceInstanceResolver or when whole-document modeling crosses this module boundary.