Update to Gradient Maker - Linear Color

{
  "name": "gradient-handoff-pack",
  "description": "Prepare a concise, semantically named gradient collection for design-to-development handoff and display it in the Gradient Picker for exact exports. Use when users need gradients organized for UI roles, CSS variables, Tailwind classes, or a shareable swatch sheet. Do not claim to edit source files, operate the widget's export controls, or persist a shared design-token library.",
  "included_files": [],
  "skill_md_contents": "---\nname: gradient-handoff-pack\ndescription: Prepare a concise, semantically named gradient collection for design-to-development handoff and display it in the Gradient Picker for exact exports. Use when users need gradients organized for UI roles, CSS variables, Tailwind classes, or a shareable swatch sheet. Do not claim to edit source files, operate the widget's export controls, or persist a shared design-token library.\n---\n\n# Gradient Handoff Pack\n\nOrganize a final or near-final gradient collection so a developer can understand each role and export exact current values from the widget.\n\n## Gather inputs\n\nIdentify:\n\n- the product or interface context;\n- the required semantic roles, such as hero, card, CTA, accent, or decorative surface;\n- fixed gradient values or brand constraints;\n- the target handoff formats: named values, CSS variables, Tailwind classes, or PNG swatches.\n\nUse valid gradients from the prompt, conversation, or model-visible widget state when supplied. If no final collection exists, design the smallest collection that covers the requested roles.\n\n## Prepare the collection\n\n1. Assign one clear responsibility to each gradient and remove redundant variants.\n2. Use short, unique, semantic names that remain understandable when converted into CSS-variable slugs.\n3. Preserve approved colors, angles, stop positions, and collection order.\n4. Keep the pack between one and eight gradients, with two to eight stops per gradient.\n5. Call `display-gradients` with the complete handoff collection and a concise `reason`.\n\nFor every gradient, provide a name of at most 80 characters, an integer angle from 0 through 359, and opaque hex stops positioned from 0 through 100.\n\n## Deliver the handoff\n\nAfter rendering:\n\n- provide a compact mapping from semantic role to gradient name;\n- note any assumption that still needs design approval;\n- tell the user to make final visual edits in the widget before exporting;\n- direct the user to the Names, CSS variables, Tailwind classes, or swatch-image action matching the requested handoff.\n\nTreat the widget export as the source of exact values after local edits. Do not reproduce supposedly final code from stale pre-edit values.\n\n## Boundaries\n\n- Do not claim to click export controls, write files, install tokens, or modify an application repository.\n- Do not invent support for formats beyond the widget's text and PNG exports.\n- Do not promise cross-session storage or synchronization with a design system.\n- Do not label the pack accessible without separate testing in its real UI context.\n"
}