This skill should be used when discussing QDoc internals, node systems, link resolution, warning diagnosis, index files, qdocconf configuration, macros, Qt Help files, or documentation generation architecture. Provides comprehensive reference for QDoc's…
Qt documentation topic tree (TOC, navigation sidebar) — how a module's tree is declared via qhp subprojects, how manually written pages attach to it through the module's *-toc.qdoc page, and how module trees merge into the Qt Framework website tree via…
Authoritative style rules for writing accessibility alt text in Qt documentation, including priority order, formatting rules, and terminology guidelines. Use when adding alt text to images.
Language, grammar, and style guidelines for Qt documentation including active voice, terminology, QUIP 25 standards, and proper API documentation patterns. Covers both WHAT to write (style/content) and HOW to write it (QDoc syntax).
Reference for checking documentation link integrity after code changes. Covers link target generation, anchor rules, search patterns, and cross-module dependencies.
Methodology for testing Claude Code skills and agents ("artifacts") before they ship — a 9-layer evaluation that moves a review from "looks fine" to "provably works." Load this skill whenever someone wants to review, test, validate, or audit a skill or agent…
Qt documentation products, modules, repository structure, and API types. Apply when working with Qt documentation, resolving module names, or understanding Qt's documentation ecosystem.
Cross-product impact checking for Qt documentation changes. Load this skill whenever a doc change (page rename, title change, filename change, API rename, QML type rename) may affect products outside the changed module. Covers all doc.qt.io products, all…