heading-hierarchy SKILL.md skillA
heading-hierarchy from thedaviddias/front-end-checklist is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add thedaviddias/front-end-checklist/heading-hierarchy@git:20261004.4b0ddb9Pins git:20261004.4b0ddb9 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- thedaviddias/front-end-checklist
- Path
skills/heading-hierarchy/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261004.4b0ddb9, committed Oct 4, 2026
- First version recorded
- May 29, 2026
- Size
- 2,078 bytes
- Repository stars
- 74,516
- License
- MIT
Use when reviewing rendered HTML, interactive components, or design-system patterns related to Use logical heading hierarchy. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Use logical heading hierarchy Screen reader users navigate by headings like a table of contents—skipping levels or poor hierarchy makes content impossible to understand and navigate. ## Quick Reference - Use exactly one h1 per page for the main title - Never skip heading levels (h1 → h2 → h3, not h1 → h3) - Heading text should describe the content that follows - Don't use headings for visual styling—use CSS instead ## Check Verify pages have exactly one h1, headings follow sequential order without skipping levels (h1 → h2 → h3), and heading text clearly describes the content that follows. Use accessibility tools to generate a heading outline. ## Fix Structure headings to reflect content hierarchy. Start with h1 for the page title, use h2 for major sections, h3 for subsections. Never skip heading levels or use headings purely for visual styling. ## Explain Explain how screen reader users navigate by headings like a table of contents, and why skipped levels or missing structure forces users to work harder to understand page organization. ## Code Review …
Read the whole file at its exact version.
How to install
mdr add thedaviddias/front-end-checklist/heading-hierarchy@sha256:a456a30fa57db719The line at the top of this page pins the label git:20261004.4b0ddb9, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_o2b6efoiy5b5qnvk)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between May 29, 2026 and Oct 4, 2026, about one every 128 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261004.4b0ddb9 latest | 2026-10-04 | 4b0ddb9 | 2,078 B | A | view · diff |
| git:20260529.7c05904 | 2026-05-29 | 7c05904 | 2,084 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (2078 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
thedaviddias/front-end-checklist · 74,516 stars · license MIT · pushed 2026-10-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_o2b6efoiy5b5qnvk GET https://markdownregistry.com/api/v1/resolve?ref=thedaviddias/front-end-checklist/heading-hierarchy GET https://markdownregistry.com/api/v1/blob/a456a30fa57db71961e2be0d897d95be88175bae3f30b136d2d3b5f9afd3961b
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.