技能创建器
skill-creator
创建、改进和评估自定义技能,把专业流程转化为可重复使用的 AI 能力。
heading-structure【数据与研究】When the user wants to write or optimize H1-H6, fix heading hierarchy, improve content structure, rewrite an H1, or align headings with page intent. This skill owns actual heading changes; page-metadata may only check and report metadata-to-heading alignment.
独立 GitHub 快照 · 自动分类 · 以原作者文档为准
Guides heading (H1-H6) optimization for SEO and content structure.
When invoking: On first use, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Project context: Read root contextus.md when present and load only the modules relevant to this task. Without Contextus, use available project material or user-provided facts and ask for missing information; do not create a parallel context system.
Identify:
| Principle | Guideline |
|---|---|
| Primary page heading | Prefer one clear H1 that identifies the page; audit accessibility and template semantics before treating an extra H1 as a ranking emergency |
| Search language | Include the primary concept naturally when useful; do not force exact-match phrasing |
| Descriptive | Clearly describe page content |
| Match intent | Serve the same page intent and promise as the title tag without requiring identical wording |
| Principle | Guideline |
|---|---|
| Logical order | Use heading levels to express document structure; do not choose a level for visual size alone |
| One idea per heading | Each heading = one topic |
| Scannable | Headings should summarize section content |
| Keyword variation | Use related keywords in subheadings |
H1 (page title)
-> H2 (section 1)
-> H3 (subsection)
-> H3
-> H2 (section 2)
-> H3
-> H2 (section 3)
| Issue | Fix |
|---|---|
| Multiple H1s | Confirm the template and accessibility semantics; prefer one clear primary H1, but do not present extra H1s as an automatic ranking failure |
| Visual styling encoded as hierarchy | Keep semantic level based on structure and style it separately |
| Generic headings | Make descriptive; avoid "Introduction," "Conclusion" |
| Keyword stuffing | Natural language; avoid forced keywords |