Update to Themely Design+Style Generator

{
  "description": "Convert pasted legacy design tokens, CSS custom properties, Tailwind theme values, or brand-system values into a complete Theme Generator theme. Trigger when the user asks to migrate, import, map, normalize, or modernize an existing token set. Accept source material supplied in conversation, distinguish exact mappings from adaptations and inferred gaps, and never claim direct access to files, Figma, URLs, or external systems.",
  "included_files": [],
  "name": "legacy-theme-token-migration",
  "skill_md_contents": "---\nname: legacy-theme-token-migration\ndescription: Convert pasted legacy design tokens, CSS custom properties, Tailwind theme values, or brand-system values into a complete Theme Generator theme. Trigger when the user asks to migrate, import, map, normalize, or modernize an existing token set. Accept source material supplied in conversation, distinguish exact mappings from adaptations and inferred gaps, and never claim direct access to files, Figma, URLs, or external systems.\n---\n\n# Legacy Theme Token Migration\n\n## Inputs\n\nCollect:\n\n- the source tokens pasted into the conversation;\n- any documented usage or aliases for those tokens;\n- the product brief or current Theme Generator theme, when available;\n- any values the user requires you to preserve exactly.\n\nDo not infer that a filename, Figma link, package, or website has been read.\nAsk the user to paste relevant values when they are not present in the\nconversation.\n\n## Workflow\n\n1. Inventory every supplied source token without renaming it yet. Resolve\n   aliases only when their referenced values are available.\n2. Consult the registered `display-theme` contract as the authority for the\n   required preview and token fields.\n3. Map source values by intended use, not merely by similar names:\n   - map semantic colors according to where foregrounds, backgrounds,\n     surfaces, actions, accents, and borders are used;\n   - map typography by role, size, weight, line height, and letter spacing;\n   - preserve meaningful spacing progression;\n   - map radii by component intent;\n   - map shadows by elevation.\n4. Classify each mapping as:\n   - `exact` when the source value and purpose are retained;\n   - `adapted` when syntax or semantic placement changes;\n   - `inferred` when a required target value is absent;\n   - `unmapped` when the source has no target in the closed theme contract.\n5. Normalize target values:\n   - convert color roles to six-digit hexadecimal values;\n   - use integer font weights from 100 through 900;\n   - use non-empty CSS-ready strings for other design tokens;\n   - resolve shorthand colors when unambiguous;\n   - do not discard alpha by guessing a backdrop.\n6. Fill only the gaps required for a cohesive complete theme. Keep inferred\n   values consistent with the supplied brand system and identify them in the\n   deliverable.\n7. Build demonstration-site content from the supplied brief or current theme.\n   When material product context is missing and the user wants to provide it,\n   invoke `specify-parameters` with only facts already known. Do not use that\n   form to collect token fields it does not support.\n8. Invoke `display-theme` with every required preview field and token.\n\n## Deliverable\n\nAfter displaying the migrated theme, provide a concise mapping ledger with the\nsource name, target role, classification, and any important adaptation. List\nunmapped source tokens and inferred target tokens separately.\n\n## Boundaries\n\n- Do not claim direct file, repository, Figma, URL, or network access.\n- Do not add unsupported token categories to `display-theme`.\n- Do not claim to operate the widget Share menu. Tell the user that its Text,\n  CSS, and Tailwind exports are available after the theme is displayed.\n"
}