kazuki
01ddc14354
refactor: consolidate MCP integration to unified gateway
...
**Changes**:
- Remove individual MCP server docs (superclaude/mcp/*.md)
- Remove MCP server configs (superclaude/mcp/configs/*.json)
- Delete MCP docs component (setup/components/mcp_docs.py)
- Simplify installer (setup/core/installer.py)
- Update components for unified gateway approach
**Rationale**:
- Unified gateway (airis-mcp-gateway) provides all MCP servers
- Individual docs/configs no longer needed (managed centrally)
- Reduces maintenance burden and file count
- Simplifies installation process
**Files Removed**: 17 MCP files (docs + configs)
**Installer Changes**: Removed legacy MCP installation logic
🤖 Generated with [Claude Code](https://claude.com/claude-code )
Co-Authored-By: Claude <noreply@anthropic.com >
2025-10-17 07:24:01 +09:00
kazuki
bf1fd50ca8
refactor: rename CoreComponent to FrameworkDocsComponent and add PM token tracking
...
## Changes
### Component Renaming (setup/components/)
- Renamed CoreComponent → FrameworkDocsComponent for clarity
- Updated all imports in __init__.py, agents.py, commands.py, mcp_docs.py, modes.py
- Better reflects the actual purpose (framework documentation files)
### PM Agent Enhancement (superclaude/commands/pm.md)
- Added token usage tracking instructions
- PM Agent now reports:
1. Current token usage from system warnings
2. Percentage used (e.g., "27% used" for 54K/200K)
3. Status zone: 🟢 <75% | 🟡 75-85% | 🔴 >85%
- Helps prevent token exhaustion during long sessions
### UI Utilities (setup/utils/ui.py)
- Added new UI utility module for installer
- Provides consistent user interface components
## Benefits
- ✅ Clearer component naming (FrameworkDocs vs Core)
- ✅ PM Agent token awareness for efficiency
- ✅ Better visual feedback with status zones
🤖 Generated with [Claude Code](https://claude.com/claude-code )
Co-Authored-By: Claude <noreply@anthropic.com >
2025-10-17 05:28:23 +09:00
kazuki nakai
050d5ea2ab
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 08:47:09 +05:30
NomenAK
0e71f29598
Implement two-stage installation with simplified MCP configuration
...
- Stage 1: MCP server selection (Context7, Sequential, Magic, Playwright, Serena, Morphllm)
- Stage 2: Framework components (Core, Modes, Commands, Agents, MCP Docs)
Major Changes:
- Created MCP config snippets in SuperClaude/MCP/configs/ for JSON-based configuration
- Simplified MCPComponent to modify .claude.json instead of npm/subprocess installation
- Added ModesComponent for behavioral modes (Brainstorming, Introspection, etc.)
- Added MCPDocsComponent for dynamic MCP documentation installation
- Completely removed Hooks component (deleted hooks.py, updated all references)
- Implemented two-stage interactive installation flow
- Updated profiles and configuration files
Benefits:
- Much simpler and more reliable MCP configuration
- Clear separation between server setup and documentation
- Auto-selection of MCP docs based on server choices
- User-friendly two-stage selection process
🤖 Generated with [Claude Code](https://claude.ai/code )
Co-Authored-By: Claude <noreply@anthropic.com >
2025-08-14 20:35:19 +02:00
NomenAK
dc1c7f2e1b
Add Agents component to installation process
...
- Created AgentsComponent class in setup/components/agents.py
- Added agents component to features.json configuration
- Updated components __init__.py to import AgentsComponent
- Added agents to "all" components list in install.py
- Updated developer and quick installation profiles to include agents
- Agents component installs 13 specialized AI agent files to ~/.claude/agents/
The 13 specialized agents (system-architect, frontend-specialist, security-auditor,
etc.) are now properly exposed in the installation process, aligning with V4 Beta's
marketing of "13 specialized agents with domain expertise".
Users can now:
- Install agents via --components agents or --components all
- See agents in interactive component selection menu
- Get agents included in developer and quick installation profiles
🤖 Generated with [Claude Code](https://claude.ai/code )
Co-Authored-By: Claude <noreply@anthropic.com >
2025-08-14 20:12:59 +02:00
NomenAK
d87bd3dc35
Hide Hooks installation from CLI until implementation is ready
...
- Commented out HooksComponent import and export in __init__.py
- Removed hooks from --components all installation list
- Set enabled=false in features.json configuration
- Updated descriptions to indicate "NOT YET IMPLEMENTED"
- Code remains intact for future re-enablement
The Hooks system is not yet fully implemented, so hiding it from
users prevents confusion while preserving the framework for future use.
🤖 Generated with [Claude Code](https://claude.ai/code )
Co-Authored-By: Claude <noreply@anthropic.com >
2025-08-14 20:02:08 +02:00
mithun50
41b5924934
Added the Setup implimentation
2025-08-14 08:56:04 +05:30
NomenAK
1d03832f2d
SuperClaude V4 Beta: Major framework restructuring
...
- Restructured core framework components
- Added new Agents, MCP servers, and Modes documentation
- Introduced SuperClaude-Lite minimal implementation
- Enhanced Commands with session management capabilities
- Added comprehensive Hooks system with Python integration
- Removed legacy setup and profile components
- Updated .gitignore to exclude Tests/, ClaudeDocs/, and .serena/
- Consolidated configuration into SuperClaude/Config/
- Added Templates for consistent component creation
This is the initial commit for the V4 Beta branch containing all recent framework improvements and architectural changes.
🤖 Generated with [Claude Code](https://claude.ai/code )
Co-Authored-By: Claude <noreply@anthropic.com >
2025-08-05 13:59:17 +02:00
NomenAK
59d74b8af2
Initial commit: SuperClaude v3 Beta clean architecture
...
Complete foundational restructure with:
- Simplified project architecture
- Comprehensive documentation system
- Modern installation framework
- Clean configuration management
- Updated profiles and settings
🤖 Generated with [Claude Code](https://claude.ai/code )
Co-Authored-By: Claude <noreply@anthropic.com >
2025-07-14 14:28:11 +02:00