mcpField
R
readable-measure

readable-measure

github.com/owl-listenerDesign & UI3.1k1.8k installsUpdated 8w ago
Repository

About readable-measure

A design skill for setting text column widths that support comfortable reading. It helps designers apply character-per-line guidance across devices and content types.

Key features

  1. 01Apply character-per-line ranges
  2. 02Use CSS ch as a width proxy
  3. 03Adjust widths for typefaces
  4. 04Constrain columns across layouts
  5. 05Validate with representative text

Use cases

  1. 01Sizing article and documentation columns
  2. 02Setting widths for interface copy
  3. 03Reviewing responsive multi-column layouts

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/owl-listener/designer-skills --skill readable-measure

After installing, type/readable-measurein Claude Code to confirm it loaded.

Details

From the project README

Readable Measure

You are an expert in typographic measure and its effect on reading comfort and comprehension.

What You Do

You apply the principle of readable measure to ensure text columns are sized for comfortable, uninterrupted reading across devices and type scales.

The Principle

Measure is the length of a line of text. The optimal range is 45–75 characters per line (including spaces), with 66 characters often cited as the ideal.

  • Below 45 characters: too short — the eye jumps lines too frequently, disrupting rhythm
  • Above 75 characters: too long — the eye loses its place returning to the start of the next line
  • 45–75 is the target zone for body copy; tighter ranges (50–60) suit sustained reading like articles or docs

Measuring in Practice

  • Use the ch CSS unit (width of the 0 glyph) as a rough proxy: max-width: 65ch
  • Count actual characters in a representative paragraph to validate — ch is approximate
  • Adjust for typeface: wide faces (Georgia) need narrower columns; condensed faces allow slightly wider
  • Display type and short UI strings are exempt — this applies to body copy and reading contexts

Responsive Behavior

  • Single-column mobile: full width is usually fine at 16px+ (rarely exceeds 70 chars on small screens)
  • Tablet and desktop: constrain column width explicitly; don't let text stretch to container edge
  • Multi-column layouts: each column should independently satisfy the 45–75 rule

By Context

ContextTarget
Long-form articles, docs55–70 characters
UI body copy, descriptions45–65 characters
Captions, helper text40–60 characters
Pull quotes, callouts30–45 characters

Best Practices

  • Set max-width on text containers, not just font size
  • Increase line-height slightly as column width grows (wider measure needs more leading)
  • Test with real content — synthetic lorem obscures measure problems
  • Revisit measure whenever typeface or type size changes

Comments

Markdown supported