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

{aab_prompts-1.1.3 → aab_prompts-1.1.5}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: aab-prompts
-Version: 1.1.3
+Version: 1.1.5
 Summary: AAB Prompts - Application Builder prompt management library
 Author: AAB Prompts
 License: MIT

{aab_prompts-1.1.3 → aab_prompts-1.1.5}/aab_prompts.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: aab-prompts
-Version: 1.1.3
+Version: 1.1.5
 Summary: AAB Prompts - Application Builder prompt management library
 Author: AAB Prompts
 License: MIT

{aab_prompts-1.1.3 → aab_prompts-1.1.5}/prompts/menu_navigations.py

@@ -33,12 +33,14 @@ SnapApp has 4 menu types (locations):
 Within an application, there can only be one menu for each type.
 
 When to create a menu:
+- Always add a Menu if it is defined in the plan generated in save_generated_plan"
 - When user intent indicates a new navigation area is needed.
 - When an app section needs a dedicated placement (e.g., a new sidebar layout).
 - When organizing large features requires isolated navigation groups.
 
 When NOT to create a menu:
-- If a menu for that location already exists.
+- If the same menu already exists
+- If a menu for the same location and the same application already exists.
 - For workflow steps or temporary flows (those belong inside views).
 - For pages that do not need a dedicated navigation region.
 
@@ -92,6 +94,7 @@ Footer menus only require the common metadata attributes.
 - **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.
 
 When navigations are used:
+- Always add a navigation if it is defined in the plan generated in save_generated_plan"
 - When adding links to objects:  
   e.g., “All Orders”, “Create Task”, “My Clients”.
 - When linking pages or dashboards.
@@ -100,6 +103,7 @@ When navigations are used:
   - CRM → Leads, Deals, Contacts
 
 When NOT to use navigations:
+- if the same navigation already exists.
 - For form steps or workflow states.
 - For view configuration logic (handled by the View Agent).
 - For system-level features hidden from user navigation.

{aab_prompts-1.1.3 → aab_prompts-1.1.5}/prompts/pages.py

@@ -41,6 +41,13 @@ You are a specialized HTML Page Planner and Creator Agent for **Snapapp**, a Low
 
 ## ⚡ Dynamic Data & Object Association
 
+### When to Create a page
+Always add a Page if it is defined in the plan generated in save_generated_plan"
+Create a page for home pages
+Create a page when you need to view more than one type of object at the same time
+Create a page when you want to summarize data from records in the view
+Replace a detail view with a page when it needs a custom layout
+
 ### When to Associate an Object
 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.
 
@@ -199,4 +206,4 @@ Return ONLY the updated HTML and CSS.
 - No markdown.
 - No JSON.
 
-"""
+"""

{aab_prompts-1.1.3 → aab_prompts-1.1.5}/prompts/solutions_applications.py

@@ -36,6 +36,7 @@ You can create new solutions as per the users' requirements.
 
 
 # When to Create a Solution
+Always add a Solution if it is defined in the plan generated in save_generated_plan"
 Create a Solution when:
 - The user explicitly asks for one.
 - 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.
 ---
 
 # When to Create an Application
+Always add an Application if it is defined in the plan generated in save_generated_plan"
 Create an Application when:
 - The user explicitly asks for one.
 - The user’s use-case requires a separate product experience.

{aab_prompts-1.1.3 → aab_prompts-1.1.5}/prompts/views.py

@@ -155,9 +155,19 @@ Views do not store data.
 Views do not define fields.  
 They only define how fields appear.
 
-## View Types
+# When to Create a View
+Always add a View if it is defined in the plan generated in save_generated_plan"
+Create a View when:
+- The user explicitly asks for one.
+- 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. 
+
+Do NOT create a View when: 
+- the view already exists. do not duplicate views.
+- it can be satisfied with a custom page
 
-{VIEW_TYPE_DETAILS}
+
+## View Types
+{VIEW_TYPE_DETAILS} provides the defintion for each view type and when to use them.
 
 
 STEP BY STEP INSTRUCTION FOR HOW TO USE THE TOOLS IN ORDER TO CREATE SATISFATORY VIEWS:

{aab_prompts-1.1.3 → aab_prompts-1.1.5}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "aab-prompts"
-version = "1.1.3"
+version = "1.1.5"
 description = "AAB Prompts - Application Builder prompt management library"
 requires-python = ">=3.8"
 license = {text = "MIT"}