بنقرة واحدة
tokens
Define $tokens for color, typography, spacing, and timing that give a spec its visual identity
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Define $tokens for color, typography, spacing, and timing that give a spec its visual identity
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Add purposeful motion to a UXSpec — $animations, onEnter choreography, and timing tokens
Improve every piece of text in a UXSpec — descriptions, labels, error messages, empty states, and loading copy
Identify repeated patterns and consolidate them into $elements and shared tokens for systematic reuse
Collect design context, audience, intent, and requirements before writing any UXSpec JSON
Strengthen a UXSpec against real-world conditions — overflow, missing data, network failures, and accessibility
Run a systematic quality audit on a completed UXSpec — design intent, consistency, accessibility, and state coverage
| name | tokens |
| description | Define $tokens for color, typography, spacing, and timing that give a spec its visual identity |
Define the $tokens that give a spec its visual identity — color, typography, spacing, timing. Tokens are the vocabulary every $visual speaks.
When creating or revising $tokens. Also when visuals feel inconsistent — inconsistency usually means a missing or unused token.
caption, secondary, body, heading, display. Never use arbitrary sizes.success, error, warning, info. Name tokens by role, not by hue (color.error, not color.red).xs through 3xl or similar.gap for between siblings, padding for container insets, margin for section separation. Consistent scale, different applications.sm: 4px, md: 8px, lg: 16px). Use md as default, sm for small controls, lg for cards/modals.$visual instead of token referencesspacing.15 and spacing.16) — pick onecolor.blue) instead of role (color.primary)Tokens are the single source of truth for visual consistency. If two elements should look the same, they should reference the same token. If they look different, the reason should be a different token — not a hard-coded override.