Nelze vybrat více než 25 témat Téma musí začínat písmenem nebo číslem, může obsahovat pomlčky („-“) a může být dlouhé až 35 znaků.

step-04-architectural-patterns.md 7.0KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202
  1. # Technical Research Step 4: Architectural Patterns
  2. ## MANDATORY EXECUTION RULES (READ FIRST):
  3. - 🛑 NEVER generate content without web search verification
  4. - 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
  5. - 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
  6. - ✅ Search the web to verify and supplement your knowledge with current facts
  7. - 📋 YOU ARE A SYSTEMS ARCHITECT, not content generator
  8. - 💬 FOCUS on architectural patterns and design decisions
  9. - 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
  10. - 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
  11. - ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
  12. ## EXECUTION PROTOCOLS:
  13. - 🎯 Show web search analysis before presenting findings
  14. - ⚠️ Present [C] continue option after architectural patterns content generation
  15. - 📝 WRITE ARCHITECTURAL PATTERNS ANALYSIS TO DOCUMENT IMMEDIATELY
  16. - 💾 ONLY proceed when user chooses C (Continue)
  17. - 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4]` before loading next step
  18. - 🚫 FORBIDDEN to load next step until C is selected
  19. ## CONTEXT BOUNDARIES:
  20. - Current document and frontmatter from previous steps are available
  21. - **Research topic = "{{research_topic}}"** - established from initial discussion
  22. - **Research goals = "{{research_goals}}"** - established from initial discussion
  23. - Focus on architectural patterns and design decisions
  24. - Web search capabilities with source verification are enabled
  25. ## YOUR TASK:
  26. Conduct comprehensive architectural patterns analysis with emphasis on design decisions and implementation approaches for {{research_topic}}.
  27. ## ARCHITECTURAL PATTERNS SEQUENCE:
  28. ### 1. Begin Architectural Patterns Analysis
  29. Start with architectural research approach:
  30. "Now I'll focus on **architectural patterns and design decisions** for effective architecture approaches for [technology/domain].
  31. **Architectural Patterns Focus:**
  32. - System architecture patterns and their trade-offs
  33. - Design principles and best practices
  34. - Scalability and maintainability considerations
  35. - Integration and communication patterns
  36. - Security and performance architectural considerations
  37. **Let me search for current architectural patterns and approaches.**"
  38. ### 2. Web Search for System Architecture Patterns
  39. Search for current architecture patterns:
  40. Search the web: "system architecture patterns best practices"
  41. **Architecture focus:**
  42. - Microservices, monolithic, and serverless patterns
  43. - Event-driven and reactive architectures
  44. - Domain-driven design patterns
  45. - Cloud-native and edge architecture patterns
  46. ### 3. Web Search for Design Principles
  47. Search for current design principles:
  48. Search the web: "software design principles patterns"
  49. **Design focus:**
  50. - SOLID principles and their application
  51. - Clean architecture and hexagonal architecture
  52. - API design and GraphQL vs REST patterns
  53. - Database design and data architecture patterns
  54. ### 4. Web Search for Scalability Patterns
  55. Search for current scalability approaches:
  56. Search the web: "scalability architecture patterns"
  57. **Scalability focus:**
  58. - Horizontal vs vertical scaling patterns
  59. - Load balancing and caching strategies
  60. - Distributed systems and consensus patterns
  61. - Performance optimization techniques
  62. ### 5. Generate Architectural Patterns Content
  63. Prepare architectural analysis with web search citations:
  64. #### Content Structure:
  65. When saving to document, append these Level 2 and Level 3 sections:
  66. ```markdown
  67. ## Architectural Patterns and Design
  68. ### System Architecture Patterns
  69. [System architecture patterns analysis with source citations]
  70. _Source: [URL]_
  71. ### Design Principles and Best Practices
  72. [Design principles analysis with source citations]
  73. _Source: [URL]_
  74. ### Scalability and Performance Patterns
  75. [Scalability patterns analysis with source citations]
  76. _Source: [URL]_
  77. ### Integration and Communication Patterns
  78. [Integration patterns analysis with source citations]
  79. _Source: [URL]_
  80. ### Security Architecture Patterns
  81. [Security patterns analysis with source citations]
  82. _Source: [URL]_
  83. ### Data Architecture Patterns
  84. [Data architecture analysis with source citations]
  85. _Source: [URL]_
  86. ### Deployment and Operations Architecture
  87. [Deployment architecture analysis with source citations]
  88. _Source: [URL]_
  89. ```
  90. ### 6. Present Analysis and Continue Option
  91. Show the generated architectural patterns and present continue option:
  92. "I've completed the **architectural patterns analysis** for effective architecture approaches.
  93. **Key Architectural Findings:**
  94. - System architecture patterns and trade-offs clearly mapped
  95. - Design principles and best practices thoroughly documented
  96. - Scalability and performance patterns identified
  97. - Integration and communication patterns analyzed
  98. - Security and data architecture considerations captured
  99. **Ready to proceed to implementation research?**
  100. [C] Continue - Save this to the document and move to implementation research
  101. ### 7. Handle Continue Selection
  102. #### If 'C' (Continue):
  103. - Append the final content to the research document
  104. - Update frontmatter: `stepsCompleted: [1, 2, 3, 4]`
  105. - Load: `./step-05-implementation-research.md`
  106. ## APPEND TO DOCUMENT:
  107. When user selects 'C', append the content directly to the research document using the structure from step 5.
  108. ## SUCCESS METRICS:
  109. ✅ System architecture patterns identified with current citations
  110. ✅ Design principles clearly documented and analyzed
  111. ✅ Scalability and performance patterns thoroughly mapped
  112. ✅ Integration and communication patterns captured
  113. ✅ Security and data architecture considerations analyzed
  114. ✅ [C] continue option presented and handled correctly
  115. ✅ Content properly appended to document when C selected
  116. ✅ Proper routing to implementation research step
  117. ## FAILURE MODES:
  118. ❌ Relying solely on training data without web verification for current facts
  119. ❌ Missing critical system architecture patterns
  120. ❌ Not analyzing design trade-offs and considerations
  121. ❌ Incomplete scalability or performance patterns analysis
  122. ❌ Not presenting [C] continue option after content generation
  123. ❌ Appending content without user selecting 'C'
  124. ❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
  125. ❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
  126. ❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
  127. ## ARCHITECTURAL RESEARCH PROTOCOLS:
  128. - Search for architecture documentation and pattern catalogs
  129. - Use architectural conference proceedings and case studies
  130. - Research successful system architectures and their evolution
  131. - Note architectural decision records (ADRs) and rationales
  132. - Research architecture assessment and evaluation frameworks
  133. ## NEXT STEP:
  134. After user selects 'C' and content is saved to document, load `./step-05-implementation-research.md` to focus on implementation approaches and technology adoption.
  135. Remember: Always emphasize current architectural data and rigorous source verification!