Skip to content
Skills Library
Design & UX · Analysis

visual-design-system

/visual-design-system

Use when choosing or reviewing typography, type scale, colour palette, dark mode, icons, imagery, elevation, a spacing scale, design tokens or a style guide for a mobile or responsive product. Do not use for a full accessibility audit (accessible-design), screen layout (adaptive-layout-and-spacing) or brand strategy and illustration.

Licence
MIT
Last repository change
10.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 10.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when choosing or reviewing typography, type scale, colour palette, dark mode, icons, imagery, elevation, a spacing scale, design tokens or a style guide for a mobile or responsive product. Do not use for a full accessibility audit (accessible-design), screen layout (adaptive-layout-and-spacing) or brand strategy and illustration.

Original author description

Use when choosing or reviewing typography, type scale, colour palette, dark mode, icons, imagery, elevation, a spacing scale, design tokens or a style guide for a mobile or responsive product. Do not use for a full accessibility audit (accessible-design), screen layout (adaptive-layout-and-spacing) or brand strategy and illustration.

How it works

  1. Hard rules
  2. Gate
  3. Steps
  4. Checklist (copy into the reply and tick as you go)
  5. Examples
  6. Common issues
  7. Next
Original SKILL.md headings · 69 lines, 753 words
SKILL.md preview
---
name: visual-design-system
description: >
  Use when choosing or reviewing typography, type scale, colour palette, dark
  mode, icons, imagery, elevation, a spacing scale, design tokens or a style
  guide for a mobile or responsive product. Do not use for a full accessibility
  audit (accessible-design), screen layout (adaptive-layout-and-spacing) or
  brand strategy and illustration.
---

# Visual Design System

Stance: frozen are legibility, semantic colour roles and consistency with the platform. Flexible are brand colours, typeface and personality, within contrast and scaling limits.

## Hard rules

- Use text styles that scale with system settings, not fixed pixel sizes. Mechanism: people who enlarge text get nothing from hard-coded sizes. Apple's default is 17 pt on iPhone with an 11 pt floor (Apple HIG); Toptal recommends no smaller than 11 pt.
- Meet contrast: 4.5:1 for normal text, 3:1 for large text (18 pt, or bold) and for controls and icons that carry meaning. Mechanism: WCAG 1.4.3 and 1.4.11; low contrast fails in sunlight and for low vision.
- Check contrast in light and dark separately. Mechanism: a pair that passes in light often fails inverted.
- Name colours by role (background, surface, text, accent, danger), not by hue. Mechanism: role tokens map cleanly to dark mode and rebranding; hue names break.
- Never use colour alone for meaning; add an icon, text or shape. Mechanism: colour-blind users and bright glare lose the signal.
- Prefer platform system fonts and colours unless the brand needs otherwise. Mechanism: they adapt to Dynamic Type, Increase Contrast and dark mode for free.
- Use one spacing scale and one icon style. Mechanism: mixed values read as errors and slow scanning.
- Avoid light font weights at small sizes. Mechanism: thin strokes disappear first on small, low-resolution or bright screens.
- Act only on what the user asked. Before answering or changing anything, open the relevant files and check what is already done; report only what you checked, never guess, and do not redo finished work. Reason: guesses and repeated work waste the user's credit.

## Gate

| Situation | Action |
|---|---|
| Project already has tokens | Use them; add only what is missing, with reasons |
| No system exists | Propose a minimal set: type scale, colour roles, spacing scale, radii, elevation, icon set |
| Brand colour fails contrast | Keep brand for large shapes; use a darker or lighter shade for text and controls |
| Request for pixel-perfect fixed type | Explain scaling; give sizes as starting values for text styles |

## Steps

1. **Detect.** Read the existing tokens, theme file and components. List the typeface, sizes, colours.
2. **Type.** Define styles (title, headline, body, caption, label) with size, weight and line height; looser leading for long text; allow wrapping and growth.
3. **Colour.** Define roles for light and dark; compute contrast for each text and control pair using a calculator; mark status colours with an icon.
4. **Space and shape.** Define the spacing scale (multiples of 4 or 8), corner radii and elevation levels; keep touch areas independent of visible size.
5. **Icons and imagery.** One set, one stroke weight, labelled where meaning is unclear; provide alt text for informative images.
6. **Record** tokens and rules in a style guide (see [ux-documentation-and-handoff](../ux-documentation-and-handoff/SKILL.md)).
7. **Verify** at the largest text size, in dark mode, with Increase Contrast, and in bright light on a real phone if possible.

## Checklist (copy into the reply and tick as you go)

```text
- [ ] Text styles scale; no fixed sizes
- [ ] Contrast computed for every text and control pair, in both themes
- [ ] Colours named by role
- [ ] Meaning never carried by colour alone
- [ ] One spacing scale, one icon style
- [ ] Tokens recorded
```

## Examples

**Example 1: brand colour on white**
User says: "Our brand light green with white text on buttons, can we use it?"
Actions: compute the ratio; if below 4.5:1 propose a darker green for the button fill (or dark text on the light green); keep the light green for decoration.
Result: brand feel kept, buttons readable.

**Example 2: invert for dark mode**
User says: "Just invert the colours for dark mode."
Actions: explain that inversion breaks contrast and elevation cues; define role tokens for dark and check each pair.
Result: a proper dark theme with verified contrast.

## Common issues

- **Colours look fine on the design screen, washed out outdoors.** Cause: marginal contrast. Fix: raise to at least the AA ratios, preferably higher for key text.
- **Text overflows at large sizes.** Cause: fixed heights. Fix: allow growth and test at the largest setting.
- **Status shown by red and green only.** Cause: colour-only signal. Fix: add icon and text.

## Next

[accessible-design](../accessible-design/SKILL.md) for the full check; [interaction-feedback-and-forms](../interaction-feedback-and-forms/SKILL.md) for state styling.

Versions

The database has no other skills named visual-design-system.

Database snapshot: 13.11.2026 · package version 47fe95d0f7c2 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 95wicked-garden-product-visual-review
    Use when auditing visual design for consistency — design system adherence, spacing tokens, typography scale, color palette, component patterns, and responsive polish. Structured checklist + scoring. NOT for UX flows or user research (use ux-review) or accessibility code audits…
  • 100vectreal-brand-ux-design
    Use for any change a user can see in Vectreal: component styling, layout, spacing, color, typography, elevation, motion, empty/loading/error states, responsive behavior, accessibility, and marketing UI. Triggers: design, styling, className, Tailwind, token, theme, dark mode,…
  • 90figma-design-patterns
    Use when designing, editing, or reviewing Figma UI layout craft for auto layout, components, spacing, typography, states, dark mode, or handoff.
  • 95brand-visual-generator
    When the user wants to define, audit, or apply visual identity (typography, colors, spacing, design tokens, frontend aesthetics). Also use when the user mentions "brand style guide," "visual identity," "design system," "typography," "color palette," "brand guidelines," "AI brand…
  • 100analyse-design
    Reverse-engineer an application, website or document's design system from its codebase and screenshots. Use when asked to analyse visual design, extract a colour palette, document UI patterns, identify typography and spacing systems, audit design consistency, or understand the…
  • 100web-visual-design
    Use when choosing a website's colours or fonts, writing design tokens or a type and layout spec, setting Chinese or bilingual Chinese-English typography, deciding layout hierarchy, or reviewing a site's visual design. Triggers include 配色, 挑字體, 字型, 中文排版, 中英混排, 版面層次, palette, dark…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.