docu.md Markdown 流程的代理技能。一个技能包，由what组织 读者想要，渲染引擎作为实现参考。

242个已验证的示例 ·183个场景 ·31个目标领域 ·5个引擎，每个图形均取自以下一个 九个主题在styles/中定义，并从源表生成，源表由[[T1]门禁] （主题漂移·对比度·块渲染·块覆盖度·主题使用·结构）plus scripts/verify-examples.mjs 用于完整的渲染通行。

技能遵循特工技能格式。

---

🧭 快速导航

** 🚀 安装** • ** 🧩 软件包** ** ⚙️ 引擎** • ** ️ documd CLI** • ** 🔀 迁移技能** • ** 🔗 链接**

---

🚀 安装

快速安装（推荐）

该方法可与多个AI编码代理（Claude Code、Codex、Cursor等）共事，并发现 documd-visuals 包裹。

手动安装

对于Claude代码（手册）

为了 claude.ai

将该包添加到项目知识中，或将SKILL.md内容粘贴到对话中。

用于GitHub Copilot / VS Code

当包裹放置在 .github/skills/ 目录时会自动检测。

---

docu.md skills

Agent skills for the docu.md Markdown pipeline. One skill package, organised by what the reader wants, with the rendering engines behind it as implementation references.

242 verified examples · 183 scenarios · 31 goal domains · 5 engines, every figure coloured from one of nine themes defined in styles/ and generated from a source table, gated by scripts/check-all.mjs (theme drift · contrast · block render · block coverage · theme usage · structure) plus scripts/verify-examples.mjs for the full render pass.

Skills follow the Agent Skills format.

---

🧭 Quick Navigation

🚀 Installation • 🧩 The Package • ⚙️ Engines • �️ The documd CLI • �🔀 Migrated Skills • 🔗 Links

---

🚀 Installation

Quick Install (Recommended)

npx skills add markdown-viewer/skills

This method works with multiple AI coding agents (Claude Code, Codex, Cursor, etc.) and discovers the documd-visuals package.

Manual Installation

For Claude Code (Manual)

cp -r skills/documd-visuals ~/.claude/skills/

For claude.ai

Add the package to project knowledge or paste SKILL.md contents into the conversation.

For GitHub Copilot / VS Code

Packages are automatically detected when placed in .github/skills/ directory.

---

🧩 The Package

skills/
├── documd-visuals/        ← the skill package — the only skill here, and the only thing installed
│   ├── SKILL.md           ← router: iron rules, 31 goals, capability boundaries
│   ├── converting.md      ← the documd CLI: install, formats, flags, what survives an export
│   ├── catalog/           ← every scenario: domain, engines, tier, example files
│   ├── goals/             ← one guide per goal domain
│   ├── engines/           ← per-engine reference + coverage/ ledgers (units, then examples by goal)
│   ├── examples/          ← 242 verified examples, grouped by goal domain
│   └── styles/            ← palette.md (the contract) + themes/.md (values + a block per engine)
├── research/              ← engine dossiers: coverage ledgers + verification notes (repo-only, never shipped)
└── scripts/               ← repo-level gates (not shipped)

The package is self-contained: it never cites research/ or scripts/, and the gate fails the build if it does. If you install the package, everything it references is inside it — and every file inside it is reachable from SKILL.md, which validate-skills.mjs enforces. The one exception is LICENSE.md: a legal attachment is not routing content, so it ships with the package without being linked from the router.

research/ and scripts/ are not discovered as skills: the CLI finds a skill by locating a SKILL.md, and neither directory contains one. Verified — npx skills add ./skills --list reports