cross-browser-typography-qa

Diagnose and repair web typography rendering defects across Chromium, WebKit, and Safari.

115|9|Updated Aug 5, 2026
One-click install
npx skills add https://github.com/AtlasOmnia/donna-starter --skill cross-browser-typography-qa-atlasomnia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cross-browser-typography-qa
Source: https://github.com/AtlasOmnia/donna-starter/tree/main/skills/software-development/cross-browser-typography-qa
Command: npx skills add https://github.com/AtlasOmnia/donna-starter --skill cross-browser-typography-qa-atlasomnia

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Web text often looks clipped, flattened, miswrapped, or inconsistent between Chromium and Safari even when DOM geometry checks pass. This Skill provides a structured workflow to reproduce, diagnose, repair, and verify typography rendering defects so glyph-level paint problems are not missed by geometry-only checks. ## Core Features & Use Cases - Defect reproduction and inspection: Capture focused screenshots, read computed styles, and inspect actual glyphs rather than relying on element bounding boxes. - Targeted repair patterns: Fix clipped gradient-text descenders via line-height correction, protect hyphenated tokens with nowrap spans, resolve flex mixed-inline-content spacing, and calibrate oversized hero scale. - Cross-browser verification: Test at 375, 390, 1024, and 1440 px in both Chromium and native Safari, validate real CSS viewport widths via CDP emulation, and confirm production fixes with cache-busted live screenshots. - Use Case: A deployed landing page shows flattened descenders on a gradient headline in Safari. Use this Skill to reproduce the defect, increase the line box on the gradient element, deploy with a new stylesheet cache marker, and verify the fix from live rendering evidence. ## Quick Start Use the cross-browser-typography-qa skill to diagnose why the lowercase 'g' in my gradient headline looks clipped in Safari and verify the fix on production.

Frequently Asked Questions about cross-browser-typography-qa

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

FAQPage Schema
How do I fix clipped descenders in gradient text with background-clip: text?

Clipped descenders in gradient text are fixed by increasing the line box on the gradient-bearing element, typically line-height 1.18 to 1.22, rather than adding outside padding. Padding enlarges the element but not the painted glyph mask. If the gradient stays unstable, use a solid accessible text color.

Why does my heading wrap awkwardly at a hyphen in Safari?

Headings wrap awkwardly when a semantic hyphenated token like 'add-ins' breaks across lines at narrow viewports. Wrap only that token in an inline span with white-space: nowrap, keeping the literal hyphen for exact-copy tests and search indexing. Never force the entire heading onto one line.

Can Chromium screenshots replace native Safari testing?

No, Chromium at Safari-like dimensions is not a Safari acceptance gate because WebKit handles font metrics, line height, and paint differently. Verify fixes in both Chromium and native Safari at the exact reported viewport widths before closing a typography defect.

Why does my deployed CSS fix not appear on the production site?

A deployment-success message only proves upload completion, not that the live site serves the new stylesheet. Add a new stylesheet cache marker, load a fresh production URL with a query marker, read back the active stylesheet URL and computed values, and inspect a fresh live screenshot.

Why does a narrow headless Chromium screenshot look wrong at 390px?

Some headless Chromium invocations keep a minimum layout viewport around 500 CSS px and crop the screenshot to 390 physical pixels. Read innerWidth in-page, and if it mismatches, use CDP Emulation.setDeviceMetricsOverride and assert the width again before inspecting the screenshot.