@getollie/cli 0.0.1

package/library/data_science-data_visualization_dashboards/g2-well-logging-curves-frontend-page.json

@@ -0,0 +1,68 @@
+{
+  "index": 1773,
+  "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. Write a front-end page for well logging curves using G2.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the well logging curve visualization implementation complete?",
+      "description": "Review whether the code accurately implements well logging curve visualization with G2, including proper data binding, axis configuration, and curve rendering. Evaluate the inclusion of essential well logging curve types (e.g., gamma ray, resistivity, density, neutron). Score 0 if core visualization is absent, 5 if only basic curves are implemented, and 10 if multiple curve types with correct scaling are fully supported.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the depth track and scale system properly implemented?",
+      "description": "Check if the code includes a proper depth track with configurable units (meters/feet), major/minor grid lines, and depth labels. Evaluate whether depth scale adjustments (zoom in/out, scrolling) are implemented with proper handling of data windowing. Deduct 5 points if depth track is missing or static, 3 points if depth scaling is inflexible, and 2 points if grid lines are improperly spaced.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Are curve interactions and data analysis tools provided?",
+      "description": "Evaluate the implementation of interactive features such as curve value display on hover/click, curve comparison tools, crosshair functionality, and data point selection. Check whether analysis tools like curve averaging, min/max identification, or interval statistics are available. Score 0 if no interactions exist, 5 for basic hover information, and 10 for comprehensive analysis capabilities.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is there track management and multi-curve display functionality?",
+      "description": "Review whether the code supports multiple track displays with proper layout management, curve overlay capabilities, and track resizing/reordering. Check if curve visibility toggling is implemented and if the code handles different curve scales within the same track. Deduct 5 points if multiple tracks aren't supported, 3 points if track management is limited, and 2 points if curve overlays aren't properly handled.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as missing data points, irregular data intervals, extremely large/small values, 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. Real-time curve data updates 2. Advanced filtering options for noise reduction 3. Formation tops overlay 4. Lithology visualization). 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 scale curves) 2. Function modules unrelated to well logging (e.g., a built-in calculator) 3. Fancy effects that affect performance (e.g., excessive animations). 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/visualization/UI components), code organization, and potential for extension. 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 there's no clear separation between G2 configuration and business logic. 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 appropriate curve color distinction 2) Proper layout spacing with clear track separation 3) Professional labeling system with readable fonts (≥ 12px, proper contrast). Deduct 3 points for each overlapping visual element, 5 points for poor curve color selection making curves difficult to distinguish, and 5 points for unclear or missing axis labels. 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) Smooth scrolling/zooming of log data 2) Responsive curve highlighting/selection 3) Clear visual indicators for interactive elements. Deduct 5 points for laggy scrolling/zooming, 3 points for delayed curve value display on interaction, and 5 points for missing visual feedback on user actions. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "easy"
+}

package/library/data_science-data_visualization_dashboards/generate-bar-charts-age-education-from-spreadsheet.json

@@ -0,0 +1,68 @@
+{
+  "index": 1585,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to provide executable code in your demonstrations. According to the spreadsheet data, automatically generate a bar chart for age groups and a bar chart for education levels.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the data processing logic correctly implemented?",
+      "description": "Review whether the code correctly extracts and processes age groups and education levels from the spreadsheet data. Check if data aggregation functions (count, average, groupBy) are implemented properly. Score 0 if data extraction is missing, 5 if basic extraction exists but with errors, and 10 if data processing is complete and handles edge cases (empty cells, invalid data types, etc.).",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are the bar charts properly implemented with appropriate visualization libraries?",
+      "description": "Evaluate whether suitable visualization libraries (D3.js, Chart.js, Highcharts, etc.) are used correctly. Check if the API calls follow best practices and if the library features are utilized effectively. Deduct 5 points if the library implementation is overly complex or verbose, and 3 points if advanced features like responsiveness are missing. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Are both charts (age groups and education levels) properly configured?",
+      "description": "Check if both charts are properly configured with appropriate scales, labels, titles, and legends. Verify that categorical data for age groups and education levels is handled correctly. Deduct 5 points if one chart is missing or severely incomplete, and 3 points for each chart with missing essential elements (axis labels, titles). The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the data-to-visualization binding automatic and responsive?",
+      "description": "Assess whether the charts automatically update when data changes and if there's a clear connection between the spreadsheet data and visualization. Check for proper event listeners or reactive frameworks. Deduct 5 points if manual intervention is needed for updates, and 3 points if the binding exists but has performance issues with larger datasets. 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, incorrect data types, empty spreadsheets, 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. Interactive tooltips with detailed information 2. Animation transitions when data updates 3. Additional statistical analysis visualizations). 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 chart generation 3. Fancy effects that affect performance (e.g., excessive animations or 3D effects that don't add value). 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/visualization/UI layers), code reusability for both charts, and proper error handling. 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 there's no separation between data and presentation layers. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the chart design follows modern data visualization principles: 1) Appropriate color scheme with sufficient contrast 2) Proper spacing between chart elements 3) Professional typography with readable labels and legends. Deduct 3 points for each cluttered visual element, 5 points for poor color choices that hinder data interpretation, and 5 points for illegible text or improper label positioning. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the chart interaction smooth and intuitive?",
+      "description": "Judge whether the charts provide useful interactivity: 1) Hover tooltips with relevant data 2) Possible filtering or sorting options 3) Clear visual feedback for user interactions. Deduct 5 points for non-interactive charts, 3 points for laggy interactions, and 5 points for confusing or unintuitive interaction patterns. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "easy"
+}

package/library/data_science-data_visualization_dashboards/goldencutchart-drilling-speed-footage-trendline.json

@@ -0,0 +1,68 @@
+{
+  "index": 1010,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be careful to ensure that the generated code is executable for display. Plot the X and Y values on a chart control named GoldenCutChart, and draw a trend line for these points. The x-axis title should be \"Mechanical Drilling Speed m/h\" and the y-axis title should be \"Single Drill Bit Footage m\".",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the chart properly initialized with correct structure?",
+      "description": "Examine whether the code initializes a chart with proper canvas/SVG elements, sets up dimensions correctly, and includes appropriate margins. The chart should have a defined container with proper styling. Deduct 5 points if responsive design is missing, 3 points if the chart lacks proper sizing attributes, and 5 points if basic structure is incomplete.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are the X and Y axes correctly implemented with proper titles?",
+      "description": "Verify that axes are properly scaled, labeled with \"Mechanical Drilling Speed m/h\" for X-axis and \"Single Drill Bit Footage m\" for Y-axis. Check if font size, style, and positioning of titles are appropriate. Deduct 3 points for missing/incorrect titles, 2 points for poorly scaled axes, and 3 points for improper tick formatting.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the data visualization (points) correctly implemented?",
+      "description": "Evaluate whether data points are properly plotted with appropriate markers (circles, squares, etc.), sizes, and colors. Check if the points are correctly positioned based on X and Y coordinates. Deduct 5 points if points are missing or incorrectly plotted, 3 points for poor marker choice/styling, and 2 points for missing hover effects.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the trend line properly calculated and displayed?",
+      "description": "Assess whether a proper algorithm (linear regression, etc.) is used to calculate the trend line, and whether it's correctly rendered on the chart. Check if the trend line color/style differs from data points for clarity. Deduct 5 points if the trend line calculation is incorrect, 3 points if styling is poor, and 5 points if the trend line is missing.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as empty data sets, outliers, different screen sizes, 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. Interactive tooltips showing exact values 2. Animation when loading data 3. Zoom/pan functionality for exploring data). 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 the chart (e.g., unnecessary UI elements) 3. Fancy effects that affect performance (e.g., excessive animations). 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/visualization/interaction layers), code reusability, and implementation elegance. 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 code lacks comments or is poorly organized. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the chart follows modern visualization principles: 1) Harmonious color scheme (no more than 3 primary colors) 2) Proper spacing and alignment (consistent margins and padding) 3) Professional typography (clear, readable font sizes and styles). Deduct 3 points for poor color choices, 3 points for inconsistent spacing, and 4 points for unprofessional typography. 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: 1) Responsive hover/click interactions with feedback ≤ 100ms 2) Smooth transitions when updating data or resizing 3) Clear focus states for interactive elements. Deduct 4 points for laggy interactions, 3 points for abrupt transitions, and 3 points for confusing interactive elements. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "easy"
+}

package/library/data_science-data_visualization_dashboards/grade-distribution-and-change-charts.json

@@ -0,0 +1,68 @@
+{
+  "index": 697,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the code you generate is executable for demonstration. Based on three years of grades, generate HTML code to display bar charts showing grade distribution across score ranges and line graphs illustrating grade changes over the years.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the data visualization for bar charts properly implemented?",
+      "description": "Evaluate whether the HTML/CSS/JavaScript code correctly implements bar charts showing grade distribution across score ranges. Check for proper axis labeling, consistent scaling, appropriate color usage, and clear visual representation of data. Score 0 if bar charts are missing, 5 if implemented with basic functionality but lacking proper styling or labels, and 10 if fully implemented with professional appearance.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the line graph functionality for grade changes over years implemented correctly?",
+      "description": "Assess the implementation of line graphs showing grade changes over the three years. Verify that the data points are accurately plotted, lines are properly connected, and trend visualization is clear. Check for proper axis scaling, year labeling, and data point markers. Deduct 5 points if the line graph lacks smoothing or animation, and 3 points if hover states for data points are missing. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the data handling and processing logic complete?",
+      "description": "Review the code's ability to process and transform the three years of grade data into appropriate formats for visualization. Check for proper aggregation functions for calculating distributions, statistical summaries (mean, median, etc.), and data normalization. Deduct 5 points if the code doesn't handle different data scales appropriately, and 3 points if it lacks validation for input data. Full score is 10 points if data processing is comprehensive and efficient.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the visualization responsive and interactive?",
+      "description": "Evaluate whether the visualization provides interactive elements such as tooltips, highlighting on hover, zoom functionality, or filtering options. Check if the charts resize properly on different screen sizes. Deduct 5 points if basic interactivity is missing (like tooltips), and 3 points if the visualization breaks on mobile screens. Award 10 points for fully responsive design with rich interactive features.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common edge cases (such as missing data points, extreme values, zero values, etc.) and provide graceful error handling with user-friendly messages. Code with strong robustness should be able to effectively handle these abnormal situations, giving 10 points. If the robustness is average, give 5 points, and if no error handling is implemented, 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 data views 2. Dynamic color coding based on performance thresholds 3. Comparative analysis tools). 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 chart libraries used for the same purpose) 2. Function modules unrelated to grade visualization (e.g., irrelevant widgets) 3. Heavy visual effects that affect performance (e.g., unnecessary 3D effects or animations). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core visualization 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/visualization/interaction layers), reusability of components, and performance optimization. Deduct 5 points if global namespace pollution is found; deduct 5 points if the code has high duplication rate (over 30%); deduct 5 points if no performance optimization is implemented for large datasets. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional data visualization standards?",
+      "description": "Evaluate whether the visualization follows data visualization best practices: 1) Appropriate color palette that distinguishes data series clearly 2) Proper chart proportions (aspect ratio between 4:3 and 16:9) 3) Consistent typography system (legends, axes, and labels follow hierarchical font sizing). Deduct 3 points for cluttered visualizations, 5 points for misleading visual representations (e.g., truncated axes), and 5 points for poor information hierarchy. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and informative?",
+      "description": "Judge whether the interactive elements enhance data understanding: 1) Smooth transitions between data views (≤ 500ms) 2) Informative tooltips that show exact values 3) Clear visual feedback on user interactions. Deduct 5 points for jerky animations, 3 points for delayed response on interaction (> 200ms), and 5 points for confusing or missing interaction cues. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "easy"
+}

package/library/data_science-data_visualization_dashboards/healthcare-big-data-dashboard-vue-echarts.json

@@ -0,0 +1,68 @@
+{
+  "index": 1173,
+  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Be sure to provide executable code when possible. Design a healthcare big data dashboard using Vue and ECharts, with visual displays including key indicators, line charts, column charts, pie charts, etc. The displayed data should include outpatient and emergency visits, inpatient admissions, surgical procedures, medical business income, proportion of discharged patients undergoing surgery, tertiary and quaternary surgical volume, bed utilization rate, average outpatient medication cost, average inpatient medication cost, average length of stay, outpatient and emergency visits at main and branch hospitals, etc. Ensure the page layout and formatting are well-optimized.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the Vue framework architecture properly implemented with component modularity?",
+      "description": "Review whether the code correctly uses Vue 3 composition API or Vue 2 options API with proper component structure. Check if dashboard components are properly modularized (header, sidebar, chart containers, data panels). Verify proper use of Vue reactivity system for data binding and state management (Vuex/Pinia). Score 0 if basic Vue structure is missing, 5 if only basic components exist without proper data flow, and 10 if full Vue ecosystem is properly implemented with reactive data management.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are ECharts visualizations comprehensively implemented for all required healthcare metrics?",
+      "description": "Evaluate whether all specified chart types are implemented: line charts (for trends like visits over time), column charts (for comparative data), pie charts (for proportional data like surgery types), and key indicator cards. Check if charts display all required healthcare data: outpatient/emergency visits, inpatient admissions, surgical procedures, medical income, bed utilization rates, medication costs, length of stay, etc. Deduct 5 points if more than 3 required metrics are missing, 3 points for each chart type not implemented. Full score requires all 10+ healthcare indicators properly visualized.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the data structure design and mock data realistic for healthcare scenarios?",
+      "description": "Check whether the data structure accurately reflects real healthcare data patterns with proper data types, ranges, and relationships. Verify mock data includes realistic values (e.g., bed utilization 70-95%, average stay 3-15 days, surgery ratios 15-40%). Evaluate data update mechanisms and whether charts respond to data changes. Deduct 5 points if data structure is overly simplified, 3 points if mock data values are unrealistic, 5 points if no data update mechanism exists. Full implementation should include time-series data and proper data relationships.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the dashboard layout and responsive design professionally executed?",
+      "description": "Assess whether the dashboard uses a professional grid layout system (12-column or CSS Grid) with proper responsive breakpoints. Check if the layout adapts to different screen sizes (desktop, tablet, mobile) while maintaining chart readability. Verify proper use of Vue layout components and CSS frameworks. Deduct 5 points if layout breaks on mobile devices, 3 points if charts don't resize properly, 5 points if no responsive design is implemented. Full score requires seamless multi-device compatibility.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust with proper error handling and edge cases?",
+      "description": "Evaluate whether the code can handle common abnormal situations (API failures, empty data sets, chart rendering errors, browser compatibility issues) and provide friendly error prompts or fallback mechanisms. Check for proper try-catch blocks, loading states, and graceful degradation. Code with strong robustness should handle data loading failures, chart initialization errors, and provide meaningful user feedback. Give 10 points if fully implemented, 5 points if basic error handling exists, 0 points if no exception handling.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there innovative features that enhance the healthcare dashboard experience?",
+      "description": "Check whether the code includes valuable features beyond basic requirements (e.g., 1. Interactive drill-down capabilities for detailed metrics 2. Real-time data refresh with WebSocket connections 3. Export functionality for reports 4. Advanced filtering and date range selection 5. Comparative analysis tools 6. Alert thresholds for critical metrics). Add 2 points for each practical innovative feature implemented (maximum 10 points). Features must be healthcare-specific and add genuine value.",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features or unnecessary complexity?",
+      "description": "Strictly check three types of redundancy: 1. Redundant chart implementations (e.g., multiple similar line chart components) 2. Unnecessary UI libraries or plugins that don't add value 3. Over-engineered animations or effects that slow down dashboard performance 4. Duplicate data processing logic. Deduct 3 points for each redundancy found, and directly deduct 10 points if core dashboard functionality is negatively impacted by redundant code or excessive dependencies.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code demonstrate high engineering quality and best practices?",
+      "description": "Review Vue component composition, proper separation of concerns (components/services/utilities), code organization, and build configuration. Check for proper use of Vue lifecycle hooks, computed properties, and watchers. Evaluate code reusability and maintainability. Deduct 5 points if components are not properly separated or props/events are misused; deduct 3 points if no build optimization (like code splitting) is implemented; deduct 5 points if coding standards are inconsistent. Full score requires professional-grade Vue architecture.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the visual design meet healthcare dashboard professional standards?",
+      "description": "Evaluate whether the design follows healthcare dashboard conventions: 1) Medical-appropriate color scheme (blues, greens, clean whites) avoiding alarming colors except for alerts 2) Proper information hierarchy with clear section divisions 3) Consistent spacing using 8px grid system 4) Professional typography (minimum 14px for data labels, proper contrast ratios for accessibility) 5) Clean, clinical aesthetic appropriate for medical professionals. Deduct 3 points for each cramped visual section, 5 points for inappropriate color choices, 5 points for poor information hierarchy.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Are the interactive elements smooth with appropriate healthcare workflow considerations?",
+      "description": "Judge whether interactions are optimized for healthcare professionals: 1) Chart hover effects display detailed medical data within 100ms 2) Smooth transitions between different time periods or data views (300-500ms) 3) Clear visual feedback for all interactive elements 4) Intuitive navigation that supports quick data analysis workflows 5) Proper loading states for data-heavy operations. Deduct 5 points for each unresponsive interaction, 3 points for confusing navigation patterns, 5 points if critical data is hard to access quickly.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "easy"
+}

package/library/data_science-data_visualization_dashboards/hebei-digital-economy-residential-consumption-dashboard.json

@@ -0,0 +1,68 @@
+{
+  "index": 1755,
+  "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 demonstration. Please help me create a comprehensive data dashboard for studying the impact of the digital economy on residential consumption in Hebei Province. It should include international internet users, registered population, and digital economy index. Output in HTML format and ensure the code is operational.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the dashboard data visualization system fully implemented?",
+      "description": "Review whether the code accurately implements essential visualizations (charts, graphs, tables) for digital economy metrics and residential consumption data specific to Hebei Province. Score 0 if no visualization components are implemented, 5 if only basic charts without interactivity are included, and 10 if the dashboard contains comprehensive, interactive visualizations with proper labeling and legends.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are all required data components and metrics incorporated?",
+      "description": "Check whether the dashboard includes all specified data points: international internet users, registered population, and digital economy index for Hebei Province. Deduct 3 points for each missing metric. The visualization should properly contextualize these metrics in relation to residential consumption. If relationships between metrics aren't visually demonstrated, deduct 5 points. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is there an effective data filtering and comparison mechanism?",
+      "description": "Evaluate whether the dashboard provides tools for filtering data by time periods, regions within Hebei, or demographic segments. Check if comparison features allow contrasting different metrics or time periods. Deduct 3 points if filtering is limited to basic options, 5 points if comparison functionality is missing, and 5 points if historical trend analysis is not possible. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Does the dashboard include appropriate data visualization techniques for economic analysis?",
+      "description": "Assess whether the code utilizes appropriate visualization types for economic data (line charts for trends, bar charts for comparisons, choropleth maps for regional distribution, etc.). Evaluate if correlation plots or regression analysis visualizations are included to show relationships between digital economy and consumption. Deduct 5 points if visualization types are inappropriate for the data, and 5 points if advanced analytical visualizations are missing. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as missing data, data loading errors, 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 experience (e.g., 1. Predictive modeling visualizations 2. AI-driven insights highlighting 3. Interactive scenario planning tools). 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 visualizations showing the same data in different formats without adding value 2. Unnecessary decorative elements that distract from the data 3. Resource-intensive animations or effects that slow dashboard performance without analytical benefit. Deduct 3 points for each redundancy found, and directly deduct 10 points if the core economic analysis 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/visualization/UI components), code reusability, and optimization for dashboard performance. Deduct 5 points if global variable pollution is found; deduct 5 points if visualization libraries are implemented inconsistently; deduct 5 points if the code doesn't optimize for data loading and rendering performance. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the dashboard design follows data visualization best practices: 1) Appropriate color schemes for data encoding (colorblind-friendly, sequential/diverging palettes) 2) Proper information hierarchy and layout (most important metrics prominently displayed) 3) Clear typography system with appropriate sizing for headlines, labels, and values. Deduct 3 points for cluttered visualizations, 5 points for misleading visual encodings, and 5 points for poor information architecture. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the dashboard interactions support effective data exploration: 1) Tooltips appear within 100ms on hover 2) Filter/selection changes reflect within 500ms 3) Smooth transitions when updating visualizations. Deduct 5 points for each interaction without visual feedback, 3 points for sluggish responses when filtering large datasets, and 5 points for confusing navigation between dashboard sections. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "easy"
+}

package/library/data_science-data_visualization_dashboards/html-chartjs-cylindrical-fairing-display.json

@@ -0,0 +1,68 @@
+{
+  "index": 1752,
+  "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. Use HTML and Chart.js to create a cylindrical fairing with a base diameter of 2 centimeters and a height of 8 centimeters.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the cylindrical fairing accurately visualized with correct dimensions?",
+      "description": "Examine whether the code correctly implements a cylindrical fairing with the specified dimensions (2cm diameter base, 8cm height). Check if the visualization maintains proper proportions and perspective. Score 10 points if dimensions are precisely implemented with proper scaling, 5 points if there are minor proportion issues, and 0 points if the dimensions are significantly inaccurate.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Does the implementation use Chart.js appropriately for 3D visualization?",
+      "description": "Evaluate how effectively Chart.js is utilized to create the 3D cylindrical effect. Since Chart.js is primarily a 2D charting library, check if creative approaches (like overlapping charts, gradients, or shadow effects) are used to simulate 3D. Award 10 points for innovative use of Chart.js capabilities to create convincing 3D effects, 5 points for basic implementation, and 0 points if Chart.js is improperly implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the fairing visualization interactive and rotatable?",
+      "description": "Check if the implementation includes user interaction capabilities such as rotation, zooming, or viewing the cylinder from different angles. Give 10 points if fully interactive with smooth transitions, 5 points if basic rotation is implemented but with limitations, and 0 points if no interactivity is provided.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Does the implementation include proper shading and lighting effects?",
+      "description": "Assess whether the cylindrical fairing includes appropriate shading and lighting effects to enhance the 3D appearance. Review gradient usage, shadow implementation, and highlight effects. Award 10 points if professional lighting effects are implemented, 5 points for basic shading, and 0 points if the cylinder appears flat with no depth cues.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as browser resizing, different screen ratios, or mobile devices). Test browser compatibility and responsiveness. Score 10 points if the visualization remains stable across different scenarios, 5 points if it works in standard conditions but has edge case issues, and 0 points if major rendering problems occur.",
+      "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. Customizable color/texture options 2. Cross-section view capability 3. Dimension annotation display). 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 methods 2. Function modules unrelated to the cylindrical fairing 3. Fancy effects that affect performance. Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating rendering logic from UI controls), code organization, and performance optimization techniques. Deduct 5 points if global variable pollution is found or if proper encapsulation isn't used; deduct 5 points if the code is poorly organized with high duplication; deduct 5 points if rendering performance is suboptimal. 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) Clean, minimalist UI with harmonious colors 2) Proper layout and spacing of controls and information 3) Professional typography and labeling. Deduct 3 points for each cluttered visual element, 5 points for poor color choices, and 5 points for disorganized 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) Immediate visual feedback on user interactions 2) Smooth animation transitions between states 3) Intuitive controls with clear visual cues. Deduct 5 points for each operation without feedback, 3 points for jerky animations, and 5 points for confusing or hidden controls. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "hard"
+}

package/library/data_science-data_visualization_dashboards/html-daily-attendance-timeline-with-color-blocks.json

@@ -0,0 +1,68 @@
+{
+  "index": 204,
+  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Be careful to ensure that the generated code is executable for demonstration. Use HTML to draw an attendance timeline for a day, with different time interval blocks marked in different colors.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the attendance timeline visualization correctly implemented?",
+      "description": "Check if the code implements a proper timeline visualization that displays a full day (24 hours) with clear time markers. The timeline should have proper time divisions (hourly/half-hourly) with time labels. Deduct 5 points if the timeline doesn't span a full day; deduct 3 points if time markers are inconsistent or missing; deduct 5 points if the timeline orientation is unclear (horizontal/vertical). The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are the time interval blocks properly implemented and color-coded?",
+      "description": "Evaluate if the code successfully implements distinct time interval blocks that represent different attendance states (e.g., present, absent, late, etc.) with different colors. Each block should accurately represent its time range. Deduct 5 points if blocks don't align with the timeline grid; deduct 5 points if color differentiation is missing or inconsistent; deduct 3 points if block boundaries are ambiguous. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the data structure for storing and manipulating attendance data well-designed?",
+      "description": "Review the data model used to represent attendance events. It should efficiently store start/end times and attendance status. The model should handle overlapping events and time zone considerations. Deduct 5 points for inefficient data structures; deduct 3 points if overlapping events aren't handled; deduct 3 points if edge cases (midnight crossing, etc.) are ignored. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Does the implementation include user interaction capabilities?",
+      "description": "Check if the code provides ways to interact with the timeline, such as hovering for details, clicking for more information, or the ability to add/edit attendance blocks. Deduct 5 points if there's no hover information; deduct 5 points if there's no way to view detailed attendance information; deduct 3 points if the timeline lacks edit capabilities. 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 invalid time inputs, overlapping attendance periods, browser compatibility issues, etc.) and provide friendly error messages 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. Customizable time granularity 2. Animation for time progression 3. Summary statistics of attendance data). 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 visual elements that clutter the timeline 2. Unnecessary calculations that slow rendering 3. Excessive styling that doesn't improve clarity. Deduct 3 points for each redundancy found, and directly deduct 10 points if the core timeline functionality is compromised by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating data/view/controller logic), reusability, and maintainability. Deduct 5 points if global variables are overused; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there's no clear separation of concerns. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the timeline design follows modern design principles: 1) Harmonious color palette for attendance states (colorblind-friendly) 2) Proper layout spacing with proportional time intervals 3) Clear typography for time labels (readable at various screen sizes). Deduct 3 points for each visual accessibility issue, 5 points for poor color contrast, and 5 points for inconsistent time block sizing. 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 tooltips appearing within 100ms 2) Smooth scrolling/panning if timeline is zoomable 3) Clear visual indication of current time. Deduct 5 points for laggy rendering when displaying many attendance blocks, 3 points for jerky transitions between states, and 5 points for confusing navigation controls. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "hard"
+}