name components correctly

update tutorial with 3. implementation phase
add implementation commands

.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]/[##]_spec_[component_name].md` with the next structure:
+ - Store description of each component to the file `docs/02_components/[##]_[component_name]/[##]._component_[component_name].md` with the next structure:
    - Component Name
    - Detailed description
    - API methods, for each method:

.cursor/commands/2.planning/2.20_gen_epics.md

@@ -13,7 +13,7 @@
  `@docs/00_problem/acceptance_criteria.md`.  
 
 ## Existing solution:
- `@docs/01_solution/solution_draft.md`
+ `@docs/01_solution/solution.md`
 
 ## Role
   You are a world class product manager

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

@@ -4,7 +4,7 @@
  --component component_spec.md
 
 ## Existing solution:
- `@docs/01_solution/solution_draft.md`
+ `@docs/01_solution/solution.md`
 
 ## Acceptance criteria for the output of the system:
  `@docs/00_problem/acceptance_criteria.md`.