add features

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

@@ -27,7 +27,7 @@
  - When you've got full understanding of how exactly each component will interact with each other, create components
 
 ## Output
- - Store description of each component to the file `docs/02_components/[##]_[component_name]/[component_name]_spec.md` with the next structure:
+ - Store description of each component to the file `docs/02_components/[##]._[component_name]/[##]_spec_[component_name].md` with the next structure:
    - Component Name
    - Detailed description
    - API methods, for each method:

.cursor/commands/2.planning/2.40_gen_features.md

@@ -1,7 +1,7 @@
 # generate Features for the provided component spec
 
 ## Input parameter
- --component @component_spec.md
+ --component component_spec.md
 
 ## Existing solution:
  `@docs/01_solution/solution_draft.md`
@@ -13,11 +13,15 @@
   You are a professional software architect
 
 ## Task
- Decompose component_spec to the features. If component is simple enough, make only 1 feature, if complex - separate per features.
-Feature can contain 0 or more APIs.
+ - Read very carefully component_spec.md
+ - Decompose component_spec.md to the features. If component is simple or atomic, then create only 1 feature.
+ - Split to the many features only if it necessary and would be easier to implement
+ - Do not create features of other components, create *only* features of this exact component
+ - Each feature should be atomic, could contain 0 API, or list of semantically connected APIs
+ - After splitting asses yourself
 
 ## Output
- In a component's folder create feature specs `[##]_[feature_name]_feature.md` with the next structure:  
+ In a component's folder create feature specs `[component's number ##].[feature's number ##]_feature_[feature_name].md` with the next structure:  
   - Name
   - Description
   - Component APIs it implements if any
@@ -27,5 +31,5 @@ Feature can contain 0 or more APIs.
   - Integration tests
 
 ## Notes
-  Do NOT generate any code yet, only brief explanations what should be done.  
-  Ask as many questions as needed.
+  - Do NOT generate any code yet, only brief explanations what should be done.  
+  - Ask as many questions as needed.