TypingMindTypingMindThe best frontend for AI
Heading Structure logo

Heading Structure

Community
Owl-Listener
heading-structure

Design heading hierarchies and content structure that work for screen readers and cognitive accessibility. Use when structuring pages, articles, dashboards, forms, or any content-heavy interface. Triggers on: headings, heading hierarchy, h1 h2 h3, content structure, page structure, screen reader navigation, document outline, semantic structure, heading levels.

Overview

PublisherOwl-Listener
Repositoryinclusive-design-skills
Skill nameheading-structure
Stars
108
Forks
28
Bundled files
Instructions only
LicenseMIT
Links
Skill sourceRepository
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by Owl-Listener on GitHub. Read the source before you install it.

Installation

Install the Heading Structure AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/Owl-Listener/inclusive-design-skills/tree/main/accessible-content/skills/heading-structure
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git /tmp/inclusive-design-skills
mkdir -p .claude/skills
cp -r /tmp/inclusive-design-skills/accessible-content/skills/heading-structure .claude/skills/heading-structure
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Heading Structure in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Heading Structure on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Heading Structure is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Heading Structure

Headings are navigation for screen reader users and cognitive signposts for everyone. A clear heading structure is the difference between content people can find and content people abandon.

Why This Matters

Screen reader users navigate by headings — they press a key to jump between headings the way sighted users scan a page visually. If your heading structure is broken, screen reader users are lost in a wall of undifferentiated text.

For people with cognitive disabilities, headings are the primary way they understand what content a page contains and where to find what they need.

Rules

One H1 Per Page

  • The H1 is the page title — what this page is about
  • It should match or closely relate to the page's title tag and the link that brought the user here
  • Never use more than one H1 on a page

No Skipped Levels

  • Go H1 → H2 → H3, never H1 → H3
  • Skipping levels breaks screen reader navigation and confuses the document outline
  • You can go back up: H3 → H2 is fine (starting a new section)

Headings Describe Content

  • Headings are signposts, not decoration
  • "Your Account Settings" not "Section 2"
  • "Choose a Delivery Date" not "Step 3"
  • A user should understand the page's content by reading only the headings

Headings Are Not Visual Styling

  • Don't use a heading tag just to make text big or bold
  • Don't skip heading tags and just style text to look like a heading
  • The tag determines the structure; CSS determines the appearance
  • If it looks like a heading but isn't one, screen reader users can't find it

Recommended Depth

  • Most pages: H1 through H3 is sufficient
  • Complex pages: H1 through H4 maximum
  • If you need H5 or H6: the page is probably too complex — consider splitting it

Patterns

Article or Blog Post

H1: Article Title
  H2: First Major Section
    H3: Subsection
    H3: Subsection
  H2: Second Major Section
    H3: Subsection
  H2: Conclusion

Dashboard

H1: Dashboard Name
  H2: Summary / Key Metrics
  H2: Recent Activity
  H2: Tasks
  H2: Notifications

Form

H1: Form Title (e.g., "Apply for an Account")
  H2: Personal Information
  H2: Contact Details
  H2: Preferences
  H2: Review and Submit

Settings Page

H1: Settings
  H2: Profile
  H2: Notifications
  H2: Privacy
  H2: Billing

Assessment Checklist

  • Exactly one H1 per page
  • No skipped heading levels
  • Headings describe the content beneath them
  • Heading tags are used for structure, not visual styling
  • A user reading only headings would understand the page
  • Heading depth does not exceed H4

Frequently asked questions

What does the Heading Structure AI skill do?

Design heading hierarchies and content structure that work for screen readers and cognitive accessibility. Use when structuring pages, articles, dashboards, forms, or any content-heavy interface. Triggers on: headings, heading hierarchy, h1 h2 h3, content structure, page structure, screen reader navigation, document outline, semantic structure, heading levels.

Why use Heading Structure on TypingMind?

Because you install it once and use it with any model. Heading Structure is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Heading Structure in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Owl-Listener/inclusive-design-skills/tree/main/accessible-content/skills/heading-structure. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Heading Structure?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Heading Structure?

As many as you like. As long as a model supports skills, you can use Heading Structure with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Heading Structure AI skill free?

Yes. It is published on GitHub by Owl-Listener under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

Related AI Skills

View all
affaan-m logo

X Api

affaan-m
CommunityPopular

X/Twitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants…

40.4K
270.2K
1 files
View
affaan-m logo

Postgres Patterns

affaan-m
CommunityPopular

Patrones de base de datos PostgreSQL para optimización de consultas, diseño de esquemas, indexación y seguridad. Basado en las buenas prácticas de Supabase.

39.1K
261.1K
Instructions
View
affaan-m logo

Android Clean Architecture

affaan-m
CommunityPopular

Android と Kotlin Multiplatform プロジェクトのクリーンアーキテクチャパターン — モジュール構造、依存関係ルール、UseCase、Repository、データ層パターン。

39.1K
261.1K
Instructions
View
NousResearch logo

Blackbox

NousResearch
OrganizationPopular

Delegate coding tasks to the Blackbox AI multi-model CLI.

53.5K
250.4K
Instructions
View

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇