Documentation

Comprehensive test writing, execution, and failure analysis. Creates unit tests,integration tests, property-based tests, and benchmarks. Analyzes test failuresand improves test coverage.

Use when the user asks to generate comprehensive feature documentation with verified test cases, create feature README with code evidence, or document a complete feature with test verification. Triggers on keywords like "feature documentation", "document feature", "comprehensive docs", "feature README", "test verification", "verified documentation".

Create properly formatted Claude Code skills with YAML frontmatter, directory structure, and best practices. Use when creating new skills, converting documentation to skills, or learning how to write skills.

Use when writing or running Python tests with pytest. Covers fixtures, mocking, parametrization, freezegun for time, and async testing. Triggers on test file creation, fixture design, mocking external dependencies, or test suite architecture. Extends python-development skill.

Expert guidance for writing database migrations using golang-migrate for the mediaz SQLite database. Covers migration creation, testing, rollback capability, data preservation, and mediaz-specific patterns. Activates when users mention migrations, schema changes, database alterations, or golang-migrate.

Testing strategies and patterns (unit, integration, E2E, API tests). TRIGGERS: 'test', 'teste', 'testing', 'E2E', 'integration test', 'unit test', 'test failure'. Use when setting up tests, writing test cases, debugging test failures, implementing test patterns.

WHEN: Go API review with Gin/Echo/Fiber/Chi, router patterns, middleware, request handlingWHAT: Router organization + Middleware patterns + Request validation + Error responses + OpenAPIWHEN NOT: General Go → go-reviewer, Rust API → rust-api-reviewer

Apply Urdu typography and RTL layout logic for Docusaurus sites.Bundled Resources: Noto Nastaliq Urdu font-stack CSS, [dir=rtl] overrides, i18n scaffolding.Use when adding Urdu/RTL support to a Docusaurus project.

プロジェクトの CLAUDE.md を更新する。「CLAUDE.md を更新して」「ルールを追加」「プロジェクトルールを変更」「Claude のルール」「AI ドキュメント更新」「CLAUDE.md に追記」「ルールを編集」などで起動。プロジェクト固有のルールやガイドラインを管理。

This skill should be used when engineering decisions are being made during code implementation. The Archivist enforces decision documentation as a standard practice, ensuring every engineering choice includes rationale and integrates with Architecture Decision Records (ADRs). Use when writing code that involves choosing between alternatives, selecting technologies, designing architectures, or making trade-offs.

Ingest project documentation and code into persistent semantic memory (Qdrant + Voyage embeddings). Use when user wants to remember context across sessions, ingest docs, or search previous work. Requires Qdrant running locally and VOYAGE_API_KEY set.

Write MIDI Markdown (MMD) files with correct syntax, timing paradigms, MIDI commands, and advanced features like loops, sweeps, random values, and modulation. Use when the user wants to create or edit .mmd files, needs help with MMD syntax, is implementing MIDI automation sequences, or is troubleshooting MMD validation errors.

Guidelines and patterns for writing bash/shell scripts. Use when creating new shell scripts, bin scripts, or bash utilities. Includes script templates, header comments, error handling, and common patterns.

Systematically challenge assumptions, scope, architecture, and design decisions in understanding documents or design docs. Use before design phase to surface risks, edge cases, and overlooked considerations.

Review documentation changes for compliance with the Metabase writing style guide. Use when reviewing pull requests, files, or diffs containing documentation markdown files.

Marketing content writing frameworks and optimization techniques

Collaborative design refinement that transforms rough ideas into fully-formed specifications through Socratic questioning. Explores alternatives, validates incrementally, and presents designs in digestible chunks for feedback. Use before writing code or implementation plans when requirements are unclear or multiple approaches exist. Do NOT use when requirements are already well-defined, you're implementing a known pattern, or making small changes - proceed directly to implementation instead.

WHEN: FastAPI project review, Pydantic models, async endpoints, dependency injectionWHAT: Pydantic validation + Dependency injection + Async patterns + OpenAPI docs + SecurityWHEN NOT: Django → django-reviewer, Flask → flask-reviewer, General Python → python-reviewer

Allow droids to interact with Outline Wiki via the outlinectl CLI (auth, collections, docs) with automation-friendly JSON output.

Update PRD docs based on discrepancies report. Use this skill after running analyze-gaps to sync PRD documentation with codebase implementation. Handles IMPLEMENTED_NOT_DOCUMENTED, DIVERGED, and OUTDATED gaps.