SuperClaude/README-ja.md

549 lines
18 KiB
Markdown
Raw Normal View History

<div align="center">
# 🚀 SuperClaudeフレームワーク
### **Claude Codeを構造化開発プラットフォームに変換**
<p align="center">
<img src="https://img.shields.io/badge/version-4.1.8-blue" alt="Version">
<img src="https://img.shields.io/badge/License-MIT-yellow.svg" alt="License">
<img src="https://img.shields.io/badge/PRs-welcome-brightgreen.svg" alt="PRs Welcome">
</p>
<p align="center">
<a href="https://superclaude.netlify.app/">
<img src="https://img.shields.io/badge/🌐_ウェブサイトを訪問-blue" alt="Website">
</a>
refactor: PEP8 compliance - directory rename and code formatting (#425) * fix(orchestration): add WebFetch auto-trigger for infrastructure configuration Problem: Infrastructure configuration changes (e.g., Traefik port settings) were being made based on assumptions without consulting official documentation, violating the 'Evidence > assumptions' principle in PRINCIPLES.md. Solution: - Added Infrastructure Configuration Validation section to MODE_Orchestration.md - Auto-triggers WebFetch for infrastructure tools (Traefik, nginx, Docker, etc.) - Enforces MODE_DeepResearch activation for investigation - BLOCKS assumption-based configuration changes Testing: Verified WebFetch successfully retrieves Traefik official docs (port 80 default) This prevents production outages from infrastructure misconfiguration by ensuring all technical recommendations are backed by official documentation. * feat: Add PM Agent (Project Manager Agent) for seamless orchestration Introduces PM Agent as the default orchestration layer that coordinates all sub-agents and manages workflows automatically. Key Features: - Default orchestration: All user interactions handled by PM Agent - Auto-delegation: Intelligent sub-agent selection based on task analysis - Docker Gateway integration: Zero-token baseline with dynamic MCP loading - Self-improvement loop: Automatic documentation of patterns and mistakes - Optional override: Users can specify sub-agents explicitly if desired Architecture: - Agent spec: SuperClaude/Agents/pm-agent.md - Command: SuperClaude/Commands/pm.md - Updated docs: README.md (15→16 agents), agents.md (new Orchestration category) User Experience: - Default: PM Agent handles everything (seamless, no manual routing) - Optional: Explicit --agent flag for direct sub-agent access - Both modes available simultaneously (no user downside) Implementation Status: - ✅ Specification complete - ✅ Documentation complete - ⏳ Prototype implementation needed - ⏳ Docker Gateway integration needed - ⏳ Testing and validation needed Refs: kazukinakai/docker-mcp-gateway (IRIS MCP Gateway integration) * feat: Add Agent Orchestration rules for PM Agent default activation Implements PM Agent as the default orchestration layer in RULES.md. Key Changes: - New 'Agent Orchestration' section (CRITICAL priority) - PM Agent receives ALL user requests by default - Manual override with @agent-[name] bypasses PM Agent - Agent Selection Priority clearly defined: 1. Manual override → Direct routing 2. Default → PM Agent → Auto-delegation 3. Delegation based on keywords, file types, complexity, context User Experience: - Default: PM Agent handles everything (seamless) - Override: @agent-[name] for direct specialist access - Transparent: PM Agent reports delegation decisions This establishes PM Agent as the orchestration layer while respecting existing auto-activation patterns and manual overrides. Next Steps: - Local testing in agiletec project - Iteration based on actual behavior - Documentation updates as needed * refactor(pm-agent): redesign as self-improvement meta-layer Problem Resolution: PM Agent's initial design competed with existing auto-activation for task routing, creating confusion about orchestration responsibilities and adding unnecessary complexity. Design Change: Redefined PM Agent as a meta-layer agent that operates AFTER specialist agents complete tasks, focusing on: - Post-implementation documentation and pattern recording - Immediate mistake analysis with prevention checklists - Monthly documentation maintenance and noise reduction - Pattern extraction and knowledge synthesis Two-Layer Orchestration System: 1. Task Execution Layer: Existing auto-activation handles task routing (unchanged) 2. Self-Improvement Layer: PM Agent meta-layer handles documentation (new) Files Modified: - SuperClaude/Agents/pm-agent.md: Complete rewrite with meta-layer design - Category: orchestration → meta - Triggers: All user interactions → Post-implementation, mistakes, monthly - Behavioral Mindset: Continuous learning system - Self-Improvement Workflow: BEFORE/DURING/AFTER/MISTAKE RECOVERY/MAINTENANCE - SuperClaude/Core/RULES.md: Agent Orchestration section updated - Split into Task Execution Layer + Self-Improvement Layer - Added orchestration flow diagram - Clarified PM Agent activates AFTER task completion - README.md: Updated PM Agent description - "orchestrates all interactions" → "ensures continuous learning" - Docs/User-Guide/agents.md: PM Agent section rewritten - Section: Orchestration Agent → Meta-Layer Agent - Expertise: Project orchestration → Self-improvement workflow executor - Examples: Task coordination → Post-implementation documentation - PR_DOCUMENTATION.md: Comprehensive PR documentation added - Summary, motivation, changes, testing, breaking changes - Two-layer orchestration system diagram - Verification checklist Integration Validated: Tested with agiletec project's self-improvement-workflow.md: ✅ PM Agent aligns with existing BEFORE/DURING/AFTER/MISTAKE RECOVERY phases ✅ Complements (not competes with) existing workflow ✅ agiletec workflow defines WHAT, PM Agent defines WHO executes it Breaking Changes: None - Existing auto-activation continues unchanged - Specialist agents unaffected - User workflows remain the same - New capability: Automatic documentation and knowledge maintenance Value Proposition: Transforms SuperClaude into a continuously learning system that accumulates knowledge, prevents recurring mistakes, and maintains fresh documentation without manual intervention. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> * docs: add Claude Code conversation history management research Research covering .jsonl file structure, performance impact, and retention policies. Content: - Claude Code .jsonl file format and message types - Performance issues from GitHub (memory leaks, conversation compaction) - Retention policies (consumer vs enterprise) - Rotation recommendations based on actual data - File history snapshot tracking mechanics Source: Moved from agiletec project (research applicable to all Claude Code projects) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> * feat: add Development documentation structure Phase 1: Documentation Structure complete - Add Docs/Development/ directory for development documentation - Add ARCHITECTURE.md - System architecture with PM Agent meta-layer - Add ROADMAP.md - 5-phase development plan with checkboxes - Add TASKS.md - Daily task tracking with progress indicators - Add PROJECT_STATUS.md - Current status dashboard and metrics - Add pm-agent-integration.md - Implementation guide for PM Agent mode This establishes comprehensive documentation foundation for: - System architecture understanding - Development planning and tracking - Implementation guidance - Progress visibility Related: #pm-agent-mode #documentation #phase-1 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> * feat: PM Agent session lifecycle and PDCA implementation Phase 2: PM Agent Mode Integration (Design Phase) Commands/pm.md updates: - Add "Always-Active Foundation Layer" concept - Add Session Lifecycle (Session Start/During Work/Session End) - Add PDCA Cycle (Plan/Do/Check/Act) automation - Add Serena MCP Memory Integration (list/read/write_memory) - Document auto-activation triggers Agents/pm-agent.md updates: - Add Session Start Protocol (MANDATORY auto-activation) - Add During Work PDCA Cycle with example workflows - Add Session End Protocol with state preservation - Add PDCA Self-Evaluation Pattern - Add Documentation Strategy (temp → patterns/mistakes) - Add Memory Operations Reference Key Features: - Session start auto-activation for context restoration - 30-minute checkpoint saves during work - Self-evaluation with think_about_* operations - Systematic documentation lifecycle - Knowledge evolution to CLAUDE.md Implementation Status: - ✅ Design complete (Commands/pm.md, Agents/pm-agent.md) - ⏳ Implementation pending (Core components) - ⏳ Serena MCP integration pending Salvaged from mistaken development in ~/.claude directory Related: #pm-agent-mode #session-lifecycle #pdca-cycle #phase-2 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> * fix: disable Serena MCP auto-browser launch Disable web dashboard and GUI log window auto-launch in Serena MCP server to prevent intrusive browser popups on startup. Users can still manually access the dashboard at http://localhost:24282/dashboard/ if needed. Changes: - Add CLI flags to Serena run command: - --enable-web-dashboard false - --enable-gui-log-window false - Ensures Git-tracked configuration (no reliance on ~/.serena/serena_config.yml) - Aligns with AIRIS MCP Gateway integration approach 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> * refactor: rename directories to lowercase for PEP8 compliance - Rename superclaude/Agents -> superclaude/agents - Rename superclaude/Commands -> superclaude/commands - Rename superclaude/Core -> superclaude/core - Rename superclaude/Examples -> superclaude/examples - Rename superclaude/MCP -> superclaude/mcp - Rename superclaude/Modes -> superclaude/modes This change follows Python PEP8 naming conventions for package directories. * style: fix PEP8 violations and update package name to lowercase Changes: - Format all Python files with black (43 files reformatted) - Update package name from 'SuperClaude' to 'superclaude' in pyproject.toml - Fix import statements to use lowercase package name - Add missing imports (timedelta, __version__) - Remove old SuperClaude.egg-info directory PEP8 violations reduced from 2672 to 701 (mostly E501 line length due to black's 88 char vs flake8's 79 char limit). * docs: add PM Agent development documentation Add comprehensive PM Agent development documentation: - PM Agent ideal workflow (7-phase autonomous cycle) - Project structure understanding (Git vs installed environment) - Installation flow understanding (CommandsComponent behavior) - Task management system (current-tasks.md) Purpose: Eliminate repeated explanations and enable autonomous PDCA cycles 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> * feat(pm-agent): add self-correcting execution and warning investigation culture ## Changes ### superclaude/commands/pm.md - Add "Self-Correcting Execution" section with root cause analysis protocol - Add "Warning/Error Investigation Culture" section enforcing zero-tolerance for dismissal - Define error detection protocol: STOP → Investigate → Hypothesis → Different Solution → Execute - Document anti-patterns (retry without understanding) and correct patterns (research-first) ### docs/Development/hypothesis-pm-autonomous-enhancement-2025-10-14.md - Add PDCA workflow hypothesis document for PM Agent autonomous enhancement ## Rationale PM Agent must never retry failed operations without understanding root causes. All warnings and errors require investigation via context7/WebFetch/documentation to ensure production-quality code and prevent technical debt accumulation. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> * feat(installer): add airis-mcp-gateway MCP server option ## Changes - Add airis-mcp-gateway to MCP server options in installer - Configuration: GitHub-based installation via uvx - Repository: https://github.com/oraios/airis-mcp-gateway - Purpose: Dynamic MCP Gateway for zero-token baseline and on-demand tool loading ## Implementation Added to setup/components/mcp.py self.mcp_servers dictionary with: - install_method: github - install_command: uvx test installation - run_command: uvx runtime execution - required: False (optional server) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> --------- Co-authored-by: kazuki <kazuki@kazukinoMacBook-Air.local> Co-authored-by: Claude <noreply@anthropic.com>
2025-10-14 12:17:09 +09:00
<a href="https://pypi.org/project/superclaude/">
<img src="https://img.shields.io/pypi/v/SuperClaude.svg?" alt="PyPI">
</a>
<a href="https://www.npmjs.com/package/@bifrost_inc/superclaude">
<img src="https://img.shields.io/npm/v/@bifrost_inc/superclaude.svg" alt="npm">
</a>
</p>
<!-- Language Selector -->
<p align="center">
<a href="README.md">
<img src="https://img.shields.io/badge/🇺🇸_English-blue" alt="English">
</a>
<a href="README-zh.md">
<img src="https://img.shields.io/badge/🇨🇳_中文-red" alt="中文">
</a>
<a href="README-ja.md">
<img src="https://img.shields.io/badge/🇯🇵_日本語-green" alt="日本語">
</a>
</p>
<p align="center">
<a href="#-クイックインストール">クイックスタート</a>
<a href="#-プロジェクトを支援">支援</a>
<a href="#-v4の新機能">新機能</a>
<a href="#-ドキュメント">ドキュメント</a>
<a href="#-貢献">貢献</a>
</p>
</div>
---
<div align="center">
## 📊 **フレームワーク統計**
| **プラグイン** | **エージェント** | **モード** | **MCPサーバー** |
|:------------:|:----------:|:---------:|:---------------:|
| **3** | **16** | **7** | **8** |
| プラグインコマンド | 専門AI | 動作モード | 統合サービス |
3つのコアプラグイン**PM Agent**(オーケストレーション)、**Research**(ウェブ検索)、**Index**(コンテキスト最適化)。
</div>
---
<div align="center">
## 🎯 **概要**
SuperClaudeは**メタプログラミング設定フレームワーク**で、動作指示の注入とコンポーネント統制を通じて、Claude Codeを構造化開発プラットフォームに変換します。強力なツールとインテリジェントエージェントを備えたシステム化されたワークフロー自動化を提供します。
## 免責事項
このプロジェクトはAnthropicと関連または承認されていません。
Claude Codeは[Anthropic](https://www.anthropic.com/)によって構築および維持されている製品です。
## 📖 **開発者および貢献者向け**
**SuperClaudeフレームワークを使用するための重要なドキュメント**
| ドキュメント | 目的 | いつ読むか |
|----------|---------|--------------|
| **[PLANNING.md](PLANNING.md)** | アーキテクチャ、設計原則、絶対的なルール | セッション開始時、実装前 |
| **[TASK.md](TASK.md)** | 現在のタスク、優先順位、バックログ | 毎日、作業開始前 |
| **[KNOWLEDGE.md](KNOWLEDGE.md)** | 蓄積された知見、ベストプラクティス、トラブルシューティング | 問題に遭遇したとき、パターンを学習するとき |
| **[CONTRIBUTING.md](CONTRIBUTING.md)** | 貢献ガイドライン、ワークフロー | PRを提出する前 |
> **💡 プロのヒント**Claude Codeはセッション開始時にこれらのファイルを読み取り、プロジェクト標準に沿った一貫性のある高品質な開発を保証します。
## ⚡ **クイックインストール**
> **重要**古いドキュメントで説明されているTypeScriptプラグインシステムは
> まだ利用できませんv5.0で予定。v4.xの現在のインストール
> 手順については、以下の手順に従ってください。
### **現在の安定バージョン (v4.1.8)**
SuperClaudeは現在スラッシュコマンドを使用しています。
**オプション1pipx推奨**
```bash
# PyPIからインストール
pipx install superclaude
# コマンドをインストール(/research、/index-repo、/agent、/recommendをインストール
superclaude install
# インストールを確認
superclaude install --list
superclaude doctor
```
インストール後、Claude Codeを再起動してコマンドを使用します
- `/sc:research` - 並列検索による深いウェブ研究
- `/sc:index-repo` - コンテキスト最適化のためのリポジトリインデックス作成
- `/sc:agent` - 専門AIエージェント
- `/sc:recommend` - コマンド推奨
- `/sc` - 利用可能なすべてのSuperClaudeコマンドを表示
**オプション2Gitから直接インストール**
```bash
# リポジトリをクローン
git clone https://github.com/SuperClaude-Org/SuperClaude_Framework.git
cd SuperClaude_Framework
# インストールスクリプトを実行
./install.sh
```
### **v5.0で提供予定(開発中)**
新しいTypeScriptプラグインシステムを積極的に開発中です詳細は[#419](https://github.com/SuperClaude-Org/SuperClaude_Framework/issues/419)を参照)。リリース後、インストールは次のように簡略化されます:
```bash
# この機能はまだ利用できません
/plugin marketplace add SuperClaude-Org/superclaude-plugin-marketplace
/plugin install superclaude
```
**ステータス**開発中。ETAは未定です。
### **パフォーマンス向上オプションのMCP**
**2〜3倍**高速な実行と**30〜50%**少ないトークンのために、オプションでMCPサーバーをインストールできます
```bash
# パフォーマンス向上のためのオプションのMCPサーバーairis-mcp-gateway経由
# - Serena: コード理解2〜3倍高速
# - Sequential: トークン効率的な推論30〜50%少ないトークン)
# - Tavily: 深い研究のためのウェブ検索
# - Context7: 公式ドキュメント検索
# - Mindbase: すべての会話にわたるセマンティック検索(オプションの拡張)
# 注エラー学習は組み込みのReflexionMemoryを介して利用可能インストール不要
# Mindbaseはセマンティック検索の拡張を提供「recommended」プロファイルが必要
# MCPサーバーのインストールhttps://github.com/agiletec-inc/airis-mcp-gateway
# 詳細はdocs/mcp/mcp-integration-policy.mdを参照
```
**パフォーマンス比較:**
- **MCPなし**:完全に機能、標準パフォーマンス ✅
- **MCPあり**2〜3倍高速、30〜50%少ないトークン ⚡
</div>
---
<div align="center">
## 💖 **プロジェクトを支援**
> 正直に言うと、SuperClaudeの維持には時間とリソースが必要です。
>
> *Claude Maxサブスクリプションだけでもテスト用に月100ドルかかり、それに加えてドキュメント、バグ修正、機能開発に費やす時間があります。*
> *日常の作業でSuperClaudeの価値を感じていただけるなら、プロジェクトの支援をご検討ください。*
> *数ドルでも基本コストをカバーし、開発を継続することができます。*
>
> コード、フィードバック、または支援を通じて、すべての貢献者が重要です。このコミュニティの一員でいてくれてありがとう!🙏
<table>
<tr>
<td align="center" width="33%">
### ☕ **Ko-fi**
[![Ko-fi](https://img.shields.io/badge/Support_on-Ko--fi-ff5e5b?logo=ko-fi)](https://ko-fi.com/superclaude)
*一回限りの貢献*
</td>
<td align="center" width="33%">
### 🎯 **Patreon**
[![Patreon](https://img.shields.io/badge/Become_a-Patron-f96854?logo=patreon)](https://patreon.com/superclaude)
*月額支援*
</td>
<td align="center" width="33%">
### 💜 **GitHub**
[![GitHub Sponsors](https://img.shields.io/badge/GitHub-Sponsor-30363D?logo=github-sponsors)](https://github.com/sponsors/SuperClaude-Org)
*柔軟な階層*
</td>
</tr>
</table>
### **あなたの支援により可能になること:**
| 項目 | コスト/影響 |
|------|-------------|
| 🔬 **Claude Maxテスト** | 検証とテスト用に月100ドル |
| ⚡ **機能開発** | 新機能と改善 |
| 📚 **ドキュメンテーション** | 包括的なガイドと例 |
| 🤝 **コミュニティサポート** | 迅速な問題対応とヘルプ |
| 🔧 **MCP統合** | 新しいサーバー接続のテスト |
| 🌐 **インフラストラクチャ** | ホスティングとデプロイメントのコスト |
> **注意:** ただし、プレッシャーはありません。フレームワークはいずれにしてもオープンソースのままです。人々がそれを使用し、評価していることを知るだけでもモチベーションになります。コード、ドキュメント、または情報の拡散による貢献も助けになります!🙏
</div>
---
<div align="center">
## 🎉 **V4.1の新機能**
> *バージョン4.1は、スラッシュコマンドアーキテクチャの安定化、エージェント機能の強化、ドキュメントの改善に焦点を当てています。*
<table>
<tr>
<td width="50%">
### 🤖 **よりスマートなエージェントシステム**
ドメイン専門知識を持つ**16の専門エージェント**
- PM Agentは体系的なドキュメントを通じて継続的な学習を保証
- 自律的なウェブ研究のための深い研究エージェント
- セキュリティエンジニアが実際の脆弱性をキャッチ
- フロントエンドアーキテクトがUIパターンを理解
- コンテキストに基づく自動調整
- オンデマンドでドメイン固有の専門知識
</td>
<td width="50%">
### ⚡ **最適化されたパフォーマンス**
**より小さなフレームワーク、より大きなプロジェクト:**
- フレームワークフットプリントの削減
- コードのためのより多くのコンテキスト
- より長い会話が可能
- 複雑な操作の有効化
</td>
</tr>
<tr>
<td width="50%">
### 🔧 **MCPサーバー統合**
**8つの強力なサーバー**airis-mcp-gateway経由
- **Tavily** → プライマリウェブ検索(深い研究)
- **Serena** → セッション持続性とメモリ
- **Mindbase** → セッション横断学習(ゼロフットプリント)
- **Sequential** → トークン効率的な推論
- **Context7** → 公式ドキュメント検索
- **Playwright** → JavaScript重量コンテンツ抽出
- **Magic** → UIコンポーネント生成
- **Chrome DevTools** → パフォーマンス分析
</td>
<td width="50%">
### 🎯 **動作モード**
異なるコンテキストのための**7つの適応モード**
- **ブレインストーミング** → 適切な質問をする
- **ビジネスパネル** → 多専門家戦略分析
- **深い研究** → 自律的なウェブ研究
- **オーケストレーション** → 効率的なツール調整
- **トークン効率** → 30-50%のコンテキスト節約
- **タスク管理** → システム化された組織
- **内省** → メタ認知分析
</td>
</tr>
<tr>
<td width="50%">
### 📚 **ドキュメントの全面見直し**
**開発者のための完全な書き直し:**
- 実際の例とユースケース
- 一般的な落とし穴の文書化
- 実用的なワークフローを含む
- より良いナビゲーション構造
</td>
<td width="50%">
### 🧪 **安定性の強化**
**信頼性に焦点:**
- コアコマンドのバグ修正
- テストカバレッジの改善
- より堅牢なエラー処理
- CI/CDパイプラインの改善
</td>
</tr>
</table>
</div>
---
<div align="center">
## 🔬 **深い研究機能**
### **DRエージェントアーキテクチャに準拠した自律的ウェブ研究**
SuperClaude v4.2は、自律的、適応的、インテリジェントなウェブ研究を可能にする包括的な深い研究機能を導入します。
<table>
<tr>
<td width="50%">
### 🎯 **適応的計画**
**3つのインテリジェント戦略**
- **計画のみ**:明確なクエリに対する直接実行
- **意図計画**:曖昧なリクエストの明確化
- **統一**:協調的な計画の洗練(デフォルト)
</td>
<td width="50%">
### 🔄 **マルチホップ推論**
**最大5回の反復検索**
- エンティティ拡張(論文 → 著者 → 作品)
- 概念深化(トピック → 詳細 → 例)
- 時間的進行(現在 → 歴史)
- 因果連鎖(効果 → 原因 → 予防)
</td>
</tr>
<tr>
<td width="50%">
### 📊 **品質スコアリング**
**信頼度ベースの検証:**
- ソースの信頼性評価0.0-1.0
- カバレッジの完全性追跡
- 統合の一貫性評価
- 最小しきい値0.6、目標0.8
</td>
<td width="50%">
### 🧠 **ケースベース学習**
**セッション横断インテリジェンス:**
- パターン認識と再利用
- 時間経過による戦略最適化
- 成功したクエリ式の保存
- パフォーマンス改善追跡
</td>
</tr>
</table>
### **研究コマンドの使用**
```bash
# 自動深度での基本研究
/research "2024年の最新AI開発"
# 制御された研究深度TypeScriptのオプション経由
/research "量子コンピューティングのブレークスルー" # depth: exhaustive
# 特定の戦略選択
/research "市場分析" # strategy: planning-only
# ドメインフィルタリング研究Tavily MCP統合
/research "Reactパターン" # domains: reactjs.org,github.com
```
### **研究深度レベル**
| 深度 | ソース | ホップ | 時間 | 最適な用途 |
|:-----:|:-------:|:----:|:----:|----------|
| **クイック** | 5-10 | 1 | ~2分 | 簡単な事実、単純なクエリ |
| **標準** | 10-20 | 3 | ~5分 | 一般的な研究(デフォルト) |
| **深い** | 20-40 | 4 | ~8分 | 包括的な分析 |
| **徹底的** | 40+ | 5 | ~10分 | 学術レベルの研究 |
### **統合ツールオーケストレーション**
深い研究システムは複数のツールをインテリジェントに調整します:
- **Tavily MCP**:プライマリウェブ検索と発見
- **Playwright MCP**:複雑なコンテンツ抽出
- **Sequential MCP**:マルチステップ推論と統合
- **Serena MCP**:メモリと学習の持続性
- **Context7 MCP**:技術ドキュメント検索
</div>
---
<div align="center">
## 📚 **ドキュメント**
### **🇯🇵 SuperClaude完全日本語ガイド**
<table>
<tr>
<th align="center">🚀 はじめに</th>
<th align="center">📖 ユーザーガイド</th>
<th align="center">🛠️ 開発者リソース</th>
<th align="center">📋 リファレンス</th>
</tr>
<tr>
<td valign="top">
refactor(docs): normalize documentation naming to lowercase for PEP8 compliance (#434) * refactor(docs): rename directories to lowercase for PEP8 compliance - Developer-Guide → developer-guide - Getting-Started → getting-started - Reference → reference - Templates → templates - User-Guide → user-guide - User-Guide-jp → user-guide-jp - User-Guide-kr → user-guide-kr - User-Guide-zh → user-guide-zh This change aligns with Python PEP8 package naming conventions. All 43 files affected. * refactor: rename root documentation files to lowercase - CHANGELOG.md → changelog.md - CODE_OF_CONDUCT.md → code_of_conduct.md - CONTRIBUTING.md → contributing.md - SECURITY.md → security.md Aligns with Python package naming conventions (PEP8). README files remain uppercase as per convention. * refactor: move documentation files to docs/ for cleaner root Moved OSS standard files to docs/: - CHANGELOG.md → docs/CHANGELOG.md - CODE_OF_CONDUCT.md → docs/CODE_OF_CONDUCT.md - CONTRIBUTING.md → docs/CONTRIBUTING.md - SECURITY.md → docs/SECURITY.md Root now contains only essential files: ✓ README files (表紙: en, ja, kr, zh) ✓ LICENSE (法的要件) ✓ Build configs (pyproject.toml, setup.py, MANIFEST.in) ✓ VERSION Rationale: Cleaner root structure following modern Python project conventions. All detailed documentation consolidated in docs/ directory. * refactor: update documentation links after restructure Auto-updated internal documentation links to reflect new structure: - docs/ subdirectories now lowercase (PEP8) - Root files moved to docs/ - All cross-references updated This commit includes linter-generated link updates. * chore(docs): keep OSS-standard uppercase root files (CHANGELOG, CODE_OF_CONDUCT, CONTRIBUTING, SECURITY) * chore(docs): remove duplicated PR docs from repo root (moved under docs) * docs: rename pm-agent-implementation-status.md -> PM_AGENT.md for clarity * docs: update links to PM_AGENT.md after rename --------- Co-authored-by: kazuki <kazuki@kazukinoMacBook-Air.local>
2025-10-16 00:37:39 +09:00
- 📝 [**クイックスタートガイド**](docs/getting-started/quick-start.md)
*すぐに開始*
refactor(docs): normalize documentation naming to lowercase for PEP8 compliance (#434) * refactor(docs): rename directories to lowercase for PEP8 compliance - Developer-Guide → developer-guide - Getting-Started → getting-started - Reference → reference - Templates → templates - User-Guide → user-guide - User-Guide-jp → user-guide-jp - User-Guide-kr → user-guide-kr - User-Guide-zh → user-guide-zh This change aligns with Python PEP8 package naming conventions. All 43 files affected. * refactor: rename root documentation files to lowercase - CHANGELOG.md → changelog.md - CODE_OF_CONDUCT.md → code_of_conduct.md - CONTRIBUTING.md → contributing.md - SECURITY.md → security.md Aligns with Python package naming conventions (PEP8). README files remain uppercase as per convention. * refactor: move documentation files to docs/ for cleaner root Moved OSS standard files to docs/: - CHANGELOG.md → docs/CHANGELOG.md - CODE_OF_CONDUCT.md → docs/CODE_OF_CONDUCT.md - CONTRIBUTING.md → docs/CONTRIBUTING.md - SECURITY.md → docs/SECURITY.md Root now contains only essential files: ✓ README files (表紙: en, ja, kr, zh) ✓ LICENSE (法的要件) ✓ Build configs (pyproject.toml, setup.py, MANIFEST.in) ✓ VERSION Rationale: Cleaner root structure following modern Python project conventions. All detailed documentation consolidated in docs/ directory. * refactor: update documentation links after restructure Auto-updated internal documentation links to reflect new structure: - docs/ subdirectories now lowercase (PEP8) - Root files moved to docs/ - All cross-references updated This commit includes linter-generated link updates. * chore(docs): keep OSS-standard uppercase root files (CHANGELOG, CODE_OF_CONDUCT, CONTRIBUTING, SECURITY) * chore(docs): remove duplicated PR docs from repo root (moved under docs) * docs: rename pm-agent-implementation-status.md -> PM_AGENT.md for clarity * docs: update links to PM_AGENT.md after rename --------- Co-authored-by: kazuki <kazuki@kazukinoMacBook-Air.local>
2025-10-16 00:37:39 +09:00
- 💾 [**インストールガイド**](docs/getting-started/installation.md)
*詳細なセットアップ手順*
</td>
<td valign="top">
- 🎯 [**スラッシュコマンド**](docs/user-guide/commands.md)
*完全な `/sc` コマンドリスト*
- 🤖 [**エージェントガイド**](docs/user-guide/agents.md)
*16の専門エージェント*
- 🎨 [**動作モード**](docs/user-guide/modes.md)
*7つの適応モード*
- 🚩 [**フラグガイド**](docs/user-guide/flags.md)
*動作制御パラメータ*
- 🔧 [**MCPサーバー**](docs/user-guide/mcp-servers.md)
*8つのサーバー統合*
- 💼 [**セッション管理**](docs/user-guide/session-management.md)
*状態の保存と復元*
</td>
<td valign="top">
refactor(docs): normalize documentation naming to lowercase for PEP8 compliance (#434) * refactor(docs): rename directories to lowercase for PEP8 compliance - Developer-Guide → developer-guide - Getting-Started → getting-started - Reference → reference - Templates → templates - User-Guide → user-guide - User-Guide-jp → user-guide-jp - User-Guide-kr → user-guide-kr - User-Guide-zh → user-guide-zh This change aligns with Python PEP8 package naming conventions. All 43 files affected. * refactor: rename root documentation files to lowercase - CHANGELOG.md → changelog.md - CODE_OF_CONDUCT.md → code_of_conduct.md - CONTRIBUTING.md → contributing.md - SECURITY.md → security.md Aligns with Python package naming conventions (PEP8). README files remain uppercase as per convention. * refactor: move documentation files to docs/ for cleaner root Moved OSS standard files to docs/: - CHANGELOG.md → docs/CHANGELOG.md - CODE_OF_CONDUCT.md → docs/CODE_OF_CONDUCT.md - CONTRIBUTING.md → docs/CONTRIBUTING.md - SECURITY.md → docs/SECURITY.md Root now contains only essential files: ✓ README files (表紙: en, ja, kr, zh) ✓ LICENSE (法的要件) ✓ Build configs (pyproject.toml, setup.py, MANIFEST.in) ✓ VERSION Rationale: Cleaner root structure following modern Python project conventions. All detailed documentation consolidated in docs/ directory. * refactor: update documentation links after restructure Auto-updated internal documentation links to reflect new structure: - docs/ subdirectories now lowercase (PEP8) - Root files moved to docs/ - All cross-references updated This commit includes linter-generated link updates. * chore(docs): keep OSS-standard uppercase root files (CHANGELOG, CODE_OF_CONDUCT, CONTRIBUTING, SECURITY) * chore(docs): remove duplicated PR docs from repo root (moved under docs) * docs: rename pm-agent-implementation-status.md -> PM_AGENT.md for clarity * docs: update links to PM_AGENT.md after rename --------- Co-authored-by: kazuki <kazuki@kazukinoMacBook-Air.local>
2025-10-16 00:37:39 +09:00
- 🏗️ [**技術アーキテクチャ**](docs/developer-guide/technical-architecture.md)
*システム設計の詳細*
refactor(docs): normalize documentation naming to lowercase for PEP8 compliance (#434) * refactor(docs): rename directories to lowercase for PEP8 compliance - Developer-Guide → developer-guide - Getting-Started → getting-started - Reference → reference - Templates → templates - User-Guide → user-guide - User-Guide-jp → user-guide-jp - User-Guide-kr → user-guide-kr - User-Guide-zh → user-guide-zh This change aligns with Python PEP8 package naming conventions. All 43 files affected. * refactor: rename root documentation files to lowercase - CHANGELOG.md → changelog.md - CODE_OF_CONDUCT.md → code_of_conduct.md - CONTRIBUTING.md → contributing.md - SECURITY.md → security.md Aligns with Python package naming conventions (PEP8). README files remain uppercase as per convention. * refactor: move documentation files to docs/ for cleaner root Moved OSS standard files to docs/: - CHANGELOG.md → docs/CHANGELOG.md - CODE_OF_CONDUCT.md → docs/CODE_OF_CONDUCT.md - CONTRIBUTING.md → docs/CONTRIBUTING.md - SECURITY.md → docs/SECURITY.md Root now contains only essential files: ✓ README files (表紙: en, ja, kr, zh) ✓ LICENSE (法的要件) ✓ Build configs (pyproject.toml, setup.py, MANIFEST.in) ✓ VERSION Rationale: Cleaner root structure following modern Python project conventions. All detailed documentation consolidated in docs/ directory. * refactor: update documentation links after restructure Auto-updated internal documentation links to reflect new structure: - docs/ subdirectories now lowercase (PEP8) - Root files moved to docs/ - All cross-references updated This commit includes linter-generated link updates. * chore(docs): keep OSS-standard uppercase root files (CHANGELOG, CODE_OF_CONDUCT, CONTRIBUTING, SECURITY) * chore(docs): remove duplicated PR docs from repo root (moved under docs) * docs: rename pm-agent-implementation-status.md -> PM_AGENT.md for clarity * docs: update links to PM_AGENT.md after rename --------- Co-authored-by: kazuki <kazuki@kazukinoMacBook-Air.local>
2025-10-16 00:37:39 +09:00
- 💻 [**コード貢献**](docs/developer-guide/contributing-code.md)
*開発ワークフロー*
refactor(docs): normalize documentation naming to lowercase for PEP8 compliance (#434) * refactor(docs): rename directories to lowercase for PEP8 compliance - Developer-Guide → developer-guide - Getting-Started → getting-started - Reference → reference - Templates → templates - User-Guide → user-guide - User-Guide-jp → user-guide-jp - User-Guide-kr → user-guide-kr - User-Guide-zh → user-guide-zh This change aligns with Python PEP8 package naming conventions. All 43 files affected. * refactor: rename root documentation files to lowercase - CHANGELOG.md → changelog.md - CODE_OF_CONDUCT.md → code_of_conduct.md - CONTRIBUTING.md → contributing.md - SECURITY.md → security.md Aligns with Python package naming conventions (PEP8). README files remain uppercase as per convention. * refactor: move documentation files to docs/ for cleaner root Moved OSS standard files to docs/: - CHANGELOG.md → docs/CHANGELOG.md - CODE_OF_CONDUCT.md → docs/CODE_OF_CONDUCT.md - CONTRIBUTING.md → docs/CONTRIBUTING.md - SECURITY.md → docs/SECURITY.md Root now contains only essential files: ✓ README files (表紙: en, ja, kr, zh) ✓ LICENSE (法的要件) ✓ Build configs (pyproject.toml, setup.py, MANIFEST.in) ✓ VERSION Rationale: Cleaner root structure following modern Python project conventions. All detailed documentation consolidated in docs/ directory. * refactor: update documentation links after restructure Auto-updated internal documentation links to reflect new structure: - docs/ subdirectories now lowercase (PEP8) - Root files moved to docs/ - All cross-references updated This commit includes linter-generated link updates. * chore(docs): keep OSS-standard uppercase root files (CHANGELOG, CODE_OF_CONDUCT, CONTRIBUTING, SECURITY) * chore(docs): remove duplicated PR docs from repo root (moved under docs) * docs: rename pm-agent-implementation-status.md -> PM_AGENT.md for clarity * docs: update links to PM_AGENT.md after rename --------- Co-authored-by: kazuki <kazuki@kazukinoMacBook-Air.local>
2025-10-16 00:37:39 +09:00
- 🧪 [**テスト&デバッグ**](docs/developer-guide/testing-debugging.md)
*品質保証*
</td>
<td valign="top">
- 📓 [**サンプル集**](docs/reference/examples-cookbook.md)
*実際の使用例*
- 🔍 [**トラブルシューティング**](docs/reference/troubleshooting.md)
*一般的な問題と修正*
</td>
</tr>
</table>
</div>
---
<div align="center">
## 🤝 **貢献**
### **SuperClaudeコミュニティに参加**
あらゆる種類の貢献を歓迎します!お手伝いできる方法は以下のとおりです:
| 優先度 | 領域 | 説明 |
|:--------:|------|-------------|
| 📝 **高** | ドキュメント | ガイドの改善、例の追加、タイプミス修正 |
| 🔧 **高** | MCP統合 | サーバー設定の追加、統合テスト |
| 🎯 **中** | ワークフロー | コマンドパターンとレシピの作成 |
| 🧪 **中** | テスト | テストの追加、機能の検証 |
| 🌐 **低** | 国際化 | ドキュメントの他言語への翻訳 |
<p align="center">
<a href="CONTRIBUTING.md">
<img src="https://img.shields.io/badge/📖_読む-貢献ガイド-blue" alt="Contributing Guide">
</a>
<a href="https://github.com/SuperClaude-Org/SuperClaude_Framework/graphs/contributors">
<img src="https://img.shields.io/badge/👥_表示-すべての貢献者-green" alt="Contributors">
</a>
</p>
</div>
---
<div align="center">
## ⚖️ **ライセンス**
このプロジェクトは**MITライセンス**の下でライセンスされています - 詳細は[LICENSE](LICENSE)ファイルを参照してください。
<p align="center">
<img src="https://img.shields.io/badge/License-MIT-yellow.svg?" alt="MIT License">
</p>
</div>
---
<div align="center">
## ⭐ **Star履歴**
<a href="https://www.star-history.com/#SuperClaude-Org/SuperClaude_Framework&Timeline">
<picture>
<source media="(prefers-color-scheme: dark)" srcset="https://api.star-history.com/svg?repos=SuperClaude-Org/SuperClaude_Framework&type=Timeline&theme=dark" />
<source media="(prefers-color-scheme: light)" srcset="https://api.star-history.com/svg?repos=SuperClaude-Org/SuperClaude_Framework&type=Timeline" />
<img alt="Star History Chart" src="https://api.star-history.com/svg?repos=SuperClaude-Org/SuperClaude_Framework&type=Timeline" />
</picture>
</a>
</div>
---
<div align="center">
### **🚀 SuperClaudeコミュニティによって情熱をもって構築**
<p align="center">
<sub>境界を押し広げる開発者のために❤️で作られました</sub>
</p>
<p align="center">
<a href="#-superclaudeフレームワーク">トップに戻る ↑</a>
</p>
</div>