@getollie/cli 0.0.1

package/library/svg_generation-svg_images/svg-crossroads-intersection.json

@@ -0,0 +1,68 @@
+{
+  "index": 181,
+  "question": "You are a coding expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the code you generate is executable for display whenever possible. Please help me implement the following requirement using SVG code: create a crossroads intersection.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the basic structure of the crossroads intersection correctly implemented with SVG?",
+      "description": "Check if the SVG code properly defines the viewBox, dimensions, and namespace. Verify that the crossroads layout includes two perpendicular roads meeting at a central intersection point. Score 0 if there's no visible intersection, 5 if the basic structure exists but has alignment issues, and 10 if the roads are properly aligned and proportioned.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are the road elements accurately drawn with appropriate styling?",
+      "description": "Evaluate whether the roads are drawn with proper width, color, and border styling. Road markings should include center lines, stop lines, and lane dividers where appropriate. Deduct 3 points if road widths are inconsistent, 3 points if essential markings are missing, and 4 points if the styling lacks realism or professional appearance. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Are traffic elements (signals, signs, pedestrian crossings) included and properly positioned?",
+      "description": "Check if the intersection includes traffic lights, road signs, and pedestrian crosswalks in appropriate positions. Score 0 if these elements are completely missing, 5 if only some basic elements are present but poorly positioned, and 10 if the intersection has a complete set of traffic elements positioned according to standard traffic engineering practices.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Does the SVG implementation use groups and reusable components efficiently?",
+      "description": "Analyze if the implementation uses <g> elements to group related items, and whether it creates reusable components (like traffic lights or road markings) that can be used multiple times. Deduct 5 points if no grouping is used, and 5 points if the code has significant redundancy instead of creating reusable components. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle different viewport sizes, browser compatibility issues, and avoid rendering artifacts. Code with strong robustness should use relative positioning where appropriate and include fallbacks or error handling. Give 10 points for robust implementation, 5 points for average robustness, and 0 points if the SVG is likely to break under common viewing conditions.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the SVG includes surprise features that enhance the visualization (e.g., 1. Animated traffic lights 2. Moving vehicles or pedestrians 3. Day/night mode toggle 4. Interactive elements). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant SVG elements that could be simplified 2. Elements unrelated to a crossroads intersection (e.g., buildings that distract from the main subject) 3. Overly complex effects that affect performance (e.g., excessive filter effects). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core representation is obscured by redundant elements.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review code organization (such as logical grouping of SVG elements), naming conventions for IDs and classes, and appropriate comments. Deduct 5 points if element IDs/classes are unclear or inconsistent; deduct 5 points if the code structure is chaotic; deduct 5 points if there are no comments explaining complex parts. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the visual representation meet professional design standards?",
+      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching (no more than 3 primary colors for road elements) 2) Proper proportioning of elements 3) Clean visual hierarchy with important elements standing out. Deduct 3 points for each visual imbalance, 5 points for garish color combinations, and 5 points for unclear visual hierarchy. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the SVG optimized for performance and accessibility?",
+      "description": "Judge whether the SVG is optimized: 1) File size is reasonable with no unnecessary decimal points in coordinates 2) Proper ARIA attributes for accessibility 3) Appropriate title and desc elements. Deduct 5 points for bloated code with redundant precision, 3 points for missing accessibility features, and 5 points if the SVG isn't properly structured for screen readers. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "SVG Generation-SVG Images",
+  "difficulty": "easy"
+}

package/library/svg_generation-svg_images/svg-cube-shaped-box-design.json

@@ -0,0 +1,68 @@
+{
+  "index": 133,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the code you generate is executable for demonstration purposes. \n\nPlease help me implement the following requirement using code. Create a cube-shaped box design using SVG code.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the basic cube structure correctly implemented in SVG?",
+      "description": "Review whether the SVG code correctly implements a 3D cube using appropriate elements (path, polygon, etc.). Check if all 6 faces are properly defined with correct coordinates to form a cube shape. Score 0 if no cube is formed, 5 if the cube shape is incomplete or distorted, and 10 if all faces are properly positioned to form a perfect cube.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the perspective projection handled properly?",
+      "description": "Evaluate whether the code implements proper perspective or isometric projection for the 3D cube. Check if the projection technique creates a convincing 3D appearance and if the cube's dimensions appear proportional. Deduct 5 points if the projection looks flat or distorted, and 3 points if only simple 2D representation is used. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is face visibility and occlusion handled correctly?",
+      "description": "Check if the code properly handles which faces should be visible from the viewing angle (hidden face removal). Verify that faces that should be hidden behind others are properly occluded. Give 10 points if z-ordering is perfect, 5 points if there are minor z-ordering issues, and 0 points if faces randomly appear in front of others regardless of spatial position.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Are colors, shading, or textures applied appropriately?",
+      "description": "Assess whether the cube has appropriate colors, shading, or textures to enhance its 3D appearance. Check if different faces have distinct colors/shades to differentiate them. Deduct 5 points if all faces have identical appearance making it hard to distinguish them, and 3 points if the coloring doesn't help with depth perception. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle different viewport sizes, browser compatibility issues, and potential calculation edge cases. Code with strong robustness should be responsive and work across browsers, giving 10 points. If the robustness is average, give 5 points, and if the code breaks easily or has fixed dimensions that don't adapt, give 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprise features that enhance the cube visualization (e.g., 1. Animation/rotation capabilities 2. Interactive manipulation 3. Light source simulation with dynamic shadows). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant SVG elements or paths that overlap unnecessarily 2. Excessive attributes or styling that don't contribute to the cube visualization 3. Complicated effects that affect performance without improving visual quality. Deduct 3 points for each redundancy found, and directly deduct 10 points if the core cube rendering is interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review code organization (such as grouping related SVG elements, using variables for repeated values), code reusability, and clarity of implementation. Deduct 5 points if SVG elements are not logically grouped; deduct 5 points if there's significant duplicate code that could be parameterized; deduct 5 points if there are no comments explaining complex calculations or transformations. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the visualization meet professional design standards?",
+      "description": "Evaluate whether the overall design follows modern design principles: 1) Clean and precise rendering without jagged edges 2) Proper proportions and perspective 3) Professional use of colors with appropriate contrast. Deduct 3 points for each visual artifact or rendering issue, 5 points for poor proportions, and 5 points for unprofessional color choices. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless (if applicable)?",
+      "description": "Judge whether any interactive or animated elements conform to human perception characteristics: 1) Smooth transitions/animations with appropriate timing 2) Intuitive interactive controls if present 3) Clear visual feedback for interactions. Deduct 5 points for each jerky animation, 3 points for confusing interaction patterns, and 5 points for missing visual feedback when interacting. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "SVG Generation-SVG Images",
+  "difficulty": "easy"
+}

package/library/svg_generation-svg_images/svg-digital-camera-for-photography.json

@@ -0,0 +1,68 @@
+{
+  "index": 139,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to ensure that the code you generate is executable and can be properly displayed. Please help me implement this SVG image using code. Camera is used for photography, some of which are digital.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the basic camera shape structure accurately implemented in SVG?",
+      "description": "Check if the code includes the fundamental camera body structure with proper dimensions and proportions. The camera should have a recognizable shape with main body, lens, viewfinder, and essential camera components. Score 0 if the shape is unrecognizable as a camera, 5 if basic outlines are present but with significant proportion issues, and 10 if the camera shape is professionally proportioned and immediately identifiable.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are the camera details and components properly represented?",
+      "description": "Evaluate the implementation of camera details such as lens elements, buttons, dials, flash, viewfinder, grip, and other distinguishing features. Check if these components are positioned correctly in relation to each other. Deduct 2 points for each missing essential component (lens, viewfinder, shutter button, etc.). Deduct 3 points if the components have unrealistic positions or proportions. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the SVG code structured with appropriate grouping and organization?",
+      "description": "Review whether the SVG elements are logically grouped (e.g., <g> elements for the camera body, lens, controls) with clear naming conventions. Check for proper nesting and structure that would facilitate future modifications. Score 0 if no grouping is used, 5 if basic grouping exists but lacks organization, 10 if components are logically grouped with descriptive IDs or classes that clearly indicate their purpose.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Does the SVG implementation include visual differentiation between digital and traditional camera elements?",
+      "description": "Assess whether the code differentiates between digital camera elements (LCD screen, memory card slots, digital controls) and traditional camera features. The implementation should clearly communicate which type of camera is being depicted or include elements from both if it's a hybrid representation. Deduct 5 points if there's no clear visual indication of camera type, and 3 points if digital elements are present but poorly implemented. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the SVG code is browser-compatible, uses proper SVG namespaces, and handles viewBox appropriately for responsiveness. Check if the code avoids hard-coded absolute positions that might break in different screen sizes. Deduct 5 points if the viewBox is missing or improperly configured, 3 points if the SVG doesn't scale properly, and 3 points if browser-specific quirks aren't addressed. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the SVG includes creative enhancements like 1) Interactive elements (clickable buttons that trigger animations), 2) Visual effects (gradients, shadows, highlights) that add depth, 3) Animation of camera parts (like lens rotation or shutter movement). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1) Duplicate path definitions that could be reused, 2) Excessive details that drastically increase file size without visual benefit, 3) Overly complex gradients or effects that impact performance. Deduct 3 points for each redundancy found, and directly deduct 10 points if these redundancies negatively impact the rendering of the core camera image.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review code organization (use of constants for repeated values, proper indentation), SVG optimization (removal of unnecessary decimal points, proper use of path commands), and maintainability. Deduct 5 points if path definitions are unnecessarily verbose; deduct 3 points if there's redundant attribute specification; deduct 3 points if the code lacks comments for complex sections. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the camera design follows modern design principles: 1) Harmonious color scheme appropriate for a camera (avoiding unrealistic colors), 2) Proper proportions and balance between components, 3) Appropriate level of detail that maintains clarity at different scales. Deduct 3 points for each unrealistic color choice, 5 points for significant proportion errors, and 3 points for poor detail scaling. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether any included animations or interactions: 1) Use appropriate SMIL or CSS animations with proper timing, 2) Provide visual feedback for interactive elements, 3) Enhance rather than distract from the camera representation. Deduct 5 points for each jerky animation, 3 points for animations that don't follow physical realism of camera mechanics, and 3 points for missing visual cues on interactive elements. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "SVG Generation-SVG Images",
+  "difficulty": "easy"
+}

package/library/svg_generation-svg_images/svg-dollar-bills-cash-currency.json

@@ -0,0 +1,68 @@
+{
+  "index": 57,
+  "question": "You are a coding expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the code you generate is executable for demonstration purposes. Please help me implement this SVG image using code. Money is in the form of dollar bills or cash currency.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the SVG dollar bill/cash currency visually accurate and detailed?",
+      "description": "Check if the SVG implementation includes essential visual elements of currency: denomination markings, security features (watermarks, security threads), serial numbers, and proper proportions. Score 0 if basic currency shape is missing, 5 if only basic outline is present, and 10 if detailed elements including textures and security features are implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are proper SVG techniques used for currency representation?",
+      "description": "Evaluate whether appropriate SVG elements (<path>, <rect>, <pattern>, <linearGradient>, etc.) are used efficiently for different parts of the currency. Check if complex details use proper techniques like gradient meshes or patterns instead of excessive path elements. Deduct 3 points for inefficient element choices, 4 points for missing essential SVG techniques like gradients for realistic shading, and 5 points if implementation relies solely on basic shapes without proper detail work.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the currency sizing and scaling properly implemented?",
+      "description": "Verify if the SVG uses proper viewBox attributes, preserveAspectRatio settings, and responsive design principles to ensure the currency renders correctly at different sizes. Check if proper width/height attributes or percentages are used. Deduct 5 points if the currency doesn't scale proportionally, and 5 points if viewBox is improperly configured causing display issues at different resolutions.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Does the implementation include interactive or animated elements?",
+      "description": "Assess whether the code includes appropriate animations or interactions that enhance the currency visualization (e.g., hover effects showing security features, flip animations to see both sides, counting/stacking animations). Give 0 points for no interactivity, 5 points for basic hover/click effects, and 10 points for smooth, meaningful animations that demonstrate currency properties.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common situations (such as browser compatibility issues, rendering in different contexts, fallback mechanisms). Code with strong robustness should work across modern browsers and include fallback options. Give 10 points for comprehensive fallbacks and browser support, 5 points for average robustness with minor issues, and 0 points if major rendering problems occur across platforms.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprise features that enhance the visualization (e.g., 1. Realistic paper texture/folding effects 2. Security features that appear under hover 3. Multiple currency types or denominations). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar visual elements 2. Excessive detail that harms performance 3. Fancy effects that don't contribute to realistic currency representation. Deduct 3 points for each redundancy found, and directly deduct 10 points if the core visualization is compromised by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating drawing functions/reusable components), code organization, and maintainability. Deduct 5 points if global variables are overused; deduct 5 points if the code duplication rate is too high; deduct 5 points if there's no structure or commenting for complex drawing functions. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the visual representation meet professional design standards?",
+      "description": "Evaluate whether the currency design follows authentic design principles: 1) Accurate color matching to real currency 2) Proper proportions and detail placement 3) Professional typography matching official currency fonts. Deduct 3 points for inaccurate colors, 5 points for unrealistic proportions, and 5 points for poor typography. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the implementation optimized for performance?",
+      "description": "Judge whether the SVG implementation is optimized: 1) Appropriate use of groups (<g>) 2) Efficient path commands 3) Proper use of symbols for repeated elements 4) Reasonable file size for detail level. Deduct 3 points for each inefficient implementation pattern, 5 points for excessive node count causing slow rendering, and 5 points for missing optimization techniques like symbol reuse for repeated elements. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "SVG Generation-SVG Images",
+  "difficulty": "easy"
+}

package/library/svg_generation-svg_images/svg-dynamically-rotating-gears-animation.json

@@ -0,0 +1,68 @@
+{
+  "index": 103,
+  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Make sure that the code you generate is executable when possible.\nPlease help me use code to implement the following requirement, using SVG code to create: Design a mechanical device with dynamically rotating gears, using <path> and <animateTransform> elements to create gear rotation animations.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Gear Geometrical Implementation",
+      "description": "Review whether the SVG code accurately implements gear teeth using <path> elements with proper mathematical calculations. Check if the teeth profiles are geometrically correct using involute curves or appropriate approximations. Score 0 if gears are just basic circles, 5 if teeth are represented but geometrically inaccurate, and 10 if teeth are precisely calculated with proper involute profiles.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Mechanical Rotation Animation",
+      "description": "Evaluate whether <animateTransform> is correctly implemented to create smooth gear rotations around proper centers. Verify that rotation speed is consistent with gear ratios (larger gears should rotate slower than smaller ones in proper proportion to their diameters). Deduct 5 points if animations are jerky or inconsistent, and 3 points if rotation centers are improperly positioned. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Gear Meshing Mechanics",
+      "description": "Check if the code implements proper gear meshing with teeth that correctly interlock without overlap or gaps. Verify that the rotation directions of adjacent gears are opposite (clockwise vs counter-clockwise). Deduct 5 points if gears visibly overlap or have significant gaps, and 3 points if rotation directions are incorrect. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Mechanical System Complexity",
+      "description": "Assess the complexity of the mechanical system. Check for the inclusion of different gear types (spur gears, bevel gears, planetary gears), gear trains, or compound mechanisms. Award 3 points for basic gear pairs, 7 points for intermediate complexity with 3-5 interacting gears, and 10 points for complex gear trains with multiple interconnected mechanisms or planetary gear systems.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Code Robustness",
+      "description": "Evaluate whether the code can handle parameter changes without breaking (such as changing gear sizes, teeth counts, or rotation speeds). Check for the use of variables and parameterized functions rather than hard-coded values. Code with strong robustness should be adaptable and scale without visual artifacts, giving 10 points. If the robustness is average, give 5 points, and if changes would break the implementation, give 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Innovative Features",
+      "description": "Check whether the code includes surprise features that enhance the visualization (e.g., 1. User-interactive controls for speed/direction 2. Dynamic gear highlighting on mouseover 3. Physical simulation elements like friction or inertia). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Redundant Implementation",
+      "description": "Strictly check three types of redundancy: 1. Duplicate definitions of similar gear elements 2. Unused or non-contributing graphical elements 3. Over-complex animations that harm performance without adding visual value. Deduct 3 points for each redundancy found, and directly deduct 10 points if core mechanics are obscured by unnecessary code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Engineering Quality",
+      "description": "Review modular SVG structure (such as using <defs> and <use> for repeated elements, organizing with <g> groups), code maintainability, and optimization. Deduct 5 points if global attributes pollute elements; deduct 5 points if the code has excessive repetition instead of reusable components; deduct 5 points if the SVG lacks proper viewBox settings or optimization. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Visual Design Quality",
+      "description": "Evaluate whether the mechanical device has professional visual design: 1) Appropriate color scheme for mechanical components (not exceeding 3 primary colors) 2) Proper proportions and balanced layout 3) Visual depth using gradients, shadows, or highlights. Deduct 3 points for visually imbalanced elements, 5 points for unrealistic mechanical appearance, and 5 points for poor use of space. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Animation Smoothness",
+      "description": "Judge whether the gear animations provide a realistic mechanical feel: 1) Consistent rotation speeds based on gear ratios 2) Smooth transitions without jumps or flickers 3) Appropriate animation timing for mechanical movement (not too fast or too slow). Deduct 5 points for jerky animations, 3 points for unrealistic movement physics, and 5 points for performance issues causing frame drops. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "SVG Generation-SVG Images",
+  "difficulty": "hard"
+}

package/library/svg_generation-svg_images/svg-eye-with-medicine-drops.json

@@ -0,0 +1,68 @@
+{
+  "index": 67,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the code you generate is executable for demonstration purposes.\nPlease help me implement the following requirement using code. Create using SVG code: an eye with liquid medicine drops falling from it, with matching colors.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the eye anatomical structure accurately represented in SVG?",
+      "description": "Evaluate whether the SVG code correctly depicts the eye's anatomical elements (sclera, iris, pupil, eyelids, tear ducts). Deduct 3 points if major anatomical structures are missing, 2 points if proportions are unrealistic. Full implementation with anatomical accuracy scores 10 points, basic implementation scores 5 points, and poor implementation scores 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are the liquid medicine drops effectively animated?",
+      "description": "Check if the animation shows drops forming, detaching, falling with gravity, and potentially splashing/dispersing. The animation should use appropriate SVG animation techniques (SMIL or CSS). Deduct 5 points if the animation is jerky or unrealistic, 3 points if timing feels unnatural. Full score requires physics-based movement with proper acceleration.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the color matching appropriate for the medical context?",
+      "description": "Assess whether the colors used for the eye and medicine drops are appropriate (typically blue/green/purple for eye medication). Score 10 points for a cohesive, intentional color scheme that enhances the medical visualization, 5 points for basic appropriate colors, 0 points for jarring or unrealistic color combinations that detract from the medical context.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the SVG implementation technically sound?",
+      "description": "Review the SVG code structure for proper use of paths, groups, gradients, and other SVG elements. Check for optimization of code (no redundant elements, appropriate use of transforms). Deduct 5 points for implementation that could be significantly optimized, 3 points if basic SVG principles are violated.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle different viewport sizes, browser compatibility, and provides fallbacks if needed. Code with strong robustness should adapt to different display contexts, giving 10 points. If the implementation breaks in common scenarios, give 5 points, and if major compatibility issues exist, give 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprise features that enhance the visualization (e.g., 1. Interactive elements responding to user input 2. Realistic liquid physics simulation 3. Environmental reflections or lighting effects). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant SVG elements that could be grouped or reused 2. Visual elements unrelated to the eye/medicine drops context 3. Excessive effects that negatively impact performance or clarity. Deduct 3 points for each redundancy found, and directly deduct 10 points if the core visualization is obscured by redundant elements.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as grouping related SVG elements, using reusable components), code readability (meaningful ids/classes), and implementation efficiency. Deduct 5 points if the SVG structure is chaotic; deduct 5 points if the code is excessively verbose without comments; deduct 5 points if basic optimizations are missing. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching (no more than 3 primary colors) 2) Proper visual hierarchy and focus 3) Balanced proportions and composition. Deduct 3 points for each visual distraction, 5 points for poor fundamental design choices, and 5 points for lack of visual coherence. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the animation effects conform to human perception characteristics: 1) Smooth transitions without jank 2) Animation timing that feels natural and intentional 3) Appropriate easing functions for liquid movement. Deduct 5 points for jerky animations, 3 points for timing that feels unnatural, and 5 points for animations that disrupt the medical visualization context. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "SVG Generation-SVG Images",
+  "difficulty": "easy"
+}

package/library/svg_generation-svg_images/svg-fast-stopwatch-image.json

@@ -0,0 +1,68 @@
+{
+  "index": 96,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate, expert responses. Take care to ensure that any code you generate is executable and can be demonstrated. Please help me implement this SVG image using code. The stopwatch is fast.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the SVG stopwatch correctly implemented with all visual components?",
+      "description": "Check if the SVG code includes all essential stopwatch elements: circular body, face with proper markings/numbers, central pivot, second/minute/hour hands, and top button(s). Deduct 3 points for each missing visual element. The stopwatch should have proper proportions and clear visual hierarchy. Score 0 if the basic structure is absent, 5 if some elements are missing or misaligned, and 10 if all elements are present and accurately positioned.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the stopwatch animation properly implemented?",
+      "description": "Evaluate the animation of the fast-moving second hand (and potentially other hands). Check for smooth continuous motion using requestAnimationFrame() or SVG animation elements (SMIL) rather than setTimeout/setInterval. The motion should be fluid without jerking. Deduct 5 points if the animation is choppy or uses inefficient methods, and 3 points if the timing is inaccurate. Give 10 points for buttery-smooth 60fps animation with precise timing.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the stopwatch functionality complete with proper timing mechanisms?",
+      "description": "Assess if the stopwatch provides expected functions: start, stop, reset, and potentially lap timing. Check if the code implements precise time tracking (high-resolution timestamps, performance.now() or similar). The stopwatch should maintain accuracy even after running for extended periods. Deduct 5 points if drift exceeds 1 second per minute of runtime. Give 10 points for a complete implementation with high precision timing.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Does the implementation include interactive controls?",
+      "description": "Check whether the SVG includes interactive elements for controlling the stopwatch (clickable buttons or touch areas). Interaction should provide visual feedback (hover/active states) and include proper event handling. Deduct 3 points if controls lack visual feedback, 5 points if they're unresponsive, and 5 points if accessibility features (keyboard navigation, ARIA attributes) are missing. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as browser compatibility issues, rapid clicking, extreme timing values, etc.) and provide friendly error handling. Code with strong robustness should be able to effectively handle edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Sound effects for button clicks/timer completion 2. Realistic shadows or lighting effects 3. Physics-based animations like spring effects when stopping). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple animation systems running simultaneously) 2. Function modules unrelated to stopwatch functionality 3. Fancy effects that affect performance (e.g., unnecessary particle effects or glow filters). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating rendering/animation/interactivity logic), code organization, and proper use of SVG features. Deduct 5 points if global namespace pollution is found; deduct 5 points if the code has excessive duplication; deduct 5 points if SVG attributes are hardcoded instead of parameterized. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the stopwatch design follows modern design principles: 1) Harmonious color matching (no more than 3 primary colors) 2) Proper layout and proportions (consistent stroke widths, appropriate scaling) 3) Professional typography for numbers and labels (legible at all sizes). Deduct 3 points for inconsistent visual elements, 5 points for poor color choices, and 5 points for illegible text or markings. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Click feedback delay ≤ 100ms 2) Smooth transitions when starting/stopping 3) Appropriate easing functions for realistic motion. Deduct 5 points for each operation without feedback, 3 points for jerky animations, and 5 points for unrealistic or physically implausible movements (like instant stops with no deceleration). The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "SVG Generation-SVG Images",
+  "difficulty": "hard"
+}

package/library/svg_generation-svg_images/svg-gray-game-controller-purple-buttons.json

@@ -0,0 +1,68 @@
+{
+  "index": 108,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Ensure that the code you generate is executable for demonstration.\nPlease help me implement the following requirement using code. Create using SVG code: a gray game controller with purple buttons.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the SVG game controller correctly structured and defined?",
+      "description": "Review whether the SVG has a proper viewport/viewBox setup, correct use of SVG namespaces, and appropriate dimensions for display. Check if the base structure uses proper SVG elements (rect, path, circle, etc.) for the controller body. Deduct 5 points for missing viewBox, 5 points for improper dimensions, and 5 points for incorrect SVG structure. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the game controller visually accurate and recognizable?",
+      "description": "Evaluate whether the SVG resembles a standard game controller with recognizable features (d-pad, analog sticks, action buttons, shoulder buttons). Score 0 if the shape is unrecognizable as a controller, 5 if it has basic controller features but with proportional issues, and 10 if it accurately depicts a realistic game controller with proper proportions.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Are the specified colors correctly implemented?",
+      "description": "Check whether the controller body uses gray color and the buttons use purple color as specified in the requirements. The gray should be an appropriate shade (not too dark or too light) and the purple should be visually distinct. Deduct 5 points if the gray color isn't used for the body, 5 points if the buttons aren't purple, and 3 points if the shades chosen are inappropriate. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Does the SVG include visual details and depth effects?",
+      "description": "Evaluate whether the implementation includes visual details like gradients, shadows, highlights, or other techniques to create a 3D effect or depth for the controller. Deduct 5 points for completely flat design without any depth cues, 3 points for minimal depth effects, and give full 10 points for professional-level shading and depth effects.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the SVG code is well-formed, valid, and compatible with standard browsers. Check for proper closing tags, valid attribute values, and absence of errors. Code with strong robustness should be able to render correctly across different browsers and contexts, giving 10 points. If there are minor issues that don't affect rendering, give 5 points, and if there are critical issues that break rendering, give 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the SVG includes surprise features that enhance the experience (e.g., 1. Interactive button press animations 2. Glowing effects 3. Creative interpretations of a game controller). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant SVG elements or groups that serve no purpose 2. Excessive detail that increases file size without visual benefit 3. Unnecessary animations or effects that distract from the main visual. Deduct 3 points for each redundancy found, and directly deduct 10 points if the core visualization is obscured by redundant elements.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review proper organization of SVG elements (logical grouping), use of reusable components, and optimization for file size. Deduct 5 points if elements aren't logically grouped; deduct 5 points if there's excessive code duplication instead of reusable patterns; deduct 5 points if the SVG isn't optimized (unnecessary decimal points, verbose paths). The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the overall design follows modern design principles: 1) Consistent stroke widths 2) Proper proportions between elements 3) Professional finish without jagged edges. Deduct 3 points for inconsistent stroke widths, 5 points for disproportionate elements, and 5 points for poor edge quality. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is there interactivity or potential for animation?",
+      "description": "Judge whether the SVG includes or is structured to allow for interactivity or animations: 1) Button states that could be animated 2) Elements with proper IDs for targeting with JavaScript 3) Organized layers that could be independently animated. Deduct 5 points if the SVG structure prevents easy animation, 3 points if only basic hover effects are possible, and 5 points if the SVG has no elements that could be targeted for interaction. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "SVG Generation-SVG Images",
+  "difficulty": "easy"
+}