mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-02-12 02:37:45 +08:00
445ac823ba
🚀 Revolutionary AI-powered development workflow orchestration system ## 🔥 Core Innovations - **Document-State Separation**: Markdown for planning, JSON for execution state - **Progressive Complexity Management**: Level 0-2 adaptive workflow depth - **5-Agent Orchestration**: Specialized AI agents with context preservation - **Session-First Architecture**: Auto-discovery and state inheritance ## 🏗️ Key Features - Intelligent workflow orchestration (Simple/Medium/Complex patterns) - Real-time document-state synchronization with conflict resolution - Hierarchical task management with 3-level JSON structure - Gemini CLI integration with 12+ specialized templates - Comprehensive file output generation for all workflow commands ## 📦 Installation Remote one-liner installation: ``` iex (iwr -useb https://raw.githubusercontent.com/catlog22/Claude-CCW/main/install-remote.ps1) ``` ## 🎯 System Architecture 4-layer intelligent development architecture: 1. Command Layer - Smart routing and version management 2. Agent Layer - 5 specialized development agents 3. Workflow Layer - Gemini templates and task orchestration 4. Memory Layer - Distributed documentation and auto-sync 🤖 Generated with Claude Code Co-Authored-By: Claude <noreply@anthropic.com>
72 lines
3.0 KiB
Markdown
72 lines
3.0 KiB
Markdown
# Gemini Memory-Gemini-Bridge Template
|
|
|
|
**Purpose**: Comprehensive project structure analysis for hierarchical CLAUDE.md documentation generation
|
|
|
|
## Template Structure
|
|
|
|
```bash
|
|
gemini --all-files -p "@{**/*} @{CLAUDE.md,**/*CLAUDE.md} @{package*.json,requirements.txt,pom.xml,Cargo.toml}
|
|
|
|
Project structure analysis for Memory-Gemini-Bridge documentation generation:
|
|
Target: [project-name or specific scope]
|
|
|
|
## Required Analysis:
|
|
1. **Project Architecture Assessment**:
|
|
- Overall system structure and module organization
|
|
- Technology stack diversity and integration complexity
|
|
- Existing CLAUDE.md hierarchy and content gaps
|
|
- Directory structure patterns and logical groupings
|
|
|
|
2. **Documentation Hierarchy Strategy**:
|
|
- Identify optimal CLAUDE.md placement levels (root, module, sub-module)
|
|
- Determine content differentiation across hierarchy levels
|
|
- Assess complexity thresholds for documentation depth
|
|
- Map existing documentation patterns and standards
|
|
|
|
3. **Cross-System Integration Analysis**:
|
|
- Claude-Gemini compatibility requirements
|
|
- Cross-system documentation synchronization patterns
|
|
- Template and guideline reference patterns
|
|
- Memory system synchronization needs
|
|
|
|
4. **Module Responsibility Mapping**:
|
|
- Core module identification and purpose analysis
|
|
- Inter-module dependencies and integration patterns
|
|
- Component organization and architectural boundaries
|
|
- Implementation pattern consistency across modules
|
|
|
|
5. **Technology Stack Integration**:
|
|
- Framework usage patterns and configuration analysis
|
|
- Build system and development workflow patterns
|
|
- Testing architecture and quality standards
|
|
- Deployment and infrastructure considerations
|
|
|
|
## Output Requirements:
|
|
- **Hierarchy Recommendation**: Specific CLAUDE.md file structure with rationale
|
|
- **Content Strategy**: Level-specific focus areas and content differentiation
|
|
- **Template Selection**: Appropriate DMS and core templates for analysis
|
|
- **Integration Plan**: Workflow coordination with update_dms and agent systems
|
|
- **Quality Standards**: Cross-system compatibility and maintenance guidelines
|
|
|
|
Focus on architectural understanding for documentation strategy rather than implementation details."
|
|
```
|
|
|
|
## Context Application
|
|
|
|
- Generate hierarchical documentation strategy based on project structure
|
|
- Create comprehensive CLAUDE.md files with appropriate content depth
|
|
- Ensure cross-system compatibility between Claude and Gemini CLI
|
|
- Establish maintainable documentation patterns for ongoing development
|
|
|
|
## Usage Guidelines
|
|
|
|
**Use Memory-Gemini-Bridge template when**:
|
|
- Creating or updating CLAUDE.md files for Gemini CLI compatibility
|
|
- Establishing hierarchical documentation strategy for complex projects
|
|
- Synchronizing memory systems between Claude and Gemini CLI
|
|
|
|
**Template focuses on**:
|
|
- Comprehensive project structure analysis
|
|
- Documentation hierarchy strategy and content differentiation
|
|
- Cross-system integration analysis for Claude-Gemini compatibility
|
|
- Architectural understanding for documentation strategy rather than implementation details |