Design References logo

Design References

Organization
MadAppGang
design-references

Predefined design system references for UI reviews. Includes Material Design 3, Apple Human Interface Guidelines, Tailwind UI, Ant Design, and Shadcn/ui. Use when conducting design reviews against established design systems.

Overview

PublisherMadAppGang
Repositoryclaude-code
Skill namedesign-references
Stars
281
Forks
26
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 MadAppGang on GitHub. Read the source before you install it.

Installation

Install the Design References 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.
  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/MadAppGang/claude-code.git /tmp/claude-code
mkdir -p .claude/skills
cp -r /tmp/claude-code/plugins/dev/skills/design/design-references .claude/skills/design-references
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Design References 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 References 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 References 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.

Design References Skill

Overview

This skill provides predefined design system references that the ui agent can use when reviewing designs. Each reference includes design principles, color guidelines, typography rules, spacing patterns, and component patterns.

Available Design Systems

Material Design 3 (Google)

Reference ID: material-3 Official URL: https://m3.material.io/

Design Principles
  1. Adaptive & Accessible - Responsive across devices, accessible to all
  2. Personal & Customizable - Dynamic color, personalization
  3. Expressive - Motion, shape, and color express brand
Color System
  • Dynamic Color - Colors derived from user wallpaper or brand
  • Tonal Palettes - 13 tones per color (0-100)
  • Color Roles:
    • Primary: Main brand color
    • Secondary: Accent elements
    • Tertiary: Contrast and balance
    • Error: Destructive actions
    • Surface: Backgrounds and containers
    • On-*: Text/icon colors on surfaces

Key Metrics:

  • Text contrast: 4.5:1 minimum (WCAG AA)
  • Large text contrast: 3:1 minimum
  • Non-text contrast: 3:1 minimum
Typography

Type Scale (Default):

RoleSizeWeightLine Height
Display Large57sp40064sp
Display Medium45sp40052sp
Display Small36sp40044sp
Headline Large32sp40040sp
Headline Medium28sp40036sp
Headline Small24sp40032sp
Title Large22sp40028sp
Title Medium16sp50024sp
Title Small14sp50020sp
Body Large16sp40024sp
Body Medium14sp40020sp
Body Small12sp40016sp
Label Large14sp50020sp
Label Medium12sp50016sp
Label Small11sp50016sp

Font: Roboto (sans-serif)

Spacing

Baseline Grid: 4dp Common Values: 4, 8, 12, 16, 24, 32, 48, 64, 96, 128

Component Patterns
  • Buttons: Filled, Outlined, Text, Elevated, Tonal
  • Cards: Elevated, Filled, Outlined
  • Navigation: Rail, Bar, Drawer
  • Inputs: Filled, Outlined
  • Dialogs: Basic, Full-screen, Date picker
Review Checklist
  • Dynamic color theming applied correctly
  • Type scale follows M3 specs
  • 4dp baseline grid followed
  • Touch targets minimum 48dp
  • Elevation levels correct (0-5)
  • Shape scale appropriate (Extra small to Extra large)

Apple Human Interface Guidelines (iOS/macOS)

Reference ID: apple-hig Official URL: https://developer.apple.com/design/human-interface-guidelines/

Design Principles
  1. Clarity - Text readable, icons precise, ornaments subtle
  2. Deference - Content over chrome, minimal UI
  3. Depth - Visual layers, motion conveys hierarchy
Color System

System Colors:

ColorLight ModeDark ModeUsage
Blue#007AFF#0A84FFLinks, interactive elements
Green#34C759#30D158Success, positive actions
Indigo#5856D6#5E5CE6Accent
Orange#FF9500#FF9F0AWarnings, attention
Pink#FF2D55#FF375FAccent
Purple#AF52DE#BF5AF2Accent
Red#FF3B30#FF453ADestructive, errors
Teal#5AC8FA#64D2FFAccent
Yellow#FFCC00#FFD60AWarnings

Semantic Colors:

  • Label (Primary, Secondary, Tertiary, Quaternary)
  • Fill (Primary through Quaternary)
  • Background (Primary, Secondary, Tertiary)
  • Separator
Typography

SF Pro (San Francisco):

StyleSizeWeightLeading
Large Title34ptBold41pt
Title 128ptRegular34pt
Title 222ptRegular28pt
Title 320ptRegular25pt
Headline17ptSemi-Bold22pt
Body17ptRegular22pt
Callout16ptRegular21pt
Subheadline15ptRegular20pt
Footnote13ptRegular18pt
Caption 112ptRegular16pt
Caption 211ptRegular13pt
Spacing

iOS Standard Margins: 16pt (compact), 20pt (regular) macOS Standard Margins: 20pt

Component Patterns
  • Navigation: Tab Bar, Sidebar, Navigation Bar
  • Buttons: System, Custom, Icon-only
  • Lists: Plain, Grouped, Inset Grouped
  • Forms: Grouped sections with headers
Review Checklist
  • SF Pro or SF Mono fonts used
  • System colors or semantically appropriate custom colors
  • Touch targets minimum 44pt x 44pt
  • Standard margins respected
  • Navigation patterns match platform conventions
  • Dark mode support with proper semantic colors

Tailwind UI

Reference ID: tailwind-ui Official URL: https://tailwindui.com/

Design Principles
  1. Utility-First - Compose styles from atomic classes
  2. Responsive - Mobile-first, breakpoint prefixes
  3. Consistent - Design tokens as class names
Color System

Tailwind Colors (50-950 shades):

  • Slate, Gray, Zinc, Neutral, Stone (Grays)
  • Red, Orange, Amber, Yellow (Warm)
  • Lime, Green, Emerald, Teal (Cool greens)
  • Cyan, Sky, Blue, Indigo, Violet, Purple, Fuchsia, Pink, Rose

Usage Patterns:

  • Primary: blue-600 (buttons, links)
  • Secondary: gray-600 (secondary text)
  • Success: green-600
  • Warning: amber-600
  • Error: red-600
  • Background: white / gray-50
  • Surface: gray-100 / gray-800
Typography

Font Scale:

ClassSizeLine Height
text-xs12px16px
text-sm14px20px
text-base16px24px
text-lg18px28px
text-xl20px28px
text-2xl24px32px
text-3xl30px36px
text-4xl36px40px
text-5xl48px48px
text-6xl60px60px
text-7xl72px72px
text-8xl96px96px
text-9xl128px128px

Font Weights: thin(100) to black(900)

Spacing Scale
ClassValue
00px
px1px
0.52px
14px
28px
312px
416px
520px
624px
832px
1040px
1248px
1664px
2080px
2496px
Component Patterns
  • Buttons: Primary, Secondary, Soft, Outline
  • Forms: Stacked, Inline, with validation states
  • Cards: Simple, with header, with footer
  • Navigation: Navbar, Sidebar, Tabs
Review Checklist
  • Spacing uses Tailwind scale (4px base)
  • Typography uses Tailwind type scale
  • Colors from Tailwind palette
  • Consistent hover/focus states
  • Responsive breakpoints (sm, md, lg, xl, 2xl)
  • Dark mode with dark: variants

Ant Design

Reference ID: ant-design Official URL: https://ant.design/

Design Principles
  1. Natural - Align with user mental models
  2. Certain - Predictable, consistent behavior
  3. Meaningful - Purpose-driven design
  4. Growing - Support user skill progression
Color System

Functional Colors:

RoleHexUsage
Primary#1677ffBrand, primary actions
Success#52c41aPositive feedback
Warning#faad14Warnings, attention
Error#ff4d4fErrors, destructive
Info#1677ffInformational

Neutral Colors: 13 shades of gray (#fff to #000)

Typography

Font Family: -apple-system, BlinkMacSystemFont, Segoe UI, Roboto, Helvetica Neue

RoleSizeWeight
h138px600
h230px600
h324px600
h420px600
h516px600
Base14px400
Small12px400
Spacing

Base Unit: 4px Scale: 4, 8, 12, 16, 20, 24, 32, 40, 48

Component Patterns
  • Forms: Horizontal, Vertical, Inline layouts
  • Tables: Sortable, Filterable, Paginated
  • Modals: Confirm, Info, with footer
  • Data Entry: Extensive input types
Review Checklist
  • 14px base font size
  • 4px spacing base unit
  • Functional colors for feedback
  • Form layouts consistent
  • Table patterns for data display
  • Enterprise-grade density (compact option)

Shadcn/ui

Reference ID: shadcn-ui Official URL: https://ui.shadcn.com/

Design Principles
  1. Copy-Paste - Components you own, not import
  2. Accessible - Built on Radix UI primitives
  3. Customizable - CSS variables for theming
  4. Composable - Small, focused components
Color System

CSS Variables Based:

css
--background: 0 0% 100%;
--foreground: 240 10% 3.9%;
--card: 0 0% 100%;
--card-foreground: 240 10% 3.9%;
--popover: 0 0% 100%;
--popover-foreground: 240 10% 3.9%;
--primary: 240 5.9% 10%;
--primary-foreground: 0 0% 98%;
--secondary: 240 4.8% 95.9%;
--secondary-foreground: 240 5.9% 10%;
--muted: 240 4.8% 95.9%;
--muted-foreground: 240 3.8% 46.1%;
--accent: 240 4.8% 95.9%;
--accent-foreground: 240 5.9% 10%;
--destructive: 0 84.2% 60.2%;
--destructive-foreground: 0 0% 98%;
--border: 240 5.9% 90%;
--input: 240 5.9% 90%;
--ring: 240 5.9% 10%;
--radius: 0.5rem;
Typography

Inter (default) or system font stack

VariantSizeWeightLeading
h136px80040px
h230px60036px
h324px60032px
h420px60028px
p16px40028px
lead20px40028px
large18px60028px
small14px50020px
muted14px40020px
Spacing

Tailwind-based: 4px base (matches Tailwind scale)

Component Patterns
  • Buttons: Default, Secondary, Destructive, Outline, Ghost, Link
  • Forms: Built on Radix primitives
  • Dialogs: AlertDialog, Dialog, Sheet
  • Data Display: Table, DataTable, Cards
Review Checklist
  • CSS variables for theming
  • Radix UI primitives for accessibility
  • Border radius using --radius variable
  • Focus rings using --ring variable
  • Consistent variant naming
  • Dark mode via class strategy

Usage in Reviews

Selecting a Design Reference

The ui agent will check for style in this order:

  1. Project Style (.claude/design-style.md) - Highest priority
  2. Predefined Reference (via Design Reference: directive or user selection)
  3. Auto-detect (if recognizable patterns found)
  4. Generic Best Practices (fallback)

Review with Specific Reference

Task: ui

Review this dashboard screenshot against Material Design 3 guidelines.

Design Reference: material-3

Image: screenshots/dashboard.png

Write review to: ${SESSION_PATH}/reviews/design-review/gemini.md

Combining Project Style + Reference

Task: ui

Review using:
- Project Style: .claude/design-style.md (brand colors, custom tokens)
- Base Reference: shadcn-ui (component patterns, accessibility)

Image: screenshots/form.png

Frequently asked questions

What does the Design References AI skill do?

Predefined design system references for UI reviews. Includes Material Design 3, Apple Human Interface Guidelines, Tailwind UI, Ant Design, and Shadcn/ui. Use when conducting design reviews against established design systems.

Why use Design References on TypingMind?

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

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

Which AI models can use Design References?

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

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

Is the Design References AI skill free?

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