agent product skill risk: low
StyleSeed UI Design Token Manager
Instructs the model to list, add, or update StyleSeed design tokens while keeping JSON sources, CSS variables, and dark-mode values synchronized according to specified rules and ou…
SKILL 1 file
SKILL.md
--- name: antigravity-awesome-skills-ui-tokens description: "List, add, and update StyleSeed design tokens while keeping JSON sources, CSS variables, and dark-mode values in sync." --- # UI Tokens ## Overview Part of [StyleSeed](https://github.com/bitjaru/styleseed), this skill manages design tokens without letting the source-of-truth files drift apart. It is meant for teams using the Toss seed's JSON token files and CSS implementation together. ## When to Use - Use when you need to inspect the current token set - Use when you want to add a new color, shadow, radius, spacing, or typography token - Use when you need to update a token and propagate the change safely - Use when the project has both JSON token files and CSS variables that must stay aligned ## How It Works ### Supported Actions - `list`: show the current tokens in a human-readable form - `add`: introduce a new token and wire it through the implementation - `update`: change an existing token value and audit the downstream usage ### Typical Source-of-Truth Split For the Toss seed: - JSON under `tokens/` - CSS variables and theme wiring under `css/theme.css` - typography support in the font and base CSS files ### Rules - keep JSON and CSS in sync - prefer semantic names over descriptive names - provide dark-mode support where relevant - update the token implementation, not just the source manifest - check for direct component usage that might now be stale ## Output Return: 1. The requested token inventory or change summary 2. Every file touched 3. Any affected components or utilities that should be reviewed 4. Follow-up actions if the new token requires broader adoption ## Best Practices - Add semantic intent, not one-off brand shades - Avoid token sprawl by extending existing scales first - Keep naming consistent with the rest of the system - Review contrast and accessibility when introducing new colors ## Additional Resources - [StyleSeed repository](https://github.com/bitjaru/styleseed) - [Source skill](https://github.com/bitjaru/styleseed/blob/main/seeds/toss/.claude/skills/ui-tokens/SKILL.md) ## Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
REQUIRED CONTEXT
- action type (list/add/update)
- token details or target token
OPTIONAL CONTEXT
- dark-mode values
- semantic name preference
ROLES & RULES
- keep JSON and CSS in sync
- prefer semantic names over descriptive names
- provide dark-mode support where relevant
- update the token implementation, not just the source manifest
- check for direct component usage that might now be stale
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
EXPECTED OUTPUT
- Format
- structured_report
- Schema
- numbered_list · The requested token inventory or change summary, Every file touched, Any affected components or utilities that should be reviewed, Follow-up actions if the new token requires broader adoption
- Constraints
- return token inventory or change summary
- list every file touched
- list affected components or utilities
- include follow-up actions if needed
SUCCESS CRITERIA
- Return the requested token inventory or change summary
- List every file touched
- Identify any affected components or utilities that should be reviewed
- Suggest follow-up actions if the new token requires broader adoption
QUALITY
- OVERALL
- 0.82
- CLARITY
- 0.90
- SPECIFICITY
- 0.85
- REUSABILITY
- 0.70
- COMPLETENESS
- 0.80
IMPROVEMENT SUGGESTIONS
- Add explicit placeholders for token name/value inputs in the add/update actions to improve reusability as a template.
USAGE
Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.
MORE FOR AGENT
- Beachhead Market Segment Analyzeragentproduct
- UI/UX Design Intelligence Guideagentproduct
- Customer Journey Map Generatoragentproduct
- Agile User Stories Generator with 3Csagentproduct
- StyleSeed UX Flow Designeragentproduct
- StyleSeed UX Flow Designeragentproduct
- New Product Feature Ideationagentproduct
- Existing Product Trio Idea Brainstormeragentproduct
- Onboarding CRO Flow Designeragentproduct
- Product Requirements Document Drafteragentproduct
- JTBD Job Stories Generatoragentproduct
- Product Feature Backlog Prioritizeragentproduct
- Research Data User Persona Creatoragentproduct
- StyleSeed UX Flow and Screen Designeragentproduct
- Turkish Car Valuation Platform Designeragentproduct
- Opportunity Solution Tree Product Discoveryagentproduct
- Product Launch Pre-Mortem Risk Analyzeragentproduct
- Niche Domain Intelligence Report Generatoragentproduct
- Impact Risk Assumption Prioritizeragentproduct
- StyleSeed UX Feedback Statesagentproduct
- Senior Product Manager Skills Agentagentproduct
- Prioritization Frameworks Reference Guideagentproduct
- Senior Product Manager Skills Agentagentproduct
- StyleSeed UX Feedback States Adderagentproduct
- Senior Product Manager Skills Agentagentproduct