feat: add prompts for generating Mermaid diagrams for Flutter application architecture and use cases
This commit is contained in:
21
docs/prompts/create-mermaid-overview-flutter.md
Normal file
21
docs/prompts/create-mermaid-overview-flutter.md
Normal file
@@ -0,0 +1,21 @@
|
||||
## What the prompt does
|
||||
This prompt generates a Mermaid diagram that provides an overview of the given Flutter application's architecture. It includes the main components of the app, such as the widget tree, state management, and navigation.
|
||||
|
||||
## Assumptions
|
||||
- Flutter project is given.
|
||||
|
||||
## Prompt
|
||||
In the given Flutter project. Carefully analyze all files to understand the app’s navigation, logic flow, state management, and how each screen connects to the next.
|
||||
|
||||
Using that analysis, generate a **Mermaid flowchart** that shows:
|
||||
|
||||
* The app’s entry point (main.dart → root widget).
|
||||
* The initial flow (e.g., splash → login/signup → authenticated home).
|
||||
* All pages/screens and how navigation occurs between them.
|
||||
* Conditional routing logic (authentication checks, API responses, state changes, etc.).
|
||||
* Any loops, flows, or background logic that impact navigation.
|
||||
* The diagram must accurately reflect the project structure and not make assumptions beyond what is found in the code.
|
||||
|
||||
Use **Mermaid `flowchart TD` or `flowchart LR`** format, with clear labels for each screen and logic decision.
|
||||
|
||||
If needed, ask me for missing files so you can produce a complete diagram.
|
||||
Reference in New Issue
Block a user