5ad0700b41
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>
63 lines
1.3 KiB
Markdown
63 lines
1.3 KiB
Markdown
# Agent Specialization Training
|
|
|
|
## Purpose
|
|
Train agents to become experts in specific domains for better performance.
|
|
|
|
## Specialization Areas
|
|
|
|
### 1. By File Type
|
|
Agents automatically specialize based on file extensions:
|
|
- **.js/.ts**: Modern JavaScript patterns
|
|
- **.py**: Pythonic idioms
|
|
- **.go**: Go best practices
|
|
- **.rs**: Rust safety patterns
|
|
|
|
### 2. By Task Type
|
|
```
|
|
Tool: mcp__claude-flow__agent_spawn
|
|
Parameters: {
|
|
"type": "coder",
|
|
"capabilities": ["react", "typescript", "testing"],
|
|
"name": "React Specialist"
|
|
}
|
|
```
|
|
|
|
### 3. Training Process
|
|
The system trains through:
|
|
- Successful edit operations
|
|
- Code review patterns
|
|
- Error fix approaches
|
|
- Performance optimizations
|
|
|
|
### 4. Specialization Benefits
|
|
```
|
|
# Check agent specializations
|
|
Tool: mcp__claude-flow__agent_list
|
|
Parameters: {"swarmId": "current"}
|
|
|
|
Result shows expertise levels:
|
|
{
|
|
"agents": [
|
|
{
|
|
"id": "coder-123",
|
|
"specializations": {
|
|
"javascript": 0.95,
|
|
"react": 0.88,
|
|
"testing": 0.82
|
|
}
|
|
}
|
|
]
|
|
}
|
|
```
|
|
|
|
## Continuous Improvement
|
|
Agents share learnings across sessions for cumulative expertise!
|
|
|
|
## CLI Usage
|
|
```bash
|
|
# Train agent specialization via CLI
|
|
npx claude-flow train agent --type coder --capabilities "react,typescript"
|
|
|
|
# Check specializations
|
|
npx claude-flow agent list --specializations
|
|
``` |