Total 30,695 skills, Documentation & Writing has 1023 skills
Showing 12 of 1023 skills
Apply brand voice, tone, and style guidelines to written content across platforms. Use this skill when writing or editing content that needs to reflect a specific brand identity, adapting content for LinkedIn, Substack, X (Twitter), or other platforms while maintaining brand consistency. Triggers include requests to write on-brand content, apply brand voice, adapt content for platforms, or review content for brand alignment.
Guide users through a structured workflow for co-authoring documentation, articles, or long-form content. Use when user wants to write documentation, proposals, articles, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting articles, or using "co-authoring" workflow.
Expert guide for documenting infrastructure including architecture diagrams, runbooks, system documentation, and operational procedures. Use when creating technical documentation for systems and deployments.
Map papers from the core set to each outline subsection and write `outline/mapping.tsv` with coverage tracking. **Trigger**: section mapper, mapping.tsv, coverage, paper-to-section mapping, 论文映射, 覆盖率. **Use when**: structure 阶段（C2），已有 `papers/core_set.csv` + `outline/outline.yml`，需要确保每小节有足够支持论文再进入 evidence/writing。 **Skip if**: 还没有 outline（先跑 `outline-builder`）或 core set 还没收敛。 **Network**: none. **Guardrail**: 覆盖率可审计（避免所有小节重复用同几篇）；为弱覆盖小节留下明确补救方向（扩 query / 合并小节）。
Planner-pass coverage + redundancy report for an outline+mapping, producing `outline/coverage_report.md` and `outline/outline_state.jsonl`. **Trigger**: planner, dynamic outline, outline refinement, coverage report, 大纲迭代, 覆盖率报告. **Use when**: you have `outline/outline.yml` + `outline/mapping.tsv` and want a verifiable, NO-PROSE planner pass before writing. **Skip if**: you don't want any outline/mapping diagnostics (or you have a frozen/approved structure and will not change it). **Network**: none. **Guardrail**: NO PROSE; do not invent papers; only report coverage/reuse and propose structural actions as bullets.
Use when documentation drift is detected. Comprehensively audits codebase and creates/updates Swagger, features docs, and general documentation to achieve full sync.
MD-Book documentation generator skill. Use when working with MD-Book, a modern mdbook replacement for generating HTML documentation from Markdown files. Supports syntax highlighting, live reload, Pagefind search, and Tera templates.
Make surgical edits to specific sections while maintaining voice cohesion across the essay
Produces concise, clear documentation by applying Elements of Style principles. Use when writing or improving any technical documentation (READMEs, guides, API docs, architecture docs). Not for code comments.
Create or update system design documents. Supports initial design and incremental design modes. Use when users need technical architecture, API design, data models, design changes, or impact analysis. Triggers on keywords like "system design", "architecture", "technical design", "API design", "design change", "impact analysis", "design change", "impact analysis".
C4 model architecture visualization and documentation
Create non-technical documentation for project features in the docs/ folder. Use when documenting completed features, writing feature documentation, explaining how features work, or when the user asks to document the project or create docs for non-developers.