TypingMindTypingMindThe best frontend for AI
Ui Components Design System logo

Ui Components Design System

Community
thakur698
ui-components-design-system

Creates maintainable component systems, design tokens, variants and interaction states for web and mobile apps.

Overview

Publisherthakur698
Repositoryuniversal-ui-skills
Skill nameui-components-design-system
Stars
5
Forks
0
Bundled files
Instructions only
LicenseMIT
Links
Skill sourceRepositoryHomepage
  • 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 thakur698 on GitHub. Read the source before you install it.

Installation

Install the Ui Components Design System 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/thakur698/universal-ui-skills/tree/main/.agents/plugins/universal-ui/skills/ui-components-design-system
  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/thakur698/universal-ui-skills.git /tmp/universal-ui-skills
mkdir -p .claude/skills
cp -r /tmp/universal-ui-skills/.agents/plugins/universal-ui/skills/ui-components-design-system .claude/skills/ui-components-design-system
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Ui Components Design System 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 Ui Components Design System 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 Ui Components Design System 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.

UI Components & Design System

Mission

Create reusable, semantically named, and maintainable component architectures. Avoid both extremes:

  • BAD: One-off visual code (inline styles, magic numbers) everywhere.
  • ALSO BAD: Turning every tiny wrapper into a bloated, over-engineered component.

Design Tokens

Require semantic design tokens. Do not hardcode magic values across the UI. At minimum cover:

  • Typography: scales, weights, line heights, and tabular figures (font-variant-numeric: tabular-nums for data/counts).
  • Spacing: padding, margins, gaps
  • Colors: semantic palette (primary, secondary, success, error, text, background). Secondary text on colored surfaces must be tinted from the background hue, NEVER generic gray.
  • Surfaces: background, elevated, raised, depressed
  • Browser Surfaces: selection-bg, selection-text, caret-color, focus-ring (with offset), scrollbar.
  • Borders: colors, widths, styles
  • Radii: none, small, medium, large (NO FULL/PILL RADII).
  • Elevation: Single elevation architecture (border OR shadow, never both/ghost cards). Shadows must have y-offset and blur (no zero-offset glow halos).
  • Motion: duration, easing curves
  • States: active, disabled, hover variables

Semantic Token Naming

Examples of good token naming:

  • color-surface-elevated
  • text-primary-inverse
  • space-layout-gutter
  • radius-control-default

Component States

Require rigorous component states. Ensure you design and implement the following states for interactive components:

  • Default: The resting state.
  • Hover: (Where relevant, primarily web)
  • Pressed: Active state during interaction.
  • Focus: Keyboard or programmatic focus.
  • Disabled: Uninteractive and visually muted.
  • Loading: Awaiting data or action completion.
  • Selected: Chosen option in a set.
  • Error: Invalid state.
  • Success: (Where applicable)

Anti-Slop Component Rules

  1. No Pill Components: Do NOT build or use pill badges, pill tags, pill chips, or floating pill containers (rounded-full enclosures). Structure metadata and labels with crisp typography, micro-borders, or simple layout hierarchy.
  2. No Icon Background Containers: Do NOT build component wrappers that add colored background fills, tinted boxes, circular backdrops, or square containers behind icons (e.g. bg-primary/10 rounded-xl p-3). Icons must render cleanly directly on the surface.
  3. Image Primacy: Design components to showcase rich visual media (screenshots, photography, 3D assets, architecture diagrams) rather than repetitive icon containers.

Documentation

Document your component structures using the docs/design-system-template.md format.

Frequently asked questions

What does the Ui Components Design System AI skill do?

Creates maintainable component systems, design tokens, variants and interaction states for web and mobile apps.

Why use Ui Components Design System on TypingMind?

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

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/thakur698/universal-ui-skills/tree/main/.agents/plugins/universal-ui/skills/ui-components-design-system. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Ui Components Design System?

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 Ui Components Design System?

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

Is the Ui Components Design System AI skill free?

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

Related AI Skills

View all
NousResearch logo

Tldraw Offline

NousResearch
OrganizationPopular

Drive and script tldraw offline canvases with an agent.

53.5K
250.4K
3 files
View
anthropics logo

Brand Guidelines

anthropics
OrganizationPopular

Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual…

21.8K
184K
Instructions
View
openclaw logo

Solid

openclaw
OrganizationPopular

Write, port, review, or test Solid 2 UI in OpenClaw (Control UI, plugin views, Canvas hosts), including state ownership, Lit interop during the migration, native overlays, testing, performance, and…

82.4K
391.7K
9 files
View
openclaw logo

Canvas

openclaw
OrganizationPopular

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

82.2K
391K
Instructions
View

Set up your own AI workspace now

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