Documentation

Keep documentation in sync with code changes across README, docs sites, API docs, runbooks, and configuration. Use when the user asks to update docs, ensure docs match behavior, or prepare docs for a release/PR.

Web search and content extraction via Brave Search API. Use for searching documentation, facts, or any web content. Lightweight, no browser required.

Building, rendering library docs, and deploying docs.cloudposse.com. Use when working with the Docusaurus build process or regenerating auto-generated content.

CSS styles, color themes, and visual conventions for docs.cloudposse.com. Use when styling components, mermaid diagrams, or working with site theming.

Generates documentation files including NotebookLM YAML and slide content. Use when user mentions ドキュメント, document, YAML, NotebookLM, スライド, slide, プレゼン. Do NOT load for: 実装作業, コード修正, レビュー, デプロイ.

Writing standards, React components, and MDX patterns for docs.cloudposse.com. Use when creating or editing documentation content.

Guides VibeCoder (non-technical users) through natural language development (legacy). Use when user mentions どうすればいい, 次は何, 使い方, 困った, help, what should I do. Do NOT load for: 技術者向け作業, 直接的な実装指示, レビュー.

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

Ingest new procedural memory (skills, patterns, docs) into the vector database.

Create, review, and refactor project documentation (README, AGENTS.md, architecture docs, runbooks, API docs) with deep codebase analysis, clear markdown structure, and diagrams/user flows. Use when asked to write or improve docs, audit existing documentation for accuracy or quality, generate diagrams/flows, or assess agent-first docs like AGENTS.md/PLANS.md for freshness and completeness.

Generate architecture diagrams as .excalidraw files from codebase analysis. Use when the user asks to create architecture diagrams, system diagrams, visualize codebase structure, or generate excalidraw files.

Systematic approach for gathering authoritative, version-accurate documentation. Claude invokes this skill when research is needed before implementation. Ensures truth over speed while achieving both.

Evaluate public API surfaces against internal guidelines and external exemplars. Triggers: API review, API design, consistency audit, API documentation, versioning, surface inventory, exemplar research Use when: reviewing API design, auditing consistency, governing documentation, researching API exemplars DO NOT use when: architecture review - use architecture-review. DO NOT use when: implementation bugs - use bug-review. Use this skill for API surface evaluation and design review.

Python testing with pytest, fixtures, mocking, and TDD workflows. Triggers: pytest, unit tests, test fixtures, mocking, TDD, test suite, coverage, test-driven development, testing patterns, parameterized tests Use when: writing unit tests, setting up test suites, implementing TDD, configuring pytest, creating fixtures, async testing DO NOT use when: evaluating test quality - use pensive:test-review instead. DO NOT use when: infrastructure test config - use leyline:pytest-config. Consult this skill for Python testing implementation and patterns.

Code quality practices: error handling, validation, logging, and DRY. Use when writing or reviewing code.

Systematic methodology to reduce skill file size through externalization, consolidation, and progressive loading patterns. Triggers: large skill, skill optimization, skill size, 300 lines, inline code, skill refactoring, skill context reduction, skill modularization Use when: skills exceed 300 lines, multiple code blocks (10+) with similar functionality, heavy Python inline with markdown, functions >20 lines embedded DO NOT use when: skill is under 300 lines and well-organized. DO NOT use when: creating new skills - use modular-skills instead. Consult this skill when skills-eval shows "Large skill file" warnings.

Design skills as modular building blocks for predictable token usage. Triggers: skill design, skill architecture, modularization, token optimization, skill structure, refactoring skills, new skill creation, skill complexity Use when: creating new skills that will be >150 lines, breaking down complex monolithic skills, planning skill architecture, refactoring overlapping skills, reviewing skill maintainability, designing skill module structure DO NOT use when: evaluating existing skill quality - use skills-eval instead. DO NOT use when: writing prose for humans - use writing-clearly-and-concisely. DO NOT use when: need improvement recommendations - use skills-eval. Use this skill BEFORE creating any new skill. Check even if unsure.

Systematically uncover and fix bugs using language-specific expertise and reproducible evidence. Triggers: bug hunting, defect detection, debugging, fix verification, bug fix, regression check, error investigation, defect documentation Use when: deep bug hunting needed, documenting defects, verifying fixes, systematic debugging required DO NOT use when: test coverage audit - use test-review instead. DO NOT use when: architecture issues - use architecture-review. Use this skill for systematic bug hunting with evidence trails.

Detect codebase bloat through progressive analysis: dead code, duplication, complexity, and documentation bloat. Triggers: bloat detection, dead code, code cleanup, duplication, redundancy, codebase health, technical debt, unused code Use when: preparing for refactoring, context usage is high, quarterly maintenance, pre-release cleanup DO NOT use when: actively developing new features, time-sensitive bug fixes. DO NOT use when: codebase is < 1000 lines (insufficient scale for bloat). Progressive 3-tier detection: quick scan → targeted analysis → deep audit.

Generate program dashboards, GitHub-ready comment digests, and CSV summaries sourced from Minister's tracker data. Triggers: initiative pulse, status report, weekly update, stakeholder briefing, github dashboard, blocker radar, initiative health, program metrics Use when: creating status reports, weekly updates, stakeholder briefings, generating GitHub comment digests, tracking initiative health DO NOT use when: release gates/readiness - use release-health-gates. DO NOT use when: project planning - use spec-kit:speckit-orchestrator. Outputs markdown digests and CSV exports for GitHub issues and PRs.