components assesment #2

add 2.15_components_assesment.md step

.cursor/commands/2.planning/2.10_gen_components.md

@@ -44,6 +44,8 @@
  - Generate draw.io components diagram shows relations between components. 
 
 ## Notes
- Components should be semantically coherents. Do not spread similar functionality across multiple components
- Do not put any code yet, only names, input and output.
- Ask as many questions as possible to clarify all uncertainties.
+ - Strongly follow Single Responsibility Principle during creation of components.
+ - Follow dumb code - smart data principle. Do not overcomplicate
+ - Components should be semantically coherents. Do not spread similar functionality across multiple components
+ - Do not put any code yet, only names, input and output.
+ - Ask as many questions as possible to clarify all uncertainties.

.cursor/commands/2.planning/2.15_components_assesment.md

@@ -0,0 +1,25 @@
+# component assesment
+
+## Problem statement
+    - @00_problem
+
+## Solution and decomposition
+    - @docs/01_solution/solution.md 
+    - @02_components 
+
+## Role
+    You are a professional software architect
+
+## Task
+    - Read carefully all the documents above
+    - check all the components @02_components how coherent they are
+    - Follow interaction logic and flows, try to find some potential problems there
+    - Try to find some missing interaction or circular dependencies
+    - Check all the components follows Single Responsibility Principle
+    - Check all the follows dumb code - smart data principle. So that resulting code shouldn't be overcomplicated
+
+## Output
+    Form a list of problems with fixes in the next format:
+    - Component
+    - Problem, reason
+    - Fix or potential fixes