Explore skills

Reviews Markdown prose against the pinned agent-style v0.3.5 rules and optionally writes a polished copy beside the source. Use for specs, ADRs, PR bodies, release notes, and technical docs when prose quality or evidence discipline matters.

Generates or updates i18n localization files, translation keys, and locale configurations. Use when adding a new language, updating translation strings, or when the user mentions localization, i18n, translation, or l10n.

Generates missing design or architecture documentation by working backwards from existing code or prototypes. Use when documentation is missing for existing code or when the user mentions documenting existing implementation or reverse engineering docs.

Syncs the .claude/ directory from an upstream template repository, showing a diff and applying new or modified files without overwriting local customizations. Use when updating SDD template files or when the user mentions template sync or upstream update.

Grounds framework, library, API, and platform-specific technical decisions in official documentation before implementation. Use when current docs, version-specific behavior, best practices, deprecations, or external API correctness matter.

Writes blameless postmortems with root cause analysis, incident timelines, contributing factors, and action items. Use when conducting incident reviews or when the user mentions postmortem, root cause analysis, or blameless review.

Session wrap-up consolidates all descriptive markdown files (README.md, AGENTS.md, HANDOFF.md, docs/*) into one canonical CLAUDE.md. It then reconciles it against the current code state so a fresh session or new teammate can pick up immediately, keeping a mandatory PROGRESS block at the top that answers: where are we now and what's the next concrete action.

Producing digital media -- writing, images, video, audio, presentations, and multimedia -- with an understanding of craft, audience, accessibility, and ethics. Covers composition principles, copyright-safe sourcing, accessibility features (alt text, captions, contrast), remix culture, attribution practices, and the difference between creating for yourself, for a small audience, and for the open we

Domain knowledge for 10 applied subjects: computer science, data science, world languages, psychology, environmental science, nutrition, economics, creative writing, logic, digital literacy. Use when generating Applied & Practical tier pack content.

Guidance for writing OpenStack operations manual procedures following NASA document standards. Use when authoring per-service procedures, maintenance workflows, or operational documentation that must be verified against running infrastructure.

Guides writing Elixir documentation with @moduledoc, @doc, @typedoc, doctests, cross-references, and metadata. Use when adding or improving documentation in .ex files.

Reviews Elixir documentation for completeness, quality, and ExDoc best practices. Use when auditing @moduledoc, @doc, @spec coverage, doctest correctness, and cross-reference usage in .ex files.