Documentation check checkpoint for conductor gates. Analyzes code changes to determine if documentation needs updating. Returns structured result with pass/fail status and documentation suggestions.

Consolidate redundant documentation while preserving 100% of valuable content.

Technical writing patterns for README files, API documentation, architecture decision records (ADRs), changelogs, contributing guides, code comments, and docs-as-code workflows. Covers documentation structure, style guides, Markdown best practices, and documentation testing.

Comprehensive MDX component patterns (Note, Pitfall, DeepDive, Recipes, etc.) for all documentation types. Authoritative source for component usage, examples, and heading conventions.

Validate consistency across SEED Design component documentation layers (design guidelines in ./docs/content/docs/components, Rootage specs in ./packages/rootage/components, and React docs in ./docs/content/react/components). Use when auditing documentation completeness, before releases, or validating new component docs.

Ensure consistency of documentation files. Use this skill when you made a significant change to the codebase that may affect the documentation (like feature addition), or when you made a significant change to the documentation itself.

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

WCAG-compliant Mermaid diagrams using verified accessible color palette. Use when creating diagrams, flowcharts, or any color-dependent visualizations requiring accessibility compliance for color blindness.

Comprehensive guide for creating by-example tutorials - code-first learning path with 75-90 heavily annotated examples achieving 95% language coverage. Covers five-part example structure, annotation density standards (1-2.25 comments per code line PER EXAMPLE), self-containment rules, and multiple code blocks for comparisons. Essential for creating by-example tutorials for programming languages on educational platforms

Add an interactive demo to the Remotion documentation. Use when creating a new <Demo> component for docs pages.

Handles multi-document operations with pattern matching and parallel execution, delegating to docs-manager-skill for each matched document

Technical documentation discovery via context7 and web search. Capabilities: library/framework docs lookup, topic-specific search. Keywords: llms.txt, context7, documentation, library docs, API docs. Use when: searching library documentation, finding framework guides, looking up API references.

Guide users through structured co-authoring, improvement, and QA of documentation. Use when users want to write or improve docs such as proposals, technical specs, decision docs, READMEs, guides, API docs, or runbooks; or when they ask for doc review, doc QA, checklists, or templates to make documentation clearer, skimmable, and correct for readers.

Explores internal documentation (brain repos, Notion) for context

Fetch current documentation for libraries to ensure accurate, up-to-date code generation.

Generate Level 1 (README.md) user documentation from design docs. Use when creating or updating package README files for npm/GitHub.

Generate Level 2 (repository docs) from design docs. Use when

Generate Level 3 (documentation sites) from design docs. Use when

Generate documentation for code, APIs, and components

Generate hierarchical documentation structures optimized for AI coding agents with minimal token usage. Supports AGENTS.md, agent.d, and custom documentation formats.

Docs Guide Agent. 튜토리얼, 사용 가이드 작성을 담당합니다.

General reference documents by domain. Use when creating architecture docs, strategy documents, specs, or guides.

Docs Internal Agent. 아키텍처 문서, 온보딩 가이드 작성을 담당합니다.

docs-keeper

Maintain sloc-guard project documentation. Use when user completes a feature and asks to update docs.

Single source of truth and librarian for ALL Claude official documentation. Manages local documentation storage, scraping, discovery, and resolution. Use when finding, locating, searching, or resolving Claude documentation; discovering docs by keywords, category, tags, or natural language queries; scraping from sitemaps or docs maps; managing index metadata (keywords, tags, aliases); or rebuilding index from filesystem. Run scripts to scrape, find, and resolve documentation. Handles doc_id resolution, keyword search, natural language queries, category/tag filtering, alias resolution, sitemap.xml parsing, docs map processing, markdown subsection extraction for internal use, hash-based drift detection, and comprehensive index maintenance.

Orchestrates complete single-document workflows with automatic validation and indexing in a write→validate→index pipeline

Orchestrates comprehensive documentation management by coordinating docs-analyzer, docs-bootstrapper, and mermaid-expert skills. Proactively monitors code changes and ensures documentation stays synchronized with the codebase.

Navigate hierarchical ai-docs indexes to find documentation. Check local docs FIRST for speed and curated context before web searching. Covers Claude Code, BAML, MCP, and other tracked libraries.

Activates the Technical Writer to generate, update, or refactor internal project documentation. Use when creating READMEs, ADRs, or technical guides.

Write YAML front matter for documentation pages with appropriate titles and descriptions for social cards.

README best practices ve proje dokümantasyon şablonları.

Retrieve documentation context from local ai-docs. Check here first when implementing features, debugging errors, or needing library information. Fall back to web search if topic not found locally.

Use when adding interactive code examples to React docs.

Searches the aem.live documentation for information on AEM Edge Delivery Services features. Use this skill when you need more information about a feature, want guidance on how to implement a feature, and using existing tools you have to search the web isn't turning up relevant results.

Search technical documentation using executable scripts to detect query type, fetch from llms.txt sources (context7.com), and analyze results. Use when user needs: (1) Topic-specific documentation (features/components/concepts), (2) Library/framework documentation, (3) GitHub repository analysis, (4) Documentation discovery with automated agent distribution strategy

Searching internet for technical documentation using llms.txt standard, GitHub repositories via Repomix, and parallel exploration. Use when user needs: (1) Latest documentation for libraries/frameworks, (2) Documentation in llms.txt format, (3) GitHub repository analysis, (4) Documentation without direct llms.txt support, (5) Multiple documentation sources in parallel

Knowledge of documentation platforms and fetching strategies. Use when adding new documentation sources, determining fetch strategy for a docs site, detecting doc frameworks, or configuring the docs registry.

Generate complete, professional documentation for any project.

Complete CRUD for SDLC documentation (stories, tasks, context retrieval). Use when creating/managing stories, creating/managing tasks, updating task state, or retrieving full context for any user story via index (<3min restoration).

Automatically applies when drafting or revising documentation to enforce repository voice, clarity, and navigation patterns.

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

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.

Automatically regenerate README.md from Betty Framework registries

Automates documentation maintenance. Detects modified files via git diff, creates docs for new files, updates docs for modified files, generates changelog. Use after implementation to keep docs current.

Standard procedure for updating documentation

Expert assistant for keeping documentation synchronized with code changes in the KR92 Bible Voice project. Use when updating API docs, maintaining architecture diagrams, syncing README, updating CLAUDE.MD, or generating documentation from code.

Comprehensive link validation methodology for markdown links including format requirements, path validation, broken link detection, external link verification, and checker implementation patterns

You are a documentation quality expert for the Logseq Template Graph project. Your role is to validate, audit, and ensure high-quality documentation across the project.

Documentation verification for 3-Tier system - validates line limits, cross-references, file counts