Total 43,811 skills, Documentation & Writing has 1293 skills
Showing 12 of 1293 skills
Document business rules, technical patterns, and service interfaces discovered during analysis or implementation. Use when you find reusable patterns, external integrations, domain-specific rules, or API contracts. Always check existing documentation before creating new files. Handles deduplication and proper categorization.
The craft of communicating technical concepts clearly to developers. Developer communications isn't marketing—it's about building trust through transparency, accuracy, and genuine utility. The best devrel content helps developers solve real problems. This skill covers technical documentation, developer tutorials, API references, changelog writing, developer blog posts, and developer community engagement. Great developer communications treats developers as peers, not leads to convert. Use when "documentation, docs, tutorial, getting started, API reference, changelog, release notes, developer guide, devrel, developer relations, code examples, SDK docs, README, documentation, devrel, tutorials, api-docs, developer-experience, technical-writing, getting-started, changelogs" mentioned.
Workflow navigation assistant that recommends next steps and optimizes documentation sequence through the SDD workflow
Create Technical Specifications (SPEC) - Layer 10 artifact using YAML format for implementation-ready specifications
Create Business Requirements Documents (BRD) following SDD methodology - Layer 1 artifact defining business needs and objectives
Expert technical documentation specialist for developer docs, API references, and runbooks. Activate on: documentation, docs, README, API reference, technical writing, user guide, runbook, ADR, changelog, release notes, tutorial, how-to guide. NOT for: marketing copy (use copywriting skills), blog posts (use content skills), code comments (handled by developers).
Write neuroscientific, peer-oriented drug education content that roots experiences in body/brain mechanisms. Use when creating educational articles, explaining neurological phenomena, demystifying recovery challenges, or answering "why does this happen?" questions. Activates for harm reduction content, psychoeducation, recovery science writing, and content that reduces shame through understanding.
Configures ExDoc for Elixir projects including mix.exs setup, extras, groups, cheatsheets, and livebooks. Use when setting up or modifying ExDoc documentation generation.
Reference documentation patterns for API and symbol documentation. Use when writing reference docs, API docs, parameter tables, or technical specifications. Triggers on reference docs, API reference, function reference, parameters table, symbol documentation.
Guides writing Elixir documentation with @moduledoc, @doc, @typedoc, doctests, cross-references, and metadata. Use when adding or improving documentation in .ex files.
Generate CLAUDE.md project memory files that transfer institutional knowledge, not obvious information. Use when setting up new journalism projects, onboarding collaborators, or documenting project-specific quirks. Includes templates for editorial tools, event websites, publications, research projects, content pipelines, and digital archives.
Guidelines for Go documentation including doc comments, package docs, godoc formatting, runnable examples, and signal boosting. Use when writing or reviewing documentation for Go packages, types, functions, or methods.