@getollie/cli 0.0.5 → 0.2.0

package/library/svg_generation-svg_images/newly-married-couple-heart-symbol.json

@@ -1,68 +0,0 @@
-{
-  "index": 101,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Take care to ensure the generated code is executable for demonstration.\n\nPlease help me implement the following requirement using code. Create an SVG illustration of: a newly married couple in wedding attire with a heart symbol positioned above them.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the SVG illustration of the married couple properly structured?",
-      "description": "Review whether the SVG code follows proper structure with appropriate viewBox, dimensions, and namespace. Check if the core elements (bride, groom, heart) are properly defined within the SVG. Score 0 if the SVG structure is missing or severely flawed, 5 if basic structure exists but with issues, and 10 if the structure is complete and standards-compliant.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are the wedding attire details well illustrated?",
-      "description": "Evaluate the level of detail in the wedding attire for both characters. The bride should have a recognizable wedding dress (with details like veil, train, or lace) and the groom should have formal attire (suit or tuxedo). Deduct 3 points if one character's attire lacks detail, 5 points if both are overly simplified, and 7 points if attire is generic without wedding-specific elements. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the heart symbol properly positioned and styled?",
-      "description": "Check if the heart symbol is clearly visible above the couple (not overlapping with the characters) and has appropriate styling (color, size, possibly animation). Deduct 5 points if the heart's position doesn't clearly indicate it's above the couple, 3 points if the heart is poorly styled or too small to notice, and 2 points if the heart lacks thematic connection to the wedding concept (e.g., wrong color palette). The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Does the illustration use appropriate visual composition?",
-      "description": "Assess whether the composition follows visual design principles with proper balance, proportion, and focal points. The couple should be centrally positioned with the heart forming a visual triangle. Deduct 5 points for unbalanced composition where elements appear randomly placed, 3 points if the scale between elements is jarring, and 2 points if visual hierarchy is unclear. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the SVG code is resilient across different browsers and viewing contexts. Check for proper fallbacks, appropriate use of groups (<g> elements), and clean path definitions. Code with strong robustness should handle scaling gracefully and avoid rendering artifacts. Give 10 points for highly robust implementation, 5 points for average implementation with minor issues, and 0 points if the SVG breaks easily under different conditions.",
-      "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. Subtle animations like a beating heart 2. Interactive elements that respond to mouse hover/click 3. Gradient effects or decorative elements like flowers/rings). 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 path definitions or duplicate elements 2. Unnecessarily complex paths that could be simplified 3. Excessive details that impair performance without visual benefit. Deduct 3 points for each redundancy found, and directly deduct 10 points if core visual elements are obscured by redundant elements.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modularity of SVG components, appropriate use of reusable elements, and optimization techniques. Deduct 5 points if paths are unnecessarily complex or unoptimized; deduct 3 points if there's no logical grouping of related elements; deduct 2 points if IDs/classes aren't used where appropriate for potential styling/animation. 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 palette appropriate for wedding theme 2) Clean silhouettes with proper figure-ground relationship 3) Thoughtful use of stroke weights and fill colors. Deduct 3 points for clashing colors, 5 points for poor visual clarity between elements, and 5 points for inconsistent styling across the illustration. 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 enhance the visual story: 1) Smooth transitions if elements animate 2) Appropriate timing for any effects (not too fast/slow) 3) Purposeful interactions that add meaning. Deduct 5 points for jarring or distracting animations, 3 points for performance issues during animation, and 5 points if interactions break the visual cohesion. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "SVG Generation-SVG Images",
-  "difficulty": "easy"
-}

package/library/svg_generation-svg_images/olympic-rings-drawing-program.json

@@ -1,68 +0,0 @@
-{
-  "index": 1291,
-  "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 for display. Program to draw the Olympic rings",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the implementation of the Olympic rings accurate?",
-      "description": "Check whether the code correctly implements the five Olympic rings with standard colors (blue, yellow, black, green, and red) in the proper interlocking arrangement. The rings should be in the correct order from left to right: blue, yellow (behind), black, green (behind), and red. Proper spacing and alignment should be observed. Score 0 if rings are missing or incorrectly colored, 5 if basic implementation exists but with minor errors, 10 if perfectly implemented according to official specifications.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are the precise dimensions and proportions maintained?",
-      "description": "Evaluate whether the code uses the correct proportions for the Olympic rings. According to official specifications, each ring should be of equal size, with proper spacing between rings (1/3 of ring diameter). The thickness of each ring should be 1/6 of the internal diameter. Deduct 3 points if proportions are incorrect, 3 points if spacing is wrong, and 4 points if the rings don't follow the official layout pattern. Full score for pixel-perfect implementation.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the implementation responsive?",
-      "description": "Check whether the Olympic rings display properly across different screen sizes. The implementation should maintain proper proportions regardless of viewport dimensions. Deduct 5 points if the rings don't scale appropriately on different screen sizes; deduct another 5 points if the layout breaks on mobile devices. Give 10 points if the implementation maintains proper spacing and proportions across all common device dimensions.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Does the implementation use appropriate rendering technology?",
-      "description": "Assess whether the chosen rendering approach (SVG, Canvas, CSS, etc.) is appropriate for the task. SVG would be ideal for the Olympic rings as a vectorized image. Deduct 3 points if using bitmap-based approaches that pixelate when scaled; deduct 5 points if the implementation causes excessive DOM elements or performance issues. Give 10 points for an efficient, scalable implementation using appropriate web technologies.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as browser compatibility issues, rendering failures, etc.) and provide fallbacks when necessary. Code with strong robustness should work across different browsers and handle edge cases. Give 10 points if the implementation works flawlessly across all major browsers, 5 points if minor compatibility issues exist, and 0 points if major rendering problems occur in common browsers.",
-      "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. Smooth animation of the rings appearing 2. Interactive elements when hovering/clicking rings 3. Dynamic color transitions or effects that maintain brand integrity). 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 code for creating similar shapes 2. Unnecessary visual effects that distract from the Olympic rings 3. Excessive animation or interaction that compromises the official representation. Deduct 3 points for each redundancy found, and directly deduct 10 points if the core presentation is negatively affected by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating drawing logic/configuration/interactions), reusability of components, and clean coding practices. Deduct 5 points if global variables are unnecessarily used; deduct 5 points if the code is not structured with proper functions or classes; deduct 5 points if hard-coded values are used instead of configurable parameters. The full score is 10 points for clean, maintainable, and well-organized code.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the Olympic rings rendering follows professional design principles: 1) Accurate official Olympic colors (correct RGB/hex values) 2) Proper ring spacing and alignment 3) Clean presentation without distracting elements. Deduct 3 points for each visual inaccuracy, 5 points for incorrect color values, and 5 points for poor layout or spacing. The full score is 10 points for a visually perfect implementation matching official IOC standards.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether any included dynamic effects (animations, transitions, interactive elements) conform to human perception characteristics: 1) Smooth rendering without jank or frame drops 2) Appropriate animation timing if implemented 3) Proper visual feedback for any interactive elements. Deduct 5 points for jerky animations, 3 points for inappropriate timing of visual effects, and 5 points for confusing or misleading interactions. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "SVG Generation-SVG Images",
-  "difficulty": "medium"
-}

package/library/svg_generation-svg_images/person-falling-cliff-parachute-svg.json

@@ -1,68 +0,0 @@
-{
-  "index": 28,
-  "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 when possible. Please help me implement the following requirement using SVG code: create a person falling off a cliff with a parachute.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the basic SVG structure properly implemented?",
-      "description": "Check whether the code includes proper SVG namespace, viewBox setting, and organized element grouping. The SVG should have appropriate dimensions and coordinate system. Deduct 3 points if namespace is missing, 3 points for improper viewBox setup, and 4 points for lack of logical grouping (<g> elements). The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the cliff scene visually represented?",
-      "description": "Evaluate whether the cliff is properly designed with clear visual distinction from the sky/background. The cliff should have some terrain details (like rocks, edges, texture). Give 3 points for basic shape representation, 7 points for a detailed cliff with texture, and 10 points for a visually compelling cliff with proper perspective. Deduct points if the cliff appears flat or poorly integrated into the scene.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the human figure properly designed and proportioned?",
-      "description": "Review the implementation of the human figure, checking for proper body proportions, limb articulation, and posture appropriate for falling. Score 3 points for a basic stick figure, 7 points for a properly proportioned body with distinguishable limbs, and 10 points for a detailed human figure with appropriate falling posture and visible facial features. Deduct points for anatomical errors or unnatural posing.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the parachute properly implemented with realistic behavior?",
-      "description": "Check if the parachute is properly designed with canopy, strings connecting to the person, and appropriate deployment state. The parachute should appear to be catching air and slowing the descent. Score 3 points for basic shape, 7 points for proper structure with strings, and 10 points if the parachute shows realistic inflation and proper connection to the person. Deduct points if physics of deployment appears incorrect.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code is well-structured, uses proper SVG attributes, and avoids redundant or conflicting definitions. Good practices include descriptive IDs, clean path definitions, and appropriate use of SVG elements. Deduct 3 points for each significant error like invalid attributes or conflicting definitions. Give 10 points for clean, maintainable, and error-free code.",
-      "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. Animation of falling/parachute deployment 2. Environmental elements like clouds or birds 3. Interactive elements responding to user input). 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 or elements serving the same purpose 2. Unnecessary complexity in shapes that could be simplified 3. Elements that distract from the core scene (falling person with parachute). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core elements are obscured by redundant visuals.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modularity (such as using <defs> for reusable elements), CSS organization (external or embedded styles), and SVG optimization techniques. Deduct 5 points if the code uses absolute positioning everywhere instead of relative positioning; deduct 5 points if there's excessive hard-coding instead of parametrization; deduct 5 points if optimization techniques like path simplification are ignored. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the visual implementation meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color palette appropriate for the scene 2) Proper perspective and scaling 3) Good use of layers and depth. Deduct 3 points for each visual inconsistency, 5 points for inappropriate color choices, and 5 points for poor visual hierarchy. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is there animation or potential for animation?",
-      "description": "Judge whether the scene includes or is prepared for animation: 1) SMIL animations or CSS/JavaScript hooks for animating the falling motion 2) Parachute deployment sequence 3) Environmental animations like clouds moving. Deduct 5 points if no animation or animation hooks are present, 3 points if animations are jerky or unrealistic, and 5 points if animation timing is inappropriate for the scene. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "SVG Generation-SVG Images",
-  "difficulty": "easy"
-}

package/library/svg_generation-svg_images/person-holding-box-close-up-portrait.json

@@ -1,68 +0,0 @@
-{
-  "index": 121,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the code you provide is executable and can be displayed. \n\nPlease help me implement the following requirements using code, with the creation to be done in SVG: Create a close-up portrait of a person holding a box in their hands.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the basic SVG structure correctly implemented?",
-      "description": "Check if the code includes proper SVG namespace, viewBox definition, and appropriate dimensions. The SVG element should have width/height attributes or CSS styling that makes it responsive. Deduct 5 points if the SVG lacks proper viewport settings, 5 points if namespaces are missing, and 3 points if responsive design is not considered. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the human face accurately and proportionally rendered?",
-      "description": "Evaluate whether facial features (eyes, nose, mouth, ears) are drawn with proper proportions and positioning. The face should show depth through shading and have realistic or stylistically consistent features. Score 0 if facial features are missing or severely distorted, 5 if proportions are slightly off but recognizable, and 10 if the face appears professionally crafted with proper anatomical understanding. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are the hands holding the box drawn with anatomical accuracy?",
-      "description": "Review the hand structure (proper finger proportions, natural positioning) and the hand-box interaction (realistic grip, appropriate tension). Hands should show proper perspective and include details like knuckles and fingernails. Deduct 5 points if hands appear anatomically incorrect, 3 points if the grip on the box looks unnatural, and 2 points if hands lack depth or detail. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the box drawn with correct perspective and dimension?",
-      "description": "Check if the box shows proper 3D perspective with consistent vanishing points, correct corner angles, and appropriate size relative to the hands. The box should appear to have weight and volume. Deduct 5 points for perspective inconsistencies, 3 points if the box lacks dimensional consistency, and 2 points if the box appears weightless or flat. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code handles browser compatibility issues, uses appropriate fallbacks for unsupported features, and avoids hard-coded values that might break in different contexts. Code with strong robustness should work across major browsers and screen sizes, giving 10 points. If the robustness is average, 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 visual experience (e.g., 1. Subtle animation like blinking or breathing effect 2. Interactive elements that respond to user input 3. Creative use of gradients or patterns for added realism). 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 identical purposes 2. Excessive or unnecessary detail that complicates the code without visual benefit 3. Over-complicated effects that could be achieved with simpler methods. Deduct 3 points for each redundancy found, and directly deduct 10 points if the core visual elements are obscured by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular structure (logical grouping of SVG elements), code reusability (use of <defs> and patterns), and overall code organization. Deduct 5 points if elements aren't properly grouped or named; deduct 5 points if the code is excessively verbose with duplicate definitions; deduct 5 points if there's no separation between structural and stylistic elements. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the portrait meet professional artistic standards?",
-      "description": "Evaluate whether the portrait follows artistic principles: 1) Balanced composition with proper focal point 2) Effective use of color theory and shading 3) Appropriate level of detail with visual hierarchy. Deduct 3 points for compositional imbalance, 5 points for unrealistic or jarring color choices, and 5 points for flat rendering without depth. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the SVG optimized for performance and filesize?",
-      "description": "Judge whether the SVG implementation is efficient: 1) Appropriate use of primitives vs. path elements 2) Optimization of path data (minimal points, no unnecessary precision) 3) Proper use of groups to reduce redundancy. Deduct 5 points for unnecessarily complex paths, 3 points for excessive precision in numerical values, and 5 points for failure to use appropriate SVG features (like symbols or gradients) where beneficial. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "SVG Generation-SVG Images",
-  "difficulty": "hard"
-}

package/library/svg_generation-svg_images/person-holding-cell-phone-close-up.json

@@ -1,68 +0,0 @@
-{
-  "index": 25,
-  "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 when possible.\nPlease help me implement this SVG image using code. A close up of a person holding a cell phone in their hand.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the basic SVG structure correctly implemented?",
-      "description": "Check if the code includes proper SVG namespace, viewBox dimensions, and appropriate canvas size. The SVG should have clear width/height attributes or style properties. Deduct 5 points if the SVG namespace is missing, 3 points for inappropriate viewBox dimensions, and 2 points for missing responsive design considerations. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the human hand accurately rendered?",
-      "description": "Evaluate the anatomical accuracy of the hand including proper finger proportions, natural finger positioning for holding a phone, and realistic skin contours. Check for correct use of path elements or complex shapes to form the hand. Score 10 points for realistic hand representation with proper shading and detail, 5 points for basic but identifiable hand structure, 0 points if the hand appears anatomically incorrect or unrecognizable. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the cell phone realistically depicted?",
-      "description": "Analyze whether the cell phone has realistic dimensions proportional to the hand, proper screen-to-body ratio, and recognizable modern smartphone features (camera, buttons, etc.). Deduct 3 points if the phone lacks detail, 4 points if proportions are unrealistic, and 3 points if the phone doesn't appear to be properly held. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Are the interaction points between hand and phone accurately represented?",
-      "description": "Check if the finger positions naturally wrap around the phone with proper contact points and if the grip looks secure and realistic. Examine if z-index and layering are handled correctly where fingers overlap the phone. Score 0 points if fingers appear to pass through the phone, 5 points for basic contact representation, 10 points for realistic gripping with proper pressure points and natural finger positioning. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle different viewports and scaling without distortion. Check if appropriate groups (<g> elements) are used for logical organization of elements and if the code includes appropriate comments for complex paths. Deduct 3 points for each brittle implementation that breaks on resizing, 2 points for poor code organization, and 2 points for lack of documentation on complex elements. The full score is 10 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 image (e.g., 1. Screen content on the phone 2. Subtle animations like finger movements or screen interactions 3. Gradient lighting effects or 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. Overlapping paths or shapes that add unnecessary complexity 2. Elements unrelated to the hand-holding-phone focus (e.g., excessive background detail) 3. Overly complex filters or effects that impact performance. Deduct 3 points for each redundancy found, and directly deduct 10 points if redundant code interferes with the core visual representation. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as using reusable components for fingers or phone elements), variable naming conventions, and optimization techniques (like path simplification). Deduct 5 points if inline styles are overused instead of CSS classes; deduct 3 points if there's excessive path data that could be simplified; deduct 2 points if there's no clear organization of SVG elements. 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) Realistic color usage for skin tones and phone materials 2) Proper use of gradients and shadows for depth 3) Attention to detail in proportions and perspective. Deduct 3 points for unrealistic coloring, 3 points for flat appearance without depth, and 4 points for perspective inconsistencies. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the rendering visually refined and detailed?",
-      "description": "Judge the level of visual refinement: 1) Fine details like finger creases, knuckle definition 2) Phone details like buttons, screen bezels, or camera lenses 3) Appropriate use of SVG filters for shadows or highlights. Deduct 3 points for each major area lacking appropriate detail, 2 points for missing subtle visual cues that would enhance realism, and 5 points if the overall image appears too simplistic. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "SVG Generation-SVG Images",
-  "difficulty": "medium"
-}

package/library/svg_generation-svg_images/person-laptop-gears-close-up.json

@@ -1,68 +0,0 @@
-{
-  "index": 50,
-  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional replies. Make sure the code you generate is executable and can be displayed. Please help me implement the following requirement using SVG code: create a close-up of a person sitting at a laptop with gears.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the SVG rendering properly structured?",
-      "description": "Evaluate whether the SVG includes proper viewport dimensions, viewBox attributes, and organized layer grouping (<g> elements) for different components (person, laptop, gears). Check if proper SVG namespaces are declared. Score 0 if basic SVG structure is missing, 5 if structure exists but lacks organization, 10 if well-organized with proper nesting and namespaces.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the human figure accurately depicted in the close-up view?",
-      "description": "Review whether the person is properly proportioned with clear upper body details (head, torso, arms, hands) and sitting posture. Look for facial features, appropriate clothing details, and natural sitting position. Deduct 3 points if proportions are significantly off, 3 points if the sitting posture looks unnatural, and 4 points if facial/clothing details are completely missing. Full score for anatomically correct rendering that clearly shows a person in close-up view.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the laptop accurately depicted with appropriate details?",
-      "description": "Check if the laptop has realistic proportions, includes essential elements (screen, keyboard, touchpad), and positioned correctly relative to the person. Evaluate screen content visibility and keyboard detail level. Deduct 5 points if the laptop looks 2D or unrealistic, 3 points if essential elements are missing, and 2 points if the positioning relative to the person is implausible. Full score for a detailed, well-proportioned laptop with appropriate perspective.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Are the gears implemented with mechanical precision and appropriate placement?",
-      "description": "Assess whether gears include teeth details, have appropriate mechanical design (spokes, center holes), and are thoughtfully positioned in the composition (around/behind laptop, near person's head suggesting thought process, etc.). Evaluate if gears look like they could theoretically mesh. Deduct 3 points if gears lack tooth detail, 4 points if gears are randomly placed without purpose, and 3 points if fewer than 3 distinct gears are shown. Full score for precisely drawn gears with meaningful placement.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the SVG code avoids hardcoded magic numbers, uses variables/functions for repeated elements (like multiple gears), and implements reusable patterns. Check if the code would scale to different viewports without breaking. Code with strong robustness should handle different display contexts effectively. Give 10 points for highly reusable code, 5 points for average implementation, and 0 points if the code is brittle with many magic numbers.",
-      "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. Animation of spinning gears 2. Interactive elements that respond to hover/click 3. Gradient/lighting effects that give depth 4. Clever use of <clipPath> or masks). 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 paths or shapes that could be defined once and reused 2. Elements unrelated to the core request (person, laptop, gears) 3. Over-detailed elements that increase complexity without adding value. Deduct 3 points for each redundancy found, and directly deduct 10 points if redundant code significantly impacts file size or readability.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as defining reusable components with <defs> and <symbol>), proper element IDs/classes, and optimized paths. Deduct 5 points if the code lacks any reuse of repeated elements; deduct 5 points if there's significant path complexity that could be simplified; deduct 5 points if basic SVG optimization techniques aren't applied (like removing unnecessary decimal precision). 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 palette (no more than 3 primary colors with appropriate shades) 2) Proper composition with clear focal point 3) Appropriate use of style attributes for visual hierarchy. Deduct 3 points for each visually jarring element, 5 points for a clashing color scheme, and 5 points for poor composition where the focus is unclear. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the visual storytelling effective?",
-      "description": "Judge whether the SVG successfully communicates the intended concept: 1) Clear relationship between person and laptop 2) Gear placement that suggests mental work/productivity 3) Overall composition that conveys focused activity. Deduct 5 points if the relationship between elements is unclear, 3 points if the mood/tone doesn't match a work/creative scenario, and 5 points if the close-up perspective isn't effectively implemented. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "SVG Generation-SVG Images",
-  "difficulty": "hard"
-}

package/library/svg_generation-svg_images/person-walking-crosswalk.json

@@ -1,68 +0,0 @@
-{
-  "index": 185,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure that the code you provide is executable when possible.\nPlease help me implement this SVG image using code: a close up of a person walking across a crosswalk",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the basic SVG structure properly implemented?",
-      "description": "Check if the SVG element has appropriate viewport dimensions, viewBox settings, and namespace declarations. The SVG should have a reasonable size (e.g., 600x400 or similar) with properly set width/height attributes or responsive sizing. Deduct 5 points if the basic structure is incorrect, 3 points if dimensions are inappropriate for the scene. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Does the implementation accurately depict a close-up of a person walking across a crosswalk?",
-      "description": "Evaluate if the core visual elements are present: (1) A recognizable human figure with walking pose, (2) Clear white crosswalk stripes on dark road surface, (3) Close-up perspective as requested. Deduct 5 points if any of these key elements is missing, 3 points if they're present but poorly executed. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the human figure properly designed and detailed?",
-      "description": "Assess the human figure's anatomical correctness and walking pose authenticity. Check if body proportions are reasonable, with proper limb articulation showing a walking gait. Figure should have appropriate level of detail for a close-up view (facial features, clothing details, etc.). Deduct 4 points for unrealistic proportions, 3 points for static pose instead of walking motion, and 3 points for lack of detail appropriate for a close-up. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the crosswalk properly designed with accurate perspective?",
-      "description": "Verify that the crosswalk stripes follow correct perspective principles, showing appropriate foreshortening based on the viewpoint. White stripes should have consistent spacing and width relative to perspective. Deduct 5 points if perspective is completely wrong, 3 points if the stripes have inconsistent spacing/width, and 2 points if the stripes don't visually read as a crosswalk. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code uses best practices like grouping (<g> elements), reusable definitions (e.g., using <defs>, <symbol>, or <use>), and appropriate element types for different shapes. Check if the code handles potential rendering issues across browsers. Code with strong robustness should be maintainable and efficient, giving 10 points. If the robustness is average, give 5 points, and if code is overly complex or brittle, 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. Animation of walking motion, 2. Interactive elements like hover effects, 3. Responsive design that adjusts to viewport, 4. Creative lighting/shadow 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 simplified or grouped, 2. Elements unrelated to the crosswalk scene (e.g., unrelated background objects), 3. Excessive detail that impacts performance (e.g., too many path points or unnecessary filters). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core image 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, and optimization techniques. Deduct 5 points if elements aren't logically grouped or named; deduct 5 points if the file size is unnecessarily large due to poor optimization; deduct 5 points if accessibility attributes are missing (e.g., role, aria-label, title elements). The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the image meet professional design standards?",
-      "description": "Evaluate whether the design follows modern visual principles: 1) Effective use of color (appropriate contrast between road, stripes, and figure), 2) Balanced composition (figure properly placed within frame), 3) Appropriate level of detail for the scene. Deduct 3 points for poor color choices, 5 points for awkward composition, and 5 points for inconsistent level of detail across elements. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Are advanced SVG techniques utilized appropriately?",
-      "description": "Judge whether the implementation uses appropriate SVG capabilities: 1) Proper use of gradients for depth and lighting, 2) Appropriate use of opacity and blending modes, 3) Efficient path construction techniques. Deduct 3 points for missing gradient opportunities, 3 points for flat/unrealistic rendering without advanced features, and 4 points for inefficient path construction. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "SVG Generation-SVG Images",
-  "difficulty": "medium"
-}

package/library/svg_generation-svg_images/pie-chart-with-large-amount-of-data.json

@@ -1,68 +0,0 @@
-{
-  "index": 195,
-  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable and can be displayed.\nPlease help me implement the following requirement using SVG code: create a close-up view of a pie chart with a large amount of data.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the pie chart correctly implemented with SVG?",
-      "description": "Check if the SVG implementation includes properly calculated arc paths using the SVG 'path' element with correct 'd' attributes for each pie slice. Arc calculations must use Math.sin/cos or SVG arc commands correctly. Score 0 if no pie chart is implemented, 5 if basic pie slices are drawn but have calculation errors, and 10 if all pie slices are mathematically precise.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the close-up view functionality properly implemented?",
-      "description": "Evaluate whether the code includes a mechanism to zoom in or focus on specific sectors of the pie chart. Look for features like hover magnification, separate detailed view, or click-to-zoom functionality. Deduct 5 points if only static magnification is implemented without interaction, and 3 points if the transition between normal and close-up views is abrupt. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "How well does the implementation handle large amounts of data?",
-      "description": "Assess how the code manages pie charts with many data points (20+ slices). Check for techniques like grouping small slices into an 'Other' category, using tooltips for small segments, employing color gradients for related categories, or implementing pagination/filtering. Deduct 5 points if small segments become unreadable, and 3 points if performance noticeably degrades with 50+ data points. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Are data labels and legends implemented effectively?",
-      "description": "Check whether the visualization includes proper labels that adjust position based on slice size, with collision detection to prevent overlapping text. For the close-up view, labels should be appropriately scaled and positioned. Verify if a legend is provided for identification of segments. Deduct 5 points if labels overlap significantly, and 3 points if labels are only visible in certain views. 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 missing data, zero values, negative values, extremely small or large segments, etc.) and provide friendly error handling or fallback displays. Code with strong robustness should be able to effectively handle these 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. Interactive animations when transitioning to close-up view 2. Smart labeling that adjusts based on segment size 3. Contextual information that appears on interaction). 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 visualization functions (e.g., multiple zoom mechanisms) 2. Function modules unrelated to pie charts (e.g., unnecessary tooltips) 3. Fancy effects that affect performance (e.g., excessive animations or gradients). 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 data processing/rendering/interaction layers), reusability of components, and code organization. Deduct 5 points if global state pollution is found or if there's no clear separation of concerns; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there are no comments or documentation. 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 data visualization principles: 1) Harmonious color matching with sufficient contrast between segments 2) Proper visual hierarchy with focus on the close-up area 3) Consistent visual language throughout the chart. Deduct 3 points for each poor color choice that makes segments hard to distinguish, 5 points for cluttered visual elements, and 5 points for inconsistent visual treatment between normal and close-up views. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the interaction smooth and intuitive?",
-      "description": "Judge whether the interaction design conforms to user expectations: 1) Clear visual cues for interactive elements 2) Smooth transitions between normal and close-up views (300-500ms duration) 3) Intuitive controls for navigating the large dataset. Deduct 5 points for each interaction without visual feedback, 3 points for confusing navigation controls, and 5 points for unintuitive zoom/focus mechanics. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "SVG Generation-SVG Images",
-  "difficulty": "hard"
-}