aab-prompts 1.1.3__tar.gz → 1.1.4__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (24) hide show
  1. {aab_prompts-1.1.3 → aab_prompts-1.1.4}/PKG-INFO +1 -1
  2. {aab_prompts-1.1.3 → aab_prompts-1.1.4}/aab_prompts.egg-info/PKG-INFO +1 -1
  3. {aab_prompts-1.1.3 → aab_prompts-1.1.4}/prompts/menu_navigations.py +2 -0
  4. {aab_prompts-1.1.3 → aab_prompts-1.1.4}/prompts/pages.py +8 -1
  5. {aab_prompts-1.1.3 → aab_prompts-1.1.4}/prompts/solutions_applications.py +2 -0
  6. {aab_prompts-1.1.3 → aab_prompts-1.1.4}/prompts/views.py +11 -2
  7. {aab_prompts-1.1.3 → aab_prompts-1.1.4}/pyproject.toml +1 -1
  8. {aab_prompts-1.1.3 → aab_prompts-1.1.4}/aab_prompts.egg-info/SOURCES.txt +0 -0
  9. {aab_prompts-1.1.3 → aab_prompts-1.1.4}/aab_prompts.egg-info/dependency_links.txt +0 -0
  10. {aab_prompts-1.1.3 → aab_prompts-1.1.4}/aab_prompts.egg-info/top_level.txt +0 -0
  11. {aab_prompts-1.1.3 → aab_prompts-1.1.4}/aab_service.py +0 -0
  12. {aab_prompts-1.1.3 → aab_prompts-1.1.4}/prompts/__init__.py +0 -0
  13. {aab_prompts-1.1.3 → aab_prompts-1.1.4}/prompts/breadcrumbs.py +0 -0
  14. {aab_prompts-1.1.3 → aab_prompts-1.1.4}/prompts/constants.py +0 -0
  15. {aab_prompts-1.1.3 → aab_prompts-1.1.4}/prompts/expressions.py +0 -0
  16. {aab_prompts-1.1.3 → aab_prompts-1.1.4}/prompts/objects_fields.py +0 -0
  17. {aab_prompts-1.1.3 → aab_prompts-1.1.4}/prompts/page_planner.py +0 -0
  18. {aab_prompts-1.1.3 → aab_prompts-1.1.4}/prompts/planner.py +0 -0
  19. {aab_prompts-1.1.3 → aab_prompts-1.1.4}/prompts/router.py +0 -0
  20. {aab_prompts-1.1.3 → aab_prompts-1.1.4}/prompts/view_filter_planner.py +0 -0
  21. {aab_prompts-1.1.3 → aab_prompts-1.1.4}/prompts/view_links_planner.py +0 -0
  22. {aab_prompts-1.1.3 → aab_prompts-1.1.4}/prompts/view_planner.py +0 -0
  23. {aab_prompts-1.1.3 → aab_prompts-1.1.4}/setup.cfg +0 -0
  24. {aab_prompts-1.1.3 → aab_prompts-1.1.4}/tests/test_prompts.py +0 -0
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: aab-prompts
3
- Version: 1.1.3
3
+ Version: 1.1.4
4
4
  Summary: AAB Prompts - Application Builder prompt management library
5
5
  Author: AAB Prompts
6
6
  License: MIT
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: aab-prompts
3
- Version: 1.1.3
3
+ Version: 1.1.4
4
4
  Summary: AAB Prompts - Application Builder prompt management library
5
5
  Author: AAB Prompts
6
6
  License: MIT
@@ -33,6 +33,7 @@ SnapApp has 4 menu types (locations):
33
33
  Within an application, there can only be one menu for each type.
34
34
 
35
35
  When to create a menu:
36
+ - Always add a Menu if it is defined in the plan generated in save_generated_plan"
36
37
  - When user intent indicates a new navigation area is needed.
37
38
  - When an app section needs a dedicated placement (e.g., a new sidebar layout).
38
39
  - When organizing large features requires isolated navigation groups.
@@ -92,6 +93,7 @@ Footer menus only require the common metadata attributes.
92
93
  - **Translations Switcher (`efdef1fa-fc39-4210-a800-04de50a4e3e5`)**: The Translations Switcher lets users switch between different languages within the application. This is typically in the default top menu, but when a custom top menu is created, it will be added to the custom top menu.
93
94
 
94
95
  When navigations are used:
96
+ - Always add a navigation if it is defined in the plan generated in save_generated_plan"
95
97
  - When adding links to objects:
96
98
  e.g., “All Orders”, “Create Task”, “My Clients”.
97
99
  - When linking pages or dashboards.
@@ -41,6 +41,13 @@ You are a specialized HTML Page Planner and Creator Agent for **Snapapp**, a Low
41
41
 
42
42
  ## ⚡ Dynamic Data & Object Association
43
43
 
44
+ ### When to Create a page
45
+ Always add a Page if it is defined in the plan generated in save_generated_plan"
46
+ Create a page for home pages
47
+ Create a page when you need to view more than one type of object at the same time
48
+ Create a page when you want to summarize data from records in the view
49
+ Replace a detail view with a page when it needs a custom layout
50
+
44
51
  ### When to Associate an Object
45
52
  Associate a page with an Object only when you need to display details or perform actions related to a **specific record** (e.g., a "Student Profile" page). Do not associate for generic "Home" or "Dashboard" pages.
46
53
 
@@ -199,4 +206,4 @@ Return ONLY the updated HTML and CSS.
199
206
  - No markdown.
200
207
  - No JSON.
201
208
 
202
- """
209
+ """
@@ -36,6 +36,7 @@ You can create new solutions as per the users' requirements.
36
36
 
37
37
 
38
38
  # When to Create a Solution
39
+ Always add a Solution if it is defined in the plan generated in save_generated_plan"
39
40
  Create a Solution when:
40
41
  - The user explicitly asks for one.
41
42
  - The use-case clearly belongs to a new vertical/industry/domain.
@@ -78,6 +79,7 @@ Given a solution, there can be multiple applications within it.
78
79
  ---
79
80
 
80
81
  # When to Create an Application
82
+ Always add an Application if it is defined in the plan generated in save_generated_plan"
81
83
  Create an Application when:
82
84
  - The user explicitly asks for one.
83
85
  - The user’s use-case requires a separate product experience.
@@ -155,9 +155,18 @@ Views do not store data.
155
155
  Views do not define fields.
156
156
  They only define how fields appear.
157
157
 
158
- ## View Types
158
+ # When to Create a View
159
+ Always add a View if it is defined in the plan generated in save_generated_plan"
160
+ Create a View when:
161
+ - The user explicitly asks for one.
162
+ - You want a unique set of fields, filter conditions, field show logic (SHOWIF), field edit logic (EDITIF), field validity logic (VALIDIF) for a particular role or function.
163
+
164
+ Do NOT create a View when:
165
+ - it is satisfied with a custom page
159
166
 
160
- {VIEW_TYPE_DETAILS}
167
+
168
+ ## View Types
169
+ {VIEW_TYPE_DETAILS} provides the defintion for each view type and when to use them.
161
170
 
162
171
 
163
172
  STEP BY STEP INSTRUCTION FOR HOW TO USE THE TOOLS IN ORDER TO CREATE SATISFATORY VIEWS:
@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
4
4
 
5
5
  [project]
6
6
  name = "aab-prompts"
7
- version = "1.1.3"
7
+ version = "1.1.4"
8
8
  description = "AAB Prompts - Application Builder prompt management library"
9
9
  requires-python = ">=3.8"
10
10
  license = {text = "MIT"}
File without changes
File without changes