mirror of https://github.com/catlog22/Claude-Code-Workflow.git synced 2026-02-04 01:40:45 +08:00

Files

catlog22 445ac823ba Initial release: Claude Code Workflow (CCW) v2.0

🚀 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>

2025-09-07 17:39:54 +08:00

2.4 KiB

Raw Blame History

Development Guidelines

Overview

This document defines project-specific coding standards and development principles.

Philosophy

Core Beliefs

Incremental progress over big bangs - Small changes that compile and pass tests
Learning from existing code - Study and plan before implementing
Pragmatic over dogmatic - Adapt to project reality
Clear intent over clever code - Be boring and obvious

Simplicity Means

Single responsibility per function/class
Avoid premature abstractions
No clever tricks - choose the boring solution
If you need to explain it, it's too complex

Code Quality Standards

Code Style

Consistent formatting - Follow project's established formatting rules
Meaningful names - Variables and functions should be self-documenting
Small functions - Each function should do one thing well
Clear structure - Logical organization of code modules

Testing Standards

Test coverage - Aim for high test coverage on critical paths
Test readability - Tests should serve as documentation
Edge cases - Consider boundary conditions and error states
Test isolation - Tests should be independent and repeatable

Project Integration

Learning the Codebase

Find 3 similar features/components
Identify common patterns and conventions
Use same libraries/utilities when possible
Follow existing test patterns

Tooling

Use project's existing build system
Use project's test framework
Use project's formatter/linter settings
Don't introduce new tools without strong justification

Important Reminders

NEVER:

Use --no-verify to bypass commit hooks
Disable tests instead of fixing them
Commit code that doesn't compile
Make assumptions - verify with existing code

ALWAYS:

Plan complex tasks thoroughly before implementation
Generate task decomposition for multi-module work (>3 modules or >5 subtasks)
Track progress using TODO checklists for complex tasks
Validate planning documents before starting development
Commit working code incrementally
Update plan documentation and progress tracking as you go
Learn from existing implementations
Stop after 3 failed attempts and reassess

Gemini CLI Guidelines

For all Gemini CLI usage, command syntax, and integration guidelines: @~~/.claude/workflows/gemini-cli-guidelines.md @~~/.claude/workflows/gemini-intelligent-context.md

2.4 KiB Raw Blame History