@getollie/cli 0.0.1

package/library/web_applications-education_learning/material-testing-specifications-data.json

@@ -0,0 +1,68 @@
+{
+  "index": 300,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable for display.\n\nlet base_data = [\n  {\n    // testing_project field\n    label: \"Test Project\",\n    search: null,\n    tensile_strength: \"Tensile Strength\",\n    elongation_at_break: \"Elongation at Break\",\n    flexural_strength: \"Flexural Strength\",\n    flexural_modulus: \"Flexural Modulus\",\n    izod_impact_strength: \"Izod Impact Strength\",\n    heat_deflection_temp: \"Heat Deflection Temperature\",\n    dielectric_strength: \"Dielectric Strength\",\n    volume_resistivity: \"Volume Resistivity\",\n    density: \"Density\",\n    melt_flow_rate: \"Melt Flow Rate\",\n    molding_shrinkage: \"Molding Shrinkage\",\n    flammability_1_5mm: \"1.5mm Flammability Rating\",\n    flammability_3_0mm: \"3.0mm Flammability Rating\",\n    yellow_card: \"Yellow Card Number\",\n    rti_elec: \"RTI (Elec)\",\n    rti_imp: \"RTI (Imp)\",\n    rti_str: \"RTI (Str)\",\n    hwi: \"HWI\",\n    hai: \"HAI\",\n    cti: \"CTI\",\n    outdoor_performance: \"Outdoor Performance\",\n    ball_pressure_temp: \"Ball Pressure Temperature\",\n    rohs: \"RoHS\",\n    reach_svhc: \"REACH, SVHC\",\n    quotation: \"Quotation\",\n    remarks: \"Remarks\"\n  },\n  {\n    // testing_standards field\n    label: \"Testing Standards\",\n    search: null,\n    tensile_strength: \"ASTM D638\",\n    elongation_at_break: \"ASTM D638\",\n    flexural_strength: \"ASTM D790\",\n    flexural_modulus: \"ASTM D790\",\n    izod_impact_strength: \"ASTM D256\",\n    heat_deflection_temp: \"ASTM D648\",\n    dielectric_strength: \"ASTM D149\",\n    volume_resistivity: \"ASTM D257\",\n    density: \"ASTM D792\",\n    melt_flow_rate: \"ASTM D1238\",\n    molding_shrinkage: \"ASTM D955\",\n    flammability_1_5mm: \"UL-94\",\n    flammability_3_0mm: \"UL-94\",\n    yellow_card: \"/\",\n    rti_elec: \"UL 746B\",\n    rti_imp: \"UL 746B\",\n    rti_str: \"UL 746B\",\n    hwi: \"UL 746B\",\n    hai: \"UL 746B\",\n    cti: \"UL 746B\",\n    outdoor_performance: \"UL 746B\",\n    ball_pressure_temp: \"IEC 60695-10-2\",\n    rohs: \"/\",\n    reach_svhc: \"/\",\n    quotation: \"\",\n    remarks: \"\"\n  },\n  {\n    // testing_conditions field\n    label: \"Testing Conditions\",\n    search: null,\n    tensile_strength: \"50mm/min\",\n    elongation_at_break: \"50mm/min\",\n    flexural_strength: \"2mm/min\",\n    flexural_modulus: \"2mm/min\",\n    izod_impact_strength: \"3.2mm, 23℃\",\n    heat_deflection_temp: \"1.82MPa, 6.4mm\",\n    dielectric_strength: \"1.6mm\",\n    volume_resistivity: \"/\",\n    density: \"23℃\",\n    melt_flow_rate: \"230℃, 2.16kg\",\n    molding_shrinkage: \"23℃\",\n    flammability_1_5mm: \"1.5mm\",\n    flammability_3_0mm: \"3.0mm\",\n    yellow_card: \"/\",\n    rti_elec: \"1.5mm\",\n    rti_imp: \"1.5mm\",\n    rti_str: \"1.5mm\",\n    hwi: \"1.5mm\",\n    hai: \"1.5mm\",\n    cti: \"1.5mm\",\n    outdoor_performance: \"/\",\n    ball_pressure_temp: \"3.0mm\",\n    rohs: \"/\",\n    reach_svhc: \"/\",\n    quotation: \"\",\n    remarks: \"\"\n  },\n  {\n    // unit field\n    label: \"Unit\",\n    search: null,\n    tensile_strength: \"Mpa\",\n    elongation_at_break: \"Tensile Strength\",\n    flexural_strength: \"Mpa\",\n    flexural_modulus: \"Mpa\",\n    izod_impact_strength: \"J/m2\",\n    heat_deflection_temp: \"℃\",\n    dielectric_strength: \"kV/mm\",\n    volume_resistivity: \"Ω·cm\",\n    density: \"g/cm3\",\n    melt_flow_rate: \"g/10min\",\n    molding_shrinkage: \"%\",\n    flammability_1_5mm: \"/\",\n    flammability_3_0mm: \"/\",\n    yellow_card: \"/\",\n    rti_elec: \"℃\",\n    rti_imp: \"℃\",\n    rti_str: \"℃\",\n    hwi: \"℃\",\n    hai: \"℃\",\n    cti: \"℃\",\n    outdoor_performance: \"/\",\n    ball_pressure_temp: \"℃\",\n    rohs: \"/\",\n    reach_svhc: \"/\",\n    quotation: \"\",\n    remarks: \"\"\n  },\n  {\n    // range field\n    label: \"Specifications\",\n    search: null,\n    tensile_strength: \"≥13\",\n    elongation_at_break: \"Tensile Strength\",\n    flexural_strength: \"≥15\",\n    flexural_modulus: \"≥800\",\n    izod_impact_strength: \"≥300\",\n    heat_deflection_temp: \"≥70\",\n    dielectric_strength: \"≥14\",\n    volume_resistivity: \"≥1E+14\",\n    density: \"0.80 - 1.25\",\n    melt_flow_rate: \"≥1.0\",\n    molding_shrinkage: \"≤1.8\",\n    flammability_1_5mm: \"V-0\",\n    flammability_3_0mm: \"5VA\",\n    yellow_card: \"/\",\n    rti_elec: \"≥80\",\n    rti_imp: \"≥80\",\n    rti_str: \"≥80\",\n    hwi: \"≤4\",\n    hai: \"≤3\",\n    cti: \"≤3\",\n    outdoor_performance: \"/\",\n    ball_pressure_temp: \"/\",\n    rohs: \"PASS\",\n    reach_svhc: \"PASS\",\n    quotation: \"\",\n    remarks: \"\"\n  }\n]\n\nWrite a multi-line fixed header based on this, using Element UI syntax, where each object corresponds to a row in the header.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the Element UI table header structure correctly implemented?",
+      "description": "Verify that the table header uses proper Element UI syntax with el-table and el-table-column components. The header structure should support the multi-line fixed header requirement with correct row spans and column spans. Each object in base_data should correspond to a row in the header.Deduct 5 points if the table structure is not using Element UI components, 5 points if fixed header functionality is not implemented, and 5 points if multi-line header configuration is incorrect. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Does the implementation correctly map all data from base_data to the table?",
+      "description": "Check whether all fields from the base_data array (including testing_project, testing_standards, testing_conditions, unit, and range specifications) are properly displayed in the table header. The implementation should handle all 23+ fields without omissions.Deduct 2 points for each missing field. Deduct 5 points if data mapping is inconsistent or illogical. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is proper alignment and styling applied to the table headers?",
+      "description": "Evaluate whether the table headers use appropriate alignment (text-align), padding, and styling to ensure readability. Headers should have consistent appearance with proper text wrapping for long content.Deduct 3 points for inconsistent text alignment, 3 points for improper padding or spacing, and 4 points if long text handling causes layout issues. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Does the implementation include proper fixed header functionality?",
+      "description": "Check if the table implements proper fixed header functionality when scrolling, ensuring that header remains visible while scrolling through data rows. Verify that the header-with-body alignment is maintained during horizontal scrolling.Deduct 5 points if fixed header functionality is not implemented, 3 points if header-body alignment issues occur during scrolling, and 2 points if there are performance issues with large datasets. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle potential issues such as missing data fields, null values, or empty strings. Check for error handling when data structure changes or when special characters appear in the data.Evaluate whether the code can handle common abnormal situations (such as null/undefined values, empty strings, etc.) and provide fallback mechanisms. 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. Column filtering/sorting 2. Responsive design for different screen sizes 3. Tooltip explanations for technical terms 4. Export functionality to CSV/Excel).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 ways to style the same element) 2. Function modules unrelated to the data display (e.g., unnecessary animations) 3. Fancy effects that affect performance (e.g., excessive DOM operations).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 component/style/logic), code reusability, and maintainability. Check if the implementation follows Vue/Element UI best practices.Deduct 5 points if global state pollution is found or component design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if proper Vue lifecycle hooks are not utilized. 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 with Element UI theme 2) Proper layout spacing and header heights 3) Consistent typography (font sizes, weights, etc.).Deduct 3 points for each crowded visual element, 5 points for inconsistent styling with Element UI standards, and 5 points for chaotic alignment of header content. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the table provides good user interaction: 1) Smooth scrolling performance 2) Responsive to screen resizing 3) Clear visual feedback for user interactions like sorting or filtering.Deduct 5 points for laggy scrolling performance with large datasets, 3 points for lack of responsive design considerations, and 5 points for missing user interaction feedback. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Education/Learning",
+  "difficulty": "easy"
+}

package/library/web_applications-education_learning/math-prize-wheel-for-students.json

@@ -0,0 +1,68 @@
+{
+  "index": 1817,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable when possible.\n\nI am a middle school math teacher who wants to reward students with excellent grades. Please help me create a prize wheel webpage with the following prizes: $5 cash, $10 cash, $20 cash, $50 cash, Study Master Time Manager, Error Correction Printer + Math Meme Tape, \"Genshin Impact\" Character Pencil Case + Function Coordinate Notebook + Draft Paper, Probability Question Mystery Box Pen, Honor of Kings Q-version Heroes + Sarcastic Quote Stickers. The webpage should have a cute style background that includes elements middle school students enjoy, with animation effects when the wheel spins.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the prize wheel core functionality fully implemented?",
+      "description": "Review whether the code accurately implements a spinning wheel mechanism through HTML5 Canvas/SVG and JavaScript, with proper physics-based deceleration and random/weighted result selection. Check if it includes prize highlighting when landing, and validation that prevents manipulation. Score 0 if the core spinning functionality is not implemented, 5 if basic spinning exists but lacks physics, and 10 if it includes realistic inertia, proper randomization, and anti-cheat mechanisms.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are all the specified prizes properly represented on the wheel?",
+      "description": "Evaluate whether all 9 required prizes ($5 cash, $10 cash, $20 cash, $50 cash, Study Master Time Manager, Error Correction Printer + Math Meme Tape, 'Genshin Impact' Character Pencil Case + Function Coordinate Notebook + Draft Paper, Probability Question Mystery Box Pen, Honor of Kings Q-version Heroes + Sarcastic Quote Stickers) are included on the wheel with equal or intentionally weighted probabilities. Deduct 1 point for each missing prize or if prizes are not clearly readable when the wheel is stationary. Full points require visually distinct prize segments with proper spacing.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the animation effect for the wheel spin implemented effectively?",
+      "description": "Check if the wheel animation includes smooth rotation transitions, proper easing functions (initial acceleration and gradual deceleration), audio feedback, and visual indicators during spinning. Score 3 points for basic rotation, 3 additional points for proper easing physics, 2 points for spinning sound effects, and 2 points for visual feedback (like sparkling effects or dynamic highlights). Ensure the animation runs at consistently smooth framerates (minimum 30 FPS).",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Does the implementation include a cute style background with middle school student appeal?",
+      "description": "Evaluate whether the background incorporates age-appropriate design elements that appeal to middle school students (gaming references, math symbols, colorful patterns, etc.). Background should be relevant to both prize themes (games like Genshin Impact/Honor of Kings and educational items) without overwhelming the main prize wheel. Deduct 5 points if the background is generic/stock, 3 points if it's too childish or too mature, and 3 points if it competes with or obscures the wheel functionality.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as rapid repeated clicks, browser resizing, touch vs. mouse interactions, etc.) and provide friendly error prompts or recovery mechanisms. 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. Confetti explosion for high-value prizes 2. Prize history tracking 3. Teacher controls for probability adjustment 4. Animated characters reacting to prizes 5. Math formula animations). Add 2 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) 2. Function modules unrelated to the prize wheel (e.g., unrelated games) 3. Fancy effects that affect performance (e.g., excessive particle systems that cause lag). 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 wheel logic/view/animation layers), code organization, and maintainability. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 3 points if variable naming is inconsistent or unclear. Check for browser compatibility across at least Chrome, Firefox and Safari. 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 with appropriate complementary colors) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional font system (body font size ≥ 16px, appropriately playful yet readable fonts). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic layout. 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) Spin button feedback delay ≤ 100ms 2) Wheel rotation animation should be fluid (60fps if possible) 3) Clear visual and audio guidance when a prize is won. Deduct 5 points for laggy spinning animations, 3 points for missing winner announcement effects, and 5 points for unresponsive or hard-to-find spin button. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Education/Learning",
+  "difficulty": "medium"
+}

package/library/web_applications-education_learning/merge-sort-visualization.json

@@ -0,0 +1,68 @@
+{
+  "index": 1020,
+  "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 demonstration purposes. Visualization of merge sort.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the merge sort algorithm correctly implemented?",
+      "description": "Check if the algorithm follows the correct divide-and-conquer approach with proper splitting and merging steps. Verify that the time complexity is O(n log n) and space complexity is O(n). Deduct 5 points if the core algorithm has logical errors, 3 points if edge cases are not handled (empty arrays, single elements), and 2 points if unnecessary operations affect performance. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Does the visualization clearly show each step of the merge sort process?",
+      "description": "Evaluate whether the visualization distinctly represents each phase: dividing the array, comparing elements, and merging the subarrays. There should be clear visual differentiation between unsorted elements, elements being compared, and sorted subarrays. Give 0 points if the core visualization logic is missing, 5 points if only basic steps are shown, and 10 points if all merge sort phases are comprehensively visualized.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the animation of the sorting process smooth and informative?",
+      "description": "Review whether the animation flows at an appropriate pace with controls for speed adjustment. Check if transitions between steps are smooth (not abrupt) and if key comparison and swap operations are highlighted. Deduct 5 points if animations are jerky or inconsistent, 3 points if speed controls are missing, and 2 points if transitions lack clarity. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Does the visualization include informative metrics and educational elements?",
+      "description": "Check if the implementation displays relevant metrics such as comparison count, array access count, current recursion depth, and time/space complexity explanations. Educational tooltips or explanatory text should help users understand the algorithm's operation. Deduct 3 points for each missing key metric, and award full 10 points only if comprehensive educational elements are included.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid input types, extremely large arrays, browser compatibility issues, etc.) and provide friendly error prompts or graceful degradation. 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. Multiple array generation options with different distributions 2. Side-by-side comparison with other sorting algorithms 3. Interactive mode allowing users to perform merge steps manually). 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 2. Function modules unrelated to merge sort or algorithm visualization 3. Fancy effects that affect performance without adding educational value. Deduct 3 points for each redundancy found, and directly deduct 10 points if the core visualization is interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating algorithm logic/visualization/UI controls), code reusability, and performance optimization. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the visualization stutters on arrays larger than 100 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) Harmonious color matching (logical color coding for different states) 2) Proper layout spacing (clear separation between controls and visualization area) 3) Professional font system (legible labels and explanatory text). Deduct 3 points for each crowded visual element, 5 points for confusing color schemes that don't aid understanding, and 5 points for poor arrangement of visualization components. 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) Responsive controls with immediate visual feedback 2) Appropriate animation timing that balances educational clarity with engaging pace 3) Clear visual indication of the current state of the algorithm. Deduct 5 points for laggy animations, 3 points for confusing transitions between steps, and 5 points for controls that don't clearly indicate their function. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Education/Learning",
+  "difficulty": "medium"
+}

package/library/web_applications-education_learning/mobile-fish-recognition-webpage-tabs.json

@@ -0,0 +1,68 @@
+{
+  "index": 1750,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate, professional responses. Be sure to create executable code for demonstration purposes whenever possible. I need to create a fish recognition webpage that is optimized only for mobile devices. It should include three bottom tabs: Recognition, Records, and Personal Center. Please provide appropriate HTML code.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the fish recognition feature fully implemented?",
+      "description": "Review whether the code effectively implements the fish recognition functionality through appropriate HTML, CSS, and JavaScript. Check for proper image upload capabilities, camera access for taking fish photos, and integration with recognition API or algorithm. Score 0 if no recognition elements are present, 5 if basic image upload is implemented but without processing logic, and 10 if complete end-to-end recognition with visual feedback is implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the tab navigation system properly implemented for mobile?",
+      "description": "Check whether the three-tab system (Recognition, Records, Personal Center) is properly implemented with appropriate mobile touch interactions, active state indicators, and smooth transitions between tabs. The tabs should be positioned at the bottom as specified, with proper sizing for mobile touch targets (minimum 44x44px). Deduct 5 points if tabs don't maintain state across content changes, 3 points if transition animations are missing, and 2 points if active states are not visually distinct. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the records/history management properly designed?",
+      "description": "Evaluate if the Records tab properly displays previous recognition results with timestamps, images, and identification details. Check for implementation of data persistence (localStorage, IndexedDB, or server-side storage), sorting/filtering capabilities, and the ability to view detailed information for each record. Deduct 5 points if no persistence mechanism exists, 3 points if sorting/filtering is absent, and 2 points if detailed view functionality is missing. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the personal center functionality properly implemented?",
+      "description": "Assess whether the Personal Center tab includes essential user management features such as profile settings, preferences, login/logout functionality, and possibly achievements or statistics related to fish recognition history. Verify if user data is properly managed and persisted. Deduct 3 points if profile customization is missing, 4 points if authentication features are absent, and 3 points if there's no integration with the recognition history. 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 image upload failures, recognition API errors, offline usage, or unexpected user inputs) and provide friendly error prompts or recovery mechanisms. 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. AR fish identification overlay 2. Social sharing with animated previews 3. Gamification elements for frequent recognition). 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 image processing methods coexisting) 2. Function modules unrelated to fish recognition (e.g., a built-in game) 3. Fancy effects that affect mobile performance (e.g., heavy animations on low-end devices). 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 recognition logic/view/data layers), responsive design implementation, and mobile optimization techniques. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if performance optimization for mobile devices is missing (e.g., no image compression before upload). The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional mobile design standards?",
+      "description": "Evaluate whether the overall design follows modern mobile design principles: 1) Touch-friendly elements (minimum tap target size of 44x44px) 2) Proper layout spacing for mobile (safe areas accounting for notches and home indicators) 3) Mobile-optimized typography (readable font sizes, minimum 16px for body text). Deduct 3 points for non-touch-friendly elements, 5 points for layouts that extend into unsafe areas, and 5 points for text that requires zooming to read. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the mobile interaction smooth and optimized?",
+      "description": "Judge whether the mobile interactions are optimized for touch devices: 1) Fast tap response ≤ 100ms 2) Proper keyboard handling for form inputs 3) Support for mobile gestures (swipe between tabs, pinch-zoom for fish images). Deduct 5 points for each operation without feedback, 3 points for keyboard issues that obscure the interface, and 5 points for missing essential mobile gestures. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Education/Learning",
+  "difficulty": "hard"
+}

package/library/web_applications-education_learning/movie-information-page-with-dynamic-effects.json

@@ -0,0 +1,68 @@
+{
+  "index": 496,
+  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Try to ensure that the generated code is executable for demonstration.\n\n## Role\nYou are an experienced code expert. I'm providing you with a software development requirement description, and I need you to generate project code based on these requirements. Strictly follow the rules to help users generate complete project code with simple and easy-to-understand comments. Don't output anything else.\n\n## Output Rules\n1. You should always generate complete, runnable project code. Please ensure the project is complete and executable\n2. Ensure all code files you output are complete, don't omit any code\n3. Carefully review and check all code before final output, evaluating its executability. If the code cannot be executed or contains errors, it needs to be regenerated\n4. If the requirements involve external API access needs or require the use of user data (images, videos, audio, etc.), please provide simulated data\n\n## Project Requirements Description\nWrite code to implement a movie information page. The left side of the page is a movie category list, and the right side is a popular movie poster display area. Posters are arranged in an irregular puzzle form. When the mouse hovers over a poster, a white border appears around the poster with a scaling effect. Clicking on the poster enters the movie details page, which includes embedded movie trailer videos, plot introduction, cast list, and other content. The page background is a dynamic mix of starry sky and film strip effects.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the movie category list on the left side properly implemented?",
+      "description": "Evaluate whether the category list includes common movie genres (at least 8 categories like Action, Comedy, Drama, etc.). Check if the list has proper styling (consistent font, appropriate spacing, clear visual hierarchy). Verify that the active/selected category is visually distinct. Check if the list is responsive to different screen sizes. Score 0 if missing, 5 if basic implementation without interaction, 10 if fully implemented with proper styling and interaction.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the irregular puzzle layout for movie posters correctly implemented?",
+      "description": "Check if movie posters are arranged in a visually appealing irregular puzzle layout (not just a standard grid). Verify that the layout is responsive and maintains its aesthetic quality across different screen sizes. The implementation should use CSS Grid or a combination of positioning techniques. Deduct 5 points if the layout is just a standard grid, 3 points if the layout breaks on certain screen sizes. Give 10 points if the layout is truly irregular, aesthetically pleasing, and responsive.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Are hover effects on movie posters properly implemented?",
+      "description": "Evaluate whether posters have the specified hover effects: white border appears AND scaling effect is present. Transitions should be smooth (300-500ms). Verify that the effects don't cause layout shifts or interfere with other elements. Deduct 5 points if only one effect is implemented, 3 points if transitions are jerky or cause layout issues. Full score for smooth, properly implemented hover effects with both required features.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the movie details page functionality complete?",
+      "description": "Check if clicking a poster properly navigates to a details page. Verify the details page contains: embedded trailer video (functional player), plot introduction, cast list, and other relevant movie information. Navigation should be smooth with proper state management. Deduct 5 points if video embedding is missing/broken, 3 points if cast information is incomplete, and 3 points if navigation causes page reloads instead of using client-side routing. Give 10 points for complete implementation with smooth transitions.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as missing poster images, failed API calls, incorrect data formats, etc.) and provide friendly error prompts or recovery mechanisms. 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. Animated transitions between pages 2. Movie rating/review system 3. Personalized recommendation feature 4. Theme customization options). 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 ways to load movie data) 2. Function modules unrelated to movie information display (e.g., unnecessary social media features) 3. Fancy effects that affect performance (e.g., excessive animations that slow down page loading). 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 components, services, and styles), code organization, and build process. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the build process is not automated or documented. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Is the dynamic starry sky and film strip background implemented professionally?",
+      "description": "Evaluate whether the background successfully creates a cinematic atmosphere with starry sky and film strip effects. Check if animations are smooth without causing performance issues. The background should be subtle enough not to distract from the main content. Deduct 5 points if only one effect is implemented (either stars or film strip), 3 points if animations cause performance issues, and 5 points if the background overwhelms the content. 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) Transition animation duration controlled between 300-500ms 3) Clear visual focus guidance. Deduct 5 points for each operation without feedback, 3 points for visual after-images during fast interactions, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Education/Learning",
+  "difficulty": "easy"
+}

package/library/web_applications-education_learning/multilayer-perceptron-animation-explanation.json

@@ -0,0 +1,68 @@
+{
+  "index": 215,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to provide executable code for demonstration. Help me create an animation explaining the principles of multilayer perceptron using HTML+CSS+JS. Focus only on the animation explanation.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the multilayer perceptron structure accurately visualized?",
+      "description": "Review whether the code correctly renders the MLP architecture through HTML/CSS/JavaScript, including input layer, hidden layers, and output layer with proper node representation. Check if neuron connections (weights) are visually displayed with appropriate styling. Score 0 if basic network structure is missing, 5 if only simple nodes are shown without connections, and 10 if complete MLP topology with weighted connections is accurately represented.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the forward propagation process animated effectively?",
+      "description": "Evaluate whether the animation demonstrates signal flow from input to output layers, showing data transformation at each layer. Check if activation functions are visually represented and if the propagation timing is educational. Deduct 5 points if layer-by-layer processing is not shown, and 3 points if activation function visualization is missing. Full score requires clear step-by-step forward pass animation.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Are the mathematical concepts properly illustrated?",
+      "description": "Check whether key MLP principles are visually explained: weighted sum calculations, bias addition, and activation function application. Evaluate if mathematical formulas are displayed alongside animations. Deduct 5 points if weight multiplication is not visualized, 3 points if bias terms are ignored, and 5 points if activation functions lack mathematical representation. Full implementation scores 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the educational flow and interaction design comprehensive?",
+      "description": "Assess whether the animation provides educational value with proper pacing, step controls, and explanatory text. Check for features like play/pause, step-by-step mode, and parameter adjustment capabilities. Deduct 5 points if no user controls are provided, 3 points if explanatory text is insufficient, and 5 points if the learning progression is unclear. Award full points for comprehensive educational experience.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid input values, animation state conflicts, browser compatibility issues, etc.) and provide friendly error prompts or recovery mechanisms. 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 learning experience (e.g., 1. Real-time parameter tweaking with instant visual feedback 2. Multiple dataset examples with different behaviors 3. Interactive weight adjustment sliders 4. Comparative visualization of different activation functions). 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 animation logic or duplicate visual elements 2. Function modules unrelated to MLP explanation (e.g., unrelated mathematical concepts) 3. Overly complex effects that distract from learning (e.g., excessive particle effects or decorative animations). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core educational purpose is interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating animation logic/rendering/mathematical computation), code organization, and maintainability. Deduct 5 points if global state pollution is found or proper class/module structure is not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 3 points if inconsistent coding style is observed. 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 educational visualization principles: 1) Harmonious color coding for different layer types (no more than 4 primary colors) 2) Proper spacing and proportions for network visualization 3) Professional typography for mathematical notation and labels (font size ≥ 14px, clear mathematical symbols). Deduct 3 points for each cluttered visual element, 5 points for poor color contrast affecting readability, and 5 points for unclear mathematical notation. 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 educational presentation standards: 1) Smooth transitions between animation states ≤ 300ms delay 2) Animation duration appropriate for learning (2-5 seconds per forward pass) 3) Clear visual focus and highlighting of active components. Deduct 5 points for each jarring transition, 3 points for animations too fast to follow educationally, and 5 points for unclear visual emphasis on active network components. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Education/Learning",
+  "difficulty": "hard"
+}

package/library/web_applications-education_learning/music-player-with-vuejs-and-ssm.json

@@ -0,0 +1,68 @@
+{
+  "index": 1540,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to ensure the generated code is executable for demonstration purposes. I've created a frontend-backend separated project in IntelliJ IDEA with Vue for the frontend and SSM for the backend. Please implement the complete code for a music player that can read and play MP3 files from a local folder, and specify which code should be created in which folder.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the music file scanning and loading system fully implemented?",
+      "description": "Review whether the backend code properly implements file system scanning for MP3 files, handling file metadata extraction (ID3 tags), and provides a well-designed API for the frontend to access. Check for proper error handling for invalid files, large directories, and potential security issues. Score 0 if file scanning is not implemented, 5 if only basic file listing is available, and 10 if complete metadata extraction and efficient file handling are included.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the audio playback functionality complete?",
+      "description": "Evaluate whether the Vue frontend implements all necessary playback functions: play, pause, stop, seek, volume control, and track navigation. The component should handle audio state management correctly and provide visual feedback on the current playback state. Deduct 3 points if seeking functionality is missing, 3 points for missing volume controls, and 5 points if playback state management is buggy. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the backend-frontend communication properly implemented?",
+      "description": "Check whether the SSM backend provides proper RESTful APIs for file access and streaming, with appropriate error handling, caching strategies, and security measures. Evaluate if the Vue frontend correctly communicates with these endpoints using axios or similar libraries, with proper loading states and error handling. Deduct 5 points if streaming is inefficient (loading entire MP3 files at once), 3 points for missing error handling, and 3 points for not implementing proper cache controls. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the music player UI/UX well-designed?",
+      "description": "Assess whether the player interface follows modern design patterns with intuitive controls, responsive layout, and clear visual feedback. Check if the player implements a playlist view, album artwork display, and track information panel. Deduct 3 points for missing playlist functionality, 3 points for poor mobile responsiveness, and 5 points for confusing navigation or controls. 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 files, corrupted MP3s, network interruption, user operation errors, etc.) and provide friendly error prompts or recovery mechanisms. 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. Audio visualization/equalizer 2. Smart playlists based on genre/mood 3. Audio effects like fade in/out, equalizer). 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 audio playing engines) 2. Function modules unrelated to music playing (e.g., a built-in calendar) 3. Fancy effects that affect performance (e.g., excessive animations that slow down the UI). 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 audio logic/UI components/API services), unit test coverage, and build process automation. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the build process is not automated. 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 layout spacing (element spacing follows the 8px multiple principle) 3) Professional font system (body font size ≥ 14px, line height over 1.5 times). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic text-image layout. 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) Transition animation duration controlled between 300-500ms 3) Clear visual focus guidance. Deduct 5 points for each operation without feedback, 3 points for visual after-images during fast sliding, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Education/Learning",
+  "difficulty": "medium"
+}

package/library/web_applications-education_learning/nodejs-webpage-amap-weather-aqi-data.json

@@ -0,0 +1,68 @@
+{
+  "index": 962,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and expert responses. Be sure to produce executable code whenever possible. Design a webpage using Node.js that displays weather data from the Amap (Gaode) API, along with AQI (Air Quality Index) data retrieved from two different APIs.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the Amap (Gaode) API integration correctly implemented?",
+      "description": "Review whether the code properly integrates Amap weather API with correct authentication, parameter handling, and data parsing. Check if the API key is properly configured, request parameters include necessary fields (city, extensions, output format), and response data is correctly parsed and validated. Score 0 if API integration is non-functional, 5 if basic weather data is retrieved but with errors, and 10 if complete weather information is accurately fetched with proper error handling.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are dual AQI data sources successfully integrated and compared?",
+      "description": "Evaluate whether the code successfully retrieves AQI data from two different APIs (such as Amap and another provider like Waqi or government APIs), implements proper data synchronization, and handles potential discrepancies between sources. Check for concurrent API calls, data normalization, and fallback mechanisms. Deduct 5 points if only one AQI source works, 3 points if data comparison logic is missing, and 2 points if no fallback mechanism exists. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the Node.js backend architecture properly structured?",
+      "description": "Check whether the Node.js server implements proper routing structure, middleware for error handling, API rate limiting, and caching mechanisms. Evaluate if the server uses appropriate frameworks (Express.js), implements CORS handling, and has proper separation of concerns. Deduct 5 points if no caching strategy is implemented, 3 points if rate limiting is missing, and 2 points if error middleware is absent. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is real-time data updating and state management implemented?",
+      "description": "Assess whether the system implements automatic data refresh mechanisms, handles API rate limits intelligently, and maintains data consistency across multiple API sources. Check for implementation of polling strategies, WebSocket connections for real-time updates, or scheduled data fetching. Deduct 5 points if no auto-refresh mechanism exists, 3 points if rate limiting is not respected, and 2 points if stale data issues are not addressed. 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 API failures, network timeouts, invalid responses, rate limit exceeded, malformed data, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should include try-catch blocks, input validation, graceful degradation, and user-friendly error messages. Give 10 points if fully robust, 5 points if average robustness, and 0 points if no exception handling exists.",
+      "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 user experience (e.g., 1. Weather forecast visualization charts 2. Historical weather data comparison 3. Location-based weather alerts 4. Weather data export functionality 5. Interactive weather maps). 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 weather data fetching mechanisms) 2. Function modules unrelated to weather display (e.g., built-in games or unrelated widgets) 3. Excessive animations or effects that impact performance. Deduct 3 points for each redundancy found, and directly deduct 10 points if core weather functionality is interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating API services, data processing, and presentation layers), configuration management, logging implementation, and deployment readiness. Deduct 5 points if environment variables are not used for API keys; deduct 5 points if no logging mechanism exists; deduct 5 points if code structure is monolithic without proper separation. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the weather data display follows modern design principles: 1) Harmonious color scheme suitable for weather themes 2) Proper information hierarchy with clear data visualization 3) Professional typography (readable font sizes ≥ 14px, appropriate line spacing) 4) Responsive design for different screen sizes. Deduct 3 points for each cluttered visual element, 5 points for poor color contrast affecting readability, and 5 points for chaotic data layout. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the weather data interactions provide good user experience: 1) Data loading states with appropriate spinners or skeletons 2) Smooth transitions between different weather views 3) Responsive interactions ≤ 100ms 4) Clear visual feedback for user actions 5) Intuitive navigation between weather information sections. Deduct 5 points for each missing loading state, 3 points for jarring transitions, and 5 points for unclear data presentation. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Education/Learning",
+  "difficulty": "hard"
+}