Design Tokens

Community

mshadmanrahman

design-tokens

Establish color, typography, spacing, radius and motion as named role-based tokens. Use before building any interface.

Overview

Publisher	mshadmanrahman
Repository	`claude-for-designers`
Skill name	`design-tokens`
Stars	40
Forks	10
Bundled files	Instructions only
License	MIT
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by mshadmanrahman on GitHub. Read the source before you install it.

Installation

Install the Design Tokens AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/mshadmanrahman/claude-for-designers/tree/main/.claude/skills/design-tokens
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/mshadmanrahman/claude-for-designers/tree/main/.claude/skills/design-tokens

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/mshadmanrahman/claude-for-designers.git /tmp/claude-for-designers
mkdir -p .claude/skills
cp -r /tmp/claude-for-designers/.claude/skills/design-tokens .claude/skills/design-tokens

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Design Tokens in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Design Tokens on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Design Tokens is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

You are establishing the design system foundation. Tokens defined here are used by every component in /frontend-design. Get this right before building anything.

First, check: does a design system already exist for this project? Ask the user to confirm. If yes, document the existing tokens rather than inventing new ones. Pull from Figma or existing CSS files if accessible.

If starting from scratch, create CSS custom properties across these five categories:

Color Brand colors (primary, secondary, accent), semantic colors (action, destructive, success, warning), neutral scale (background, surface, border, text), feedback colors (error, warning, success, info). Name every token by its purpose, not its value. Use --color-action not --color-blue. Use --color-text-primary not --color-gray-900.

Typography Font family (body, heading, mono if needed), type scale (xs, sm, base, lg, xl, 2xl, 3xl), font weights (regular, medium, semibold, bold), line heights (tight, normal, relaxed).

Spacing A consistent scale, not arbitrary values. Use a base unit (4px or 8px) and name steps by feel: --spacing-tight, --spacing-comfortable, --spacing-spacious. At minimum: 4px, 8px, 12px, 16px, 24px, 32px, 48px, 64px.

Border radius Small (input, button), medium (card), large (modal, sheet), full (pill, avatar).

Motion A duration scale (fast, default, slow) and one easing curve. Justify the slow end against the slowest device your user is actually holding.

Output as a ready-to-paste CSS :root block. Include a brief comment above each category explaining the system logic. No inline documentation that pads length; every comment must earn its space.

Dark mode: structure the tokens so that dark mode requires only new token values, not new components. Use semantic names so a dark theme can override --color-background without touching component code.

Token audit (use this when Figma and the frontend do not match)

If a value looks correct in Figma but renders differently in the browser, run this audit before filing a bug. Paste your Figma token export and your CSS file and ask:

"I am going to paste two things: a Figma token export and a CSS file. Compare them. Tell me: (1) which tokens in the export are not referenced anywhere in the CSS, (2) which CSS values are hardcoded instead of using a token, and (3) whether there are any unit mismatches between the token values and the CSS values (for example, a px value in the token but a rem value in the CSS). List each issue with the specific token name and the line in the CSS where the problem appears."

The four most common causes of a mismatch: the token was never exported from Figma, the token was exported but the CSS references a hardcoded value instead, the units differ (px in Figma, rem in CSS), or the comparison is being made at different zoom levels. Confirm all four before concluding something is broken.

Frequently asked questions

What does the Design Tokens AI skill do?

Establish color, typography, spacing, radius and motion as named role-based tokens. Use before building any interface.

Why use Design Tokens on TypingMind?

Because you install it once and use it with any model. Design Tokens is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Design Tokens in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/mshadmanrahman/claude-for-designers/tree/main/.claude/skills/design-tokens. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Design Tokens?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Design Tokens?

As many as you like. As long as a model supports skills, you can use Design Tokens with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Design Tokens AI skill free?

Yes. It is published on GitHub by mshadmanrahman under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Canvas

openclaw

OrganizationPopular

Present hosted widget documents on a connected macOS panel and control panel visibility or navigation.

Diagram Maker

Create SVG/HTML or Excalidraw diagrams for concepts, architecture, flows, and whiteboards.

Grill With Docs

A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.

Grill Me

A relentless interview to sharpen a plan or design.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Frequently asked questions

Related AI Skills

Set up your own AI workspace now