Update to Themely Design+Style Generator

{
  "description": "Audit and minimally repair WCAG color contrast in a currently displayed Theme Generator theme. Trigger when the user asks to check accessibility, verify contrast, fix an inaccessible palette, meet WCAG AA or AAA, or repair specific semantic color relationships. Work only from a complete theme available in conversation or model-visible widget state, and do not claim that token contrast alone is a complete accessibility certification.",
  "included_files": [
    {
      "relative_path": "scripts/contrast_ratio.py",
      "size_in_bytes": 1980
    }
  ],
  "name": "accessible-palette-repair",
  "skill_md_contents": "---\nname: accessible-palette-repair\ndescription: Audit and minimally repair WCAG color contrast in a currently displayed Theme Generator theme. Trigger when the user asks to check accessibility, verify contrast, fix an inaccessible palette, meet WCAG AA or AAA, or repair specific semantic color relationships. Work only from a complete theme available in conversation or model-visible widget state, and do not claim that token contrast alone is a complete accessibility certification.\n---\n\n# Accessible Palette Repair\n\n## Inputs\n\nRequire a complete current Theme Generator theme from the latest\n`display-theme` structured content or from `widgetState.modelContent`.\nTreat model-visible widget state as authoritative because the user may have\nchanged colors with the widget picker.\n\nIf no complete theme is available, ask the user to provide or display one.\nDo not invent the missing theme merely to perform an audit.\n\n## Workflow\n\n1. Copy the current theme as the repair baseline.\n2. Resolve this skill's directory from the loaded `SKILL.md`. Run\n   `python3 scripts/contrast_ratio.py FOREGROUND BACKGROUND` from that\n   directory for every audited pair; do not estimate ratios.\n3. Audit at least these semantic text relationships:\n   - `foreground` on `background`, `surface`, and `surfaceMuted`\n   - `foregroundMuted` on `background`, `surface`, and `surfaceMuted`\n   - `primary` on `background`\n   - `primaryForeground` on `primary`\n   - `secondaryForeground` on `secondary`\n4. Use a minimum ratio of 4.5:1 for normal text and 3:1 for large text. Use\n   7:1 for normal text only when the user requests AAA. Check `border`\n   against adjacent surfaces at 3:1 when that border is the only visible\n   control or component boundary.\n5. Record every failure before changing anything.\n6. Repair the smallest practical set of color tokens:\n   - preserve passing colors;\n   - prefer changing the role with the narrowest impact;\n   - retain recognizable brand hues where contrast permits;\n   - preserve distinct background, surface, and muted-surface layers;\n   - keep every color as a six-digit hexadecimal value.\n7. Re-run every affected pair and confirm the requested threshold.\n8. Invoke `display-theme` with the complete repaired theme. Preserve all\n   preview content and every typography, spacing, radius, and shadow token\n   unless the user explicitly requested another change.\n\n## Deliverable\n\nAfter displaying the repaired theme, report:\n\n- each audited pair and its final ratio;\n- failures and their before-to-after ratios;\n- exactly which color tokens changed;\n- whether the requested AA or AAA target passed.\n\n## Boundaries\n\n- Describe the result as a semantic color-contrast audit, not a complete WCAG\n  audit or accessibility certification.\n- Do not claim to test focus behavior, keyboard navigation, screen-reader\n  output, motion, layout, or production components.\n- Do not claim to control the widget color picker, clipboard, or Share menu.\n"
}