Documentation
Documentation tools and technical writing skills
6825 skills in this category
Subcategories
writing-documentation
Creates technical documentation including READMEs, API references, user guides, architecture docs, ADRs, and runbooks. Use for requests to create, write, generate, or draft documentation. Trigger phrases include "document this", "write docs", "create readme", "API reference", "user guide", "architecture docs", "ADR", "runbook". For updating existing READMEs, use updating-readme instead.
test-writing
TDD(テスト駆動開発)に基づいたテストコード作成スキル。Red-Green-Refactorサイクルを実践し、t-wadaのベストプラクティスに従ってテストファーストで高品質なテストを作成します。Backend(Go test)とFrontend(Jest)の両方に対応。
zenn-markdown
This skill should be used when the user asks about "Zenn記法", "Zenn Markdown", "メッセージブロック", "アコーディオン", "埋め込み", "Zenn特有の記法", or mentions writing Zenn articles with specific formatting needs. Provides comprehensive knowledge of Zenn-specific Markdown syntax and best practices.
pal-analyze
Comprehensive code analysis for architecture, performance, security, and quality using PAL MCP. Use when reviewing codebases, assessing technical decisions, or planning improvements. Triggers on analysis requests, architecture reviews, or code quality assessments.
project-linking
Use when session starts with CLAUDE.local.md containing Vault project field - automatically loads vault index, enables dual-location routing (vault + local docs), style adaptation, and cross-location linking with GitHub URLs for Obsidian project documentation