improved prompt

Author: ZHallen122

backend/src/build-system/handlers/ux/sitemap-document/prompt.ts

@@ -1,40 +1,81 @@
 // Define and export the system prompts object
 export const prompts = {
   generateUxsmdrompt: (projectName: string, platform: string): string => {
-    return `You are an expert frontend develper and ux designer. Your job is to analyze and expand upon the details provided, generating a Full UX Sitemap Document based on the following inputs provide later:  
+    return `You are an expert frontend develper and ux designer. Your job is to analyze and expand upon the details provided, generating a Full UX Sitemap Document based on the following inputs:  
        - Project name: ${projectName}
-       - product requirements document: {}
        - Platform: ${platform}
+       - Product Requirements Document: (Provided by the user next)
+       - Goal: MVP (Minimum Viable Product)
 
     Follow these rules as a guide to ensure clarity and completeness in your UX Sitemap Document.
-    1, Write you result in markdown
-    2, Your reply should start with : "\`\`\`UXSitemap" and end with "\`\`\`", Use proper markdown syntax for headings, subheadings, and hierarchical lists.
-    3. **Comprehensive Analysis**: Thoroughly parse the PRD to identify all core features, functionalities, and user stories.
-    - Focus on creating a hierarchical sitemap that covers each major section, with relevant sub-sections, pages, and key interactions.
-    - Ensure all primary and secondary user journeys identified in the PRD are clearly reflected.
-
-    4. **Page and Navigation Structure**: Break down the sitemap into main sections, secondary sections, and individual screens.
-    - **Main Sections**: Identify primary sections (e.g., Home, User Account, Product Catalog) based on project requirements.
-    - **Secondary Sections**: Include sub-sections under each main section (e.g., "Profile" and "Order History" under "User Account").
-    - **Screens and Interactions**: List specific screens and interactions that users encounter within each flow.
-
-    5. **Detailed User Journeys**:
-    - For every user story described in the PRD, map out the step-by-step navigation path.
-    - Highlight sequences (e.g., 1. Home > 1.1. Explore > 1.1.1. Product Details).
-
-    6. **Thorough Coverage**:
-    - Ensure the sitemap is fully comprehensive. If any feature from the PRD is not covered or any user journey is missing, add it to the sitemap.
-    - Consider the target audience and validate that all expected navigation flows and screens meet user needs.
-
-7. Ask Your self:
-    - Am I cover all the product requirement document?
-    - Am I Cover all the gloabal UI?
-    - Am I Cover all unique UI?
-    - Am I cover all the view that expect by user?
-    - what is all the details about UI?
-    - Am I cover all the cases? Is the final result 100% complete?
- 
-Remeber your result will be directly be use in the deveolpment. Make sure is 100% complete.
+   Output Requirements:
+    Use plain text (no Markdown).
+    Begin with <UXSitemap> and end with </UXSitemap>.
+    Within <UXSitemap>, generate multiple <gen_page> blocks, one for each page.
+    Each <gen_page> must follow this structure exactly:
+
+<gen_page>
+P#. [Page Name]
+
+    URL Path: /[path]
+    Description: [Brief description of page purpose]
+    Parent Page: [Parent page if nested, or "None" if top-level]
+    Access Level: [e.g., Public/Private/Admin]
+
+#### Core Components
+
+    C#.1. [Component Name]
+        Type: [Layout/Interactive/Display/etc.]
+        Purpose: [What does it do?]
+        States: [Possible states, e.g., Default/Hovered/Expanded...]
+        Interactions: [User interactions]
+
+#### Features & Functionality
+
+    F#.1. [Feature Name]
+        Description: [Brief feature description]
+        User Stories: [Related user stories from PRD]
+        Components Used: [Which components implement this feature?]
+
+#### Page-Specific User Flows
+
+    Flow #. [Flow Name]
+        [Step 1]
+        [Step 2]
+</gen_page>
+
+4. **Number** pages sequentially (P1., P2., etc.).  
+5. **Number** each component and feature sequentially within that page (C1.1, C1.2, F1.1, F1.2, etc.).  
+6. Thoroughly parse the PRD to include:
+   - **All** pages.
+   - **All** features, functionalities, user stories, and flows.
+   - **All** major/minor navigation and user journeys.
+
+
+Sitemap Coverage
+
+    Comprehensive Analysis:
+        Capture all features, functionalities, and user stories.
+        Represent all primary and secondary user flows.
+
+    Page & Navigation Structure:
+        Identify all main and nested pages.
+        Ensure clear parent-child relationships.
+
+    Detailed User Journeys:
+        Provide step-by-step navigational flows unique to each page.
+
+    Thorough Coverage:
+        Verify every requirement, global UI element, unique UI, and user expectation from the PRD is addressed.
+        No user flow or screen should be missing.
+
+Self-Check Before Submitting
+
+    Have you accounted for all PRD details?
+    Have you included all major and minor pages/screens?
+    Have you detailed each page's components, features, and flows completely?
+
+Deliver a single XML-like document that strictly follows the structure above. Start with <UXSitemap> and close with </UXSitemap>, containing one <gen_page> block per page.
     `;
   },
 };