Total 44,738 skills, Documentation & Writing has 1312 skills
Showing 12 of 1312 skills
Guidelines for Go documentation including doc comments, package docs, godoc formatting, runnable examples, and signal boosting. Use when writing or reviewing documentation for Go packages, types, functions, or methods.
Diagnose sentence-level issues after structure is solid. Use when prose feels flat, sentences are monotonous, word choices are generic, or voice is inconsistent.
Auto-generates professional README.md files for Arduino/ESP32/RP2040 projects following open-source best practices. Use when user wants to document their project for GitHub, needs help writing a README, or says "make my project shareable". Follows awesome-readme standards with sections for Overview, Hardware, Software, Setup, Usage, Troubleshooting, and Contributing.
Use when complex systems need visual documentation, mapping component relationships and dependencies, creating hierarchies or taxonomies, documenting process flows or decision trees, understanding system architectures, visualizing data lineage or knowledge structures, planning information architecture, or when user mentions concept maps, system diagrams, dependency mapping, relationship visualization, or architecture blueprints.
Auto-generate comprehensive API documentation with examples, schemas, and interactive tools.
Writing Juejin-style technical articles: structure, headlines, openings, technical explanations, rankings & critical reviews, examples & code, and personalized tone, facilitating Agents to produce Simplified Chinese technical content.
Remove signs of AI-generated writing from text to make it sound more natural and human-written. Use when editing or reviewing any form of document including: markdown, technical docs, emails, blog posts, PRDs, or any dedicated writing content. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.
Create and maintain TYPO3 extension documentation following official docs.typo3.org standards. Use when creating/editing Documentation/*.rst files or README.md, using TYPO3 directives (confval, versionadded, card-grid, accordion, tabs, admonitions), creating/adding screenshots, rendering/testing/viewing docs locally, or deploying to docs.typo3.org. By Netresearch.
Creates Architecture Decision Records documenting key technical decisions with context, alternatives considered, tradeoffs, consequences, and decision owners. Use when documenting "architecture decisions", "technical choices", "design decisions", or "ADRs".
PDCA document templates for consistent documentation. Plan, Design, Analysis, and Report templates with proper structure. Use proactively when generating PDCA documents to ensure consistent format. Triggers: template, plan document, design document, analysis document, report, 템플릿, 계획서, 설계서, 분석서, 보고서, テンプレート, 計画書, 設計書, 模板, 计划书, 设计书, plantilla, documento de plan, documento de diseño, documento de análisis, informe, modèle, document de plan, document de conception, document d'analyse, rapport, Vorlage, Plandokument, Designdokument, Analysedokument, Bericht, modello, documento di piano, documento di progettazione, documento di analisi, rapporto Do NOT use for: code implementation, deployment, or non-documentation tasks.
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.
Update and maintain CLAUDE.md and README.md documentation