2.5천건 · 관련도순
Audit your project's documentation health and identify gaps. Scans for README, changelog, API docs, ADRs, runbooks, onboarding guides, and diagrams. Triggers: you need a documentation audit, want to check doc coverage, find missing documentation, or assess documentation quality.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when setting up or auditing how compliance documentation is structured, collected, and preserved for regulatory audit in Salesforce FSC — covering KYC data collection workflows, AML screening integration setup, audit trail configuration, and regulatory reporting readiness. Triggers: KYC form setup, AML integration configuration, compliance data collection, audit trail setup, regulatory documentation workflow, Field Audit Trail configuration, Setup Audit Trail, Event Monitoring, Discovery Framework, FSC KYC objects, Identity Document setup, Party Identity Verification. NOT for security implementation, NOT for designing AML/KYC architecture (use architect/aml-kyc-process-architecture), NOT for configuring who can access deal or client data (use admin/compliant-data-sharing-setup).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Produce or review API contract documentation for Salesforce integrations: versioning policy artifacts, request/response schema specs, error code catalogs, rate limit documentation, OpenAPI generation for sObjects. Trigger keywords: Salesforce API versioning policy, API end-of-life policy, document API endpoints, REST API rate limits, OpenAPI sObjects, API contract record, error contract, errorCode catalog, 410 GONE retired API version, HTTP 300 external ID upsert, idempotency key, deprecation notice, composite subrequest limit. NOT for building the endpoint or writing the Apex REST service — use apex/apex-rest-services. NOT for upgrading the API version on your own Apex, LWC or sfdx-project.json — use devops/api-version-management.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
ALWAYS invoke for any task involving docstrings, JSDoc/TSDoc, or REST API documentation — even when the request seems handleable without it. Enforces Microsoft contract-first conventions and a bare-minimum rule that Claude won't apply by default: never restate the signature, drop @param/@returns that only echo names and types, always document @throws, and document data shapes as WHAT not WHY. Covers Python docstring styles (Google/NumPy/Sphinx), TSDoc tags and @inheritDoc, and API doc patterns for NestJS/Express/FastAPI/Django. Trigger on: adding or auditing docstrings, redundant or missing tags, deleting comment rot, or producing a documentation-health report. Do not skip for documentation tasks — consistent conventions are the whole point.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generates OpenAPI 3.0/3.1 specs, TypeScript client types, and curl examples from existing route handler code. Supports Express, Next.js API routes, Fastify, and Hono. Produces complete documentation including auth requirements, rate limits, error codes, and request/response examples. Activate on: 'generate API docs', 'OpenAPI from code', 'document endpoints', 'API reference', 'swagger generation', 'endpoint documentation'. NOT for: API design from scratch (use api-architect), deployment (use devops-automator), testing (use test-automation-expert).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Writing quality guidelines, formatting conventions, and styling constraints for documentation. Trigger when: - Writing, editing, or auditing documentation files, READMEs, markdown files, or guides. - Modifying files with suffixes like: *.md, *.qmd, *.txt, *.rst. - Prompt contains keywords: doc, documentation, spelling, grammar, headers, links, table alignment, Divio, tone, voice, clarity.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Documentation quality standards and writing principles. Use when establishing formatting rules, reviewing doc quality metrics, creating writing guidelines, or enforcing consistent documentation style across a project.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write, review, or audit this repository's technical documentation, including README.md, CONTRIBUTING.md, root and scoped AGENTS.md files, docs pages, and documentation drift. Use for source-backed documentation authoring, behavior verification, and cross-surface consistency. Do not use for code review, deslop diff cleanup, or whole-page rewrites, splits, or reorganizations handled by docs-refactor.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Refactor a whole documentation page in this repository without losing source-verified behavior facts. Use for page rewrites, splits, reorganizations, or substantial shortening of README sections, docs pages, or instruction files. Do not use for ordinary documentation authoring, targeted corrections, or documentation review; use technical-documentation instead.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Provides patterns to generate comprehensive REST API documentation using SpringDoc OpenAPI 3.0 and Swagger UI in Spring Boot 3.x applications. Use when setting up API documentation, configuring Swagger UI, adding OpenAPI annotations, implementing security documentation, or enhancing REST endpoints with examples and schemas.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generates OpenAPI 3.0/3.1 specs, TypeScript client types, and curl examples from existing route handler code. Supports Express, Next.js API routes, Fastify, and Hono. Produces complete documentation including auth requirements, rate limits, error codes, and request/response examples. Activate on: 'generate API docs', 'OpenAPI from code', 'document endpoints', 'API reference', 'swagger generation', 'endpoint documentation'. NOT for: API design from scratch (use api-architect), deployment (use devops-automator), testing (use test-automation-expert).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Documentation knowledge base. Provides documentation types, audiences, best practices, and antipatterns for technical documentation creation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Diátaxis Documentation Expert. An expert technical writer specializing in creating high-quality software documentation, guided by the principles and structure of the Diátaxis technical documentation authoring framework.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert C4 Component-level documentation specialist. Synthesizes C4 Code-level documentation into Component-level architecture, defining component boundaries, interfaces, and relationships. Creates component diagrams and documentation. Use when synthesizing code-level documentation into logical components.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert C4 Context-level documentation specialist. Creates high-level system context diagrams, documents personas, user journeys, system features, and external dependencies. Synthesizes container and component documentation with system documentation to create comprehensive context-level architecture. Use when creating the highest-level C4 system context documentation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Documentation and narrative content for create-vue-dsfr. Use for markdown files, Storybook stories, VitePress guides, component documentation, and API documentation. Read the shared project skill before acting.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Documents TypeScript code with JSDoc comments, generates API documentation, and creates type-safe documentation. Use when users request "JSDoc", "code documentation", "API docs", "TypeDoc", or "inline documentation".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used when writing documentation for codebases, including README files, architecture documentation, code comments, and API documentation. Use this skill when users request help documenting their code, creating getting-started guides, explaining project structure, or making codebases more accessible to new developers. The skill provides templates, best practices, and structured approaches for creating clear, beginner-friendly documentation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
OpenClaw 기존 문서를 소스와 대조하며 재구성합니다. 정확한 사양 설명을 보존하고 세부 내용을 옮긴 페이지, 링크, 문서 형식까지 검증합니다.
장기 프로젝트의 기존 문서를 규칙, 구조, 현황, 결정 이력으로 정리합니다. 에이전트의 참조 경로와 갱신 규칙을 마련해 문서 불일치와 삭제한 파일의 재생성을 방지하도록 돕습니다.
제안서와 명세서를 배경 정리부터 절별 작성, 독자 검증까지 대화로 완성합니다. 작성 대화를 모르는 별도의 Claude로 설명 부족과 모호한 부분을 확인합니다.
설계 결정의 이유와 비교한 대안을 기록하고 README, API 문서, 변경 이력을 정리합니다. 새 담당자와 AI 에이전트가 구현 배경을 이해하도록 돕습니다.
최근 git 기록을 README·사양·제품 문서와 대조해 구현과 설명의 차이를 찾고, 기존 문체를 유지하며 최소한의 사실 수정 사항을 검토용 PR로 정리합니다.