SuperClaude/README-kr.md
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

12 KiB

🚀 SuperClaude 프레임워크

Claude Code를 구조화된 개발 플랫폼으로 변환

Version License PRs Welcome

Website PyPI npm

English 中文 日本語 한국어

빠른 시작후원새로운 기능문서기여


📊 프레임워크 통계

명령어 수 에이전트 모드 MCP 서버
21 14 5 6
슬래시 명령어 전문 AI 작동 모드 통합 서비스

🎯 개요

SuperClaude는 메타프로그래밍 설정 프레임워크로, 동작 지시 주입과 컴포넌트 통제를 통해 Claude Code를 구조화된 개발 플랫폼으로 변환합니다. 강력한 도구와 지능형 에이전트를 갖춘 체계적인 워크플로우 자동화를 제공합니다.

빠른 설치

설치 방법 선택

방법 명령어 최적 사용처
🐍 pipx pipx install SuperClaude && pipx upgrade SuperClaude && SuperClaude install 권장 - Linux/macOS
📦 pip pip install SuperClaude && pip upgrade SuperClaude && SuperClaude install 기존 Python 환경
🌐 npm npm install -g @bifrost_inc/superclaude && superclaude install 크로스 플랫폼, Node.js 사용자
⚠️ 중요: SuperClaude V3에서 업그레이드

SuperClaude V3가 설치되어 있다면 V4를 설치하기 전에 제거해야 합니다:

# 먼저 V3 제거
관련된 모든 파일과 디렉토리 삭제:
*.md *.json 및 commands/

# 그런 다음 V4 설치
pipx install SuperClaude && pipx upgrade SuperClaude && SuperClaude install

업그레이드 시 유지되는 내용:

  • ✓ 커스텀 슬래시 명령어 (commands/sc/ 외부)
  • CLAUDE.md 내의 커스텀 콘텐츠
  • ✓ Claude Code의 .claude.json, .credentials.json, settings.json, settings.local.json
  • ✓ 추가한 커스텀 에이전트 및 파일

⚠️ 참고: V3의 다른 SuperClaude 관련 .json 파일은 충돌을 일으킬 수 있으므로 삭제하세요.

💡 PEP 668 오류 해결방법
# 옵션 1: pipx 사용 (권장)
pipx install SuperClaude

# 옵션 2: 사용자 설치
pip install --user SuperClaude

# 옵션 3: 강제 설치 (주의해서 사용)
pip install --break-system-packages SuperClaude

💖 프로젝트 후원하기

솔직히 말씀드리면, SuperClaude를 유지하는 데는 시간과 리소스가 필요합니다.

테스트를 위한 Claude Max 구독료만 매월 100달러이고, 거기에 문서화, 버그 수정, 기능 개발에 쓰는 시간이 추가됩니다. 일상 업무에서 SuperClaude의 가치를 느끼신다면, 프로젝트 후원을 고려해주세요. 몇 달러라도 기본 비용을 충당하고 개발을 계속할 수 있게 해줍니다.

코드, 피드백, 또는 후원을 통해, 모든 기여자가 중요합니다. 이 커뮤니티의 일원이 되어주셔서 감사합니다! 🙏

Ko-fi

Ko-fi

일회성 기여

🎯 Patreon

Patreon

월간 후원

💜 GitHub

GitHub Sponsors

유연한 티어

여러분의 후원으로 가능한 것들:

항목 비용/영향
🔬 Claude Max 테스트 검증과 테스트를 위해 월 100달러
기능 개발 새로운 기능과 개선 사항
📚 문서화 포괄적인 가이드와 예제
🤝 커뮤니티 지원 신속한 이슈 대응과 도움
🔧 MCP 통합 새로운 서버 연결 테스트
🌐 인프라 호스팅 및 배포 비용

참고: 하지만 부담은 없습니다. 프레임워크는 어쨌든 오픈소스로 유지됩니다. 사람들이 사용하고 가치를 느끼고 있다는 것만 알아도 동기부여가 됩니다. 코드, 문서, 또는 정보 확산을 통한 기여도 큰 도움이 됩니다! 🙏


🎉 V4의 새로운 기능

버전 4는 커뮤니티 피드백과 실제 사용 패턴을 기반으로 중요한 개선 사항을 제공합니다.

🤖 더 스마트한 에이전트 시스템

14개의 전문 에이전트가 도메인 전문성을 제공:

  • 보안 엔지니어가 실제 취약점 포착
  • 프론트엔드 아키텍트가 UI 패턴 이해
  • 컨텍스트 기반 자동 조정
  • 필요 시 도메인별 전문 지식 제공

📝 개선된 네임스페이스

모든 명령어에 /sc: 접두사:

  • 커스텀 명령어와 충돌 없음
  • 전체 라이프사이클을 다루는 21개 명령어
  • 브레인스토밍부터 배포까지
  • 정리된 명령어 구조

🔧 MCP 서버 통합

6개의 강력한 서버가 함께 작동:

  • Context7 → 최신 문서
  • Sequential → 복잡한 분석
  • Magic → UI 컴포넌트 생성
  • Playwright → 브라우저 테스트
  • Morphllm → 대량 변환
  • Serena → 세션 지속성

🎯 작동 모드

다양한 컨텍스트를 위한 5가지 적응형 모드:

  • 브레인스토밍 → 적절한 질문하기
  • 오케스트레이션 → 효율적인 도구 조정
  • 토큰 효율성 → 30-50% 컨텍스트 절약
  • 작업 관리 → 체계적인 구성
  • 성찰 → 메타인지 분석

최적화된 성능

더 작은 프레임워크, 더 큰 프로젝트:

  • 프레임워크 풋프린트 감소
  • 코드를 위한 더 많은 컨텍스트
  • 더 긴 대화 가능
  • 복잡한 작업 활성화

📚 문서 전면 개편

개발자를 위한 완전한 재작성:

  • 실제 예제와 사용 사례
  • 일반적인 함정 문서화
  • 실용적인 워크플로우 포함
  • 개선된 탐색 구조

📚 문서

🇰🇷 SuperClaude 완전 한국어 가이드

🚀 시작하기 📖 사용자 가이드 🛠️ 개발자 리소스 📋 레퍼런스

🤝 기여하기

SuperClaude 커뮤니티에 참여하세요

모든 종류의 기여를 환영합니다! 도움을 줄 수 있는 방법:

우선순위 영역 설명
📝 높음 문서 가이드 개선, 예제 추가, 오타 수정
🔧 높음 MCP 통합 서버 설정 추가, 통합 테스트
🎯 중간 워크플로우 명령어 패턴과 레시피 작성
🧪 중간 테스트 테스트 추가, 기능 검증
🌐 낮음 국제화 문서를 다른 언어로 번역

Contributing Guide Contributors


⚖️ 라이선스

이 프로젝트는 MIT 라이선스 하에 라이선스가 부여됩니다 - 자세한 내용은 LICENSE 파일을 참조하세요.

MIT License


Star 히스토리

Star History Chart

🚀 SuperClaude 커뮤니티가 열정으로 구축

한계를 뛰어넘는 개발자들을 위해 ❤️로 제작되었습니다

맨 위로 ↑