agentleFS
Gaurav890Gaurav890/everything-agentic-engineering/.claude/skills/design-tokens/SKILL.md

design-tokens

Skill1 starsChanged 2 months agoMITView on GitHub

Encode approved visual and interaction decisions as DTCG-compatible primitive, semantic, component, theme, layout, density, motion, and agentic-state tokens. Use after a visual thesis exists or when evolving an established token system across web and mobile.

35 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use brief-to-tasks, design-flow and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • julianoczkowskiSkill

    brief-to-tasks

    Break a design brief into an ordered checklist of independently buildable tasks using vertical slices. Saves as a markdown checklist. Use when user wants to break down work, create tasks from a brief, plan implementation order, or mentions "tasks" or "breakdown".

    Also in 7 projects that use this

  • julianoczkowskiSkill

    design-flow

    Run the full design-to-build workflow as a guided sequence. Orchestrates all designer skills in order, from grilling through review. Use when user wants to go through the complete design process, start a project from scratch, run the full flow, or mentions "design flow" or "full workflow".

    Also in 6 projects that use this

  • 45ckSkill

    information-architecture

    Define the information architecture for a prototype -- sitemap, navigation model, grouping logic, labeling, and action placement.

    Also in 10 projects that use this

  • nandanosqlSkill

    design-brief

    Create a design brief that clearly communicates the product context, user needs, constraints, and success criteria to the design team — bridging PM requirements and design execution.

    Also in 8 projects that use this

  • solinkzSkill

    micro-interactions

    Expert micro-interaction architect for mobile apps, web applications, and responsive websites. Use this skill when the user asks to add, build, fix, audit, or consult on micro-interactions, animations, transitions, motion design, gesture feedback, haptics, loading states, skeleton screens, pull-to-refresh, swipe actions, scroll animations, button states, form validation feedback, toast notifications, modals, dropdowns, toggles, progress indicators, shared element transitions, spring physics, easing curves, motion tokens, or any interaction that provides visual/haptic/auditory feedback to user actions. Triggers on: "micro-interaction", "animation", "transition", "motion", "easing", "spring", "gesture", "haptic", "feedback", "loading state", "skeleton", "shimmer", "pull to refresh", "swipe", "drag", "hover effect", "press state", "focus ring", "scroll animation", "parallax", "stagger", "orchestration", "reduced motion", "View Transitions", "layout animation", "shared element", "hero animation", "morphing", "Framer Motion", "GSAP", "Lottie", "Rive", "React Spring", "anime.js", or any request to make an interface "feel better", "feel alive", "feel snappy", "feel responsive", or "feel polished".

    Also in 3 projects that use this

  • dillonluiSkill

    design-review

    Review a view or flow for UX and UI issues. Provides severity-ranked, actionable findings grounded in established design heuristics. Use when the user asks for design feedback, UX review, or UI critique.

    Also in 12 projects that use this

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 32 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use packages/design-tokens/tokens/ as canonical source:

    line 10
  2. Very specific:

    Use DTCG $type, $value, $description, aliases, and $extensions for rationale/decision provenance.

    line 18
  3. Very specific:

    Before adding a token ask whether it is reusable, semantically meaningful, and different from an existing token.

    line 22
  4. Distinctive:

    Keep semantic key and type parity across themes.

    line 28
  5. Distinctive:

    Before adoption, run the token build and require:

    line 30

“Common” is measured: kept by at least 6 in 10 of the 32 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Design tokens

Tokens encode decisions; they do not create the design direction.

Use packages/design-tokens/tokens/ as canonical source:

  1. primitives: raw color, dimension, typography, radius, border, shadow, motion;
  2. semantic: intent such as surface, text, action, feedback, focus, layout, density, and agent status;
  3. component: only stable component-specific contracts;
  4. themes: light/dark semantic overrides.

Use DTCG $type, $value, $description, aliases, and $extensions for rationale/decision provenance. Product components normally consume semantic or component tokens, never raw primitives.

Before adding a token ask whether it is reusable, semantically meaningful, and different from an existing token. Before changing one assess cross-platform and theme impact. Document legitimate one-offs as TOKEN_EXCEPTION with rationale.

Component tokens reference mode-independent semantic roles, never theme.light.* or theme.dark.*. The build resolves those roles once per mode. Keep semantic key and type parity across themes.

Before adoption, run the token build and require:

  • valid aliases without cycles;
  • identical semantic keys across modes;
  • WCAG contrast for declared text and UI pairs;
  • current generated web/native outputs and token preview;
  • a token audit after implementation.

For redesigns, update the smallest correct layer. Deprecate renamed public tokens and document migration rather than breaking consumers silently.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.