📘Technical Writing Skills
Browse skills in the Technical Writing category.
Typescript Docs
A powerful skill for Claude agents.
Docs Workflow
A powerful skill for Claude agents.
Professional Communication
A powerful skill for Claude agents.
Crafting Effective Readmes
A powerful skill for Claude agents.
technical-to-business-translator
Translate technical analysis into business language. Use when explaining statistical concepts to non-analysts, simplifying technical findings, or bridging communication between data teams and business stakeholders.
technical-writing
Technical documentation best practices for clear, accurate, and useful documentation. Use when writing documentation, README files, API docs, architecture guides, or any technical communication.
v2-docs-audit
Orchestrate V2 transaction MDX documentation coverage and quality tracking
game-systems-doc
AAA-quality Game Design Document creation for casino-farming hybrid games. Use when creating GDDs, minigame specifications, system design documents, feature briefs, or technical design docs. Triggers on requests for game design documentation, mechanic specifications, system breakdowns, or professional game dev deliverables. Specialized for card game mechanics, farming simulation systems, and hybrid genre documentation.
tech-article-humanizer
Transform technical article drafts or source materials into human-like, high-quality Japanese technical articles. Use this skill when the user wants to generate, rewrite, or humanize technical articles (especially about TypeScript, JavaScript, React, or frontend topics) following specific human-writing patterns and style guidelines. Triggers include requests like "記事を人間風に", "tech article を生成", "humanize this article", or providing article source materials.
onboarding-docs
This skill should be used when generating developer onboarding documentation including architecture overviews, setup guides, code tours, and decision records.
docs
Write clear documentation including API docs, READMEs, and code comments
modules-readme-updater
Update the README.md file to list all available journal modules under the Features section. Use when adding, removing, or reorganizing modules and keeping documentation in sync.
changelog-writer
变更日志编写技能。当用户需要编写 CHANGELOG、版本发布说明、更新记录，或需要整理 Git 提交历史生成变更日志时使用此技能。
documenting-chores
Creates lightweight documentation for chore tasks and maintenance work. Use when the user needs to document a chore, maintenance task, dependency update, refactoring, or minor fix that doesn't require full feature requirements.
methodology-explainer
Explain analysis methodology to diverse audiences. Use when documenting 'how we did this' sections, building trust through transparency, or teaching analytical approaches to stakeholders.
documentation-writing
Audience-first documentation guidance for READMEs, API docs, architecture docs, and tutorials. Ensures clarity, completeness, and maintainability.
spec-metadata
Generates metadata for research documents and specifications including date/time, git commit, branch, and repository info. Use when creating research documents, handoffs, or any documentation that needs timestamp and git metadata.
technical-writer
Create, update, and improve clear, accurate, and actionable documentation for developers and users.
readme-generator
Generate a comprehensive, developer-friendly README.md in English by analyzing the project structure and source code. This skill scans the repository to understand the project's purpose, technical implementation, and setup requirements. Use this when a user asks to create, initialize, or update a README file for their project.
tech-article-polished-writer
Generate clear, professional, and polished Japanese technical articles suitable for corporate blogs, official documentation, and technical publications. Use this skill when the user wants to create enterprise-level content with consistent polite tone (です/ます), logical structure, and authoritative voice. Triggers include requests like "polished article", "professional tone", "enterprise blog", "公式ドキュメント", "プロフェッショナルな記事", or when content needs formal technical writing.
doc-generator
技术文档生成技能。当用户需要编写 README、API 文档、项目文档、技术规范、使用指南或任何技术文档时使用此技能。
v2-docs-review
Review individual V2 transaction MDX documentation for coverage and accuracy
doc-coauthoring
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
api-documentation
Comprehensive guidance for documenting REST, GraphQL, gRPC, and WebSocket APIs. Use when creating API endpoints, updating existing APIs, preparing public API releases, or documenting external integrations.
documenting-features
Creates structured feature requirement documents for software features. Use when defining new features, writing requirements, specifying CLI commands, API endpoints, or when the user asks for feature documentation, requirements, specs, or PRDs.
chronicle-structure
Guide for adding structure information to Chronicle with visual hints
documentation
Use when writing or updating documentation - generates function docs, API specs, architecture diagrams (Mermaid), READMEs, code explanations. Activates when user says "document this", "write README", "explain this code", mentions "docs", "documentation", "API docs", or asks "how does this work?".
ieee-writer
Translate, polish, restructure, and validate academic papers for IEEE publications. Strict adherence to IEEE style, academic tone, and formatting rules.
writing-documentation
Apply Strunk's timeless writing rules to ANY prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Makes your writing clearer, stronger, and more professional.
odoo-docs-scaffolder
Streamlines creation of new Odoo documentation pages using standard templates. Use when starting a new documentation page, tutorial, or API reference to ensure correct initial structure, metadata, and media folder organization.
odoo-docs-validator
Automated style and structure validation for Odoo documentation. Use when creating or modifying RST files to ensure compliance with Odoo's heading hierarchy, line length limits, image metadata requirements, and UI element formatting rules. This skill provides validation scripts and a comprehensive rule reference for maintaining documentation quality.
technical-writer
Create clear, accurate technical documentation for developers and end users
doc-coauthoring
Guide users through structured documentation workflows for RawDrive. Use when creating specs, proposals, feature docs, ADRs, or technical documentation. Provides three-stage co-authoring process.
help-article-writer
Write clear, effective help center articles that reduce support tickets and empower users
doc-coauthoring
문서 작성, 문서화, 문서, 스펙 작성, 기술 문서, 제안서 - Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content.
tdc-docs
Create and maintain The Dreamer's Cave documentation. Use when updating README, CHANGELOG, API docs, component docs, or any documentation in docs/.
white-paper-author
Create authoritative white papers that establish thought leadership and educate audiences
prd
Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out.
documentation-updates
Update IBL5 documentation during pull requests and feature development. Use when updating docs, creating README files, or documenting completed work.
doc-coauthoring
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
library-docs
Write prosaic, narrative-style documentation for Lean 4 libraries. Use when creating README files, user guides, tutorials, or comprehensive library documentation.
prd-writer
PRD（Product Requirements Document）を、Universal PRDフォーマット（軽量1ページ〜詳細版まで同じ型）で作成する。 ユーザーが「PRDを書いて」「要件定義書を作って」「仕様をまとめて」「Press Release / FAQ（Working Backwards）を書いて」 「Shape UpのPitchっぽく提案書を作って」「成功指標/KPIとスコープを整理して」などを依頼したときに使う。 出力はMarkdown。必要に応じて1ページ版→標準版→詳細版へ段階的に拡張する（progressive disclosure）。
hypopermits-jupyterbook-format
Normalize or convert Markdown documents to the Jupyter Book/MyST format used by docs/source/hypopermits_jb.md, including prf: directives, admonitions for remarks, internal/external hyperlinks, and LaTeX math conventions (especially table math without raw |). Use when updating project docs to match that format.
rulebook-writing
Expert guidance for writing UP SHIP! rulebook content following Euro-style board game best practices. Use when drafting rules sections, reviewing rules clarity, restructuring content, or ensuring consistency. Covers section ordering, terminology, formatting, cross-referencing, and audience design.
codebase-documenter
This skill should be used when writing documentation for codebases, including README files, architecture documentation, code comments, and API documentation. Use this skill when users request help documenting their code, creating getting-started guides, explaining project structure, or making codebases more accessible to new developers. The skill provides templates, best practices, and structured approaches for creating clear, beginner-friendly documentation.
doc-maintenance
Guide documentation updates when changing versions, adding content, or preparing releases
tech-spec-writer
Technical specification writer. Use when creating detailed technical documentation, API specifications, or architecture documents.
do-docs-generation
Sphinx, MkDocs, TypeDoc, Nextra 등 실제 도구를 사용한 기술 명세서, API 문서, 사용자 가이드 생성 패턴. 코드에서 문서 생성, 문서 사이트 구축, 문서화 워크플로우 자동화에 활용.
manage-mdx-content
Managing "Work" and "Insight" posts using MDX and Frontmatter.
prd-writer
写 PRD、写产品需求文档、PRD 模板、新功能需求。帮助撰写高质量的产品需求文档，支持多种类型：新功能（有UI/无UI）、第三方集成、功能重构、性能/安全优化。