Brandkit logo

Brandkit

CommunityPopular
plugin87
brandkit

Generate a complete, accessible brand design system from a brief, as primitive → semantic → component DTCG tokens (color, type, spacing, radius, shadow, motion), light + dark, plus a single theme.css, verified for WCAG. Use when the user wants a from-scratch brand/design foundation, a new palette + type system, or a themeable token kit for a product.

Overview

Publisherplugin87
Repositoryux-ui-agent-skills
Skill namebrandkit
Stars
3K
Forks
290
Bundled files
Instructions only
LicenseMIT
Links
  • 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 plugin87 on GitHub. Read the source before you install it.

Installation

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

1

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.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/plugin87/ux-ui-agent-skills/tree/main/.claude/skills/brandkit
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

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/plugin87/ux-ui-agent-skills.git /tmp/ux-ui-agent-skills
mkdir -p .claude/skills
cp -r /tmp/ux-ui-agent-skills/.claude/skills/brandkit .claude/skills/brandkit
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Brandkit 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 Brandkit 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 Brandkit 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.

Skill: Brand Kit

Step 0: is the kit here? This skill reads files from the kit. Check once: ls ${CLAUDE_SKILL_DIR}/../../../tokens >/dev/null 2>&1 && echo KIT_OK || echo KIT_MISSING On KIT_MISSING only the skill folders were installed, which is what npx skills add does. Say so plainly, point the user at npx ux-ui-agent-skills init or the plugin install, and stop. Do not guess the contents of a file you could not open.

Stand up the foundation (one token system everything renders from) before any screen. Get this right and every page stays consistent and themeable from one place.

Steps

  1. Brief Inference (mandatory): name the industry, audience, the one mood adjective, and motion depth (${CLAUDE_SKILL_DIR}/../../../taste/design-taste.md → Brief Inference). Pick an anchoring archetype from ${CLAUDE_SKILL_DIR}/../../../taste/aesthetic-systems.md.
  2. Primitives: generate the brand color ramp in OKLCH (11 shades, consistent chroma) + a neutral ramp; verify the 500 shade ≥ 4.5:1 on white (text) and 600 ≥ 3:1 (UI) per ${CLAUDE_SKILL_DIR}/../../../.claude/rules/tokens-and-color.md → Color Generation.
  3. Semantic layer: map roles to primitives (action.primary/-hover/destructive, text.{primary,secondary,on-action,link}, surface.{page,card,raised}, border.{default,strong}, feedback.{success,warning,error,info}), and the dark overrides (designed, not inverted).
  4. Scales: Major Third type scale + composite text styles, 4px spacing scale, radius tiers, elevation, and ${CLAUDE_SKILL_DIR}/../../../tokens/motion.json-style durations/easings.
  5. Emit the DTCG ${CLAUDE_SKILL_DIR}/../../../tokens/*.json (3-tier) + a single theme.css (the one shared source, [data-theme="dark"] overrides). Optionally feed the token-build pipeline (token-build skill) for other platforms.

Verification (definition of done)

  • python3 ${CLAUDE_SKILL_DIR}/../../../scripts/validate_tokens.py: valid JSON, all aliases resolve.
  • python3 ${CLAUDE_SKILL_DIR}/../../../scripts/validate_contrast.py: required text/action/border pairs pass WCAG AA in light AND dark; border.strong ≥ 3:1.
  • python3 ${CLAUDE_SKILL_DIR}/../../../scripts/validate_theme_refs.py: every component var(--…) resolves to the theme.
  • One theme, no per-page palettes; destructive = danger token (not primary); zero hardcoded values.

Output is a verified token foundation: the measurable part is provable (run npm run verify). Brand "feel" still benefits from a human review against ${CLAUDE_SKILL_DIR}/../../../taste/design-taste.md.

Frequently asked questions

What does the Brandkit AI skill do?

Generate a complete, accessible brand design system from a brief, as primitive → semantic → component DTCG tokens (color, type, spacing, radius, shadow, motion), light + dark, plus a single theme.css, verified for WCAG. Use when the user wants a from-scratch brand/design foundation, a new palette + type system, or a themeable token kit for a product.

Why use Brandkit on TypingMind?

Because you install it once and use it with any model. Brandkit 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 Brandkit in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/plugin87/ux-ui-agent-skills/tree/main/.claude/skills/brandkit. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Brandkit?

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 Brandkit?

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

Is the Brandkit AI skill free?

Yes. It is published on GitHub by plugin87 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

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇