debug-ui-layout

Measure text rendering and adjust copy for clean line breaks.

588|9|Updated Jun 13, 2018
One-click install
npx skills add https://github.com/s4wave/spacewave --skill debug-ui-layout
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug-ui-layout
Source: https://github.com/s4wave/spacewave/tree/main/.claude/skills/debug-ui-layout
Command: npx skills add https://github.com/s4wave/spacewave --skill debug-ui-layout

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Long UI copy often wraps awkwardly, creating orphaned words and inconsistent line counts across viewports. This Skill provides a repeatable workflow to measure rendering and tune copy for clean, readable layouts.

Core Features & Use Cases

  • Measure rendered line counts and line breaks with the spacewave-debug bridge.
  • Iteratively adjust wording to eliminate orphans and widows and balance lines in responsive layouts.
  • Apply to headings, paragraphs, and captions in web UIs for clearer, more accessible content.

Quick Start

Iteratively tune on-screen copy using the spacewave-debug eval bridge to ensure clean line breaks across viewports.

Frequently Asked Questions about debug-ui-layout

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix orphaned words and awkward line breaks in responsive UI text?

To fix orphaned words and awkward line breaks in UI text, measure how copy renders at current viewport widths and iteratively adjust wording to achieve clean wrapping and balanced line counts.

How do I measure rendered line counts for web UI copy across viewports?

You measure rendered line counts by using the spacewave-debug eval bridge to collect per-element dimensions and line counts, verifying how text wraps against expected layouts at varying viewport widths.

Do I need the spacewave-debug integration to debug UI layout text?

Yes, you need the spacewave-debug integration to run eval scripts and verify line breaks against expected layouts, as it provides the bridge to collect per-element dimensions and line counts.

What is the best way to balance headings and paragraphs to avoid widows in web UIs?

The best way to balance headings and paragraphs to avoid widows is to iteratively tune on-screen copy using eval measurements, adjusting wording until lines are balanced across responsive viewports.

Why does my UI copy wrap inconsistently across different screen sizes?

UI copy wraps inconsistently across screen sizes because long text creates orphaned words and varying line counts, requiring iterative wording adjustments based on measured per-element dimensions at each viewport width.

Can I apply UI copy debugging to captions and headings, or just paragraphs?

You can apply UI copy debugging to headings, paragraphs, and captions in web UIs, measuring rendered line counts and adjusting wording to ensure clearer, more accessible content across all text elements.