Total 30,661 skills, Documentation & Writing has 1023 skills
Showing 12 of 1023 skills
Produce clear, accurate, and maintainable technical documentation for APIs, systems, and user workflows.
Build per-chapter (H2) writing briefs (NO PROSE) so the final survey reads like a paper (chapter leads + cross-H3 coherence) without inflating the ToC. **Trigger**: chapter briefs, H2 briefs, chapter lead plan, section intent, 章节意图, 章节导读, H2 卡片. **Use when**: `outline/outline.yml` + `outline/subsection_briefs.jsonl` exist and you want thicker chapters (fewer headings, more logic). **Skip if**: the outline is still changing heavily (fix outline/mapping first). **Network**: none. **Guardrail**: NO PROSE; do not invent papers; only reference subsection ids and already-mapped papers.
Apply documentation standards: comment why not what, minimal comments (prefer clear code), maintain README with quick start, update docs with breaking changes. Use when writing comments, creating docs, reviewing documentation, or discussing what to document.
Rewrite AI-generated developer text to sound human — fix inflated language, filler, tautological docs, and robotic tone. Use after review-ai-writing identifies issues.
Generate and update structured documentation from project data sources. Supports initial generation and modification of existing documents. Use this skill when users request creating, generating, updating, or modifying documentation.
Update the API reference documentation by downloading the latest OpenAPI spec from production and regenerating the Docusaurus API docs
Update and maintain CLAUDE.md and README.md documentation
Publish documentation generated by doc-smith-create to DocSmith Cloud and obtain an online preview URL. Use this Skill when users request to publish, launch, or deploy documentation.
Enforces strict use of Chinese in all interactions, code comments, and documentation generation, in compliance with advanced technical writing standards. Enforces strict adherence to the Chinese language in all interactions, code comments, and documentation with high-quality technical writing standards.
Sync documentation with implementation progress. Use when users need to update docs after development, verify doc-code consistency, or track implementation progress. Triggers on keywords like "sync docs", "update progress", "doc consistency", "同步文档", "更新进度".
Use when documenting public APIs. Use when writing library code. Use when using JSDoc-style comments. Use when generating documentation. Use when explaining complex types.
Expert guidance for writing clear, comprehensive documentation including READMEs, API docs, docstrings, and technical guides. Use when creating or improving documentation.