Designs implementation blueprints for features using exploration findings and architectural best practices (converted from agent)
日本語の概要は準備中です。原文の説明を表示しています。
212 件 ・ 関連度順
概要と使いどころ
Designs implementation blueprints for features using exploration findings and architectural best practices (converted from agent)
日本語の概要は準備中です。原文の説明を表示しています。
Generates MkDocs-flavored or standard GitHub-flavored Markdown documentation from codebase analysis findings including API references, architecture guides, standalone markdown files, and change summaries (converted from agent)
日本語の概要は準備中です。原文の説明を表示しています。
Generate a markdown report documenting codebase changes from the current session -- files added, modified, deleted, and a summary of what was done. Use when asked to "document changes", "generate change report", "save changes report", "what did I change", "session report", "summarize my changes", or "write a changes report".
日本語の概要は準備中です。原文の説明を表示しています。
Generate a markdown report documenting codebase changes from the current session — files added, modified, deleted, and a summary of what was done.
日本語の概要は準備中です。原文の説明を表示しています。
Deep exploration and synthesis workflow with dynamic planning and hub-and-spoke coordination. Use for deep analysis, codebase understanding, or thorough investigation of a focus area.
日本語の概要は準備中です。原文の説明を表示しています。
Executes diagnostic investigation tasks to test debugging hypotheses. Runs tests, traces execution, checks git history, and reports evidence. (converted from agent)
日本語の概要は準備中です。原文の説明を表示しています。
Behavioral rules and lifecycle event handlers for the core-tools package. Defines automated behaviors that trigger at specific points in the agent workflow. (converted from hooks)
日本語の概要は準備中です。原文の説明を表示しています。
Deep exploration and synthesis workflow with dynamic planning and hub-and-spoke coordination. Use for deep analysis, deep understanding, or codebase investigation.
日本語の概要は準備中です。原文の説明を表示しています。
Synthesizes exploration findings into unified analysis with deep investigation capabilities and completeness evaluation (converted from agent)
日本語の概要は準備中です。原文の説明を表示しています。
Documentation management workflow for MkDocs sites and standalone markdown files -- initialize, generate, update docs, and create change summaries. Use when asked to "create docs", "write README", "update documentation", "generate docs site", "write CONTRIBUTING", "manage documentation", or "docs changelog".
日本語の概要は準備中です。原文の説明を表示しています。
Deep exploration and synthesis workflow using agent teams with dynamic planning and hub-and-spoke coordination. Use when asked for "deep analysis", "deep understanding", "analyze codebase", "explore and analyze", or "investigate codebase".
日本語の概要は準備中です。原文の説明を表示しています。
Systematic, hypothesis-driven debugging workflow with triage-based track routing. Use for debugging, fixing bugs, and investigating errors.
日本語の概要は準備中です。原文の説明を表示しています。
Reviews code implementations for correctness, security, maintainability with confidence-scored findings (converted from agent)
日本語の概要は準備中です。原文の説明を表示しています。
Commit staged changes with conventional commit message. Use when user says "commit changes", "commit this", "save my changes", or wants to create a git commit.
日本語の概要は準備中です。原文の説明を表示しています。
Feature development workflow with exploration, architecture, implementation, and review phases. Use for implementing new features or significant changes.
日本語の概要は準備中です。原文の説明を表示しています。
Updates an existing OpenCode agent to match current platform best practices, fixes deprecated patterns, and validates the result. Use when user says "update opencode agent", "fix opencode agent", "migrate agent to opencode", or wants to modernize an existing OpenCode agent file.
日本語の概要は準備中です。原文の説明を表示しています。
Updates previously-ported plugins when source plugins change or the target platform evolves
日本語の概要は準備中です。原文の説明を表示しています。
Solve competitive programming and LeetCode-style problems with educational explanations. Use when asked to "solve this problem", "help with this leetcode", "competitive programming solution", "solve this algorithm problem", "coding challenge solution", "how to solve this coding problem", or any algorithmic problem-solving request.
日本語の概要は準備中です。原文の説明を表示しています。
Documentation management workflow for MkDocs sites and standalone markdown files — initialize, generate, update docs, and create change summaries. Use when asked to "create docs", "write README", "update documentation", "generate docs site", "write CONTRIBUTING", "manage documentation", or "docs changelog".
日本語の概要は準備中です。原文の説明を表示しています。
Reference for Claude Code's 6 Task Management tools — TaskCreate, TaskGet, TaskList, TaskUpdate (structured tracking) and TaskOutput, TaskStop (background execution). Covers tool parameters, status lifecycle, completion rules, dependency management, and conventions
日本語の概要は準備中です。原文の説明を表示しています。
Analyze test coverage and identify gaps with actionable recommendations
日本語の概要は準備中です。原文の説明を表示しています。
Provides Mermaid diagram syntax, best practices, and styling rules for technical visualizations. Use when creating diagrams, flowcharts, sequence diagrams, class diagrams, state diagrams, ER diagrams, architecture diagrams, C4 diagrams, visualizations, or any visual documentation in markdown. Always use this skill when generating or updating Mermaid code blocks.
日本語の概要は準備中です。原文の説明を表示しています。
Generate a markdown report documenting codebase changes from the current session — files added, modified, deleted, and a summary of what was done. Use when asked to "document changes", "generate change report", "save changes report", "what did I change", "session report", "summarize my changes", or "write a changes report".
日本語の概要は準備中です。原文の説明を表示しています。
Guides discovery and application of project-specific conventions including code patterns, naming, structure, and team practices. Use when exploring a codebase or implementing features to match existing patterns.
日本語の概要は準備中です。原文の説明を表示しています。