2,099 件 ・ 関連度順
概要と使いどころ
You are a documentation expert specializing in creating comprehensive, maintainable documentation from code. Generate API docs, architecture diagrams, user guides, and technical references using AI-powered analysis and industry best practices.
日本語の概要は準備中です。原文の説明を表示しています。
Creates comprehensive technical documentation from existing codebases. Analyzes architecture, design patterns, and implementation details to produce long-form technical manuals and ebooks. Use PROACTIVELY for system documentation, architecture guides, or technical deep-dives.
日本語の概要は準備中です。原文の説明を表示しています。
Expert C4 Code-level documentation specialist. Analyzes code directories to create comprehensive C4 code-level documentation including function signatures, arguments, dependencies, and code structure. Use when documenting code at the lowest C4 level for individual directories and code modules.
日本語の概要は準備中です。原文の説明を表示しています。
Master API documentation with OpenAPI 3.1, AI-powered tools, and modern developer experience practices. Create interactive docs, generate SDKs, and build comprehensive developer portals. Use PROACTIVELY for API documentation or developer portal creation.
日本語の概要は準備中です。原文の説明を表示しています。
Expert C4 Container-level documentation specialist. Synthesizes Component-level documentation into Container-level architecture, mapping components to deployment units, documenting container interfaces as APIs, and creating container diagrams. Use when synthesizing components into deployment containers and documenting system deployment architecture.
日本語の概要は準備中です。原文の説明を表示しています。
Chooses documentation tooling. Starlight, Docusaurus, DocFX decision tree, migration paths.
日本語の概要は準備中です。原文の説明を表示しています。
Git commit and pull request conventions. USE FOR: writing commit messages; checking Conventional Commits and gitmoji; branch naming; rebase workflow on develop; PR titles and target branch. PRIORITY: this skill overrides other rules when creating commits/PRs. DO NOT USE FOR: code implementation (use code-implementation skill); testing (use test-writing skill); general documentation (use documentation skill).
日本語の概要は準備中です。原文の説明を表示しています。
Unit and integration testing strategy. USE FOR: writing tests; coverage improvements; vitest specs; test refactoring. DO NOT USE FOR: production code changes (use code-implementation skill); documentation (use documentation skill); commits (use commit-conventions skill).
日本語の概要は準備中です。原文の説明を表示しています。
Generate comprehensive documentation for content authors taking over an AEM Edge Delivery Services project. Use when onboarding content authors, training content managers, or creating author-focused handover documentation — analyzes project structure and produces a complete authoring guide with blocks, templates, configurations, and publishing workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Generate comprehensive admin documentation for AEM Edge Delivery Services project handover. Use when handing over admin responsibilities, onboarding a new site administrator, or documenting admin procedures — e.g., "admin guide", "admin documentation", "admin handover".
日本語の概要は準備中です。原文の説明を表示しています。
Generate project handover documentation for AEM Edge Delivery Services projects. Creates comprehensive guides for content authors, developers, and administrators. Use for "handover docs", "project documentation", "generate handover", "create guides".
日本語の概要は準備中です。原文の説明を表示しています。
Generate comprehensive technical documentation for developers taking over an AEM Edge Delivery Services project. Use when onboarding developers, creating technical handover documentation, or documenting a project's architecture — analyzes codebase structure, custom implementations, design tokens, and produces a complete developer guide.
日本語の概要は準備中です。原文の説明を表示しています。
Write and review component documentation (MDX) and registry descriptions. Covers doc structure, description writing, Features, Composition, Credits, and References sections. Use when creating new component docs, updating descriptions, adding Features sections, adding Composition sections, adding Credits sections, adding References sections, or reviewing component documentation quality.
日本語の概要は準備中です。原文の説明を表示しています。
Create or update source-grounded documentation when the user explicitly asks for docs/ADR/onboarding material, a public contract change requires docs, or an accepted hard-to-reverse decision meets the ADR gate; do not trigger for every feature, architecture discussion, implementation, review, or SHIP request.
日本語の概要は準備中です。原文の説明を表示しています。
Sets up Storybook for component documentation with controls, actions, accessibility testing, and visual regression. Use when users request "Storybook setup", "component documentation", "UI library", "component stories", or "design system docs".
日本語の概要は準備中です。原文の説明を表示しています。
Generates OpenAPI 3.0/3.1 specifications from Express, Next.js, Fastify, Hono, or NestJS routes. Creates complete specs with schemas, examples, and documentation that can be imported into Postman, Insomnia, or used with Swagger UI. Use when users request "generate openapi", "create swagger spec", "openapi documentation", or "api specification".
日本語の概要は準備中です。原文の説明を表示しています。
Generates comprehensive README files with badges, installation, usage, API docs, and contribution guidelines. Use when users request "README", "project documentation", "readme template", "documentation generator", or "project setup docs".
日本語の概要は準備中です。原文の説明を表示しています。
Generates comprehensive documentation templates for open-source and internal projects including README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT, LICENSE, and other standard docs with suggested sections and best practices. Use when users request "create project docs", "add OSS documentation", "setup standard docs", or "make it open-source ready".
日本語の概要は準備中です。原文の説明を表示しています。
Generate comprehensive, developer-friendly API documentation from code, including endpoints, parameters, examples, and best practices
日本語の概要は準備中です。原文の説明を表示しています。
Creates comprehensive documentation for design systems - token tables, usage guidelines, component examples, and accessibility notes. Use after generating tokens to create developer-friendly docs.
日本語の概要は準備中です。原文の説明を表示しています。
計画や設計を掘り下げる質問を重ね、内容を具体化しながら設計判断の記録と用語集も作ります。検討と文書化を同じ対話の中で進めたいときに使うスキルです。
TypeScriptのパッケージ内部への直接参照や循環依存を検出し、公開ファイルだけを入口にする構成を、設定・検証・文書化まで整えるスキル。
公式文書・ソースコード・仕様などの一次資料で疑問を調べ、各主張の出典を添えた調査メモをMarkdownにまとめてリポジトリへ保存するスキル。
Perform evidence-backed impact analysis before changing code, data, interfaces, or governance documents, then compare the planned impact with the actual diff after implementation. Covers call paths, data and schema, API contracts, tests, documentation, ADRs, deployment, migration, and rollback. Use for cross-module or high-risk changes, database migrations, authentication, public interfaces, blast-radius questions, pre-change checks, and post-implementation alignment.
日本語の概要は準備中です。原文の説明を表示しています。