Documentation knowledge base. Provides documentation types, audiences, best practices, and antipatterns for technical documentation creation.
Skills（SKILL.md）は、AIエージェント（Claude Code、Cursor、Codexなど）に特定の能力を追加するための設定ファイルです。
詳しく見る →Documentation knowledge base. Provides documentation types, audiences, best practices, and antipatterns for technical documentation creation.
Add a professional footer to README files with engagement prompts, community channels, and call-to-action for subscriptions. Use when you need to enhance your README with a footer that encourages interaction and builds community.
Analyze code changes and recommend appropriate documentation. Evaluates git diffs to determine if changes warrant README updates, inline doc additions, or dedicated documentation files. Triggers on: document changes, what should I document, doc writer, write docs for changes, documentation recommendation.
Documentation management for README, CHANGELOG, API docs, and user-facing documentation. Use when creating or updating project documentation.
Human and agent coordination protocol for repos using .agentprotocol. Use to manage TODO intake, open and archived work items, and plan/build docs with deterministic indexes.
Album concepts, tracklist architecture, and thematic planning
Создание профессиональных аналитических справок в формате DOCX. Использовать при запросах на создание аналитических справок, информационных записок, правовых меморандумов, обзоров судебных споров, корпоративных отчётов для руководства. Документы создаются на русском языке с профессиональным юридическим стилем изложения.
Copy this checklist and track progress:
Use when structuring and reusing code with Ansible roles for modular, maintainable automation and configuration management.
Validate ASCII diagram alignment in markdown. TRIGGERS - diagram alignment, ASCII art, box-drawing diagrams.
Create atomic commits grouped by logical features with README.md and CLAUDE.md awareness.
Audits the project for consistency issues that may arise from manual editing. Checks package scripts, tsconfig paths, README tables, and other conventions.
Use when managing blueprints directory structure and avoiding duplication. Always search_blueprints before creating to prevent duplicate documentation. Handles naming conventions and cross-references.
Use when creating or updating technical blueprint documentation for new features, API changes, or architectural modifications. Always use search_blueprints first to avoid duplication, then write_blueprint with proper structure.
How to create & maintain TypeDoc site documentation and the README for Bupkis
Use when documenting component implementation patterns, internal structure, or hand-off points - enforces NO CODE rule and diagram-first approach for leaf-level C3 documentation
Use when changes affect component organization, technology stack, or cross-container communication - triggered by new components, pattern changes, or needing to map external interfaces to internal components
Use when exploring Context level impact during scoping - system boundaries, actors, cross-container interactions, and high-level concerns
Use when designing, updating, or exploring system architecture with C3 methodology - iterative scoping through hypothesis, exploration, and discovery across Context/Container/Component layers
When fetching library documentation, API references, or technical docs for project dependencies via WebFetch, automatically save a copy to the docs/ folder. Also triggers when user pastes documentation or discusses library APIs that should be cached for reference. Every non-stdlib import in the project should have corresponding reference docs cached.
William Strunk Jr.'s _The Elements of Style_ (1918) teaches you to write clearly and cut ruthlessly.
>-
Shadow DOM 팝업을 가진 컴포넌트를 생성합니다. 컴포넌트가 직접 데이터를 fetch하고 팝업으로 표시합니다. 3D 씬, 독립 위젯 등에 사용합니다.
Create new pages or notes in the readme-pages project. Use when the user asks to create, add, or write a new page, note, article, or blog post. This skill handles file creation with proper frontmatter, filename conventions, and placement in the correct content collection.
RNBT 아키텍처 패턴에 맞는 완전한 대시보드 페이지를 생성합니다. Master/Page 레이어, 여러 컴포넌트, Mock 서버, datasetList.json을 포함합니다.
표준 RNBT 컴포넌트를 생성합니다. 페이지가 GlobalDataPublisher로 데이터를 제어합니다.
Git リポジトリの慣習に則って新しいブランチを作成します。ユーザーがブランチの作成を求めたときや、エージェントがブランチを作成するときに必ず使用してください。
Patterns and standards for creating new AWS service subpackages in the monorepo. Use when adding new service packages like Lambda, DynamoDB, Step Functions, etc.
CS 문서의 폴더 구조나 파일명이 변경될 때 깨진 마크다운 링크를 찾아 수정하는 Skill입니다.
General documentation standards for README, AsciiDoc, and technical documentation
データベースアダプター（PostgreSQL/MySQL両対応）の開発・修正を行う際に使用。SqlExecutorパターン、マイグレーション、DB固有SQL実装時に役立つ。
The unified AI agent for Polyprophet - combines deep analysis, precise execution, and atomic-level investigation. One agent, one skill, one mission.
코드베이스를 분석하여 README, API 문서, 아키텍처 가이드를 자동으로 생성/업데이트합니다.
CareMatch V3 개발 로그를 작성하고 프로젝트 상태를 추적합니다.
Create comprehensive developer onboarding documentation including setup guides, README files, contributing guidelines, and getting started tutorials. Use when onboarding new developers or creating setup documentation.
Read product and technical docs, then summarize requirements and gaps.
doc-blueprint
Post structured documentation to GitHub issue as a comment. Use when starting work on an issue to document approach and track progress.
Maintains high-quality, concise, project-aligned documentation. Creates, updates, and validates README.md, CLAUDE.md, code comments, and other documentation. Activates after implementing features, when documentation is outdated, or when explicitly requested.
doc-structure
Maintains the CLAUDE.md navigation hierarchy and optional README.md architecture docs across a repository. This skill is self-contained and performs all documentation work directly.
技术文档工程 - Diátaxis框架 / PDF / DOCX / XLSX / PPTX 处理。Create, maintain, and structure clear technical documentation.
> **Triggers** (ANY of these should invoke this skill):
docs-workflow
Assess organizational doctrine and universally useful patterns
プロジェクト内のドキュメント（README.md、CHANGELOG.md、docs/ など）を監査し、コード変更に基づいて更新が必要な箇所を特定・提案します。作業完了後のドキュメント更新確認に使用。
Create comprehensive technical documentation including API docs, component libraries, README files, architecture diagrams, and developer guides using tools like JSDoc, Storybook, or Docusaurus. Use when documenting APIs, creating component documentation, writing README files, generating API references, documenting architecture decisions, creating onboarding guides, maintaining changelogs, documenting configuration options, or building developer documentation sites.
Keep project documentation accurate when behavior changes. EXCLUSIVE to project-manager agent.
Apply when writing code documentation: JSDoc comments, README files, API documentation, and inline comments.
Universal documentation standards and best practices for software projects