External/SuperClaude
1
0
Fork 0
mirror of https://github.com/SuperClaude-Org/SuperClaude_Framework.git synced 2025-12-29 16:16:08 +00:00
Code Issues Packages Projects Releases Wiki Activity
354 Commits 9 Branches 17 Tags
e799c35efd8d972de383ce98641ce72bbec71f9e
Commit Graph

4 Commits

Author SHA1 Message Date
kazuki
2ec23b14e5 feat: implement lazy loading architecture with PM Agent Skills migration 
## Changes

### Core Architecture
- Migrated PM Agent from always-loaded .md to on-demand Skills
- Implemented lazy loading: agents/modes no longer installed by default
- Only Skills and commands are installed (99.5% token reduction)

### Skills Structure
- Created `superclaude/skills/pm/` with modular architecture:
  - SKILL.md (87 tokens - description only)
  - implementation.md (16KB - full PM protocol)
  - modules/ (git-status, token-counter, pm-formatter)

### Installation System Updates
- Modified `slash_commands.py`:
  - Added Skills directory discovery
  - Skills-aware file installation (→ ~/.claude/skills/)
  - Custom validation for Skills paths
- Modified `agent_personas.py`: Skip installation (migrated to Skills)
- Modified `behavior_modes.py`: Skip installation (migrated to Skills)

### Security
- Updated path validation to allow ~/.claude/skills/ installation
- Maintained security checks for all other paths

## Performance

**Token Savings**:
- Before: 17,737 tokens (agents + modes always loaded)
- After: 87 tokens (Skills SKILL.md descriptions only)
- Reduction: 99.5% (17,650 tokens saved)

**Loading Behavior**:
- Startup: 0 tokens (PM Agent not loaded)
- `/sc:pm` invocation: ~2,500 tokens (full protocol loaded on-demand)
- Other agents/modes: Not loaded at all

## Benefits

1. **Zero-Footprint Startup**: SuperClaude no longer pollutes context
2. **On-Demand Loading**: Pay token cost only when actually using features
3. **Scalable**: Can migrate other agents to Skills incrementally
4. **Backward Compatible**: Source files remain for future migration

## Next Steps

- Test PM Skills in real Airis development workflow
- Migrate other high-value agents to Skills as needed
- Keep unused agents/modes in source (no installation overhead)

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
 2025-10-21 05:17:53 +09:00
kazuki
3d05475c68 fix: resolve installation failures after framework_docs rename 
## Problems Fixed
1. **Syntax errors**: Duplicate docstrings in all component files (line 1)
2. **Dependency mismatch**: Stale framework_docs references after rename to knowledge_base

## Changes
- Fix docstring format in all component files (behavior_modes, agent_personas, slash_commands, mcp_integration)
- Update all dependency references: framework_docs → knowledge_base
- Update component registration calls in knowledge_base.py (5 locations)
- Update install.py files in both setup/ and superclaude/ (5 locations total)
- Fix documentation links in README-ja.md and README-zh.md

## Verification
✅ All components load successfully without syntax errors
✅ Dependency resolution works correctly
✅ Installation completes in 0.5s with all validations passing
✅ make dev succeeds

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
 2025-10-18 21:55:02 +09:00
kazuki
35e924c39b Merge responsibility-driven components 2025-10-18 21:29:16 +09:00
kazuki
1fab5bb39e refactor: responsibility-driven component architecture 
Rename components to reflect their responsibilities:
- framework_docs.py → knowledge_base.py (KnowledgeBaseComponent)
- modes.py → behavior_modes.py (BehaviorModesComponent)
- agents.py → agent_personas.py (AgentPersonasComponent)
- commands.py → slash_commands.py (SlashCommandsComponent)
- mcp.py → mcp_integration.py (MCPIntegrationComponent)

Each component now clearly documents its responsibility:
- knowledge_base: Framework knowledge initialization
- behavior_modes: Execution mode definitions
- agent_personas: AI agent personality definitions
- slash_commands: CLI command registration
- mcp_integration: External tool integration

Benefits:
- Self-documenting architecture
- Clear responsibility boundaries
- Easy to navigate and extend
- Scalable for future hierarchical organization

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
 2025-10-17 17:31:51 +09:00