EuConquisto Composer MCP

# EuConquisto Composer MCP - Project Reorganization Plan ## Current Issues - 44+ files in project root (should be ~10 max) - Fragile versioning with suffixes like `-fixed`, `-clean`, `-v2` - Mixed purposes: production, development, testing, debug files together - Multiple duplicate configuration files - No proper .gitignore - Poor separation of concerns ## Proposed Clean Structure ``` euconquisto-composer-mcp/ ├── .gitignore # Proper ignore rules ├── .github/ # GitHub workflows │ └── workflows/ ├── README.md # Main project documentation ├── CHANGELOG.md # Version history ├── package.json # Dependencies and scripts ├── package-lock.json # Lock file ├── tsconfig.json # TypeScript config ├── ├── bin/ # Executable entry points │ ├── start-production.sh # Production startup │ └── start-development.sh # Development startup ├── ├── src/ # Source code (TypeScript) │ ├── index.ts # Main entry point │ ├── server/ # MCP server implementation │ ├── content/ # Content generation modules │ ├── browser/ # Browser automation │ ├── auth/ # Authentication handling │ ├── types/ # TypeScript definitions │ └── utils/ # Utility functions ├── ├── dist/ # Compiled JavaScript (gitignored) ├── ├── config/ # Configuration files │ ├── claude-desktop.json # Claude Desktop config │ ├── development.json # Dev environment config │ └── production.json # Production config ├── ├── docs/ # Documentation │ ├── api/ # API documentation │ ├── user-guide/ # User guides │ ├── development/ # Developer docs │ └── deployment/ # Deployment guides ├── ├── tests/ # Test files │ ├── unit/ # Unit tests │ ├── integration/ # Integration tests │ └── e2e/ # End-to-end tests ├── ├── tools/ # Development and utility tools │ ├── auth/ # JWT and authentication tools │ ├── monitoring/ # Monitoring and debugging │ └── migration/ # Migration scripts ├── ├── logs/ # Log files (gitignored) ├── temp/ # Temporary files (gitignored) └── archive/ # Deprecated/legacy files └── legacy/ # Old implementations ``` ## Migration Strategy ### Phase 1: Backup and Preparation 1. Create full project backup 2. Initialize proper git repository with tags 3. Create clean directory structure ### Phase 2: File Categorization and Migration 1. **Production Files** → `src/` and `bin/` 2. **Configuration Files** → `config/` 3. **Documentation** → `docs/` 4. **Test Files** → `tests/` 5. **Tools and Scripts** → `tools/` 6. **Legacy/Deprecated** → `archive/` ### Phase 3: Version Control Cleanup 1. Remove versioned suffixes (-v1, -fixed, etc.) 2. Implement proper git tagging 3. Create .gitignore for generated files 4. Clean commit history ### Phase 4: Reference Updates 1. Update package.json entry points 2. Update Claude Desktop configurations 3. Update documentation links 4. Update import statements ## File Migration Map ### Keep in Root (Essential Only) - README.md - CHANGELOG.md - package.json - package-lock.json - tsconfig.json - .gitignore ### Migrate to src/ - All .ts files from root and subdirectories - Main implementation files - Current: `src/*` → New: `src/` ### Migrate to bin/ - start-*.sh scripts - Executable entry points ### Migrate to config/ - claude-desktop-*.json → `config/claude-desktop.json` - Environment-specific configs ### Migrate to docs/ - All .md files (except README.md, CHANGELOG.md) - Current: `docs/*` → New: `docs/` ### Migrate to tests/ - All test-*.js files - Current: `tests/*` → New: `tests/` ### Migrate to tools/ - Current: `tools/*` → New: `tools/` - Utility scripts and debugging tools ### Migrate to archive/ - Versioned files (-fixed, -clean, -v2, etc.) - Deprecated implementations - Old backups ### Remove/Gitignore - dist/ contents (will be regenerated) - logs/ contents - Debug screenshots - Temporary files - .DS_Store files ## Benefits of Reorganization 1. **Clean Root**: Only essential files visible 2. **Proper Versioning**: Git tags instead of file suffixes 3. **Clear Separation**: Source, config, docs, tests separated 4. **Better Maintainability**: Easy to find and modify files 5. **Professional Structure**: Follows Node.js best practices 6. **Easier CI/CD**: Clear build and deployment paths 7. **Better Collaboration**: Contributors can navigate easily ## Implementation Commands Will be provided in migration script for safe execution.