feat: prompt tuning for shorter blueprints

Author: AshishKumar4

worker/agents/planning/blueprint.ts

@@ -25,7 +25,7 @@ const SYSTEM_PROMPT = `<ROLE>
     Enhance the user's request and expand on it, think creatively, be ambitious and come up with a very beautiful, elegant, feature complete and polished design. We strive for our products to be masterpieces of both function and form - visually breathtaking, intuitively designed, and delightfully interactive.
 
     **REMEMBER: This is not a toy or educational project. This is a serious project which the client is either undertaking for building their own product/business OR for testing out our capabilities and quality.**
-    **Keep the size and complexity of blueprint proportional to the size and complexity of the project.** eg, No need to overengineer a 'todo' app.
+    **Keep the size and complexity of blueprint proportional to the size and complexity of the project.** eg, No need to overengineer a 'todo' app. And limit the overall blueprint size to no more than 2 pages.
 </TASK>
 
 <GOAL>
@@ -104,7 +104,7 @@ const SYSTEM_PROMPT = `<ROLE>
 </INSTRUCTIONS>
 
 <KEY GUIDELINES>
-    • **Ultra think:** Do thorough thinking internally first before writing the blueprint. Your planning and design should be meticulous and thorough in every detail. The final blueprint should be concise, information dense and well thought out.
+    • **Ultra think:** Do thorough thinking internally first before writing the blueprint. Your planning and design should be meticulous and thorough in every detail. The final blueprint should be concise, information dense and well thought out and not overly verbose. It should be explicit and to the point.
     • **Completeness is Crucial:** The AI coder relies *solely* on this blueprint. Leave no ambiguity.
     • **Precision in UI/Layout:** Define visual structure explicitly. Use terms like "flex row," "space-between," "grid 3-cols," "padding-4," "margin-top-2," "width-full," "max-width-lg," "text-center." Specify responsive behavior.
     • **Explicit Logic:** Detail application logic, state transitions, and data transformations clearly.

worker/agents/schemas.ts

@@ -95,11 +95,11 @@ export const BlueprintSchema = z.object({
         dataFlow: z.string().describe('Conscise description of how data flows through the application'),
     }).describe('Description of the architecture of the application, only needed for a dynamic application'),
     pitfalls: z.array(z.string()).describe('Exhaustive yet concise list of all the various framework and domain specific pitfalls, issues, challenges, and bugs that can occur while developing this and to avoid during implementation'),
-    frameworks: z.array(z.string()).describe('Essential Frameworks, libraries and dependencies to be used in the application, with only major versions optionally specified'),
+    frameworks: z.array(z.string()).describe('Essential Frameworks, libraries and dependencies to be used in the application (apart from what is already in the template), with only major versions optionally specified'),
     implementationRoadmap: z.array(z.object({
         phase: z.string().describe('Phase name'),
-        description: z.string().describe('Description of the phase'),
-    })).describe('Phases of the implementation roadmap'),
+        description: z.string().describe('Concise and brief description of the phase'),
+    })).describe('Rough roadmap of the project'),
     initialPhase: PhaseConceptSchema.describe('The first phase to be implemented, in **STRICT** accordance with <PHASE GENERATION STRATEGY>'),
     // commands: z.array(z.string()).describe('Commands to set up the development environment and install all dependencies not already in the template. These will run before code generation starts.'),
 });