diff --git a/backend/src/build-system/node/ux-sitemap-structure/index.ts b/backend/src/build-system/node/ux-sitemap-structure/index.ts
new file mode 100644
index 0000000..b761b3f
--- /dev/null
+++ b/backend/src/build-system/node/ux-sitemap-structure/index.ts
@@ -0,0 +1,34 @@
+import { BuildHandler, BuildResult } from 'src/build-system/types';
+import { BuilderContext } from 'src/build-system/context';
+import { ModelProvider } from 'src/common/model-provider';
+import { prompts } from './prompt';
+
+export class UXStructureHandler implements BuildHandler {
+  readonly id = 'op:UX_Structure::STATE:GENERATE';
+
+  async run(context: BuilderContext, args: unknown): Promise<BuildResult> {
+    console.log('Generating UX Structure Document...');
+
+    // extract relevant data from the context
+    const projectName =
+      context.getData('projectName') || 'Default Project Name';
+
+    const prompt = prompts.generateUXDataMapPrompt(
+      projectName,
+      args as string,
+      // TODO: change later
+      'web',
+    );
+
+    const uxStructureContent = await context.model.chatSync(
+      {
+        content: prompt,
+      },
+      'gpt-4o-mini',
+    );
+    return {
+      success: true,
+      data: uxStructureContent,
+    };
+  }
+}
diff --git a/backend/src/build-system/node/ux-sitemap-structure/prompt.ts b/backend/src/build-system/node/ux-sitemap-structure/prompt.ts
new file mode 100644
index 0000000..f57017f
--- /dev/null
+++ b/backend/src/build-system/node/ux-sitemap-structure/prompt.ts
@@ -0,0 +1,61 @@
+export const prompts = {
+  generateUXDataMapPrompt: (
+    projectName: string,
+    sitemapDoc: string,
+    platform: string,
+  ): string => {
+    return `You are an expert UX Designer. Your task is to analyze the provided sitemap documentation and generate a Detailed UX Structure Map to support the user experience and frontend implementation. The output should address all aspects of user interaction, content layout, based on the following inputs:
+  
+         - Project name: ${projectName}
+         - Sitemap Documentation: ${sitemapDoc}
+         - Platform: ${platform}
+  
+  Follow these guidelines to analyze requirements from a UX perspective:
+  
+  ### Instructions and Rules:
+  
+  1, Your job is to analyzing how the ui element should be layed out and distributed on the page based on the Sitemap Documentation.
+  2, You need to ensure all features from the sitemap documentation are addressed.
+  3, You need to identify and define every page/screen required for the application.
+  4, Detailed Breakdown for Each Page/Screen:
+    Page Purpose: Clearly state the user goal for the page.
+    Core Elements:
+        List all components (e.g., headers, buttons, sidebars) and explain their role on the page.
+        Include specific interactions and behaviors for each element.
+    Content Display:
+        Identify the information that needs to be visible on the page and why it’s essential for the user.
+    Navigation and Routes:
+        Specify all frontend routes required to navigate to this page.
+        Include links or actions that lead to other pages or states.
+    Restrictions:
+        Note any restrictions or conditions for accessing the page (e.g., login required, specific user roles).
+
+  5, Focus on Detail:
+    Provide a component-level breakdown for each page, including layouts.
+    Explain how the design supports user goals and aligns with their journey.
+
+  6. For each page/screen in the sitemap:
+     - How the block should be place on the view?
+     - What information does the user need to see?
+     - What elements should be on the page?
+     - What are all the routes require for the frontend?
+     - What dynamic content needs to be displayed?
+     - What are the restriction for the page?
+  
+  7. Consider:
+     - User goals on each page
+     - User journy
+     - Element purposes
+     - Content that needs to be displayed
+
+  Your reply must start with: "\`\`\`UXStructureMap" and end with "\`\`\`". 
+
+  Focus on describing the UX Structure from a user experience perspective. For each page:
+  1. What element appear on each page and why
+  2. What information needs to be displayed and why
+  3. How the element supports user goals
+
+  Make sure is 100% completed. It will be directly be use in development.
+  `;
+  },
+};