Total 30,671 skills, Documentation & Writing has 1023 skills
Showing 12 of 1023 skills
Generate VitePress documentation sites for source code learning and analysis. Use when creating tutorials that explain how a codebase is implemented internally.
Comprehensive documentation specialist covering API documentation, technical writing, design documentation, migration guides, and changelog generation. Use when creating OpenAPI/Swagger specs, generating SDKs, writing user guides, creating README files, documenting architecture, writing design specs, creating ADRs, writing migration guides, or generating changelogs from git commits. Handles versioning, examples, developer experience, and user-facing documentation.
Systematically reduces AI detection rate and adds human touch through three-pass proofreading (content, style, details). Use when proofreading articles, reducing AI flavor, when content feels robotic, or when user mentions AI detection rate or lack of authenticity.
Automatically check consistency of character behavior, world rules and timeline during chapter writing - Alert before potential contradictions become major issues
Use when building scenes or planning chapter content - provides scene-sequel framework, tension management, and beat-based structure for engaging scenes
Guidelines for preparing changelog entries for nextest releases following Keep a Changelog format
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.
Generates Request for Comments documents for technical proposals including problem statement, solution design, alternatives, risks, and rollout plans. Use for "RFC", "technical proposals", "design docs", or "architecture proposals".
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.
Structured workflow for writing technical articles on WeChat Official Accounts. Use cases: Users need to write an official account article, create an article directory, organize materials, and iterate on drafts. Must follow the naming conventions and directory structure specified in blogs/wechat/README.md.
Validate and enforce markdown document structure including frontmatter positioning, heading hierarchy, and content organization. Use when creating or validating markdown files.
[Docs] Autonomous subagent variant of documentation. Use when creating or updating technical documentation, API documentation, or inline code documentation.