Agent skill

Readability Rhythm And Prose

by hashgraph-online in hashgraph-online/awesome-codex-plugins

Apply paragraph rhythm and prose-level readability — calibrating leading, paragraph spacing, subheading frequency, and visual breathing room so that long-form text reads smoothly without fatigue.

Apache-2.0Auto-check passedWriting & Content

Install Readability Rhythm And Prose

skills CLI
$ npx skills add hashgraph-online/awesome-codex-plugins --skill readability-rhythm-and-prose -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install hashgraph-online/awesome-codex-plugins readability-rhythm-and-prose --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/HDeibler/universal-design-principles/plugins/perception-and-hierarchy-principles/skills/readability-rhythm-and-prose .claude/skills/readability-rhythm-and-prose && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
readability-rhythm-and-prose
GitHub stars
1.3k
Token cost
~2.5k tokens
SKILL.md length
1,362 words
Files
2 (incl. references)
Skills in repo
716
Repo updated
First seen
Licence
Apache-2.0

At a glance

Apply paragraph rhythm and prose-level readability — calibrating leading, paragraph spacing, subheading frequency, and visual breathing room so that long-form text reads smoothly without fatigue.

  • Designing article layouts
  • SKILL.md covers Leading (line height) for prose, Paragraph spacing, Subheading frequency and Visual breathing room, plus 7 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Any context with sustained prose

What it does

Readability Rhythm And Prose is an agent skill from hashgraph-online/awesome-codex-plugins. Apply paragraph rhythm and prose-level readability — calibrating leading, paragraph spacing, subheading frequency, and visual breathing room so that long-form text reads smoothly without fatigue. Use when designing article layouts, documentation, reports, transcripts, or any context with sustained prose. Beyond line length and legibility, the rhythm of prose layout — the rest points provided by paragraph breaks, the hierarchy provided by subheadings, the breathing room provided by margins — determines whether…

Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/prose-layout-patterns.md`).

It sits in Writing & Content, covering Plain language and style rules. The repository describes itself as: A curated list of awesome OpenAI Codex / ChatGPT plugins, skills, and resources. The 1 Codex Marketplace. See live plugins at: https://hol.org/plugins/best-codex-plugins. The licence is Apache-2.0.

When your agent uses it

  • Designing article layouts
  • Any context with sustained prose

Example prompts

  • “/readability-rhythm-and-prose”

What it can do on your machine

Read from SKILL.md and the folder at commit 3e1456a. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Readability Rhythm And Prose loads about 2.5k tokens when it runs, and up to ~4.5k if it reads all its reference files. Until then it costs about 146 tokens; SKILL.md has 1,362 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~146
When it runs · the whole SKILL.md, loaded when a task matches
~2.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from hashgraph-online/awesome-codex-plugins at commit 3e1456a, republished under its Apache-2.0 licence (© hashgraph-online). 1,362 words, ~2,509 tokens.

Download SKILL.mdSave it as .claude/skills/readability-rhythm-and-prose/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
readability-rhythm-and-prose
description
Apply paragraph rhythm and prose-level readability — calibrating leading, paragraph spacing, subheading frequency, and visual breathing room so that long-form text reads smoothly without fatigue. Use when designing article layouts, documentation, reports, transcripts, or any context with sustained prose. Beyond line length and legibility, the rhythm of prose layout — the rest points provided by paragraph breaks, the hierarchy provided by subheadings, the breathing room provided by margins — determines whether readers stay engaged with long content.

Readability — rhythm and prose

Beyond line length, readability is determined by the rhythm of prose layout: the spacing between lines, the spacing between paragraphs, the frequency of subheadings, the visual breathing room around the text. Together these create a reading experience that either flows or stutters, that either invites continued reading or discourages it.

The right rhythm makes long content feel approachable. The wrong rhythm makes the same content feel like a wall.

Leading (line height) for prose

Leading is the vertical space between baselines of consecutive lines. For body prose:

1.5× to 1.7× the font size is the comfortable range. So 16px text needs 24–28px line height; 18px text needs 27–31px line height.

Why this range:

  • Tighter than 1.4× makes ascenders and descenders crowd, the eye drift to adjacent lines, and reading slow.
  • Looser than 1.8× makes lines feel disconnected from each other; the prose breaks into discrete strips rather than flowing.
  • The comfortable range balances visual flow (lines connected enough) and visual separation (lines distinct enough).

For UI and dense text (tables, captions, helper text), tighter leading (1.3–1.4×) is often appropriate because the text is shorter and scanned rather than read continuously.

For display sizes (headlines, hero text), tighter leading (1.0–1.2×) keeps the headline feeling unified.

Paragraph spacing

The space between paragraphs creates the rest points that prose depends on. For body prose:

0.75em to 1em of vertical space between paragraphs (in addition to the line-height of the last line of the previous paragraph). So 16px text typically has 12–16px of space between paragraphs.

This makes paragraph breaks visible from a distance — the reader can see paragraph structure even when scanning. Without enough space, paragraphs blur together visually.

The alternative pattern (used in print books) is first-line indent: each new paragraph starts with a small indent (typically 1em) and there's no extra space between paragraphs. This is appropriate for traditional book layouts but rare on the web; block paragraphs with space between are the modern web convention.

Subheading frequency

Long content needs structural breaks beyond paragraphs. Subheadings provide:

Structural navigation. The reader can scan the subheadings to understand the article's structure and find the section they want.

Visual rest. A subheading creates a break point that gives the eye a moment to recover before continuing.

Cognitive chunking. Each section under a subheading is a discrete unit that the reader can process and set aside.

Frequency: every 3–5 paragraphs is a comfortable rhythm for most prose. Articles longer than ~500 words benefit from at least one subheading. Articles longer than ~1500 words need multiple levels of hierarchy (h2 sections, possibly h3 subsections).

Visual breathing room

The space around the text block matters too:

Margins. Body prose should have visible margins on all sides, not just left and right. Padding above and below the article, not just within paragraphs.

Container structure. Article layouts work best when the prose has a clear single-column structure with little visual competition. Sidebars, ads, and pop-ups all reduce reading focus.

Section breaks. Major sections within an article can have additional vertical space, decorative dividers, or other visual signals that mark a transition.

Other rhythm considerations

Sentence length variety. Not strictly typography, but related to perceived rhythm: prose that varies sentence length feels more readable than prose with all-similar sentences. (This is the writer's job, not the designer's, but layout can support it by not breaking sentences awkwardly with hard line breaks.)

Word and character spacing in prose. Use the typeface's defaults; don't tweak letter or word spacing for body prose unless you have a specific reason. The typeface designer has already calibrated these.

Drop caps and pull quotes. Editorial conventions that can punctuate long prose, but use sparingly. Heavy use feels overdesigned; light use can mark the start of a major section or highlight a key passage.

Diagnosing rhythm problems

Symptoms of prose-rhythm issues:

The page feels intimidating before reading starts. A wall of text without visible structure. Add subheadings, more paragraph breaks, or more vertical breathing room.

Reading time drops sharply over content length. Readers fatigue earlier than the content warrants. Likely too-tight leading, too-long paragraphs, or insufficient subheadings.

Readers complain that the content "feels long" even when it isn't. A 1000-word article that feels like 3000 words. Often a rhythm problem; the content is fine but the layout doesn't break it up enough.

Users reach for reader mode. They're invoking the browser's tool for the reading experience your design failed to provide.

Worked examples

A blog post layout

A blog post container: 18px Georgia body type with 1.6 line height (29px), 65ch max-width, 0.8em paragraph spacing (~14px), subheadings (h2 in 24px) every 3–5 paragraphs, generous vertical margin around the article (4em above and below).

The reader can scan the subheadings to see the article's structure. Within each section, paragraphs are 3–5 sentences with comfortable spacing. The eye flows down the page without effort.

Show full SKILL.md (552 more words)Show less
An article with poor rhythm

A 2000-word article: 16px text with 1.2 line height (default browser), no max-width (full container width), single paragraphs of 10+ sentences with no spacing between, no subheadings. The page is one continuous block of text.

Readers open the article, see the wall, and leave. Even those who try to read tire quickly. The content may be excellent; the rhythm has destroyed it.

The fix: bump line-height to 1.6, cap max-width to 65ch, break paragraphs into 3-5 sentences each with visible spacing, add subheadings every 3–5 paragraphs.

A documentation page

Documentation typically has more interruptions than article prose: code blocks, callouts, lists, tables. The rhythm needs to accommodate these.

A pattern that works:

  • Body prose at 16px / 1.6 leading / 0.8em paragraph spacing / 65ch max-width.
  • Code blocks at 90ch max-width with 1em vertical space above and below.
  • Callouts (info, warning) with their own background tinting and 1em margins.
  • Subheadings (h2, h3) with extra space before to create clear section breaks.

The result is a page that flows through prose, pauses for code or callouts, and resumes prose with clear visual boundaries.

A FAQ layout

A FAQ page is structurally a sequence of question-answer pairs. Treat each Q+A as a distinct chunk:

  • Question: 16px medium weight, with 1em margin below to attach answer.
  • Answer: 16px regular weight, 1.5 line height, indented or visually distinct.
  • Between Q+A pairs: 2em vertical space.

The rhythm makes the page scannable (jumping between questions) and readable within each answer.

Anti-patterns

Tight leading on body prose. Browser default (~1.2) is too tight for sustained reading. Set explicit line-height for prose containers.

No paragraph spacing. Paragraphs visually merging together is one of the fastest ways to make prose feel impenetrable.

No subheadings in long content. Long articles without structural breaks are walls of text. Add hierarchy.

Paragraphs that are too long. A 12-sentence paragraph is intimidating regardless of layout. Shorter paragraphs (3–5 sentences) feel more approachable. (Writer's job, but designers can encourage by leaving room.)

Text crammed into the available container. No margin around the article, no space between sections. The text feels claustrophobic.

Animation or interaction during reading. Sticky headers, scroll-triggered animations, pop-ups during reading all interrupt rhythm. Long-form reading deserves a quiet layout.

Justified text without proper hyphenation. Justified text without good hyphenation produces uneven word spacing — "rivers" of white space that disrupt reading rhythm.

Lists of bullet points used as a substitute for prose. Bullet points break rhythm; they're lists, not prose. Use them when the content is genuinely a list, not as a way to avoid writing connected prose.

Heuristic checklist

Before shipping long-form content, ask: Is the leading at least 1.5× the font size for body prose? Tighter is uncomfortable. Is paragraph spacing visible from a distance? It should clearly mark paragraph breaks. Are there subheadings every 3–5 paragraphs? Long content needs structural breaks. Does the article have visible breathing room around it? Cramped layouts cost reading comfort. Does the page have any interruptions during reading? Sticky headers, animations, pop-ups all disrupt rhythm; minimize during reading flow.

  • readability — parent principle on sustained-reading ease.
  • readability-line-length — sibling skill on measure (line length).
  • chunking — paragraphs and subheadings chunk content into readable units.
  • hierarchy — subheadings express structural hierarchy.
  • signal-to-noise — clean prose layouts maximize signal.

See also

  • references/prose-layout-patterns.md — patterns for specific kinds of long-form content.

© hashgraph-online, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in plugins/HDeibler/universal-design-principles/plugins/perception-and-hierarchy-principles/skills/readability-rhythm-and-prose of hashgraph-online/awesome-codex-plugins.

  • SKILL.md
  • references/prose-layout-patterns.md

Open the folder on GitHubat commit 3e1456a

Compare with similar skills

Readability Rhythm And Prose next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Readability Rhythm And Prose compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Readability Rhythm And Prose this skillhashgraph-online/awesome-codex-plugins1.3k—~2.5kAutomated safety check: PassApache-2.0
Asd Ste100danyuchn/asd-ste100-skill4.3k—~4.1kAutomated safety check: PassMIT
Ponytail AuditDietrichGebert/ponytail160k—~1.4kAutomated safety check: PassMIT
Technical Writing Standardcursor/plugins11k10 repos~2.4kAutomated safety check: PassNone
Natural Japanese Business Writingcoji/natural-japanese1.9k—~2.1kAutomated safety check: PassMIT
PgjevrealZachi/pg-jev1.1k—~2.9kAutomated safety check: PassCustom licence

Similar skills

  • Asd Ste100

    danyuchn/asd-ste100-skill

    A skill your agent uses when English text must be parsed without a human to resolve ambiguity — tool descriptions, error messages, inter-agent instructions, system prompts, status reports — and…

    4.3k GitHub stars~4.1k tokensUpdated 6 days ago
    Writing & ContentAuto-check passed
  • Ponytail Audit

    DietrichGebert/ponytail

    Quality audit of a whole repo: bugs, security holes, what breaks under real load, risky code without tests, slow paths, and what to delete, merge or split.

    160k GitHub stars~1.4k tokensUpdated today
    Writing & ContentAuto-check passed
  • Official

    Applies four layers of technical-writing rules to docs, RFCs, readmes, PR descriptions and commit messages so a tired engineer follows them on the first read.

    11k GitHub starsUsed in 10 repos~2.4k tokens
    Writing & ContentAuto-check passed
  • Writes and edits Japanese business documents so they read clearly and naturally, removes AI-sounding phrasing and can score how AI-like a text reads.

    1.9k GitHub stars~2.1k tokensUpdated 1 mo ago
    Writing & ContentAuto-check passed
  • Pgjev

    realZachi/pg-jev

    Install, configure, query and explain pgjev (the jev PostgreSQL extension that filters, ranks and classifies rows with plain-language conditions via TypeSafe's Jev model).

    1.1k GitHub stars~2.9k tokensUpdated 4 days ago
    Writing & ContentAuto-check passed
  • Defensive Writing Editor

    lennney/stop-that-shit

    Cuts defensive disclaimers, stacked hedging and self-protective narration from proposals and summaries, keeping only limits that affect the reader's decision.

    2.5k GitHub starsUsed in 1 repo~1.2k tokens
    Writing & ContentAuto-check passed

More from hashgraph-online/awesome-codex-plugins

All 716 skills in this repo
  • Anime Reaction Gif

    hashgraph-online/awesome-codex-plugins

    Create original anime-style reaction stickers as looping GIFs and MP4 previews, using generated character pose sheets and timed key poses.

    1.3k GitHub stars~922 tokensUpdated today
    Auto-check passed
  • Calibredb

    hashgraph-online/awesome-codex-plugins

    Manage and query Calibre libraries with the calibredb CLI (local paths or Calibre Content server URLs).

    1.3k GitHub stars~1k tokensUpdated today
    Auto-check passed
  • Rust API Test Harness

    hashgraph-online/awesome-codex-plugins

    A skill your agent uses when adding, changing, testing, or debugging Rust HTTP APIs and services, especially when Codex needs black-box integration tests, random-port app startup, real database test…

    1.3k GitHub stars~1.7k tokensUpdated today
    Auto-check passed
  • Art

    hashgraph-online/awesome-codex-plugins

    Make a studio's game look like something at build time — a cover from a real frame of the game (free), painted covers, backdrops, textures and character plates from image models through the…

    1.3k GitHub stars~2.4k tokensUpdated today
    Auto-check passed
  • Calle

    hashgraph-online/awesome-codex-plugins

    Use CALL-E from Codex through the calle CLI. An agent skill from hashgraph-online/awesome-codex-plugins.

    1.3k GitHub stars~2.9k tokensUpdated today
    Auto-check passed
  • Game Balance Economy

    hashgraph-online/awesome-codex-plugins

    Balance game difficulty, resources, rewards, probability, progression, economies, and dominant strategies.

    1.3k GitHub stars~618 tokensUpdated today
    Auto-check passed

Questions about Readability Rhythm And Prose

What does Readability Rhythm And Prose do?

Apply paragraph rhythm and prose-level readability — calibrating leading, paragraph spacing, subheading frequency, and visual breathing room so that long-form text reads smoothly without fatigue. Readability Rhythm And Prose is an agent skill from hashgraph-online/awesome-codex-plugins. Apply paragraph rhythm and prose-level readability — calibrating leading, paragraph spacing, subheading frequency, and visual breathing room so that long-form text reads smoothly without fatigue.

When should I use Readability Rhythm And Prose?

Readability Rhythm And Prose fits situations like: designing article layouts; any context with sustained prose.

How do I install Readability Rhythm And Prose in Claude Code?

Run `npx skills add hashgraph-online/awesome-codex-plugins --skill readability-rhythm-and-prose -a claude-code`. Or copy the skill folder (plugins/HDeibler/universal-design-principles/plugins/perception-and-hierarchy-principles/skills/readability-rhythm-and-prose in hashgraph-online/awesome-codex-plugins) into .claude/skills/readability-rhythm-and-prose in your project. Claude Code loads it when a task matches its description.

How do I install Readability Rhythm And Prose in Codex?

Run `npx skills add hashgraph-online/awesome-codex-plugins --skill readability-rhythm-and-prose -a codex`. Or copy the skill folder (plugins/HDeibler/universal-design-principles/plugins/perception-and-hierarchy-principles/skills/readability-rhythm-and-prose in hashgraph-online/awesome-codex-plugins) into .agents/skills/readability-rhythm-and-prose in your project. Codex loads it when a task matches its description.

Can I use Readability Rhythm And Prose in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add hashgraph-online/awesome-codex-plugins --skill readability-rhythm-and-prose -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/readability-rhythm-and-prose, .gemini/skills/readability-rhythm-and-prose, .github/skills/readability-rhythm-and-prose and .opencode/skills/readability-rhythm-and-prose in your project.

What does Readability Rhythm And Prose need to run?

SKILL.md names no scripts, command-line tools or credentials: Readability Rhythm And Prose is instructions for the agent only.

Does Readability Rhythm And Prose access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Readability Rhythm And Prose safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Readability Rhythm And Prose use?

Readability Rhythm And Prose is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Readability Rhythm And Prose use?

About 2.5k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2k tokens, read only when the agent opens those files.

What are the alternatives to Readability Rhythm And Prose?

Skills that share tags, products or a category with Readability Rhythm And Prose: Asd Ste100 (danyuchn/asd-ste100-skill, 4.3k stars), Ponytail Audit (DietrichGebert/ponytail, 160k stars), Technical Writing Standard (cursor/plugins, 11k stars) and Natural Japanese Business Writing (coji/natural-japanese, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Readability Rhythm And Prose?

hashgraph-online (a GitHub organization) maintains it in hashgraph-online/awesome-codex-plugins, which has 1,267 GitHub stars. The repository holds 716 skills in this directory. The repository was last updated on October 10, 2026.

Source: hashgraph-online/awesome-codex-plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.