docu.md Markdown 파이프라인을 위한 에이전트 스킬. what에서 조직한 하나의 스킬 패키지 독자가 원한다, 렌더링 엔진이 구현 참조 역할을 하는 것.

242개의 검증된 예시 · 183개의 시나리오 · 31개의 목표 도메인 · 5개의 엔진, 모든 도형은 다음 중 하나에서 색칠되었습니다 styles/에서 정의된 아홉 가지 주제, 소스 테이블에서 생성되며, [[T1]로 게이팅됨] (테마 드리프트 · 대비 · 블록 렌더링 · 블록 커버리지 · 테마 사용 · 구조) 플러스 scripts/verify-examples.mjs는 전체 렌더 패스를 위한 것입니다.

기술은 에이전트 기술 형식을 따릅니다.

---

🧭 빠른 내비게이션

** 🚀 설치** • ** 🧩 패키지** • ** ⚙️ 엔진** • ** ️ documd CLI** • ** 🔀 마이그레이션된 기술** • ** 🔗 링크**

---

🚀 설치

빠른 설치 (권장)

이 방법은 여러 AI 코딩 에이전트(Claude Code, Codex, Cursor 등)와 함께 작동하며, documd-visuals 패키지.

수동 설치

클로드 코드 (매뉴얼)에 대해

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