Total 43,555 skills, Documentation & Writing has 1289 skills
Showing 12 of 1289 skills
Guide for creating and maintaining project documentation (README, guides, API specs). Emphasizes doc/code synchronization, consistency checks, and use of the docs-excellence-architect subagent.
Update an existing specification file for the solution, optimized for Generative AI consumption based on new requirements or updates to any existing code.
Update the llms.txt file in the root folder to reflect changes in documentation or specifications following the llms.txt specification at https://llmstxt.org/
Analyzes code repositories and generates hierarchical documentation structures with onboarding guides. Use when the user wants to create a wiki, generate documentation, map a codebase structure, or...
Generates rich technical documentation pages with dark-mode Mermaid diagrams, source code citations, and first-principles depth. Use when writing documentation, generating wiki pages, creating tech...
Remove signs of AI-generated writing from text. Use after drafting to make copy sound more natural and human-written. Based on Wikipedia's "Signs of AI writing" guide.
Set up a complete book writing workspace with AI agents, instructions, prompts, and scripts. Use when users want to create a new book/technical writing project with Markdown + Re:VIEW + PDF output workflow. Triggers on "book writing workspace", "technical book project", "執筆ワークスペース", or similar project setup requests.
Generate detailed content briefs for blog posts with target keywords, content outlines, competitive analysis, recommended statistics, image and chart suggestions, word count targets, internal linking architecture, template recommendations (12 types), TL;DR drafts, citation capsule planning, information gain prompts, and multi-channel distribution plans. Briefs are optimized for Google rankings and AI citations (GEO/AEO). Use when user says "content brief", "blog brief", "write brief", "outline blog", "plan blog post", "blog outline", "content outline".
ADR format and methodology for documenting significant technical decisions with context, alternatives considered, and consequences. Use when making or documenting architectural decisions.
Documentation best practices — README structure, inline code comments, API docs, changelogs, and technical writing principles. Reference when writing any documentation.
Comprehensive academic textbook chapter writing system for medical/scientific content. Use when the user wants to: (1) Write a full textbook chapter (5,000-15,000 words) on any medical/scientific topic, (2) Generate a detailed table of contents with section word counts, (3) Research topics via PubMed MCP and compile 20-30 references, (4) Write section-by-section with proper citations in Vancouver format, (5) Create publishable academic content with Eric Topol-inspired voice and authentic human prose, (6) Get approval at TOC stage before writing begins, (7) Export well-structured chapters for textbook publication.
Эксперт по документации кода. Используй для JSDoc, docstrings, комментариев и автогенерации документации.