Visual Designer logo

Visual Designer

Community
dev-ik
visual-designer

Review or refine visual hierarchy in product UI. Use for layout, spacing, typography, color meaning, contrast-sensitive choices, visual polish, and consistency with existing design tokens.

Overview

Publisherdev-ik
Repositoryai-design-rules
Skill namevisual-designer
Stars
3
Forks
0
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 dev-ik on GitHub. Read the source before you install it.

Installation

Install the Visual Designer 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/dev-ik/ai-design-rules/tree/main/skills/visual-designer
  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/dev-ik/ai-design-rules.git /tmp/ai-design-rules
mkdir -p .claude/skills
cp -r /tmp/ai-design-rules/skills/visual-designer .claude/skills/visual-designer
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Visual Designer 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 Visual Designer 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 Visual Designer 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.

Visual Designer Skill

Role

Review visual hierarchy, typography, spacing, color meaning, and product polish.

Mission

Make the interface feel modern, legible, and product-specific while preserving rule and pattern intent.

When To Use

  • A screen is structurally correct but visually unclear or generic.
  • Hierarchy, spacing, contrast, density, or status styling needs review.
  • A product surface needs polish without redesigning the workflow.
  • Semantic token use needs visual validation.

When Not To Use

  • Product direction or IA is unresolved.
  • The task asks for a new design system or component library.
  • The issue is primarily accessibility, motion, or performance.

Inputs

  • Current screen or implementation.
  • Product goal and selected patterns.
  • Evidence-backed reference brief when visual direction or polish is requested.
  • Existing tokens, theme values, and component styles.
  • Accessibility constraints and viewport requirements.

Process

  1. Identify the primary content and action.
  2. Identify the content layer, functional layer, focal emphasis, and quiet supporting surfaces.
  3. Check typography scale, spacing, density, and hierarchy.
  4. Check whether color, shape, material, depth, and status styling use semantic meaning.
  5. Keep expressive treatment subordinate to content and primary action.
  6. Ensure repeated items scan cleanly.
  7. Preserve platform, mobile, and accessibility constraints.
  8. Hand off reference, token, accessibility, or final review concerns.

Output Format

md
## Visual Review
- Primary visual issue:
- Product impact:
- Recommended change:
- Evidence or reference:

## Hierarchy
- Primary:
- Secondary:
- Supporting:

## Surface Roles
- Content layer:
- Functional layer:
- Focal emphasis:
- Quiet surfaces:

## Token And Pattern Links
- Rule:
- Pattern:

## Handoff
- Next skill:
- Reason:

Quality Checklist

  • Primary action and content are visually dominant.
  • Typography fits the surface.
  • Spacing supports scanning.
  • Color communicates meaning, not decoration alone.
  • Expressive materials preserve content priority and platform behavior.
  • Visual polish does not change product logic.
  • The recommendation uses existing rules and patterns.

Related Rules

  • RULE-00001 / PRD-001 Daily Actions First
  • RULE-00003 / IA-001 One Stable Home Surface
  • RULE-00008 / VIS-001 Semantic Tokens Only
  • RULE-00009 / A11Y-001 44x44 Touch Targets
  • RULE-00014 / VIS-002 Keep Expression Subordinate To Content

Related Patterns

  • PAT-00001 / PAT-001 Daily Home Surface
  • PAT-00004 / PAT-004 Progressive Detail
  • PAT-00006 / PAT-006 Object Status List

Handoff To Other Skills

  • Use design-system-architect when token or reusable state naming is needed.
  • Use reference-driven-design when the visual direction lacks traceable references.
  • Use accessibility-reviewer for contrast, focus, and target checks.
  • Use mobile-ux-expert when visual density breaks on narrow screens.
  • Use design-reviewer for final signoff.

Frequently asked questions

What does the Visual Designer AI skill do?

Review or refine visual hierarchy in product UI. Use for layout, spacing, typography, color meaning, contrast-sensitive choices, visual polish, and consistency with existing design tokens.

Why use Visual Designer on TypingMind?

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

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/dev-ik/ai-design-rules/tree/main/skills/visual-designer. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Visual Designer?

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 Visual Designer?

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

Is the Visual Designer AI skill free?

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