/cm-dockit

name: cm-dockit
description: "Knowledge systematization engine — analyze codebases, generate Personas, JTBD, Process Flows, technical docs, SOP user guides, API references. Output as Markdown or VitePress Premium. SEO-optimized, AI/LLM-readable. One scan = complete knowledge base."

CM DocKit: Knowledge Systematization Engine

A professional knowledge systematization engine powered by codebase analysis and UX design principles. **One source scan = one complete knowledge base** — Personas, JTBD, Process Flows, Technical Docs, SOPs, API Reference. Supports plain Markdown output or a premium VitePress site. Includes SEO optimization, sitemap generation, and AI/LLM-readable content.

When to Activate

• User asks to "create documentation", "generate docs"
• User mentions "SOP", "user guide", "manual"
• User wants technical docs from a codebase
• User runs `/DocKit Master`

Document Types

| Type | Skill File | Description | |------|-----------|-------------| | **knowledge** | `skills/persona-builder.md` + `skills/jtbd-analyzer.md` + `skills/flow-mapper.md` *(files pending)* | Personas, JTBD, Process Flows — knowledge foundation | | **tech** | `skills/tech-docs.md` | Architecture, database, deployment, data flow | | **sop** | `skills/sop-guide.md` | Step-by-step user guides (enriched with knowledge) | | **api** | `skills/api-reference.md` | API endpoint reference with examples | | **all** | All above | Full knowledge base + documentation suite |

| Support Skill | File | Purpose | |--------------|------|---------| | **SEO Checklist** | `skills/seo-checklist.md` | Per-page SEO audit (title, meta, headings, robots) | | **Content Writing** | `skills/content-writing.md` | SEO copywriting, keywords, active voice, FAQ | | **LLM Optimization** | `skills/llm-optimization.md` | AI-readable structure, NotebookLM-friendly |

Output Formats

| Format | Workflow | Description | |--------|---------|-------------| | **markdown** | `workflows/export-markdown.md` | Plain `.md` files in `docs/` folder | | **vitepress** | `workflows/setup-vitepress.md` | Premium VitePress static site (**default**) — built-in Mermaid, search, dark mode |

Procedure

Step 1: Gather Input (Single Consolidated Prompt)

**CRITICAL:** Ask ALL questions in ONE message. Do NOT ask one at a time. Present the following intake form to the user, using this **📚 DocKit Master — Configuration**

Please answer the following questions so I can automatically create an execution plan:

| # | Question | Options | Default | |---|---------|---------|--------| | 1 | **📑 Document type?** | `knowledge` · `tech` · `sop` · `api` · `all` | `all` | | 2 | **🎨 Output format?** | `markdown` (plain) · `vitepress` (premium site) | `vitepress` | | 3 | **📂 Code scan scope?** | `full` (entire project) · `focused` (specific folder/feature) | `full` | | 4 | **🎯 Focus area?** *(only if `focused`)* | Folder name, module, or specific feature | — | | 5 | **🌏 Writing language?** | Auto-detect from chat language *(see below)* | auto-detect | | 6 | **🌐 Add multi-language?** | `yes` (add English + source language) · `no` | `no` | | 7 | **📹 Record video demo?** | `yes` (record browser walkthrough) · `no` | `no` | | 8 | **📁 Project path?** | *(absolute path)* | current workspace | | 9 | **🔍 SEO optimization?** | `yes` (SEO frontmatter + checklist + sitemap) · `no` | `yes` | | 10 | **🤖 Optimize for AI/LLM?** | `yes` (AI-readable + NotebookLM sitemap) · `no` | `yes` |

*You can answer briefly, e.g.: "all, vitepress, full, yes, no, yes, yes"*

**🌏 Smart language rules:**

1. **Auto-detect**: Determine default language from the user's chat language

• User chats in Vietnamese → default `vi`
• User chats in Chinese → default `zh`
• User chats in Japanese → default `ja`
• User chats in English → default `en`
• *(Applies similarly for any other language)*

2. **Multi-language (`yes`)**: Automatically add English (`en`) as secondary language

• Example: Vietnamese user + multi-language → `vi` + `en`
• Example: Chinese user + multi-language → `zh` + `en`
• If user already chats in English + multi-language → ask which secondary language

3. **Override**: User can override by specifying explicitly, e.g.: \"write in Japanese\"

---

Step 1b: Auto-Generate Execution Plan

After receiving answers, **immediately create an execution plan** (do NOT ask more questions).

Map the answers to this execution config:

DOC_TYPE     = [knowledge | tech | sop | api | all]
FORMAT       = [markdown | vitepress]
SCOPE        = [full | focused]
FOCUS_TARGET = [directory/module name if focused, else null]
LANGUAGE     = [vi | en | vi+en]
I18N         = [yes | no] (only relevant for vitepress)
RECORD       = [yes | no]
PROJECT_PATH = [absolute path]
SEO          = [yes | no] (default: yes)
LLM_OPTIMIZE = [yes | no] (default: yes)

Then present the plan to user as a checklist artifact, like:

## 🚀 Execution Plan

- [ ] Scan code: [full/focused → target]
- [ ] Generate documents: [type] in [language]
- [ ] Export format: [markdown/vitepress]
- [ ] [If vitepress + i18n] Configure multi-language
- [ ] [If record] Record video walkthrough
- [ ] [If seo] Run SEO checklist + generate sitemap
- [ ] [If llm_optimize] Apply LLM optimization rules
- [ ] Review and deliver

**After presenting the plan → proceed to Step 2 immediately (auto-execute).** Do NOT wait for approval unless the plan has ambiguity.

Step 2: Analyze Codebase

Read and follow `skills/analyze-codebase.md` in this directory.

Output: structured analysis saved to `docs/analysis.md` (NOT `_analysis.md`) including:

• Project type, languages, frameworks
• Directory structure and architecture layers
• Entry points, routes, database schema
• Key business logic modules
• Dependencies overview
• Test coverage

Step 3: Apply Content Guidelines

**MANDATORY** — Read `skills/content-guidelines.md` before generating any content.

Key rules to enforce:

• **Filenames**: