Ui Design logo

Ui Design

Community
flitzrrr
ui-design

Layouts, components, visual hierarchy, grid systems, and design systems for professional web interfaces. Defines rules for grid systems, whitespace, styleguides, design tokens, and UI patterns.

Overview

Publisherflitzrrr
Repositoryfrontend-design-skills
Skill nameui-design
Stars
9
Forks
2
Bundled files
1
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.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by flitzrrr on GitHub. Read the source before you install it.

Installation

Install the Ui Design 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/flitzrrr/frontend-design-skills/tree/main/skills-src/ui-design
  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/flitzrrr/frontend-design-skills.git /tmp/frontend-design-skills
mkdir -p .claude/skills
cp -r /tmp/frontend-design-skills/skills-src/ui-design .claude/skills/ui-design
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Ui Design 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 Design 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 Design 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 Design

Professional web interfaces through systematic layouts, clear visual hierarchy, and consistent components.

Scope

Use this skill when: You are creating layouts, designing UI components, establishing visual hierarchy, defining grid systems, building styleguides or design tokens, or auditing existing interfaces for visual consistency.

Principles

1. User-Centered Design Over Aesthetics

Every design decision is guided by the needs of the target audience. An interface that is visually impressive but poorly usable has failed.

2. Visual Hierarchy Determines Perception

Size, color, contrast, and position control what users see first. Every page needs exactly ONE primary focal point.

3. Consistency Builds Trust

Identical elements must look and behave identically everywhere. Inconsistency increases cognitive load.

4. Reduction Is Strength

Every element without a measurable purpose must be removed. Whitespace is not wasted space -- it improves readability and focus.

5. The Grid Is the Foundation

Without a grid system, there is no professional layout. The grid enforces alignment, creates rhythm, and enables responsive design.

Rules

Layout & Grid

  • DO: Use a 12-column grid as the basis for desktop (divisible by 2, 3, 4, 6).
  • DO: Use an 8px baseline grid for all spacing (8, 16, 24, 32, 48, 64px).
  • DO: Set a maximum content width of 1200-1440px.
  • DON'T: Mix different grid systems within one application.
  • DON'T: Place more than 3-4 content blocks side by side on desktop, or more than 1-2 on mobile.

Visual Hierarchy

  • DO: Establish at least 3 hierarchy levels: primary (hero), secondary (features), tertiary (details).
  • DO: Make the most important element at least 1.5x larger than the second most important.
  • DON'T: Use more than 3 different font sizes within a single viewport area.
  • DON'T: Place multiple equally weighted CTAs in the same viewport. One primary CTA per viewport.

Components

  • DO: Use established UI patterns for standard interactions.
  • DO: Define clear states for all input elements: default, hover, focus, active, disabled, error.
  • DO: Include progress indicators for multi-step processes.
  • DON'T: Invent new interaction patterns for standard tasks.

Whitespace & Spacing

  • DO: Use generous whitespace between sections (min. 64-96px vertical on desktop).
  • DO: Place related elements close together, separate groups far apart (Gestalt law of proximity).
  • DON'T: Fill empty space with decorative elements.

Styleguide & Design Tokens

  • DO: Create a UI styleguide BEFORE implementation: colors, typography, icons, buttons, spacing.
  • DO: Use design tokens: --color-primary, --spacing-lg, --font-heading.
  • DON'T: Use magic numbers (hard-coded pixel values) instead of token references.

Patterns

Detailed pattern descriptions: see references/patterns.md

Hero Section

Large-scale visual + concise headline (max. 7 words) + subline + primary CTA in a contrasting color. Must communicate the core message within 3 seconds.

Card Layout (Bento Grid)

Modular cards in a grid. Each card is a self-contained information unit. Max. 6-9 cards in the initial viewport on desktop, 2-3 on mobile.

Split Screen

Two equally weighted halves -- one visual, one textual. Stack vertically on mobile.

Sticky Navigation

Header remains visible on scroll. Active section is highlighted. Max. height 64px.

Modals & Overlays

Centered overlay with a dimmed background. Clear close button. Focus trap. Escape closes.

Anti-Patterns

Overloaded Interfaces

Too many elements, too little whitespace, competing CTAs. Solution: One page = one primary goal.

Inconsistent Styles

Buttons that look different across pages. Solution: Create and enforce a styleguide.

Dark Patterns

Manipulative design (hidden unsubscribe buttons, confirm shaming). Solution: Every interaction must be transparent and in the user's interest.

Carousel as Content Strategy

Auto-carousels: only slide 1 is noticed (< 1% click rate on slides 2+). Solution: Static hero or manual tabs.

Scroll Hijacking

Overriding native scroll behavior. Solution: Preserve native scrolling, keep animations subtle.

Checklist

  • 12-column grid with 8px baseline defined?
  • Maximum content width set (1200-1440px)?
  • Visual hierarchy verifiable: primary, secondary, tertiary levels?
  • Only ONE primary CTA per viewport?
  • All components have defined states (default, hover, focus, active, disabled, error)?
  • Whitespace between sections consistent and generous (min. 64px)?
  • Styleguide/design tokens in place and applied?
  • No magic numbers -- all values reference tokens?
  • No scroll hijacking or auto-carousel?
  • Dark patterns ruled out?
  • Modals have focus trap and escape-to-close?

Cross-References

  • web-typography -- Font selection and sizing for hierarchy
  • color-theory -- Color systems and contrast rules
  • accessibility -- WCAG compliance for all UI components
  • usability -- Heuristics for user-friendliness
  • responsive-design -- Grid behavior across breakpoints
  • design-trends -- Current award-winning UI patterns
  • component-patterns -- Technical component implementation
  • visual-direction -- Visual direction and style decisions

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Ui Design AI skill do?

Layouts, components, visual hierarchy, grid systems, and design systems for professional web interfaces. Defines rules for grid systems, whitespace, styleguides, design tokens, and UI patterns.

Why use Ui Design on TypingMind?

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

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/flitzrrr/frontend-design-skills/tree/main/skills-src/ui-design. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Ui Design?

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

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

Is the Ui Design AI skill free?

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