aab-prompts 1.1.6__py3-none-any.whl → 1.1.7__py3-none-any.whl

{aab_prompts-1.1.6.dist-info → aab_prompts-1.1.7.dist-info}/METADATA

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

{aab_prompts-1.1.6.dist-info → aab_prompts-1.1.7.dist-info}/RECORD

@@ -1,4 +1,4 @@
-aab_service.py,sha256=HWzQjc9pTHajiR8LKVMT2FTRxxDVzDF1-qeNZWxrh5g,14175
+aab_service.py,sha256=vh_tzuk45cSLo8ZCw7bvUBfLtatWi2dFjeb6C_3htx0,13660
 prompts/__init__.py,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
 prompts/breadcrumbs.py,sha256=GrcI7w_6VbOG7vo3F5afHMJQKTpClePllEW1OMdHcps,5621
 prompts/constants.py,sha256=3QtDlHG1jr5KRK1kfX5F_1CEtc2QEB0JWl0Cir-bbp4,53274
@@ -7,14 +7,14 @@ prompts/menu_navigations.py,sha256=otB4_pD78Y-2u4zJtBnB4_k9IE1Uf0K1Lq2YgxOe0qk,1
 prompts/objects_fields.py,sha256=a--HwdoXgMdos8Sr6xHOIS_1FMeq_8tHCQacGw3lDRA,35856
 prompts/page_planner.py,sha256=C1DXktj-O2LvJpapHgv1X2AL8zrLY5LtDaRl1fxOwX8,6686
 prompts/pages.py,sha256=5x4bfXHutKK5TqyZkd7zaHlti-8TFKsJNnk2s7cu_NE,7143
-prompts/planner.py,sha256=bIunm-kmsOOWFXGYDZbU_h8MxhhyxLCevlYxL4nwwn4,32520
-prompts/router.py,sha256=IZqoiBmCYabR2iXFoZZdJonF3p-xg3ESP5b3_ibp3Cc,14535
+prompts/planner.py,sha256=GKr-_uNFG4NFYj3-4A8hi0hEolT47mkw00qUipDstYM,32736
+prompts/router.py,sha256=0DAr4FO3_y83olZriGd6LiwS7BWO5zgewOpr7PAZYmI,12048
 prompts/solutions_applications.py,sha256=OPscwiz_6HlT_CFZqnnNBtKDPRekDyd6mesSZf9fhkQ,6130
 prompts/view_filter_planner.py,sha256=DtYZQ7qfFZiXMYosjSGPiPmUu8cSFYAjcAgpCbZf9LA,3466
 prompts/view_links_planner.py,sha256=Bb7UUO15LIDmNjzkFZyzT3eAWCWnzcrm4vvyc8NsJJA,2341
 prompts/view_planner.py,sha256=Og1bOeDqcMIGLAKzYiJAJLgPLaxQ9Wf7nydfFAzivRY,3803
 prompts/views.py,sha256=oQIAiF8KYIbp8q8zBhwrQF4XFauBG7jkiZ9Nh4_eBf8,21638
-aab_prompts-1.1.6.dist-info/METADATA,sha256=tz5kD-JOkC93j3ojcPojINg_krqlcvpbJ4SYt6Wxhtw,712
-aab_prompts-1.1.6.dist-info/WHEEL,sha256=wUyA8OaulRlbfwMtmQsvNngGrxQHAvkKcvRmdizlJi0,92
-aab_prompts-1.1.6.dist-info/top_level.txt,sha256=bvREqxmC7tnWTsG-q-oA5Qzkt1SLk0sK3aD5wlHjhII,20
-aab_prompts-1.1.6.dist-info/RECORD,,
+aab_prompts-1.1.7.dist-info/METADATA,sha256=MHR8pD4taSBPc4XrRAHRP9UeEPhbc5jUTVVV5k1Vc2I,712
+aab_prompts-1.1.7.dist-info/WHEEL,sha256=wUyA8OaulRlbfwMtmQsvNngGrxQHAvkKcvRmdizlJi0,92
+aab_prompts-1.1.7.dist-info/top_level.txt,sha256=bvREqxmC7tnWTsG-q-oA5Qzkt1SLk0sK3aD5wlHjhII,20
+aab_prompts-1.1.7.dist-info/RECORD,,

aab_service.py

@@ -9,22 +9,49 @@ from prompts.expressions import (
     VIEW_FILTER_EXPRESSION_AGENT_PROMPT_TEMPLATE,
     VIEWS_EXPRESSION_AGENT_PROMPT_TEMPLATE,
 )
-from prompts.menu_navigations import MENU_NAVIGATIONS_AGENT_SYSTEM_PROMPT_TEMPLATE
-from prompts.objects_fields import OBJECTS_FIELDS_AGENT_SYSTEM_PROMPT_TEMPLATE, STANDARD_OBJECTS_DESCRIPTIONS_TEMPLATE, SYSTEM_OBJECTS_DESCRIPTIONS_TEMPLATE
+from prompts.menu_navigations import (
+    MENU_NAVIGATIONS_AGENT_SYSTEM_PROMPT_TEMPLATE,
+)
+from prompts.objects_fields import (
+    OBJECTS_FIELDS_AGENT_SYSTEM_PROMPT_TEMPLATE,
+    STANDARD_OBJECTS_DESCRIPTIONS_TEMPLATE,
+    SYSTEM_OBJECTS_DESCRIPTIONS_TEMPLATE,
+)
 from prompts.page_planner import PAGE_PLANNER_AGENT_SYSTEM_PROMPT_TEMPLATE
-from prompts.pages import PAGE_DATA_BINDER_TEMPLATE, PAGES_AGENT_SYSTEM_PROMPT_TEMPLATE
-from prompts.planner import PLANNER_AGENT_SYSTEM_PROMPT_TEMPLATE, PLANNER_EXAMPLES_TEMPLATE
+from prompts.pages import (
+    PAGE_DATA_BINDER_TEMPLATE,
+    PAGES_AGENT_SYSTEM_PROMPT_TEMPLATE,
+)
+from prompts.planner import (
+    PLANNER_AGENT_SYSTEM_PROMPT_TEMPLATE,
+    PLANNER_EXAMPLES_TEMPLATE,
+)
 from prompts.router import ROUTER_AGENT_SYSTEM_PROMPT_TEMPLATE
-from prompts.solutions_applications import SOLUTIONS_APPLICATIONS_AGENT_SYSTEM_PROMPT_TEMPLATE
+from prompts.solutions_applications import (
+    SOLUTIONS_APPLICATIONS_AGENT_SYSTEM_PROMPT_TEMPLATE,
+)
 from prompts.view_filter_planner import VIEW_FILTER_PLANNER_PROMPT_TEMPLATE
 from prompts.view_links_planner import VIEW_LINKS_PLANNER_PROMPT_TEMPLATE
 from prompts.view_planner import VIEWS_PLANNER_AGENT_SYSTEM_PROMPT_TEMPLATE
-from prompts.views import CALENDAR_VIEW_PROPERTIES_TEMPLATE, CARD_VIEW_PROPERTIES_TEMPLATE, COMMON_VIEW_PROPERTIES_TEMPLATE, CREATE_VIEW_PROPERTIES_TEMPLATE, DECK_VIEW_PROPERTIES_TEMPLATE, DETAIL_VIEW_PROPERTIES_TEMPLATE, LIST_VIEW_PROPERTIES_TEMPLATE, MAP_VIEW_PROPERTIES_TEMPLATE, VIEW_FILTERS_PROPERTIES_TEMPLATE, VIEW_LINKS_PROPERTIES_TEMPLATE, VIEW_TYPE_DETAILS_TEMPLATE, VIEWS_AGENT_SYSTEM_PROMPT_TEMPLATE
+from prompts.views import (
+    CALENDAR_VIEW_PROPERTIES_TEMPLATE,
+    CARD_VIEW_PROPERTIES_TEMPLATE,
+    COMMON_VIEW_PROPERTIES_TEMPLATE,
+    CREATE_VIEW_PROPERTIES_TEMPLATE,
+    DECK_VIEW_PROPERTIES_TEMPLATE,
+    DETAIL_VIEW_PROPERTIES_TEMPLATE,
+    LIST_VIEW_PROPERTIES_TEMPLATE,
+    MAP_VIEW_PROPERTIES_TEMPLATE,
+    VIEW_FILTERS_PROPERTIES_TEMPLATE,
+    VIEW_LINKS_PROPERTIES_TEMPLATE,
+    VIEW_TYPE_DETAILS_TEMPLATE,
+    VIEWS_AGENT_SYSTEM_PROMPT_TEMPLATE,
+)
 
 
 class _BreadcrumbsHandler:
     """Handler for all breadcrumb-related prompts."""
-    
+
     @property
     def BREADCRUMB_AGENT_SYSTEM_PROMPT(self) -> str:
         return BREADCRUMB_AGENT_SYSTEM_PROMPT_TEMPLATE
@@ -32,10 +59,10 @@ class _BreadcrumbsHandler:
 
 class _ExpressionsHandler:
     """Handler for all expression-related prompts."""
-    
+
     def __init__(self, core_expressions: dict) -> None:
         self.core_expressions = core_expressions
-    
+
     def _generate_system_prompt(self, expressions: dict) -> str:
         sections: list[str] = []
 
@@ -48,13 +75,16 @@ class _ExpressionsHandler:
 
             example_lines = (
                 "\n".join(
-                    f"- {ex.get('syntax')} → {ex.get('returns')}" for ex in examples
+                    f"- {ex.get('syntax')} → {ex.get('returns')}"
+                    for ex in examples
                 )
                 or "None"
             )
 
             alias_lines = (
-                "\n".join(f"- {alias}" for alias in aliases) if aliases else "None"
+                "\n".join(f"- {alias}" for alias in aliases)
+                if aliases
+                else "None"
             )
 
             sections.append(
@@ -88,29 +118,29 @@ class _ExpressionsHandler:
 
                 {self._generate_system_prompt(self.core_expressions)}
                 """
-    
+
     @property
     def EXPRESSION_REQUIREMENTS(self) -> str:
         return EXPRESSION_REQUIREMENTS_TEMPLATE
-    
+
     @property
     def EXPRESSIONS_AGENT_PROMPT(self) -> str:
         return EXPRESSIONS_AGENT_PROMPT_TEMPLATE.format(
             EXPRESSION_REQUIREMENTS=self.EXPRESSION_REQUIREMENTS,
             CORE_EXPRESSIONS=self.CORE_EXPRESSIONS,
         )
-    
+
     @property
     def SHOW_IF_EXPRESSION_AGENT_PROMPT(self) -> str:
         return SHOW_IF_EXPRESSION_AGENT_PROMPT_TEMPLATE.format(
             EXPRESSION_REQUIREMENTS=self.EXPRESSION_REQUIREMENTS,
             CORE_EXPRESSIONS=self.CORE_EXPRESSIONS,
         )
-    
+
     @property
     def INITIAL_VALUE_EXAMPLES(self) -> str:
         return INITIAL_VALUE_EXAMPLES_TEMPLATE
-    
+
     @property
     def VIEW_FILTER_EXPRESSION_AGENT_PROMPT(self) -> str:
         return VIEW_FILTER_EXPRESSION_AGENT_PROMPT_TEMPLATE.format(
@@ -124,14 +154,14 @@ class _ExpressionsHandler:
             EXPRESSION_REQUIREMENTS=self.EXPRESSION_REQUIREMENTS,
             CORE_EXPRESSIONS=self.CORE_EXPRESSIONS,
         )
-    
+
     @property
     def VIEWS_EXPRESSION_AGENT_PROMPT(self) -> str:
         return VIEWS_EXPRESSION_AGENT_PROMPT_TEMPLATE.format(
             EXPRESSION_REQUIREMENTS=self.EXPRESSION_REQUIREMENTS,
             CORE_EXPRESSIONS=self.CORE_EXPRESSIONS,
         )
-    
+
     @property
     def PAGE_DATA_BINDER_AGENT_PROMPT(self) -> str:
         return PAGE_DATA_BINDER_AGENT_PROMPT_TEMPLATE.format(
@@ -139,9 +169,10 @@ class _ExpressionsHandler:
             CORE_EXPRESSIONS=self.CORE_EXPRESSIONS,
         )
 
+
 class _MenuNavigationsHandler:
     """Handler for all menu navigation-related prompts."""
-    
+
     @property
     def MENU_NAVIGATIONS_AGENT_SYSTEM_PROMPT(self) -> str:
         return MENU_NAVIGATIONS_AGENT_SYSTEM_PROMPT_TEMPLATE
@@ -149,14 +180,14 @@ class _MenuNavigationsHandler:
 
 class _ObjectsFieldsHandler:
     """Handler for all object and field-related prompts."""
-    
+
     def __init__(self, restricted_objects_list: list[str]) -> None:
         self.restricted_objects_list = restricted_objects_list
-    
+
     @property
     def STANDARD_OBJECTS_DESCRIPTIONS(self) -> str:
         return STANDARD_OBJECTS_DESCRIPTIONS_TEMPLATE
-    
+
     @property
     def SYSTEM_OBJECTS_DESCRIPTIONS(self) -> str:
         return SYSTEM_OBJECTS_DESCRIPTIONS_TEMPLATE
@@ -170,7 +201,7 @@ class _ObjectsFieldsHandler:
 
 class _PagePlannerHandler:
     """Handler for all page planner-related prompts."""
-    
+
     @property
     def PAGE_PLANNER_AGENT_SYSTEM_PROMPT(self) -> str:
         return PAGE_PLANNER_AGENT_SYSTEM_PROMPT_TEMPLATE
@@ -178,11 +209,11 @@ class _PagePlannerHandler:
 
 class _PagesHandler:
     """Handler for all page-related prompts."""
-    
+
     @property
     def PAGES_AGENT_SYSTEM_PROMPT(self) -> str:
         return PAGES_AGENT_SYSTEM_PROMPT_TEMPLATE
-    
+
     @property
     def PAGE_DATA_BINDER(self) -> str:
         return PAGE_DATA_BINDER_TEMPLATE
@@ -190,17 +221,23 @@ class _PagesHandler:
 
 class _PlannerHandler:
     """Handler for all planner-related prompts."""
-    
-    def __init__(self, restricted_objects_list: list[str], standard_objects_descriptions: str, system_objects_descriptions: str, view_type_details_template: str) -> None:
+
+    def __init__(
+        self,
+        restricted_objects_list: list[str],
+        standard_objects_descriptions: str,
+        system_objects_descriptions: str,
+        view_type_details_template: str,
+    ) -> None:
         self.restricted_objects_list = restricted_objects_list
         self.standard_objects_descriptions = standard_objects_descriptions
         self.system_objects_descriptions = system_objects_descriptions
         self.view_type_details_template = view_type_details_template
-    
+
     @property
     def PLANNER_EXAMPLES(self) -> str:
-        return '\n\n\n'.join(PLANNER_EXAMPLES_TEMPLATE)
-    
+        return "\n\n\n".join(PLANNER_EXAMPLES_TEMPLATE)
+
     @property
     def PLANNER_AGENT_SYSTEM_PROMPT(self) -> str:
         return PLANNER_AGENT_SYSTEM_PROMPT_TEMPLATE.format(
@@ -214,28 +251,24 @@ class _PlannerHandler:
 
 class _RouterHandler:
     """Handler for all router-related prompts."""
-    
-    def __init__(self, standard_objects_descriptions: str, system_objects_descriptions: str, planner_examples: list[str]) -> None:
-        self.standard_objects_descriptions = standard_objects_descriptions
-        self.system_objects_descriptions = system_objects_descriptions
-        self.planner_examples = planner_examples
-    
+
+    def __init__(self) -> None:
+        pass
+
     @property
     def ROUTER_AGENT_SYSTEM_PROMPT(self) -> str:
-        return ROUTER_AGENT_SYSTEM_PROMPT_TEMPLATE.format(
-            STANDARD_OBJECTS_DESCRIPTIONS=self.standard_objects_descriptions,
-            SYSTEM_OBJECTS_DESCRIPTIONS=self.system_objects_descriptions,
-            PLANNER_EXAMPLES=self.planner_examples,
-        )
+        return ROUTER_AGENT_SYSTEM_PROMPT_TEMPLATE
 
 
 class _SolutionsApplicationsHandler:
     """Handler for all solutions and applications-related prompts."""
-    
-    def __init__(self, default_solution_id: str, default_application_id: str) -> None:
+
+    def __init__(
+        self, default_solution_id: str, default_application_id: str
+    ) -> None:
         self.default_solution_id = default_solution_id
         self.default_application_id = default_application_id
-    
+
     @property
     def SOLUTIONS_APPLICATIONS_AGENT_SYSTEM_PROMPT(self) -> str:
         return SOLUTIONS_APPLICATIONS_AGENT_SYSTEM_PROMPT_TEMPLATE.format(
@@ -250,15 +283,15 @@ class _ViewsHandler:
     @property
     def VIEW_TYPE_DETAILS(self) -> str:
         return VIEW_TYPE_DETAILS_TEMPLATE
-    
+
     @property
     def COMMON_VIEW_PROPERTIES(self) -> str:
         return COMMON_VIEW_PROPERTIES_TEMPLATE
-    
+
     @property
     def LIST_VIEW_PROPERTIES(self) -> str:
         return LIST_VIEW_PROPERTIES_TEMPLATE
-    
+
     @property
     def CARD_VIEW_PROPERTIES(self) -> str:
         return CARD_VIEW_PROPERTIES_TEMPLATE
@@ -274,11 +307,11 @@ class _ViewsHandler:
     @property
     def MAP_VIEW_PROPERTIES(self) -> str:
         return MAP_VIEW_PROPERTIES_TEMPLATE
-    
+
     @property
     def CALENDAR_VIEW_PROPERTIES(self) -> str:
         return CALENDAR_VIEW_PROPERTIES_TEMPLATE
-    
+
     @property
     def DECK_VIEW_PROPERTIES(self) -> str:
         return DECK_VIEW_PROPERTIES_TEMPLATE
@@ -326,7 +359,6 @@ class _ViewsHandler:
         return VIEW_LINKS_PLANNER_PROMPT_TEMPLATE.format(
             VIEW_LINKS_PROPERTIES=self.VIEW_LINKS_PROPERTIES,
         )
-    
 
     @property
     def VIEW_FILTER_PLANNER_PROMPT(self) -> str:
@@ -335,11 +367,16 @@ class _ViewsHandler:
         )
 
 
-
 class AABPrompts:
     """Main prompts class that coordinates all prompt handlers."""
-    
-    def __init__(self, core_expressions: dict, restricted_objects_list: list[str], default_solution_id: str, default_application_id: str) -> None:
+
+    def __init__(
+        self,
+        core_expressions: dict,
+        restricted_objects_list: list[str],
+        default_solution_id: str,
+        default_application_id: str,
+    ) -> None:
         # Initialize handlers
         self._objects_fields = _ObjectsFieldsHandler(restricted_objects_list)
         self._views = _ViewsHandler()
@@ -347,9 +384,9 @@ class AABPrompts:
             restricted_objects_list,
             self._objects_fields.STANDARD_OBJECTS_DESCRIPTIONS,
             self._objects_fields.SYSTEM_OBJECTS_DESCRIPTIONS,
-            self._views.VIEW_TYPE_DETAILS
+            self._views.VIEW_TYPE_DETAILS,
         )
-        
+
         # Store all handlers in a list for easy iteration
         self._handlers = [
             _BreadcrumbsHandler(),
@@ -359,22 +396,18 @@ class AABPrompts:
             _PagePlannerHandler(),
             _PagesHandler(),
             self._planner,
-            _RouterHandler(
-                self._objects_fields.STANDARD_OBJECTS_DESCRIPTIONS,
-                self._objects_fields.SYSTEM_OBJECTS_DESCRIPTIONS,
-                self._planner.PLANNER_EXAMPLES,
+            _RouterHandler(),
+            _SolutionsApplicationsHandler(
+                default_solution_id, default_application_id
             ),
-            _SolutionsApplicationsHandler(default_solution_id, default_application_id),
             self._views,
         ]
-    
+
     def __getattr__(self, name: str):
         """Automatically delegate method calls to the appropriate handler."""
         for handler in self._handlers:
             if hasattr(handler, name):
                 return getattr(handler, name)
-        raise AttributeError(f"'{self.__class__.__name__}' object has no attribute '{name}'")
-
-
-
-    
+        raise AttributeError(
+            f"'{self.__class__.__name__}' object has no attribute '{name}'"
+        )

prompts/planner.py

@@ -556,8 +556,11 @@ Your only output should be the plan as plain text following the examples.
 ---
 
 <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.
+    - Call the `generate_comprehensive_plan` tool to generate a comprehensive plan. ALWAYS CALL THIS TOOL FIRST.
+    - Make sure each component of the plan is very detailed, with all the proper details and context.
+    - Each of them should say the name of the component, data type, and the details of the component.
+
+    - Always retuen the exact plan back to the user. Do not add or remove any characters or spaces. This is very important.
 </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.

prompts/router.py

@@ -157,30 +157,12 @@ All SnapApp construction must always follow this strict sequence:
 2. Objects  
    - Create all data entities first; everything else depends on them.
 
-   The following are key elements that should be considered when planning an object:
-   - track_activities: Whether the object includes activity tracking. This creates logs of all activities on the data stored in the object. This includes activites like emails/SMS notifications, tasks, and PubSub topics. Should be 1 or 0.
-   - track_notes: Whether the object allows for notes and comments from the application's users. This creates a notes section for the object. Should be 1 or 0.
-   - track_attachments: Whether the object allows for attachments on the data stored in the object like Files, Images, Videos, etc. Should be 1 or 0. This is typically used when there is a non-standard list of attachments that will be added to the record. Alternatively, a field of type `File` or `Image` can be used to store a single file or image attachment when the use case is for a specific file.
-   - track_favorites: Whether the object allows users to favorite items of the object. Should be 1 or 0.
-   - track_tags: Whether the object allows users to tag items of the object. Should be 1 or 0. 
-   - track_audit_trails: Whether field-level changes to records of this object will be included in audit trails. Should be 1 or 0.
-   - enable_feed: Whether the object is enabled for feed. This creates a user facing chat feed for everyone to comment and interact for the records of the object. Should be 1 or 0.
-   - feed_tracking: Whether all changes in the record be logged in the feed. Works like track activities. Should be 1 or 0.
-
 3. Fields  
    - Add fields only after objects exist.
    - Define business logic for automatically calculated fields (formulas)
    - Define business logic for visibility, validity, requirements, and read-only (show_if, valid_if, required_if, editable_if)
 
    When planning objects and fields, always consider necessary business logic and formulaic automations as these are best handled at the time of field creation, which is accomplished by another domain-expert agent. 
-
-   The following are key details to consider when creating a field. When making your plan, these kind of requirements should be implemented within the object and fields section. They should not be a separate portion of the plan.:
-   - formula: The formula to calculate the value of the field. Max 1024 characters. Optional. This is an expression that is applied to the field when a new record is updated. If the same expression is set for the formula and initial_values fields, the field will always be set to this and can not be changed by the user.  Always use available tools to build expressions and set it here.
-   - initial_value: Define the initial value of the field. Max 1024 characters. This is an expression that is applied to the field when a new record is created. If the same expression is set for the formula and initial_values fields, the field will always be set to this and can not be changed by the user. Always use available tools to build expressions and set it here.
-   - show_if: The show if condition for the field. This is an expression that defines when the field should be shown to the user. If the expression evaluates to true, the field is shown. If it evaluates to false, the field is hidden. ALways use available tools to build expressions and set it here.
-   - valid_if: The valid if condition for the field. This is an expression that defines when the field value is valid. If the expression evaluates to true, the field value is valid. If it evaluates to false, the field value is invalid. Always use available tools to build expressions and set it here.
-   - required_if: The required if condition for the field. This is an expression that defines when the field is required. If the expression evaluates to true, the field is required. If it evaluates to false, the field is not required. Always use available tools to build expressions and set it here.
-   - editable_if: The editable if condition for the field. This is an expression that defines when the field is editable. If the expression evaluates to true, the field is editable. If it evaluates to false, the field is read-only. Always use available tools to build expressions and set it here. 
    
 4. Relationships  
    - Define relationships after both participating objects and fields exist.
@@ -208,32 +190,9 @@ Snappy must always generate Todos in this exact dependency-safe order. If you ha
     3. Correct Example: task(subagent="objects", description="Find the table named conversations and list its columns")
     4. Incorrect Example: task(subagent="objects", description="get_object(name='conversations')")
 
-### IMPORTANT RULES FOR CREATING OBJECTS:
-
-SnapApp is deployed with many standard and system objects that you must be aware of before creating new objects. The user may request objects that have the same name as a standard or system object. In these cases, you must create a custom object with a different name that reflects the user's intent while avoiding conflicts.
-
-#### **Standard Objects**
-
-You should keep the following standard objects in mind when planning so that you can leverage them where appropriate, and so that you can avoid creating new objects with conflicting names. You should NEVER create an object with the same name as a standard object. If the user's application requires an object of the same name, you should create a unique app-specific name.
-
-You can use the `get_object` tool to retrieve the fields and relationships of a standard object. For example `get_object('contacts')` will return the fields and relationships of the Contacts standard object. You should always check the fields before referencing them in your plan or creating new fields that conflict with them.:
-
-{STANDARD_OBJECTS_DESCRIPTIONS}
-
-#### **System Objects**
-
-The following are system objects. You should NEVER create new objects with these names. If the user's application requires an object of the same name, you should create a unique app-specific name. (e.g., Applications is a system object, so any app that tracks applications will need a custom name like "Grant Applications"). You should not modify these objects (such as by adding fields to them):
-
-{SYSTEM_OBJECTS_DESCRIPTIONS}
-
 ### Planning a Solution Build
 
-The planning of a solution should following the examples below:
-
-{PLANNER_EXAMPLES}
-
-
-ALWAYS PROVIDE ALL ANSWERS IN MARKDOWN FORMAT.
+The planning of a solution should always call the planner subagent to generate a detailed plan. Always remember to return the very detailed and ellaborate plan to the user.
 
 # ABSOLUTELY PROHIBITED ACTIONS, WHICH ARE MANDATORY AND NON NEGOTIABLE
 NEVER CALL THESE FOLLOWING TOOLS:
@@ -244,4 +203,37 @@ NEVER CALL THESE FOLLOWING TOOLS:
 - `write_file`
 - `edit_file`
 
+
+<VERY_IMPORTANT_AND_NON_NEGOTIABLE_INSTRUCTIONS>
+    - YOU MUST NOT MAKE A PLAN OF YOUR OWN.
+        You must always use the `generate_comprehensive_plan` tool to get the plan created by the `planner` subagent,
+        and then execute that plan by following the lifecycle of a plan phase execution mentioned below.
+    - You MUST NOT continue without having a plan. The generated plan should be fetched by using `get_plan` tool.         
+
+    - Once you have the plan, you will start working in different plan phases. The plan phases are:
+        - `solutions_and_applications`
+        - `objects_and_fields`
+        - `views`
+        - `menus_and_navigations`
+        - `pages`
+        - `breadcrumbs`
+
+    - Lifecycle of a plan phase execution (YOU MUST FOLLOW THIS ORDER):
+        1. Call the `get_plan` tool to get the plan, this makes sure you don't miss any details and you have a clear understanding of the tasks to be executed in that phase.
+        2. Execute the tasks of that phase by delegating to the appropriate subagent using the `task` tool.
+        3. After executing the tasks of that phase, use the `ensure_progress` tool to ensure that the plan is being followed throughly.
+        4. After executing the tasks of that phase, use the `ensure_cleanup` tool to ensure that any invalid, duplicate, or inconsistent data resources are identified and marked for cleanup.
+        5. Rinse and repeat for the next plan phase until all phases are complete.
+</VERY_IMPORTANT_AND_NON_NEGOTIABLE_INSTRUCTIONS>
+
+
+<PLAN_PHASES_YOU_MUST_FOLLOW>
+The plan phases are:
+    1. `solutions_and_applications`: In this phase, you will create the solution and application containers based on the user requirements. This is the foundational step for organizing a SnapApp application.
+    2. `objects_and_fields`: In this phase, you will create the data model by defining objects (tables) and their fields (columns). This is a critical step as everything else depends on the data model.
+    3. `views`: In this phase, you will create the views (list/detail/form/create) based on the objects and fields defined in the previous phase. Views are essential for users to interact with the data.
+    4. `menus_and_navigations`: In this phase, you will set up the navigation structure, including menus and navigation paths, to ensure users can easily access different parts of the application.
+    5. `pages`: In this phase, you will create custom pages if required by the user. Pages are used for building custom UIs and dashboards.
+    6. `breadcrumbs`: In this phase, you will set up breadcrumbs for better navigation and user experience, allowing users to understand their location within the application and easily navigate back to previous pages.
+</PLAN_PHASES_YOU_MUST_FOLLOW>
 """