mirror of
https://github.com/SuperClaude-Org/SuperClaude_Framework.git
synced 2025-12-24 13:16:52 +00:00
* 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>
10 KiB
10 KiB
SuperClaude 标志指南 🏁
大多数标志会自动激活 - Claude Code 读取行为指令,根据您请求中的关键词和模式来调用适当的上下文。
基本自动激活标志(90% 的使用案例)
核心分析标志
| 标志 | 何时激活 | 作用 |
|---|---|---|
--think |
5+ 个文件或复杂分析 | 标准结构化分析(约 4K 令牌) |
--think-hard |
架构分析、系统依赖关系 | 深度分析(约 10K 令牌)配合增强工具 |
--ultrathink |
关键系统重设计、遗留系统现代化 | 最大深度分析(约 32K 令牌)配合所有工具 |
MCP 服务器标志
| 标志 | 服务器 | 目的 | 自动触发 |
|---|---|---|---|
--c7 / --context7 |
Context7 | 官方文档、框架模式 | 库导入、框架问题 |
--seq / --sequential |
Sequential | 多步推理、调试 | 复杂调试、系统设计 |
--magic |
Magic | UI 组件生成 | /ui 命令、前端关键词 |
--play / --playwright |
Playwright | 浏览器测试、E2E 验证 | 测试请求、视觉验证 |
--morph / --morphllm |
Morphllm | 批量转换、模式编辑 | 批量操作、样式强制执行 |
--serena |
Serena | 项目内存、符号操作 | 符号操作、大型代码库 |
行为模式标志
| 标志 | 何时激活 | 作用 |
|---|---|---|
--brainstorm |
模糊请求、探索关键词 | 协作发现思维模式 |
--introspect |
自我分析、错误恢复 | 透明地展现推理过程 |
--task-manage |
>3 步骤、复杂范围 | 通过委托进行协调 |
--orchestrate |
多工具操作、性能需求 | 优化工具选择和并行执行 |
--token-efficient / --uc |
上下文 >75%、效率需求 | 符号增强通信,减少 30-50% 令牌使用 |
执行控制标志
| 标志 | 何时激活 | 作用 |
|---|---|---|
--loop |
"improve"、"polish"、"refine" 关键词 | 迭代增强循环 |
--safe-mode |
生产环境,>85% 资源使用 | 最大验证,保守执行 |
--validate |
风险 >0.7,生产环境 | 执行前风险评估 |
--delegate |
>7 个目录或 >50 个文件 | 子智能体并行处理 |
特定命令标志
分析命令标志 (/sc:analyze)
| 标志 | 目的 | 值 |
|---|---|---|
--focus |
针对特定领域 | security, performance, quality, architecture |
--depth |
分析彻底程度 | quick, deep |
--format |
输出格式 | text, json, report |
构建命令标志 (/sc:build)
| 标志 | 目的 | 值 |
|---|---|---|
--type |
构建配置 | dev, prod, test |
--clean |
构建前清理 | 布尔值 |
--optimize |
启用优化 | 布尔值 |
--verbose |
详细输出 | 布尔值 |
设计命令标志 (/sc:design)
| 标志 | 目的 | 值 |
|---|---|---|
--type |
设计目标 | architecture, api, component, database |
--format |
输出格式 | diagram, spec, code |
解释命令标志 (/sc:explain)
| 标志 | 目的 | 值 |
|---|---|---|
--level |
复杂度级别 | basic, intermediate, advanced |
--format |
解释风格 | text, examples, interactive |
--context |
领域上下文 | 任何领域(如 react、security) |
改进命令标志 (/sc:improve)
| 标志 | 目的 | 值 |
|---|---|---|
--type |
改进焦点 | quality, performance, maintainability, style, security |
--safe |
保守方法 | 布尔值 |
--interactive |
用户指导 | 布尔值 |
--preview |
显示但不执行 | 布尔值 |
任务命令标志 (/sc:task)
| 标志 | 目的 | 值 |
|---|---|---|
--strategy |
任务方法 | systematic, agile, enterprise |
--parallel |
并行执行 | 布尔值 |
--delegate |
子智能体协调 | 布尔值 |
工作流命令标志 (/sc:workflow)
| 标志 | 目的 | 值 |
|---|---|---|
--strategy |
工作流方法 | systematic, agile, enterprise |
--depth |
分析深度 | shallow, normal, deep |
--parallel |
并行协调 | 布尔值 |
故障排除命令标志 (/sc:troubleshoot)
| 标志 | 目的 | 值 |
|---|---|---|
--type |
问题类别 | bug, build, performance, deployment |
--trace |
包含跟踪分析 | 布尔值 |
--fix |
执行修复 | 布尔值 |
清理命令标志 (/sc:cleanup)
| 标志 | 目的 | 值 |
|---|---|---|
--type |
清理目标 | code, imports, files, all |
--safe / --aggressive |
清理强度 | 布尔值 |
--interactive |
用户指导 | 布尔值 |
--preview |
显示但不执行 | 布尔值 |
估算命令标志 (/sc:estimate)
| 标志 | 目的 | 值 |
|---|---|---|
--type |
估算焦点 | time, effort, complexity |
--unit |
时间单位 | hours, days, weeks |
--breakdown |
详细分解 | 布尔值 |
索引命令标志 (/sc:index)
| 标志 | 目的 | 值 |
|---|---|---|
--type |
索引目标 | docs, api, structure, readme |
--format |
输出格式 | md, json, yaml |
反思命令标志 (/sc:reflect)
| 标志 | 目的 | 值 |
|---|---|---|
--type |
反思范围 | task, session, completion |
--analyze |
包含分析 | 布尔值 |
--validate |
验证完整性 | 布尔值 |
生成命令标志 (/sc:spawn)
| 标志 | 目的 | 值 |
|---|---|---|
--strategy |
协调方法 | sequential, parallel, adaptive |
--depth |
分析深度 | normal, deep |
Git 命令标志 (/sc:git)
| 标志 | 目的 | 值 |
|---|---|---|
--smart-commit |
生成提交消息 | 布尔值 |
--interactive |
引导操作 | 布尔值 |
工具选择命令标志 (/sc:select-tool)
| 标志 | 目的 | 值 |
|---|---|---|
--analyze |
工具分析 | 布尔值 |
--explain |
解释选择 | 布尔值 |
测试命令标志 (/sc:test)
| 标志 | 目的 | 值 |
|---|---|---|
--coverage |
包含覆盖率 | 布尔值 |
--type |
测试类型 | unit, integration, e2e |
--watch |
监视模式 | 布尔值 |
高级控制标志
范围和焦点
| 标志 | 目的 | 值 |
|---|---|---|
--scope |
分析边界 | file, module, project, system |
--focus |
领域定向 | performance, security, quality, architecture, accessibility, testing |
执行控制
| 标志 | 目的 | 值 |
|---|---|---|
--concurrency [n] |
控制并行操作 | 1-15 |
--iterations [n] |
改进循环 | 1-10 |
--all-mcp |
启用所有 MCP 服务器 | 布尔值 |
--no-mcp |
仅使用本地工具 | 布尔值 |
系统标志(SuperClaude 安装)
| 标志 | 目的 | 值 |
|---|---|---|
--verbose / -v |
详细日志 | 布尔值 |
--quiet / -q |
静默输出 | 布尔值 |
--dry-run |
模拟操作 | 布尔值 |
--force |
跳过检查 | 布尔值 |
--yes / -y |
自动确认 | 布尔值 |
--install-dir |
目标目录 | 路径 |
--legacy |
使用传统脚本 | 布尔值 |
--version |
显示版本 | 布尔值 |
--help |
显示帮助 | 布尔值 |
常用使用模式
前端开发
/sc:implement "responsive dashboard" --magic --c7
/sc:design component-library --type component --format code
/sc:test ui-components/ --magic --play
/sc:improve legacy-ui/ --magic --morph --validate
后端开发
/sc:analyze api/ --focus performance --seq --think
/sc:design payment-api --type api --format spec
/sc:troubleshoot "API timeout" --type performance --trace
/sc:improve auth-service --type security --validate
大型项目
/sc:analyze . --ultrathink --all-mcp --safe-mode
/sc:workflow enterprise-system --strategy enterprise --depth deep
/sc:cleanup . --type all --safe --interactive
/sc:estimate "migrate to microservices" --type complexity --breakdown
质量和维护
/sc:improve src/ --type quality --safe --interactive
/sc:cleanup imports --type imports --preview
/sc:reflect --type completion --validate
/sc:git commit --smart-commit
标志交互
兼容组合
--think+--c7:带文档的分析--magic+--play:UI 生成带测试--serena+--morph:项目内存带转换--safe-mode+--validate:最大安全性--loop+--validate:带验证的迭代改进
冲突标志
--all-mcpvs 单独的 MCP 标志(使用其中之一)--no-mcpvs 任何 MCP 标志(--no-mcp 获胜)--safevs--aggressive(清理强度)--quietvs--verbose(输出级别)
自动启用关系
--safe-mode自动启用--uc和--validate--ultrathink自动启用所有 MCP 服务器--think-hard自动启用--seq+--c7--magic触发以 UI 为中心的智能体
标志故障排除
常见问题
- 工具过多:使用
--no-mcp仅用本地工具测试 - 操作太慢:添加
--uc压缩输出 - 验证阻塞:在开发中使用
--validate而不是--safe-mode - 上下文压力:在 >75% 使用率时自动激活
--token-efficient
调试标志
/sc:analyze . --verbose # 显示决策逻辑和标志激活
/sc:select-tool "操作" --explain # 解释工具选择过程
/sc:reflect --type session --analyze # 审查当前会话决策
快速修复
/sc:analyze . --help # 显示命令的可用标志
/sc:analyze . --no-mcp # 仅本地执行
/sc:cleanup . --preview # 显示将被清理的内容
标志优先级规则
- 安全第一:
--safe-mode>--validate> 优化标志 - 显式覆盖:用户标志 > 自动检测
- 深度层次:
--ultrathink>--think-hard>--think - MCP 控制:
--no-mcp覆盖所有单独的 MCP 标志 - 范围优先级:system > project > module > file