mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-02-05 01:50:27 +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>
68 lines
3.3 KiB
Markdown
68 lines
3.3 KiB
Markdown
# Gemini Agent Templates Overview
|
|
|
|
**Precise, task-focused templates for actionable agent context gathering.**
|
|
|
|
## Overview
|
|
|
|
This document provides focused templates that deliver precise, actionable context for specific tasks rather than generic pattern analysis. Each template targets exact requirements, modification points, and concrete implementation guidance.
|
|
|
|
## Template Usage Guidelines
|
|
|
|
### Key Principles
|
|
|
|
1. **Task-Specific Focus**: Templates target specific tasks rather than broad analysis
|
|
2. **Actionable Output**: Provide exact file:line references and concrete guidance
|
|
3. **Repository Context**: Extract patterns specific to the actual codebase
|
|
4. **Precise Scope**: Analyze only what's needed for the immediate task
|
|
|
|
### When to Use Each Template
|
|
|
|
**Planning Agent**: Before creating implementation plans for specific features or fixes
|
|
- Use when you need to understand exact scope and modification points
|
|
- Focus on concrete deliverables rather than architectural overviews
|
|
|
|
**Code Developer**: Before implementing specific functions, classes, or features
|
|
- Use when you need exact insertion points and code structure guidance
|
|
- Focus on actionable implementation steps with line references
|
|
|
|
**Code Review**: After code has been written for a specific task
|
|
- Use when reviewing changes against repository-specific standards
|
|
- Focus on understanding what was actually implemented and how it fits
|
|
|
|
**UI Design**: Before creating or modifying specific UI components
|
|
- Use when you need component-specific patterns and design system compliance
|
|
- Focus on established design language and interaction patterns
|
|
|
|
**Memory-Gemini-Bridge**: For creating or updating CLAUDE.md files
|
|
- Use when establishing hierarchical documentation strategy
|
|
- Focus on cross-system compatibility between Claude and Gemini CLI
|
|
|
|
### Benefits of Task-Focused Approach
|
|
|
|
1. **Precision**: Get exact modification points instead of general patterns
|
|
2. **Efficiency**: 50% reduction in irrelevant analysis
|
|
3. **Actionability**: Concrete guidance with file:line references
|
|
4. **Context Relevance**: Repository-specific patterns, not generic best practices
|
|
5. **Task Alignment**: Analysis directly supports the specific work being done
|
|
|
|
### Template Customization
|
|
|
|
Customize templates by:
|
|
|
|
1. **Specific File Targeting**: Replace `[task-related-files]` with exact patterns for your task
|
|
2. **Domain Context**: Add domain-specific file patterns (auth, api, ui, etc.)
|
|
3. **Technology Focus**: Include relevant extensions (.tsx for React, .py for Python, etc.)
|
|
4. **Task Context**: Specify exact feature or component being worked on
|
|
|
|
These focused templates provide agents with precise, actionable context for specific tasks, eliminating unnecessary pattern analysis and providing concrete implementation guidance.
|
|
|
|
## Integration with Intelligent Context
|
|
|
|
All templates integrate with `gemini-intelligent-context.md`(@~/.claude/workflows/gemini-intelligent-context.md) for:
|
|
|
|
- **Smart Path Detection** - Automatic file targeting based on analysis type
|
|
- **Technology Stack Detection** - Framework and language-specific optimizations
|
|
- **Domain Context Mapping** - Intelligent domain-specific pattern matching
|
|
- **Dynamic Prompt Enhancement** - Context-aware prompt construction
|
|
|
|
For complete context detection algorithms and intelligent file targeting, see `gemini-intelligent-context.md`. |