EuConquisto Composer MCP

# Development Protocol - v5.2.0 Knowledge Preservation **Version**: v5.2.0 FULLY OPERATIONAL **Updated**: January 12, 2025 **Purpose**: Prevent knowledge loss and feature regression through systematic documentation **Status**: ✅ Current Development Guidelines **Sync**: EuConquisto Composer MCP v5.2.0 --- ## 📋 **Pre-Development Checklist** ### **Before Making ANY Changes**: 1. **Reference Check**: Read `/docs/technical-knowledge-base.md` 2. **JSON Validation**: Verify against `/docs/references/json-example.md` 3. **Working Examples**: Check `/docs/working-examples.md` for proven patterns 4. **Status Review**: Check current status in `CLAUDE.md` ### **For New Features**: 1. **Build on Proven Patterns**: Use existing working components 2. **Document First**: Update knowledge base BEFORE implementing 3. **Test Incrementally**: Small changes with immediate validation 4. **Preserve Working Code**: Never modify components marked as "WORKING" --- ## 🔍 **Debugging Protocol** ### **Step 1: Knowledge Base Consultation** - Check if this issue was solved before - Reference the JSON structure specification - Verify working components are intact - Review previous solutions ### **Step 2: Minimal Reproduction** - Create smallest possible test case - Use known working examples as baseline - Test single components in isolation - Avoid assumptions about root cause ### **Step 3: Systematic Analysis** - Follow proven debugging patterns - Document findings in real-time - Update knowledge base with insights - Preserve working solutions --- ## 📚 **Documentation Update Rules** ### **When to Update Documentation**: - ✅ New working solution discovered - ✅ Critical technical decision made - ✅ Root cause identified and fixed - ✅ Working pattern validated - ✅ Debugging insight gained ### **What to Update**: - `/docs/technical-knowledge-base.md` - Core technical knowledge - `/docs/working-examples.md` - Proven patterns and code - `CLAUDE.md` - Project status and context - `/docs/progress/latest.md` - Progress tracking - Code comments in critical files ### **How to Update**: 1. **Real-time Updates**: Document as you discover 2. **Preserve History**: Don't overwrite working solutions 3. **Link References**: Cross-reference related documents 4. **Status Tracking**: Mark components as WORKING/BROKEN/UNKNOWN --- ## 🚫 **Forbidden Actions** ### **Never Do This**: - ❌ Modify files marked as "WORKING" without consultation - ❌ Assume root cause without referencing knowledge base - ❌ Rebuild features that are already working - ❌ Ignore the JSON reference specification - ❌ Make changes without updating documentation ### **Always Do This**: - ✅ Consult knowledge base first - ✅ Test with minimal examples - ✅ Document findings immediately - ✅ Preserve working patterns - ✅ Update status tracking --- ## 🔄 **Knowledge Validation Cycle** ### **Every Development Session**: 1. **Start**: Read knowledge base and current status 2. **Plan**: Reference proven patterns and working examples 3. **Implement**: Build on existing working components 4. **Test**: Validate against known working cases 5. **Document**: Update knowledge base with findings 6. **Status**: Update project status and next steps ### **Monthly Reviews**: - Audit knowledge base for accuracy - Validate working examples still work - Update documentation structure - Archive obsolete information --- ## 🎯 **Success Metrics** ### **Knowledge Preservation Success**: - ✅ Zero regression of working features - ✅ Debugging sessions reference prior solutions - ✅ New team members can understand system quickly - ✅ Technical decisions are documented and traceable ### **Development Efficiency Success**: - ✅ Issues resolved faster through knowledge reuse - ✅ Less time spent rebuilding working features - ✅ More time spent on actual new functionality - ✅ Clear understanding of system architecture --- **Last Updated**: January 11, 2025 **Status**: ✅ **MANDATORY** - Follow this protocol for all development work