Update prompt

Author: ZHallen122

backend/src/build-system/__tests__/fullstack-gen.spec.ts

@@ -3,22 +3,23 @@ import { BuildSequence } from '../types';
 import { ProjectInitHandler } from '../handlers/project-init';
 import { PRDHandler } from '../handlers/product-manager/product-requirements-document/prd';
 import { UXSMDHandler } from '../handlers/ux/sitemap-document';
-import { UXSMSHandler } from '../handlers/ux/sitemap-structure';
 import { DBRequirementHandler } from '../handlers/database/requirements-document';
 import { UXDMDHandler } from '../handlers/ux/datamap';
 import { BuilderContext } from '../context';
-import { FrontendCodeHandler } from '../handlers/frontend-code-generate';
-import { FileStructureAndArchitectureHandler } from '../handlers/file-manager/file-struct';
+import { DBSchemaHandler } from '../handlers/database/schemas/schemas';
 import { BackendRequirementHandler } from '../handlers/backend/requirements-document';
+import { FileStructureAndArchitectureHandler } from '../handlers/file-manager/file-struct';
+import { UXSMSHandler } from '../handlers/ux/sitemap-structure';
+import { BackendCodeHandler } from '../handlers/backend/code-generate';
+import { FrontendCodeHandler } from '../handlers/frontend-code-generate';
 
 (isIntegrationTest ? describe : describe.skip)('Build Sequence Test', () => {
   it('should execute build sequence successfully', async () => {
     const sequence: BuildSequence = {
       id: 'test-backend-sequence',
       version: '1.0.0',
       name: 'Wrtie a Cool personal website',
-      description:
-        'A personal blog website. I am a cybersecurity engineer so i want it to show i am a really cool hacker, with cool terminal functionality',
+      description: `A personal blog website. I am a cybersecurity engineer so i want it to show i am a really cool hacker, with cool terminal functionality`,
       databaseType: 'SQLite',
       model: 'gpt-4o-mini',
       projectSize: 'medium', // limit for fun
@@ -38,7 +39,6 @@ import { BackendRequirementHandler } from '../handlers/backend/requirements-docu
         {
           handler: UXSMSHandler,
           name: 'UX Sitemap Structure Node',
-          // requires: ['op:UX:SMD'],
         },
         {
           handler: UXDMDHandler,
@@ -53,15 +53,33 @@ import { BackendRequirementHandler } from '../handlers/backend/requirements-docu
           name: 'Database Requirements Node',
           // requires: ['op:UX:DATAMAP:DOC'],
         },
+        {
+          handler: DBSchemaHandler,
+          name: 'Database schema Node',
+          // requires: ['op:UX:DATAMAP:DOC'],
+        },
         {
           handler: BackendRequirementHandler,
           name: 'Backend Requirements Node',
           // requires: ['op:DATABASE_REQ', 'op:UX:DATAMAP:DOC', 'op:UX:SMD'],
         },
+        {
+          handler: BackendCodeHandler,
+          name: 'Backend Code Generator Node',
+        },
         {
           handler: FrontendCodeHandler,
           name: 'Frontend Code Generator Node',
         },
+
+        // // {
+        // //   handler: BackendFileStructureAndArchitectureHandler,
+        // //   name: 'Backend File Structure and Architecture',
+        // // },
+        // {
+        //   handler: BackendFileReviewHandler,
+        //   name: 'Backend File review Node',
+        // },
       ],
       packages: [],
     };

backend/src/build-system/handlers/backend/code-generate/prompt.ts

@@ -48,7 +48,7 @@ export const generateBackendCodePrompt = (
        **Include:**
        1. **Server Setup:**
           - Initialize the server using the Express framework with ES Module syntax (use \`import\` instead of \`require\`).
-          - Configure middleware for JSON parsing and CORS it should allow localhost.
+          - Configure middleware for JSON parsing and CORS example "app.use(cors()); "
    
        2. **Database Connection and Initialization:**
           Database schemas: These schemas are defined in \`./schema.sql\`. The code must read and execute this file during database initialization.

backend/src/build-system/handlers/backend/requirements-document/index.ts

@@ -12,6 +12,7 @@ import { BuildNode, BuildNodeRequire } from 'src/build-system/hanlder-manager';
 import { DBRequirementHandler } from '../../database/requirements-document';
 import { UXDMDHandler } from '../../ux/datamap';
 import { DBSchemaHandler } from '../../database/schemas/schemas';
+import { MessageInterface } from 'src/common/model-provider/types';
 
 type BackendRequirementResult = {
   overview: string;
@@ -65,14 +66,42 @@ export class BackendRequirementHandler implements BuildHandler<string> {
       packages,
     );
 
+    const messages = [
+      {
+        role: 'system' as const,
+        content: overviewPrompt,
+      },
+      {
+        role: 'user' as const,
+        content: `## Database Requirements:
+            ${dbRequirements}
+                              `,
+      },
+      {
+        role: 'user' as const,
+        content: `## DataBase Schema:
+            ${dbSchema}
+                              `,
+      },
+      {
+        role: 'user' as const,
+        content: `## Frontend Data Requirements:
+            ${datamapDoc} `,
+      },
+      {
+        role: 'user',
+        content: `Now you can provide the code, don't forget the <GENERATE></GENERATE> tags. Do not be lazy.`,
+      },
+    ] as MessageInterface[];
+
     let backendOverview: string;
 
     try {
       backendOverview = await chatSyncWithClocker(
         context,
         {
           model: 'gpt-4o-mini',
-          messages: [{ content: overviewPrompt, role: 'system' }],
+          messages: messages,
         },
         'generateBackendOverviewPrompt',
         BackendRequirementHandler.name,

backend/src/build-system/handlers/backend/requirements-document/prompt.ts

@@ -10,6 +10,7 @@ export const generateBackendOverviewPrompt = (
   return `Role: You are a Senior Backend Architect specializing in backend systems. Generate the System Overview and API Endpoints specifications based on the following inputs.
 
 Task: Generate a Backend Overview Document following these guidelines:
+Project Name: ${projectName}
 
 ### Technology Stack
 - Language: ${language}
@@ -29,35 +30,25 @@ ${Object.entries(packages)
 4. Consider:
    - Data flow between frontend pages
    - Required data transformations
-   - Authentication and authorization needs
 5. IMPORTANT: Carefully differentiate between public and authenticated endpoints:
-   - Public endpoints (No Auth): Content retrieval endpoints (GET blog posts, portfolio items, etc.)
-   - Authenticated endpoints (Auth Required): Content creation/modification endpoints (POST/PUT/DELETE blog posts, etc.)
+   - Public endpoints (No Auth)
 6. For authenticated endpoints only, include authentication in the headers section using "Authorization": "Bearer {token}"
 7. Don't add authentication requirements to public-facing read operations (GET requests for viewing content)
+8. Do not add login when no documentation mentioned.
+9. It MUST be COMPLETE DO NOTE write TODO, and Future for api.
 
 Your reply must start with: "<GENERATE>" and end with "</GENERATE>".
 
 Include these sections:
-
-<System_Overview>
-#### 1. System Overview
-- **Project Name**: ${projectName}
-- **Framework architecture**
-- **Data Flow**
-  - Frontend-Backend data interactions
-  - Data transformation layers
-</System_Overview>
-
-<ApiDoc>
+## API Documentation
 Group endpoints by functional areas based on site structure.
 For each endpoint:
 \`\`\`
 Route: GET|POST|PUT|DELETE /api/resource
 Purpose: Functional description
 Data Requirements:
   - Required data transformations
-Required Auth: Yes/No
+Required Auth: No/Yes
 Request:
 {
   "headers": {},
@@ -70,22 +61,6 @@ Response:
   "success": {},
   "errors": {}
 }
-</ApiDoc>
-
-
-# Context input
-Project Name: ${projectName}
-
-## Requirements Documentation
-1. Database Requirements:
-${dbRequirements}
-
-2. DataBase Schema:
-${dbSchema}
-
-2. Frontend Data Requirements:
-${datamapDoc}
-
 \`\`\``;
 };
 

backend/src/build-system/handlers/database/requirements-document/prompt.ts

@@ -10,14 +10,17 @@ export const prompts = {
 Follow these guidelines to generate the database requirements:
 
 ### Instructions and Rules:
-1. Analyze data elements mentioned in the UX Datamap
-2. Carefully distinguish between frontend state management and actual database storage needs
-3. Only include entities and attributes that require persistent storage
-4. For each feature in the UX Datamap, clearly determine if it needs database support or is purely frontend
-5. Identify entities and their relationships
-6. Determine data types and constraints
-7. Consider data persistence requirements
-8. Plan for scalability and performance
+1. IMPORTANT: Only include features and entities that are EXPLICITLY mentioned in the UX Datamap.
+2. Analyze data elements mentioned in the UX Datamap.
+3. DO NOT include any conditional or optional features (phrases containing "if", "optional", "may", "possible", or similar qualifiers).
+4. Do not add User, login, authentication unless specifically mentioned in the UX Datamap.
+5. Carefully distinguish between frontend state management and actual database storage needs
+6. Only include entities and attributes that require persistent storage
+7. For each feature in the UX Datamap, clearly determine if it needs database support or is purely frontend
+8. Identify entities and their relationships
+9. Determine data types and constraints
+10. Consider data persistence requirements
+11. Plan for scalability and performance
 
 ### Database Requirements Structure:
 ---
@@ -56,10 +59,10 @@ For each entity:
 - Performance considerations
 
 #### 6. Security Requirements
-- Access control
-- Data privacy considerations
-- Audit requirements
-- Encryption needs
+- Only include access control if user authentication is EXPLICITLY REQUIRED
+- Only include data privacy considerations for sensitive data that is actually being stored
+- Only include audit requirements if explicitly mentioned
+- Only include encryption needs if sensitive data is being stored
 
 #### 7. Performance Requirements
 - Expected data volume
@@ -93,8 +96,8 @@ Focus on creating practical, implementable database requirements that will effec
    - Partitioning needs
 
 4. Security & Compliance:
-   - Access control
-   - Data encryption
+   - Only include access control if authentication is explicitly required
+   - Data encryption only if sensitive data is being stored
    - Audit requirements
 
 5. Maintenance & Operations:

backend/src/build-system/handlers/frontend-code-generate/CodeReview.ts

@@ -276,8 +276,8 @@ export class CodeQueueProcessor {
         fixResponse = await chatSyncWithClocker(
           this.context,
           {
-            // model: 'o3-mini-high',
-            model: 'gpt-4o-mini',
+            model: 'o3-mini-high',
+            // model: 'gpt-4o-mini',
             messages: [
               { role: 'system', content: fixPrompt },
               {

backend/src/build-system/handlers/ux/datamap/prompt.ts

@@ -83,50 +83,6 @@ For each page in sitemap:
 - How data changes based on user actions
 - What feedback is needed
 - When/how data updates
-
-Example for Login Page:
-
-##### Login Page
-**Purpose**: Allow users to authenticate and access their account
-
-**User Goals**:
-- Sign into their account
-- Recover forgotten password
-- Stay signed in for convenience
-
-**Required Data Elements**:
-
-*Input Data*:
-- Username/Email
-  - Purpose: Identify the user account
-  - User expectation: Email format or username rules
-  - Should be remembered if user chooses
-- Password
-  - Purpose: Authenticate the user
-  - Should be masked for security
-  - Should support paste functionality
-- "Remember Me" option
-  - Purpose: Convenience for returning users
-  - Optional selection
-
-*Display Data*:
-- Login form status
-- Authentication feedback
-- Password requirements (if needed)
-- Account recovery options
-
-*Feedback & States*:
-- Loading state during authentication
-- Success feedback and redirect
-- Error messages for invalid credentials
-- Password recovery confirmation
-
-**User Interactions**:
-- Form validation feedback
-- Login button state changes
-- Immediate feedback on input errors
-- Clear path to password recovery
-
 ---
 
 Your reply must start with: "\`\`\`UXDataMap" and end with "\`\`\`".