markdown-for-mdsvr

Markdown for mdsvr Skill

Generate a complete, valid, multi-file Markdown documentation set for use with mdsvr — supports both server mode and static export.

When this skill is triggered, produce multiple .md files that form a cohesive documentation site, following all mdsvr conventions strictly.

---

Step 1 — Understand the Request

Before generating files, extract from the user's request:

1. Topic / product name — what is being documented?
2. Target audience — developers, end-users, ops teams, etc.
3. Scope — how many pages / sections are needed?
4. Language — Vietnamese, English, or bilingual?
5. Diagrams needed? — if yes, read rules/mermaid.md for syntax rules.
6. Quizzes needed? — if the doc set includes self-check questions or chapter quizzes, read rules/quiz.md for the ```quiz JSON format.
7. Math needed? — if the doc set includes formulas or equations, read rules/math.md for the $...$ / $$...$$ / ```math LaTeX syntax.

If any of these are unclear, ask ONE focused question before proceeding.

---

Step 2 — Plan the File Structure

Design the file structure before writing content. Prefer a flat structure because it is easier to browse, link, reorder, and maintain:

docs/
├── README.md                    ← Homepage (required)
├── 01-installation.md
├── 02-quickstart.md
├── 03-configuration.md
├── 04-basic-usage.md
├── 05-advanced.md
├── 06-api-reference.md
└── 07-troubleshooting.md

Create subdirectories only when the documentation is large enough that a flat list becomes difficult to navigate, such as when a section contains many closely related pages or needs its own index. Do not create a subdirectory for only one or two pages. When subdirectories are justified, each must contain a README.md section index.

Adapt the structure to the user's topic and scale it up or down as needed.

---

Step 3 — Apply mdsvr File & Link Rules (MANDATORY)