TestGenerator

{ "launchBrief": { "productName": "System Prompt: CCAT Spatial Reasoning Engine1. Project Vision & IdentityCore Objective: Develop a procedural generator for CCAT-style spatial reasoning questions (Matrices, Sequences, and Odd-One-Out).Visual Aesthetic: \"Industrial Workstation.\"Do Not Use: Rounded corners, bubble buttons, pastel colors, or \"soft\" UI.Required: Sharp corners ($0px$ radius), high-contrast $1px$ grids, glassmorphism (glass-fill), glowing borders (#00ff00 or #00ffff), and a monospaced font hierarchy.2. Technical Stack RequirementsFramework: Next.js (App Router) + TypeScript.Styling: Tailwind CSS (Strictly utility-first).Graphics: Dynamic SVG Generation (No static image assets).State Management: React Context or Zustand for test-session tracking.Animation: Framer Motion (Linear or \"mechanical\" easing only).3. Architecture: The Rule-Based FactoryThe developer must implement a Factory Pattern for question generation. Do not hardcode questions.A. The Atomic State (ShapeState)Every shape must be represented by a TypeScript interface:TypeScripttype ShapeType = 'polygon' | 'circle' | 'line_cluster' | 'composite';", "productType": "interface ShapeState {", "audience": "type: ShapeType; sides: number; // e.g., 3 for triangle, 4 for square rotation: number; // degrees (0, 45, 90, 180, etc.) fill: 'none' | 'solid' | 'pattern-diagonal' | 'pattern-grid'; scale: number; // 0.1 to 1.0 internalElements: number; // e.g., dots inside a shape position: { x: number; y: number }; // Relative to a 100x100 SVG coordinate system } B. ConstraintsStability: Ensure generated shapes never overlap the SVG boundaries.Distinctness: Distractors must be algorithmically similar to the correct answer to ensure high difficulty (e.g., if the correct answer is a $90^\\circ$ rotation, one distractor should be a $45^\\circ$ rotation).Functional Integrity: Do not remove existing features; provide the entire code for any modified files.", "problem": "type: ShapeType; sides: number; // e.g., 3 for triangle, 4 for square rotation: number; // degrees (0, 45, 90, 180, etc.) fill: 'none' | 'solid' | 'pattern-diagonal' | 'pattern-grid'; scale: number; // 0.1 to 1.0 internalElements: number; // e.g., dots inside a shape position: { x: number; y: number }; // Relative to a 100x100 SVG coordinate system } B. The Rule EngineImplement \"Transformers\" that take a ShapeState and return a modified ShapeState.Rotation Transformer: (state) => { ...state, rotation: state.rotation + step }Growth Transformer: (state) => { ...state, sides: state.sides + 1 }Inversion Transformer: Swaps fill and stroke colors.4. Question Logic ModulesThe app must support three distinct generator modules:Next in Series (Horizontal): * Input: A starting ShapeState + 2 random Transformers.Output: 4 sequence frames + 1 correct answer (5th frame) + 4 distractors (incorrect transformer logic).$3 \\times 3$ Logic Matrix:Implement \"Row-wise\" or \"Column-wise\" logic.Example: Row3 =...", "offer": "Turn the uploaded brief into the strongest possible implementation-ready plan without inventing facts that are not supported by the source.", "differentiators": "The final brief should stay tightly aligned to the source material instead of drifting into generic templates.", "features": "", "deliverables": "The final output should be specific enough for product, design, engineering, QA, and deployment handoff.", "brandStyle": "Clear, rigorous, and implementation-oriented.", "techStack": "No fixed stack specified beyond modern frontend, backend, real-time transport, auth, persistence, and deployment choices.", "monetization": "Monetization is not explicitly defined in the source document. Prioritize extensibility, sustainable AI cost controls, and a platform foundation that can support future pricing decisions.", "assets": "Available source material includes the uploaded requirements document.", "deadline": "Use the timeline specified in the uploaded requirements document.", "successMetrics": "Success means the final plan is accurate, feasible, testable, launch-ready, and clearly aligned to the source requirements." }, "prompt": { "role": "Senior product strategist, systems thinker, and implementation planner", "objective": "Turn the requirements for System Prompt: CCAT Spatial Reasoning Engine1. Project Vision & IdentityCore Objective: Develop a procedural generator for CCAT-style spatial reasoning questions (Matrices, Sequences, and Odd-One-Out).Visual Aesthetic: \"Industrial Workstation.\"Do Not Use: Rounded corners, bubble buttons, pastel colors, or \"soft\" UI.Required: Sharp corners ($0px$ radius), high-contrast $1px$ grids, glassmorphism (glass-fill), glowing borders (#00ff00 or #00ffff), and a monospaced font hierarchy.2. Technical Stack RequirementsFramework: Next.js (App Router) + TypeScript.Styling: Tailwind CSS (Strictly utility-first).Graphics: Dynamic SVG Generation (No static image assets).State Management: React Context or Zustand for test-session tracking.Animation: Framer Motion (Linear or \"mechanical\" easing only).3. Architecture: The Rule-Based FactoryThe developer must implement a Factory Pattern for question generation. Do not hardcode questions.A. The Atomic State (ShapeState)Every shape must be represented by a TypeScript interface:TypeScripttype ShapeType = 'polygon' | 'circle' | 'line_cluster' | 'composite'; into a production-quality implementation prompt that is detailed, accurate, and build-ready.", "context": "type: ShapeType; sides: number; // e.g., 3 for triangle, 4 for square rotation: number; // degrees (0, 45, 90, 180, etc.) fill: 'none' | 'solid' | 'pattern-diagonal' | 'pattern-grid'; scale: number; // 0.1 to 1.0 internalElements: number; // e.g., dots inside a shape position: { x: number; y: number }; // Relative to a 100x100 SVG coordinate system } B. The Rule EngineImplement \"Transformers\" that take a ShapeState and return a modified ShapeState.Rotation Transformer: (state) => { ...state, rotation: state.rotation + step }Growth Transformer: (state) => { ...state, sides: state.sides + 1 }Inversion Transformer: Swaps fill and stroke colors.4. Question Logic ModulesThe app must support three distinct generator modules:Next in Series (Horizontal): * Input: A starting ShapeState + 2 random Transformers.Output: 4 sequence frames + 1 correct answer (5th frame) + 4 distractors (incorrect transformer logic).$3 \\times 3$ Logic Matrix:Implement \"Row-wise\" or \"Column-wise\" logic.Example: Row3 = Row1 + Row2 (Overlaying SVGs) or Row3 = Row1 shifted 90 degrees.Odd One Out:Generate 5 shapes where 4 share a specific ShapeState constant (e.g., all have prime-numbered sides) and 1 does not.5. The...", "constraints": "The Rule EngineImplement \"Transformers\" that take a ShapeState and return a modified ShapeState.Rotation Transformer: (state) => { ...state, rotation: state.rotation + step }Growth Transformer: (state) => { ...state, sides: state.sides + 1 }Inversion Transformer: Swaps fill and stroke colors.4. Question Logic ModulesThe app must support three distinct generator modules:Next in Series (Horizontal): * Input: A starting ShapeState + 2 random Transformers.Output: 4 sequence frames + 1 correct answer (5th frame) + 4 distractors (incorrect transformer logic).$3 \\times 3$ Logic Matrix:Implement \"Row-wise\" or \"Column-wise\" logic.Example: Row3 = Row1 + Row2 (Overlaying SVGs) or Row3 = Row1 shifted 90 degrees.Odd One Out:Generate 5 shapes where 4 share a specific ShapeState constant (e.g., all have prime-numbered sides) and 1 does not.5. DeliverablesStrictly Typed Interfaces: No any types.Procedural Component: A SpatialCanvas component that renders a ShapeState using pure SVG paths.The Generator Logic: A generateQuestion(type: 'matrix' | 'series') function that outputs a JSON object containing the question data and an obfuscated answer key.UI/UX: A \"Terminal\" style layout. Favor explicit ass...", "input": "Source document: System Prompt: CCAT Spatial Reasoning Engine1. Project Vision & IdentityCore Objective: Develop a procedural generator for CCAT-style spatial reasoning questions (Matrices, Sequences, and Odd-One-Out).Visual Aesthetic: \"Industrial Workstation.\"Do Not Use: Rounded corners, bubble buttons, pastel colors, or \"soft\" UI.Required: Sharp corners ($0px$ radius), high-contrast $1px$ grids, glassmorphism (glass-fill), glowing borders (#00ff00 or #00ffff), and a monospaced font hierarchy.2. Technical Stack RequirementsFramework: Next.js (App Router) + TypeScript.Styling: Tailwind CSS (Strictly utility-first).Graphics: Dynamic SVG Generation (No static image assets).State Management: React Context or Zustand for test-session tracking.Animation: Framer Motion (Linear or \"mechanical\" easing only).3. Architecture: The Rule-Based FactoryThe developer must implement a Factory Pattern for question generation. Do not hardcode questions.A. The Atomic State (ShapeState)Every shape must be represented by a TypeScript interface:TypeScripttype ShapeType = 'polygon' | 'circle' | 'line_cluster' | 'composite';. Use the original case study, feature requirements, app integration contract, testing scenarios, deadlines, planning checklist, and cost-analysis requirements as the source of truth.\n\nSystem Prompt: CCAT Spatial Reasoning Engine1. Project Vision & IdentityCore Objective: Develop a procedural generator for CCAT-style spatial reasoning questions (Matrices, Sequences, and Odd-One-Out).Visual Aesthetic: \"Industrial Workstation.\"Do Not Use: Rounded corners, bubble buttons, pastel colors, or \"soft\" UI.Required: Sharp corners ($0px$ radius), high-contrast $1px$ grids, glassmorphism (glass-fill), glowing borders (#00ff00 or #00ffff), and a monospaced font hierarchy.2. Technical Sta...", "output": "Produce the strongest possible build prompt and implementation brief. Produce a structured implementation brief with decisions, workflows, constraints, deliverables, risks, and next steps.", "examples": "Use the most concrete examples from the source document as anchors for the final plan.", "tone": "executive" } }