typography/SKILL.md
Apply professional typography principles when generating documents, web pages, presentations, or any formatted text output. Use this skill when creating or reviewing HTML/CSS, print documents, resumes, letters, reports, slide decks, emails, or any content where typographic quality matters. Also use when the user asks about font choices, text formatting, spacing, layout, or typographic best practices.
npx skillsauth add rhino-labs/skills typographyInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Professional typography guidelines based on Butterick's Practical Typography. Apply these rules when generating any formatted output.
Body text is the most important element — it comprises the majority of any document. Get body text right first, then style everything else relative to it.
line-height (e.g., 1.3–1.45)-): compound words, line breaks–): ranges (1990–2000, pp. 10–15), connections (liberal–conservative)—): parenthetical breaks — stronger than commas, lighter than parentheses--)smcp feature), never fakedFor detailed layout rules, see references/layout.md.
line-height with unitless valuesmax-width (e.g., max-width: 33em)text-indent for first-line indents, not marginsletter-spacing: 0.05em–0.12em for caps/small-capsfont-variant: small-caps for real small caps<ul>/<ol> for lists, never manual bulletsFor tables, lists, block quotations, and sample document guidance, see references/elements.md.
development
Generate a complete set of favicons (ICO, PNGs, web manifest) from a source image, then wire them into the project's framework (Next.js metadata, Rails layout, Astro head, plain HTML, etc.). Use when the user asks to create, generate, update, or replace favicons, app icons for the web, or wants a `favicon.ico` / `apple-touch-icon` / `site.webmanifest` from a source image (PNG, JPG, SVG, WEBP, GIF).
development
Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.
development
Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.
development
Run, watch, debug, and extend OpenClaw QA testing with qa-lab and qa-channel. Use when Codex needs to execute the repo-backed QA suite, inspect live QA artifacts, debug failing scenarios, add new QA scenarios, or explain the OpenClaw QA workflow. Prefer the live OpenAI lane with regular openai/gpt-5.4 in fast mode; do not use gpt-5.4-pro or gpt-5.4-mini unless the user explicitly overrides that policy.