🏗️ Architecture: How to fix code generation producing generic Item entities i...

📋 Decision Context

Question:

How to fix code generation producing generic Item entities instead of domain-specific entities?

Task: Review and enhance code generation improvement plan

🎯 Decision Made

Chosen:

Multi-phase approach: Fix entity extraction in ModuleKnowledgeService, create domain templates, implement multi-module generation in orchestrator, fix category classification

Options Considered:

• No alternatives documented

💭 Reasoning

Current generation produces generic Item with id/name/description instead of Member, Booking, Trainer with domain fields. Root causes: extractEntitiesFromPrompt() uses simple keyword matching that fails for complex prompts like fitness center; template placeholder resolution uses first extracted entity only; category always defaults to other; VibeCodingOrchestratorService creates proper hierarchy but ModuleGeneratorService only creates single module. The plan correctly identifies these issues but needs sequencing refinement.

📁 Files Involved

• docs/english/Plans/current-plans/improving-universe-code-generation.md
• libs/libs-ai/module-generator/src/lib/services/module-knowledge.service.ts
• libs/libs-ai/module-generator/src/lib/services/module-generator.service.ts
• libs/libs-ai/gograb-ai/src/lib/services/vibe-coding-orchestrator.service.ts

🔗 Related

• Decision ID: dev_1767984263310_ncm6cvm
• Session: 31
• Workspace: editor2

Auto-generated by MCP Smart Consolidation