Technical Writing

The seo skill helps audit, plan, and implement technical SEO, on-page optimization, structured data, Core Web Vitals, and keyword mapping. Use it for crawlability, indexability, metadata, schema, internal linking, sitemap and robots changes, or seo for Keyword Research, with page-specific, implementable guidance.

The java-coding-standards skill provides practical guidance for readable, maintainable Java 17+ in Spring Boot services, covering naming, immutability, Optional, streams, exceptions, generics, and package layout. Use it for coding, refactoring, and java-coding-standards for Code Review.

cpp-coding-standards is a C++ coding standards guide based on the C++ Core Guidelines. Use it for writing, reviewing, and refactoring modern C++ with a focus on safety, clarity, maintainability, RAII, type safety, and good design. Ideal for cpp-coding-standards for Code Review and practical team decisions.

code-tour creates reusable CodeTour .tour files with real file and line anchors. Use the code-tour skill for onboarding tours, architecture walkthroughs, PR tours, RCA paths, and code-tour for Technical Writing when you need a guided sequence instead of a flat summary.

The article-writing skill helps draft long-form content with strong structure, voice consistency, and evidence. Use it for articles, guides, tutorials, newsletters, and article-writing for Copywriting workflows where polished, publishable prose matters.

architecture-decision-records helps capture architectural decisions during Claude Code sessions as structured ADRs. It detects decision moments, records context, alternatives, and rationale, and keeps an ADR log for future maintainers. Useful for Technical Writing and engineering teams that need durable decision history.

api-design is a REST API design skill for planning and reviewing endpoints, resource naming, status codes, pagination, filtering, versioning, and error responses.

brainstorming is a pre-implementation skill that explores context, asks clarifying questions one at a time, and requires design approval before any code. Includes an optional visual companion and strong support for Requirements Planning.

writing-plans helps turn a spec or requirements doc into a detailed implementation plan with file-level guidance, task sequencing, testing steps, and a review prompt before coding starts.

doc-coauthoring is a structured workflow for drafting docs with AI through context gathering, iterative outlining, section-by-section writing, and reader testing for review-ready specs, RFCs, and proposals.

technical-writer is a lightweight documentation skill for creating clearer README files, API docs, setup guides, tutorials, onboarding docs, and release notes. It centers Technical Writing on user goals, quick starts, examples, and troubleshooting. The skill is delivered as a single SKILL.md file with no extra scripts or templates.

document-release is a post-ship documentation update skill that reads project docs, cross-references the shipped diff, and updates README, ARCHITECTURE, CONTRIBUTING, CLAUDE.md, CHANGELOG, and VERSION so docs match what actually shipped. Use the document-release skill for technical writing when code is already merged and you need a reliable document-release guide.

caveman is an ultra-compressed communication skill for concise technical replies, summaries, and debugging help. It keeps technical meaning intact, drops filler, and stays active after trigger until you say stop caveman or normal mode. Best for Technical Writing, code review notes, incident updates, and faster back-and-forth when you already know the topic.

The edit-article skill helps you restructure existing drafts, improve clarity, and tighten prose. Use it when you need a reliable edit-article guide for revising articles, especially in technical writing workflows where section order and dependencies matter.

writing-shape is a conversational drafting skill for turning markdown raw material into a publishable article. It helps with opening selection, paragraph-by-paragraph development, and structure choices for Technical Writing, interview notes, transcript cleanup, and rough drafts. Use the writing-shape guide when you need a guided editorial process rather than a one-shot prompt.

grill-with-docs is a planning-and-documentation skill that pressure-tests your plan against the repo’s existing domain model, sharpens terminology, and updates CONTEXT.md and ADRs as decisions crystallize. Use it for Technical Writing, product-minded engineering, and any workflow where repo-grounded language matters more than a prompt-only brainstorm.

ubiquitous-language is a DDD-style skill that extracts a shared glossary from conversations, flags ambiguous terms and synonyms, and writes UBIQUITOUS_LANGUAGE.md. Use it to define domain terms, align teams, and improve ubiquitous-language for Technical Writing.

python-code-style helps with Python formatting, linting, naming, type hints, and docstrings. Use it to review pull requests, standardize team conventions, and set up ruff, mypy, or pyright guidance in pyproject.toml.

architecture-decision-records helps teams draft and maintain ADRs with clear context, decisions, alternatives, and consequences for durable technical decision documentation.

The changelog-automation skill helps teams design changelog workflows with Keep a Changelog, SemVer, release notes, and Conventional Commits. Use it to plan install context, define usage inputs, and improve release-note consistency for Technical Writing and developer documentation.

The add-educational-comments skill adds teaching-focused comments to a specified code file while preserving structure and behavior. It can ask for a file if missing, adapts to reader level, and follows clear line-growth limits for educational code editing.

gws-docs helps you read and write Google Docs through the gws CLI with method-level control for creation, fetching, and batch updates. Follow the install, schema, and usage flow in the gws-docs guide for technical writing and documentation automation.

adr-skill helps teams create and maintain Architecture Decision Records that agents can execute. It supports drafting, bootstrapping ADR folders, choosing templates, updating status, and validating decisions with checklists, scripts, and examples.

Clarify improves confusing UX copy, error messages, labels, onboarding steps, and instructions so users can act with less guesswork. It is useful for Technical Writing, support content, and product teams that need clearer interface text. The skill starts with context, audience, and user state before rewriting, so the result is more direct, specific, and usable.