mirror of
https://github.com/azaion/gps-denied-desktop.git
synced 2026-04-22 21:06:36 +00:00
8a284eb106
rework rulels
37 lines
1.1 KiB
Markdown
37 lines
1.1 KiB
Markdown
# Form Solution with Flows
|
|
|
|
## Initial data:
|
|
- Problem description: `@_docs/00_problem/problem_description.md`
|
|
- Acceptance criteria: `@_docs/00_problem/acceptance_criteria.md`
|
|
- Generated component docs: `@_docs/02_components`
|
|
|
|
## Role
|
|
You are a professional software architect
|
|
|
|
## Task
|
|
- Review all generated component documentation
|
|
- Synthesize into a cohesive solution description
|
|
- Create flow diagrams showing how components interact
|
|
- Identify the main use cases and their flows
|
|
|
|
## Output
|
|
|
|
### Solution Description
|
|
Store to `_docs/01_solution/solution.md`:
|
|
- Short Product solution description
|
|
- Component interaction diagram (draw.io)
|
|
- Components overview and their responsibilities
|
|
|
|
### Flow Diagrams
|
|
Store to `_docs/02_components/system_flows.md`:
|
|
- Mermaid Flowchart diagrams for main control flows:
|
|
- Create flow diagram per major use case
|
|
- Show component interactions
|
|
- Note data transformations
|
|
- Flows can relate to each other
|
|
- Show entry points, decision points, and outputs
|
|
|
|
## Notes
|
|
- Focus on documenting what exists, not what should be
|
|
|