Documentation
Documentation tools and technical writing skills
6825 skills in this category
Subcategories
scottink-writer
Write in Scott's authentic voice - British, conversational, self-deprecating, code-first. Use when writing blog posts, technical content, or documentation.
blog-post-creator
Create new blog posts with proper frontmatter, structure, and ScottInk voice. Use when writing blog posts or starting technical articles.
content-linter
Lint content for spelling errors, en-GB compliance, and writing quality. Use when checking markdown files before publication.
vibe-flow
Collaborative problem-solving protocols: write technical specifications (spec), create implementation plans (plan), or use Discuss-Then-Do Protocol (dtdp). Also generates PR messages.
documentation-authoring
Create or augment skills and documentation. Use when writing new skills, updating existing skills, or modifying project documentation like AGENTS.md.
ecto-thinking
Use when writing Ecto code. Contains insights about Contexts, DDD patterns, schemas, changesets, and database gotchas from José Valim.
technical-documentation
This skill should be used when the user asks to "write documentation", "create README", "API docs", "design document", "specification", "user guide", or needs documentation guidance. Provides comprehensive documentation patterns for developers, teams, and end-users in both English and Japanese.
using-elixir-skills
Use when writing Elixir, Phoenix, or OTP code - routes to the correct thinking skill before any code is written
fact-check
This skill should be used when the user asks to "verify claims", "fact check", "validate documentation", "check sources", or needs verification of external source references. Provides patterns for systematic fact verification using Context7 and WebSearch.
phoenix-thinking
Use when writing Phoenix, LiveView, or Plug code. Contains insights about LiveView lifecycle, Scopes, PubSub, and gotchas from Chris McCord.
technical-writing
This skill should be used when the user asks to "write blog post", "technical article", "tutorial", "explain concept", or needs guidance on technical writing for external audiences. Provides patterns for technical blogs and articles in both English and Japanese.
context7-usage
This skill should be used when the user asks to "check documentation", "latest API", "library docs", "context7", or needs up-to-date library documentation. Provides Context7 MCP usage patterns.
elixir-thinking
Use when writing Elixir code. Contains paradigm-shifting insights about processes, polymorphism, and the BEAM runtime that differ from OOP thinking.
composewebview-documentation
Manages MkDocs documentation site and API references for ComposeWebView. Use when creating, updating, or building documentation, adding guides, or generating API docs. Handles mkdocs serve, build, and validation.
otp-thinking
Use when writing OTP code in Elixir. Contains insights about GenServer bottlenecks, supervision patterns, ETS caching, and choosing between OTP abstractions.
llms-txt-support
Detect and use llms.txt files for LLM-optimized documentation. Use when checking if a site has LLM-ready docs before scraping.
llms-txt-support
Detect and use llms.txt files for LLM-optimized documentation. Use when checking if a site has LLM-ready docs before scraping.
ai-pattern-detection
Detects AI-generated writing patterns and suggests authentic alternatives. Auto-applies when reviewing content, editing documents, generating text, or when user mentions writing quality, AI detection, authenticity, or natural voice. Use when relevant to the task.
source-unifier
Merge multiple documentation sources (docs, GitHub, PDF) with conflict detection. Use when combining docs + code for complete skill coverage.
voice-analyze
Reverse-engineer voice profiles from sample content by analyzing writing patterns. Use when relevant to the task.