Restructured project from nested workspace pattern to flat single-repo layout. This eliminates redundant nesting and consolidates all project files under version control. ## Migration Summary **Before:** ``` alex/ (workspace, not versioned) ├── chess-game/ (git repo) │ ├── js/, css/, tests/ │ └── index.html └── docs/ (planning, not versioned) ``` **After:** ``` alex/ (git repo, everything versioned) ├── js/, css/, tests/ ├── index.html ├── docs/ (project documentation) ├── planning/ (historical planning docs) ├── .gitea/ (CI/CD) └── CLAUDE.md (configuration) ``` ## Changes Made ### Structure Consolidation - Moved all chess-game/ contents to root level - Removed redundant chess-game/ subdirectory - Flattened directory structure (eliminated one nesting level) ### Documentation Organization - Moved chess-game/docs/ → docs/ (project documentation) - Moved alex/docs/ → planning/ (historical planning documents) - Added CLAUDE.md (workspace configuration) - Added IMPLEMENTATION_PROMPT.md (original project prompt) ### Version Control Improvements - All project files now under version control - Planning documents preserved in planning/ folder - Merged .gitignore files (workspace + project) - Added .claude/ agent configurations ### File Updates - Updated .gitignore to include both workspace and project excludes - Moved README.md to root level - All import paths remain functional (relative paths unchanged) ## Benefits ✅ **Simpler Structure** - One level of nesting removed ✅ **Complete Versioning** - All documentation now in git ✅ **Standard Layout** - Matches open-source project conventions ✅ **Easier Navigation** - Direct access to all project files ✅ **CI/CD Compatible** - All workflows still functional ## Technical Validation - ✅ Node.js environment verified - ✅ Dependencies installed successfully - ✅ Dev server starts and responds - ✅ All core files present and accessible - ✅ Git repository functional ## Files Preserved **Implementation Files:** - js/ (3,517 lines of code) - css/ (4 stylesheets) - tests/ (87 test cases) - index.html - package.json **CI/CD Pipeline:** - .gitea/workflows/ci.yml - .gitea/workflows/release.yml **Documentation:** - docs/ (12+ documentation files) - planning/ (historical planning materials) - README.md **Configuration:** - jest.config.js, babel.config.cjs, playwright.config.js - .gitignore (merged) - CLAUDE.md 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
78 lines
2.0 KiB
Markdown
78 lines
2.0 KiB
Markdown
# Development Workflow Coordination
|
|
|
|
## Purpose
|
|
Structure Claude Code's approach to complex development tasks for maximum efficiency.
|
|
|
|
## Step-by-Step Coordination
|
|
|
|
### 1. Initialize Development Framework
|
|
```
|
|
Tool: mcp__claude-flow__swarm_init
|
|
Parameters: {"topology": "hierarchical", "maxAgents": 8, "strategy": "specialized"}
|
|
```
|
|
Creates hierarchical structure for organized, top-down development.
|
|
|
|
### 2. Define Development Perspectives
|
|
```
|
|
Tool: mcp__claude-flow__agent_spawn
|
|
Parameters: {
|
|
"type": "architect",
|
|
"name": "System Design",
|
|
"capabilities": ["api-design", "database-schema"]
|
|
}
|
|
```
|
|
```
|
|
Tool: mcp__claude-flow__agent_spawn
|
|
Parameters: {
|
|
"type": "coder",
|
|
"name": "Implementation Focus",
|
|
"capabilities": ["nodejs", "typescript", "express"]
|
|
}
|
|
```
|
|
```
|
|
Tool: mcp__claude-flow__agent_spawn
|
|
Parameters: {
|
|
"type": "tester",
|
|
"name": "Quality Assurance",
|
|
"capabilities": ["unit-testing", "integration-testing"]
|
|
}
|
|
```
|
|
Sets up architectural and implementation thinking patterns.
|
|
|
|
### 3. Coordinate Implementation
|
|
```
|
|
Tool: mcp__claude-flow__task_orchestrate
|
|
Parameters: {
|
|
"task": "Build REST API with authentication",
|
|
"strategy": "parallel",
|
|
"priority": "high",
|
|
"dependencies": ["database setup", "auth system"]
|
|
}
|
|
```
|
|
|
|
### 4. Monitor Progress
|
|
```
|
|
Tool: mcp__claude-flow__task_status
|
|
Parameters: {"taskId": "api-build-task-123"}
|
|
```
|
|
|
|
## What Claude Code Actually Does
|
|
1. Uses **Write** tool to create new files
|
|
2. Uses **Edit/MultiEdit** tools for code modifications
|
|
3. Uses **Bash** tool for testing and building
|
|
4. Uses **TodoWrite** tool for task tracking
|
|
5. Follows coordination patterns for systematic implementation
|
|
|
|
Remember: All code is written by Claude Code using its native tools!
|
|
|
|
## CLI Usage
|
|
```bash
|
|
# Start development workflow via CLI
|
|
npx claude-flow workflow dev "REST API with auth"
|
|
|
|
# Create custom workflow
|
|
npx claude-flow workflow create --name "api-dev" --steps "design,implement,test,deploy"
|
|
|
|
# Execute saved workflow
|
|
npx claude-flow workflow execute api-dev
|
|
``` |