Update to Themely Design+Style Generator

{
  "name": "locale-aware-theme-adaptation",
  "description": "Adapt a complete current Theme Generator theme for a target language, region, and writing system. Trigger when the user asks to localize a theme, preview it in another language, tune typography for Latin, CJK, Devanagari, or another script, or prepare a locale-specific variant. Preserve the brand, use system or web-safe fonts, state translation limitations, and never claim full RTL layout support from the current widget.",
  "included_files": [],
  "skill_md_contents": "---\nname: locale-aware-theme-adaptation\ndescription: Adapt a complete current Theme Generator theme for a target language, region, and writing system. Trigger when the user asks to localize a theme, preview it in another language, tune typography for Latin, CJK, Devanagari, or another script, or prepare a locale-specific variant. Preserve the brand, use system or web-safe fonts, state translation limitations, and never claim full RTL layout support from the current widget.\n---\n\n# Locale-Aware Theme Adaptation\n\n## Inputs\n\nRequire:\n\n- a complete source theme from the latest `display-theme` result or\n  `widgetState.modelContent`;\n- a target language or locale.\n\nUse region, audience, tone, formality, and approved translations when supplied.\nAsk for the target locale when it is missing because that choice materially\nchanges the result.\n\n## Workflow\n\n1. Treat model-visible widget state as the authoritative source theme.\n2. Identify the target language, region, script, expected text expansion, and\n   tone. Preserve the brand name unless the user requests localization.\n3. Adapt all demonstration-site copy naturally:\n   - keep one to four concise navigation labels;\n   - retain the intended hierarchy across eyebrow, title, subtitle, and body;\n   - use short, idiomatic action labels;\n   - provide exactly three feature cards;\n   - preserve the source meaning rather than translating word for word.\n4. Select system or web-safe heading, body, and monospace stacks that support\n   the target script. Do not introduce remote font dependencies.\n5. Tune display, base, and small sizes; line height; letter spacing; and, when\n   justified, font weights for the target script:\n   - avoid negative tracking for scripts where it harms readability;\n   - allow more line height for dense or vertically complex glyphs;\n   - account for language expansion without shrinking text unnecessarily.\n6. Preserve colors, spacing, radii, and shadows unless a change is necessary\n   for legibility or the user requests a broader cultural adaptation.\n7. Keep every value within the current `display-theme` schema and invoke\n   `display-theme` with the complete locale-adapted theme.\n\n## Deliverable\n\nAfter displaying the adapted theme, summarize:\n\n- localized content and tone decisions;\n- font-stack and typography changes;\n- preserved brand decisions;\n- translation or cultural-review caveats.\n\n## Boundaries\n\n- Do not present generated copy as certified professional, legal, or cultural\n  localization.\n- The current theme contract has no text-direction field. For an RTL language,\n  explain that the widget cannot validate or demonstrate a fully mirrored RTL\n  layout; provide only the supported content and typography adaptation unless\n  the user requests separate app changes.\n- Do not claim to inspect external locale files, websites, or translation\n  systems.\n"
}