markdown

Enforce Markdown formatting conventions for accessible, diff-stable documents.

Updated Feb 24, 2026

Search Tags:#documentation #markdown #accessibility #readability #conventions #diff-friendly

Ready to run

npx skills add https://github.com/drmowinckels/dotfiles --skill markdown-drmowinckels

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: markdown
Source: https://github.com/drmowinckels/dotfiles/tree/main/config/claude/skills/markdown
Command: npx skills add https://github.com/drmowinckels/dotfiles --skill markdown-drmowinckels

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Markdown conventions reduce formatting drift, improve accessibility, and keep diffs readable across revisions by standardizing how documents are written and displayed.

Core Features & Use Cases

Enforces one sentence per line to minimize diff noise.
Requires alt text and captions for all images to ensure accessibility.
Promotes the use of descriptive links, consistent lists, and clear headings without redundant styling.
Encourages the use of Quarto-style chunk options for code figures and reproducible results.
Supports consistent typography and formatting rules that improve readability and maintainability.

Quick Start

Apply these conventions to your Markdown documents to ensure accessibility and clean diffs.

Frequently Asked Questions about markdown

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

FAQPage Schema

How do I keep markdown diffs readable across document revisions?▼

To keep markdown diffs readable across revisions, enforce a one-sentence-per-line formatting convention. This approach minimizes diff noise by ensuring that edits to individual sentences do not cause entire paragraphs to appear as changed text in version control.

What are the best markdown conventions for writing accessible technical documentation?▼

Accessible markdown conventions require adding alt text to all images, using descriptive link text, and applying clear headings without redundant bold styling. These rules ensure screen readers can interpret content and improve overall document readability for technical docs.

How do I format markdown lists and typography to maintain consistent readability?▼

Consistent markdown readability is maintained by standardizing lists, avoiding hard-wrapping, and applying uniform typography rules. These formatting conventions prevent structural drift and ensure documents remain easy to read and maintain over time.

Does this markdown formatting convention support Quarto-style chunk options?▼

Yes, these markdown conventions support the use of Quarto-style chunk options for code figures. This integration encourages reproducible results and standardizes how code outputs are embedded within technical documentation and educational notes.

Why should I avoid hard-wrapping and bold headings in markdown documents?▼

You should avoid hard-wrapping and bold headings in markdown to prevent formatting drift and reduce diff noise. Removing redundant styling from headings and keeping lines unwrapped ensures documents remain accessible and consistently formatted across revisions.