文件

Use when creating new skills, editing existing skills, or verifying skills work before deployment - applies TDD to process documentation by testing with subagents before writing, iterating until bulletproof against rationalization

Generates README files, API documentation, changelogs, runbooks, and SDK code from project analysis. Use when creating documentation, generating changelogs, documenting APIs, creating runbooks, or generating client SDKs.

Your approach to handling global validation. Use this skill when working on files where global validation comes into play.

Review and improve documentation quality using best practices. Use when reviewing changelogs, documentation, or any written content to ensure clarity, accuracy, and helpfulness.

プロジェクトドキュメントの作成・編集を支援します。ドキュメントの追加、更新、翻訳（日本語・英語の両方）、Markdown フォーマット、ドキュメント構造の維持などに使用します。必ず日本語版と英語版の両方を同時に更新します。

Synchronized documentation updates across CLAUDE.md, README.md, .claude/CLAUDE.md, and deployment checklist to ensure consistency. Use when adding new architecture documents, analysis documents, or critical reference documents.

Expert at TSDoc comments, Storybook stories, VitePress docs, TypeDoc API generation. Use when documenting code, adding comments, creating stories, or generating API docs.

Skills wiki intro - mandatory workflows, search tool, brainstorming triggers

비정형 마크다운 작성을 markdown-writer-agent에 위임

Writing style guidelines for clear, human-centered communication. Use when writing blog posts, documentation, README files, marketing copy, emails, or any external-facing content. Apply these rules to produce direct, specific, jargon-free writing.

Build and maintain high-quality documentation using MkDocs Material. Use this skill to set up new documentation sites or maintain existing ones with a modern, dark-mode-first aesthetic.

Newman/Postman collection testing patterns for API testing with environment variables, test assertions, and reporting. Use when building API tests, running Newman collections, testing REST APIs, validating HTTP responses, creating Postman collections, configuring API test environments, generating test reports, or when user mentions Newman, Postman, API testing, collection runner, integration tests, API validation, test automation, or CI/CD API testing.

Clear writing standards based on Zinsser's principles. Use for documentation, commit messages, PR descriptions, and technical communication.

Use when working with docusaurus-plugin-glossary to configure, manage glossary terms, troubleshoot issues, and explain features

Spec-First, Agent-Implemented Software Development Lifecycle. Use when: (1) Starting a new software project that needs structured design-before-code approach, (2) User mentions "SDLC", "spec-first", "design docs", or "implementation spec", (3) User wants to go from requirements/intent to working code with traceability, (4) Project requires documented architectural decisions and review checkpoints, (5) User has existing design artifacts and wants to continue from a specific phase. Produces: Intent doc → HLD → ADR-Lite → EIS → Code → Validation tests.

Design system architectures with focus on scalability, maintainability, and user value. Create comprehensive architectural documentation including technology decisions, API design, data architecture, and security. Use when designing new systems, making technology choices, or planning system migrations.

Product Owner & App Journey Architect role skill. Use when Claude needs to act as a seasoned product owner who translates business goals into clear, actionable product requirements; identifies gaps, ambiguities, and hidden assumptions; designs and documents user journeys, system flows, and state diagrams using Mermaid; reviews high-level designs for completeness and feasibility; uncovers edge cases, failure scenarios, and error-handling strategies; and validates specifications are build-ready. Triggered by requests to review product specs, design user journeys, create system flows, challenge requirements clarity, identify design gaps, or architect application flows.

Analyzes codebases to generate comprehensive documentation including structure, languages, frameworks, dependencies, design patterns, and technical debt. Use when user says "analyze repository", "understand codebase", "document project", or when exploring unfamiliar code.

This is a new rule

Guide experienced developers on test structure, patterns, assertions, and test doubles for effective test-driven development