ss-tokens
starsforks
How to install ss-tokens?
bitjaru/styleseed/ss-tokens
$npx -y skills add bitjaru/styleseed --skill ss-tokensView, add, or modify design tokens in the StyleSeed design system
SKILL.md
| 1 | # Design Token Manager |
| 2 | |
| 3 | ## When NOT to use |
| 4 | |
| 5 | - For applying tokens in components → use `/ss-component` or `/ss-pattern` |
| 6 | - For finding token violations in existing code → use `/ss-lint` |
| 7 | - For brand-wide color/font choices that don't exist yet — define a skin first, then add tokens |
| 8 | - For non-CSS token systems (Figma, native iOS/Android) — Tailwind v4 / CSS variables only |
| 9 | |
| 10 | Action: **$0** | Token type: **$1** |
| 11 | Arguments: $ARGUMENTS |
| 12 | |
| 13 | ## Token File Locations |
| 14 | |
| 15 | | Type | JSON Source | CSS Implementation | |
| 16 | |------|-----------|-------------------| |
| 17 | | Colors | `tokens/colors.json` | `css/theme.css` `:root` + `@theme inline` | |
| 18 | | Typography | `tokens/typography.json` | `css/fonts.css` + `css/base.css` | |
| 19 | | Spacing | `tokens/spacing.json` | Tailwind utilities (no custom CSS needed) | |
| 20 | | Radius | `tokens/radii.json` | `css/theme.css` `@theme inline` | |
| 21 | | Shadows | `tokens/shadows.json` | `css/theme.css` `:root` | |
| 22 | |
| 23 | ## Instructions |
| 24 | |
| 25 | ### `list` — Show current tokens |
| 26 | Read and display the requested token file in a formatted table. |
| 27 | |
| 28 | ### `add` — Add new token |
| 29 | 1. Add the token to the JSON source file (`tokens/*.json`) |
| 30 | 2. Add the CSS custom property to `css/theme.css` under `:root` |
| 31 | 3. If it needs a Tailwind utility, add to the `@theme inline` block |
| 32 | 4. If it has a dark mode variant, add to the `.dark` block |
| 33 | |
| 34 | ### `update` — Modify existing token |
| 35 | 1. Update the value in the JSON source file |
| 36 | 2. Update the CSS custom property in `theme.css` |
| 37 | 3. Check all components for direct usage that might need updating |
| 38 | |
| 39 | ## Rules |
| 40 | - Always keep JSON and CSS in sync |
| 41 | - Use semantic names, not descriptive names (`--success` not `--green-500`) |
| 42 | - Colors should support both light and dark modes |
| 43 | - New tokens must be added to BOTH the JSON source AND the CSS implementation |
People who liked this also viewed
6 picksType
- web-design-guidelinesReview UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".SkillsJul 2026
- lark-slides飞书幻灯片：创建和编辑幻灯片。创建演示文稿、读取幻灯片内容、管理幻灯片页面（创建、删除、读取、局部替换）。当用户需要创建或编辑幻灯片、读取或修改单个页面时使用。当用户给出 doubao.com 的 /slides/ URL/token 时，也应直接使用本 skill，不要因为域名不是飞书而回退到 WebFetch；路由依据是 URL 路径模式和 token，而不是域名。不负责：云文档内容编辑（走 SkillsJul 2026
- design-taste-frontendTaste-Skill - gives your AI good taste. stops the AI from generating boring, generic slop SkillsJul 2026
- ui-ux-pro-maxUI/UX design intelligence for web and mobile. Searchable local database with 84 styles, 192 color palettes, 74 font pairings, 192 product types, 98 UX guidelines, 104 icon entries, 16 GSAP motion presSkillsJul 2026
- caveman-helpQuick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".SkillsJul 2026
- codebase-designShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-nSkillsJul 2026
