agentleFS
fatihkanfatihkan/badi/.claude/skills-vault/design-tokens/SKILL.md

design-tokens

Skill8 starsChanged 3 months agoMITView on GitHub

Project-level DESIGN.md tokens reference. When the project has a DESIGN.md file, agents producing UI / components / visuals must consult this skill to use canonical color/typography/spacing tokens rather than inventing new ones. Triggers on: UI generation, component creation, design brief, visual asset, tailwind config, CSS variables.

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 10 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

  • 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

  • jpoindexterSkill

    design-system-audit

    Audit code for design system violations - grid spacing, tokens, existing components

    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

  • +1 more from julianoczkowski

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 32 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When this skill is active, agents producing UI / visuals / components must:

    line 16
  2. Very specific:

    Cite the token: when generating code: bg-[var(--color-primary)] or theme.colors.primary rather than raw hex

    line 21

“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 Reference

When this skill is active, agents producing UI / visuals / components must:

  1. Check for DESIGN.md at the project root
  2. Read the frontmatter for canonical tokens (colors, typography, spacing, radius, elevation)
  3. Use only those tokens — do not invent ad-hoc colors, font sizes, or spacing values
  4. Cite the token when generating code: bg-[var(--color-primary)] or theme.colors.primary rather than raw hex

Token contract

The expected DESIGN.md frontmatter shape (produced by tasarim-kurator agent):

---
colors:
  primary: "#0a84ff"
  secondary: "#7c3aed"
  surface: "#0a0e1a"
  text: "#e2e8f0"
  muted: "#94a3b8"
typography:
  display: "Inter"
  body: "Inter"
  mono: "JetBrains Mono"
  scale: 1.25
spacing:
  unit: 8           # base unit in px
radius:
  sm: 4
  md: 8
  lg: 16
elevation:
  card: "0 1px 3px rgba(0,0,0,0.1)"
  modal: "0 12px 40px rgba(0,0,0,0.4)"
---

When to apply

  • Generating React/Vue components → use the colors/typography from DESIGN.md
  • Producing Tailwind config → mirror tokens via theme.extend
  • Writing CSS / Sass → emit --color-*, --font-*, --spacing-* variables
  • Visual brief (visual-director) → reference colors as palette, not hex
  • Mobile UI (RN/Flutter) → emit theme constants from tokens

When DESIGN.md is missing

Skill becomes a no-op. Agents fall back to project conventions or invent reasonable defaults — but at the next opportunity, suggest running badi tasarim init --interactive to capture decisions.

Validation

The skill loader cross-checks:

  • DESIGN.md frontmatter parses as YAML
  • Required keys: colors.primary, typography.body, spacing.unit
  • WCAG AA contrast for colors.text against colors.surface (warns if < 4.5:1)

References

  • DESIGN.md spec: lib/commands/tasarim.js
  • tasarim-kurator agent for interactive token generation
  • visual-director delegates here when DESIGN.md exists

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.