Total 43,450 skills, Documentation & Writing has 1289 skills
Showing 12 of 1289 skills
Create Requirements Document - generates a structured requirements document, asking clarifying questions about ambiguities before proceeding
Documentation and codemap specialist. Use PROACTIVELY for updating codemaps and documentation. Generates docs/CODEMAPS/*, updates READMEs and guides.
Research a specific system and create or update its blueprints/ documentation
Troubleshooting Guide Creator - Auto-activating skill for Technical Documentation. Triggers on: troubleshooting guide creator, troubleshooting guide creator Part of the Technical Documentation skill category.
Generate a README introduction following the Diataxis 4-paragraph structure for product documentation.
Design algorithms with LaTeX pseudocode and UML diagrams. Generate algorithmic environments, Mermaid class/sequence diagrams, and ensure consistency between pseudocode and implementation. Use when formalizing methods for a paper.
Generate publication-quality LaTeX tables from experimental results. Convert JSON/CSV data to booktabs-styled tables with bold best results, multi-row layouts, and proper captions. Use when creating result tables, comparison tables, or ablation tables for papers.
Structure, classify, and write documentation using the Diátaxis framework. Use when writing docs, README files, guides, tutorials, how-to guides, API references, or organizing documentation architecture. Also use when asked to improve documentation, restructure docs, decide what type of doc to write, or classify existing content. Covers tutorials, how-to guides, reference, and explanation.
Use when transforming technical content (notes, reports, results, drafts, experiment logs) into a polished blog post for senior engineers. Supports case studies, deep dives, and how-to guides.
Patterns and structure for writing API reference documentation including endpoint descriptions, request/response schemas, and error documentation.
고유한 저자 페르소나를 구성하기 위한 특성 DNA 라이브러리. 목소리 패턴(격식체, 대화체, 서사체, 기술체), 전문성 영역(아키텍처, 구현, 산업, 교육), 관점 스타일(분석적, 경험적, 비판적, 비전적), 어조 특성(권위적, 공감적, 도발적, 양육적)을 포함한다. 페르소나를 정의하거나 커스터마이징할 때, 저자 특성을 이해할 때, 콘텐츠 전반에 일관된 특성을 적용할 때 사용한다.
Project docs system: sync codebase to docs, research what to build next, or work on a roadmap item.