2.6천건 · 관련도순
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Documentation templates and structure guidelines. README, API docs, code comments, and AI-friendly documentation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create sales collateral such as decks, one-pagers, objection docs, demo scripts, playbooks, and proposal templates. Use when a sales team needs assets that help reps move deals forward and close.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate two complementary onboarding documents that together give any engineer — from newcomer to principal — a complete understanding of a codebase. Use when user asks for onboarding docs or getting-started guides, user runs /deep-wiki, or user wants to help new team members understand a codebase.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Ensure requirement docs define scope, terminology, acceptance criteria, edge cases, and non-functional requirements.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Checks design/ADR docs for consistency and missing decisions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Ensure architecture docs define RPO/RTO, failover paths, data consistency, and DR drillability.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Ensure design docs explicitly capture risks, assumptions, and open questions with owners, deadlines, and mitigation plans.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Ensure architecture/design docs state traffic assumptions, performance budgets, resource limits, and cost risks for critical paths.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Ensure architecture docs define bounded contexts, ownership, and a consistent ubiquitous language to prevent domain drift and coupling.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Ensure architecture docs capture availability targets, failover strategy, capacity headroom, and resilience trade-offs for critical services.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Ensure architecture/design docs define clear boundaries, ownership, dependency direction, and change impact to avoid tight coupling.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Normalizes documentation and examples for consistency in style, format, and accuracy. Ensures code matches existing patterns and documentation. Use when reviewing docs, examples, or writing new code that should follow established patterns.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
microCMSの公式開発者ドキュメント(document.microcms.io)を取得し、API仕様・制限・認証・クエリ・管理画面の操作手順を出典付きで確認する。最新の仕様確認や公式資料・コード例の参照が必要な場合に使用する。プロジェクトの設計・実装・改善はmicrocms-guide、Next.js固有の実装はmicrocms-nextjsを優先し、必要な仕様確認をこのSkillで補う。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Interactive Domain-Driven Design modeling sessions based on DDD Distilled (Vaughn Vernon) and Domain Modeling Made Functional (Scott Wlaschin). Guides users through strategic and tactical design via 13 phases: discover, storming, contexts, mapping, aggregates, events, validate, glossary, workflows, types, simulate, publish, sync. Phase 13 (sync) reconciles divergences found by --analyze between the domain model and the implementation — judging whether the model or the code is authoritative, then planning and implementing the fix and re-aligning the model. Phases 9-11 take the conceptual model from phases 1-8 and produce workflow pipeline designs, compilable type definitions (TypeScript, Kotlin, Scala, Rust, C#, F#), workflow verification via type-level tests, and automatic UI field enumeration from the domain model. Phase 12 (publish) renders all docs/domain artifacts into one self-contained, cross-linked HTML site (separate files joined by a shared nav). Each phase is an interactive dialogue where AI acts as facilitator and domain expert challenger. Use when: "DDD", "ドメイン設計", "ドメインモデリング", "Event Storming", "Bounded Context", "集約設計", "ユビキタス言語", "コンテキストマップ", "ワークフロー設計", "パイプライン設計", "ステップ分割", "中間型", "型駆動フロー", "型駆動設計", "Domain Modeling Made Functional", "Railway Oriented Programming", "入力画面項目", "フォーム項目洗い出し", "UI 項目抽出", "HTMLにまとめる", "ドキュメントサイト化", "成果物を1つのHTMLに", "publish", "モデルと実装の差異", "差異解消", "実装との乖離", "モデルとコードを一致", "差異の実装計画", "sync", "複数フェーズを逐次実行", "フェーズをまとめて実行", "/ddd run", "サブコマンド一覧", "/ddd list", "/ddd", "ドメイン分析したい", "モデリングしたい", or any domain design / type modeling activity.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate AI agent skills from TypeScript documentation
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
MCP server documentation conventions for high-quality generated skills. Use when writing tool descriptions, `_meta` annotations, or input schemas for MCP extraction.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Documentation conventions for generating high-quality AI agent skills from TypeScript source. Use when preparing a library for skill generation, auditing JSDoc quality, fixing audit warnings, writing @useWhen/@avoidWhen/@never tags, or asking about documentation conventions for skills.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Check task processing statistics to see how much data and how many docs are moving. Use when checking throughput, diagnosing a stalled task, verifying data movement, or reporting on task activity. Use when user says "is data flowing", "how much data", "check throughput", "how many documents", "task not processing", "data not arriving", "stats", "bytes processed", "stalled capture", "no data in destination", "data volume", "task report", "usage report", or "how much data did we process".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use and maintain automatic versioning from conventional commits; VERSION as source of truth; sync to READMEs and docs. Use when working on version bumps, release workflow, or when the user asks about versioning or conventional commits.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Normalize skills already in the tree using ls/docs/SKILL_NORMALIZATION.md: documents first, tooling second, with user choice for platform-specific skills. Use when normalizing one or more skills in ls/skills/ after import, copying, or batch review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when building UI, components, motion icons, loaders, or visual design. In BDB projects, routes to the BDB component and motion-icon library (npm @hybridlabor-api/ui-motion-library, shadcn namespace @bdb) as the first source before third-party registries or building from scratch. Outside BDB projects, the same lookup order applies with the original sources listed in the bdb-ui-library repository docs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.