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

{aab_prompts-1.1.4 → aab_prompts-1.1.6}/PKG-INFO

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

{aab_prompts-1.1.4 → aab_prompts-1.1.6}/aab_prompts.egg-info/PKG-INFO

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

{aab_prompts-1.1.4 → aab_prompts-1.1.6}/prompts/menu_navigations.py

@@ -33,13 +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"
+- Always add a Menu if it is defined in the 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.
 
@@ -93,7 +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"
+- Always add a navigation if it is defined in the plan"
 - When adding links to objects:  
   e.g., “All Orders”, “Create Task”, “My Clients”.
 - When linking pages or dashboards.
@@ -102,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.4 → aab_prompts-1.1.6}/prompts/objects_fields.py

@@ -163,7 +163,7 @@ that you CAN'T use, which are listed below:
 
 ---
 # Required Output
-You must have an object for every object defined in the plan generated in `save_generated_plan`
+You must have an object for every object defined in the plan
 You must always have the Objects in this specific schema. Each Object must follow this exact structure.
 For each key, read and follow its meaning and usage rules:
 
@@ -209,7 +209,7 @@ Key points
 # When to Create a Field
 Create a Field when:
 - The user mentions a real property that must be saved with the object
-- The field is defined in the plan generated in `save_generated_plan`
+- The field is defined in the plan
 
 Do NOT create an Field when:
 - Something is already another field on this object

{aab_prompts-1.1.4 → aab_prompts-1.1.6}/prompts/pages.py

@@ -42,7 +42,7 @@ 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"
+Always add a Page if it is defined in the 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

{aab_prompts-1.1.4 → aab_prompts-1.1.6}/prompts/planner.py

@@ -486,7 +486,9 @@ The following are key details to consider when creating a field. When making you
 - Must incorporate conditional fields, validation logic, and process stage requirements, which are all configured at the field level
 - Can be multi-record or single-record
 - Business logic for filtering multi-record views  
-- Apply {VIEW_TYPE_DETAILS_TEMPLATE} logic to determine the view type
+- When designing a detailed plan for views, you should remember the different view types and their properties.
+{VIEW_TYPE_DETAILS_TEMPLATE}
+
 
 ### **8. Pages**
 - Can be associated with an object
@@ -552,8 +554,11 @@ NOTE: Your behavior must follow the examples provided below.
 Your only output should be the plan as plain text following the examples.
 
 ---
-NEXT STEPS:
-    - Call the `generate_comprehensive_plan` tool to generate a comprehensive plan.
-    - Call the `save_generated_plan` tool to save the generated plan.
 
+<IMPORTANT STEPS [ MANDATORY AND NON-NEGOTIABLE ]>
+    Call the `generate_comprehensive_plan` tool to generate a comprehensive plan. ALWAYS CALL THIS TOOL FIRST.
+    Make sure everything that you plan, each component, is very detailed, with all the proper details and context.
+</IMPORTANT STEPS [ MANDATORY AND NON-NEGOTIABLE ]>
+
+You will always use these tools in the order specified above. If you miss any of these steps, you will be penalized.
 """

{aab_prompts-1.1.4 → aab_prompts-1.1.6}/prompts/solutions_applications.py

@@ -36,7 +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"
+Always add a Solution if it is defined in the plan
 Create a Solution when:
 - The user explicitly asks for one.
 - The use-case clearly belongs to a new vertical/industry/domain.
@@ -79,7 +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"
+Always add an Application if it is defined in the 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.4 → aab_prompts-1.1.6}/prompts/views.py

@@ -156,13 +156,14 @@ Views do not define fields.
 They only define how fields appear.
 
 # When to Create a View
-Always add a View if it is defined in the plan generated in save_generated_plan"
+Always add a View if it is defined in the 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: 
-- it is satisfied with a custom page
+- the view already exists. do not duplicate views.
+- it can be satisfied with a custom page
 
 
 ## View Types

{aab_prompts-1.1.4 → aab_prompts-1.1.6}/pyproject.toml

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