@getollie/cli 0.0.1

package/library/data_science-data_visualization_dashboards/tech-changes-talent-demand-chart.json

@@ -0,0 +1,68 @@
+{
+  "index": 1546,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to ensure that the code you generate is executable and demonstrable. Here's how technological changes affect future talent demands:\n\nTable 1: Talent Demand Change Table\nTechnological Direction | Key Areas | Talent Demand Growth Rate (2024-2030)\n---|---|---\nAI & Big Data | Smart Grid, Power System Optimization | 50%\nInternet of Things | Smart Grid, Home, Industrial Automation | 60%\nEnergy Storage Technology | Storage Equipment Design, Energy Management Systems | 70%\nNew Energy Technology | Solar, Wind Power, Microgrids | 90%\nElectrified Intelligent Transportation | New Energy Vehicles, Transportation Power Infrastructure | 80%\n\nPlease generate a chart that combines bar and line graphs.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the chart correctly implemented with combined bar and line graphs?",
+      "description": "Evaluate whether the implementation properly combines bar and line charts in a single visualization to represent the technological data. The bars should represent one metric (e.g., key areas count) while the line should represent another (e.g., growth rate). Check if the correct HTML5 Canvas/SVG elements are used with proper rendering of both chart types. Score 0 if only one chart type is implemented, 5 if both are implemented but poorly integrated, and 10 if there's seamless integration with proper visual differentiation.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is all data from Table 1 accurately represented in the visualization?",
+      "description": "Verify that all five technological directions, their key areas, and corresponding growth rates (2024-2030) are accurately displayed in the chart. Check that the values match exactly with the provided table (AI & Big Data: 50%, IoT: 60%, etc.). Deduct 2 points for each missing or inaccurate data point. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Does the chart have proper axes, scales, and legends?",
+      "description": "Examine whether the chart includes clearly labeled x and y axes with appropriate scales, units (percentage for growth rate), and a legend that distinguishes between the bar and line elements. Verify that the scales are appropriate for the data range (0-100% for growth rates). Deduct 3 points for missing axes labels, 3 points for inappropriate scaling, and 4 points for missing or confusing legends. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the chart interactive with appropriate user experience features?",
+      "description": "Assess whether the chart includes interactive features such as tooltips showing precise values on hover, zoom/pan capabilities for detailed exploration, or clicking functionality to highlight specific technological areas. Check if transitions are smooth when interacting with the chart. Deduct 3 points for each missing essential interactive feature, and 5 points if there's no interactivity at all. 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, browser compatibility issues, screen size adaptation, etc.) and provide graceful fallbacks. Code with strong robustness should validate input data, implement error handling for rendering failures, and adapt responsively to different screen sizes. Give 10 points for comprehensive robustness, 5 points for average handling, and 0 points if no edge cases are considered.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the chart includes surprise features that enhance the experience (e.g., 1. Dynamic data updates with animations 2. Additional trend projections beyond 2030 3. Interactive filtering by technology category). 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 visualization components showing the same data in multiple ways 2. Unnecessary decorative elements that don't add informational value 3. Excessive animations or effects that distract from data comprehension. Deduct 3 points for each redundancy found, and directly deduct 10 points if the core visualization is obscured by redundant elements.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating data processing/visualization rendering/interaction handlers), reusability of chart components, and maintainability. Deduct 5 points if global variable 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. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the overall design follows modern data visualization principles: 1) Harmonious color palette that distinguishes between chart elements while maintaining cohesion 2) Proper spacing and alignment of chart components 3) Professional typography with readable labels and titles (font size ≥ 12px for charts). Deduct 3 points for each cluttered visual element, 5 points for poor color choices that hinder data interpretation, and 5 points for overlapping or unreadable text. 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) Chart rendering and data updates occur within 500ms 2) Transition animations duration controlled between 300-500ms 3) Clear visual feedback for interaction states. Deduct 5 points for noticeable lag when interacting with the chart, 3 points for jarring or stuttering animations, and 5 points for confusing 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/three-3d-pie-charts-distributions.json

@@ -0,0 +1,68 @@
+{
+  "index": 1156,
+  "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 and ready for demonstration. Based on the data in this table, please generate three 3D pie charts for me. The first one should show the age distribution, divided into categories of 20-25 years old, 26-30 years old, 31-35 years old, 36-40 years old, and over 40 years old, displaying the proportion of each category. The second one should show the gender distribution, divided into male and female, displaying the proportion of each category. The third one should show the education distribution, divided into bachelor's degree, master's degree, and doctorate, displaying the proportion of each category.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the age distribution 3D pie chart implemented correctly?",
+      "description": "Evaluate whether the code accurately groups and displays the age data in a 3D pie chart with the specified categories (20-25, 26-30, 31-35, 36-40, and over 40). Check if proportions are calculated correctly and if the visualization reflects accurate percentages. Score 0 if the chart is missing, 5 if the basic implementation has errors in grouping or calculation, and 10 if the age distribution chart is fully implemented with proper labels and accurate proportions.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the gender distribution 3D pie chart implemented correctly?",
+      "description": "Assess whether the code properly creates a 3D pie chart showing gender distribution (male and female). Verify that the data proportions are calculated accurately and the visualization clearly represents the gender ratio. Score 0 if the chart is missing, 5 if the basic implementation has calculation or display issues, and 10 if the gender distribution chart is completely implemented with proper labels and accurate percentages.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the education distribution 3D pie chart implemented correctly?",
+      "description": "Review whether the code successfully implements a 3D pie chart showing education distribution (bachelor's, master's, doctorate). Confirm that the proportions reflect the actual data distribution and segments are properly labeled. Score 0 if the chart is missing, 5 if the implementation has data calculation or presentation flaws, and 10 if the education distribution chart is fully functional with accurate proportions and clear labeling.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Are the 3D visual effects properly implemented?",
+      "description": "Evaluate the three-dimensional quality of the pie charts. Check for proper depth, perspective, lighting effects, and shadows that enhance the 3D appearance. Score 0 if charts are essentially 2D, 5 if 3D effects are basic (just extrusion without proper lighting/shadows), and 10 if charts feature professional 3D elements including proper depth perception, lighting, angle, and interactive viewing capabilities.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as missing data, incomplete data, negative values, extremely small percentage 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. Interactive tooltips with detailed statistics 2. Animation transitions between chart views 3. Custom color palettes with thematic consistency 4. Drill-down capabilities to explore subcategories). 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 charting libraries used for the same purpose) 2. Function modules unrelated to the requested charts (e.g., extraneous analytics) 3. Fancy effects that affect performance (e.g., excessive animations that slow rendering). 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 logic/user interface layers), reusability of chart creation functions, and code organization. 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 initialization process is not properly structured. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the overall design follows modern data visualization principles: 1) Harmonious color matching (no more than 3 primary colors per chart) 2) Proper layout spacing (charts properly sized and positioned) 3) Professional typography (readable labels with proper contrast). Deduct 3 points for each visually cramped element, 5 points for clashing colors that hamper readability, and 5 points for poorly positioned or sized labels/legends. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the interaction features conform to modern visualization standards: 1) Responsive hover effects with tooltips ≤ 100ms delay 2) Smooth rotation/perspective changes for 3D visualization 3) Clear visual cues for interactive elements. Deduct 5 points for each interaction without feedback, 3 points for jerky animations or transitions, and 5 points for inaccessible or unintuitive interaction controls. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "easy"
+}

package/library/data_science-data_visualization_dashboards/tonghuashun-k-line-chart-rising-limit.json

@@ -0,0 +1,68 @@
+{
+  "index": 1438,
+  "question": "You are a coding expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to provide executable code when possible. Help me write a code for a Tonghuashun K-line chart where the rising limit/ceiling price is displayed as a yellow solid bar.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Does the K-line chart implementation include the basic candlestick visualization?",
+      "description": "Check if the code correctly implements the fundamental K-line chart with proper visualization of OHLC (Open, High, Low, Close) data using candlestick representation. Verify if candles correctly display rising (typically red/white) and falling (typically green/black) states. Score 0 if candlesticks are not implemented, 5 if basic implementation exists but with issues, 10 if properly implemented with clear visual distinction.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the rising limit/ceiling price functionality correctly implemented with yellow solid bars?",
+      "description": "Evaluate whether the code specifically identifies and visualizes rising limit/ceiling price conditions (typically 10% price increase in Chinese markets) with yellow solid bars as required. Check if the detection logic for limit-up conditions is accurate. Deduct 5 points if the yellow bars are present but implementation is incorrect, deduct 7 points if the concept is misunderstood. Give 0 points if the feature is completely missing.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Does the implementation include proper data handling and processing?",
+      "description": "Review how the code processes financial data, including data cleaning, normalization, and handling of missing values. Check if the code can accommodate various data formats (CSV, JSON, API responses) and if it includes proper validation. Assess if time/date handling follows proper standards. Deduct 3 points for each major data handling issue, with a maximum deduction of 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the chart responsive and interactive?",
+      "description": "Check if the chart includes essential interactive features like zooming, panning, tooltips showing detailed information on hover, and crosshair functionality. Assess whether the chart resizes appropriately for different screen sizes. Deduct 2 points for each missing interactive feature and 4 points if responsiveness is absent. 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 data input, network failures when fetching data, 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. Volume profile analysis 2. Technical indicators overlay options 3. Pattern recognition highlighting 4. Comparison with index or other stocks). Add 2.5 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. Feature modules unrelated to financial charts (e.g., unnecessary animations) 3. Fancy effects that affect performance (e.g., excessive rendering 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 chart logic/view/data processing layers), component reusability, and code organization. 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 data processing and visualization. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional financial chart standards?",
+      "description": "Evaluate whether the chart follows professional financial visualization principles: 1) Appropriate color scheme for financial data (standard industry colors) 2) Clean grid lines and axis labels 3) Professional typography with readable font sizes 4) Clear visual hierarchy between primary and secondary elements. Deduct 2.5 points for each visual element that doesn't meet industry standards. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the performance optimized for large datasets?",
+      "description": "Judge whether the implementation considers performance optimization for large financial datasets: 1) Data downsampling techniques for different zoom levels 2) Virtual rendering for off-screen elements 3) Efficient drawing methods (Canvas/WebGL vs. SVG for large datasets) 4) Throttling/debouncing for interactive events. Deduct 2.5 points for each missing optimization technique. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "medium"
+}

package/library/data_science-data_visualization_dashboards/training-industry-data-dashboard.json

@@ -0,0 +1,68 @@
+{
+  "index": 1586,
+  "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. Help me design a data dashboard using HTML code that would be used in the training industry.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the dashboard structure properly implemented?",
+      "description": "Check if the HTML structure includes key dashboard components: header section, navigation menu, main content area with data widgets, and footer. Evaluate whether semantic HTML5 elements (header, nav, main, section, footer) are used appropriately. Score 0 if missing essential dashboard structure, 5 if basic structure exists but semantic elements are misused, and 10 if structure is complete with proper semantic markup.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are training-specific data visualizations included?",
+      "description": "Verify the implementation of at least 3 training-industry specific visualizations: learner progress charts, course completion rates, assessment performance metrics, attendance tracking, or certification status. Each visualization should have relevant data structures and rendering logic. Deduct 3 points for each missing visualization. Award full points if all visualizations are training-relevant and properly implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the dashboard interactive with filtering and drill-down capabilities?",
+      "description": "Evaluate whether the dashboard includes interactive elements: date range filters, course/trainer/learner selectors, and detail drill-down functionality. Check if the JavaScript implements proper event handlers and data manipulation. Deduct 5 points if filtering is missing, 5 points if drill-down functionality isn't implemented, and 5 points if interactivity doesn't update visualizations dynamically.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Does the dashboard support data export and reporting functions?",
+      "description": "Check for implementation of data export capabilities (CSV/PDF), scheduled report generation, and customizable report templates specific to training metrics. Deduct 3 points if basic export is missing, 3 points if data formatting for reports is inadequate, and 4 points if no training-specific report templates are available.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as missing data, API failures, user input errors, etc.) and provide friendly error prompts or fallback displays. Code with strong robustness should include data validation, error handling for empty datasets, and graceful degradation. Give 10 points for comprehensive error handling, 5 points for basic error checks, and 0 points if no error 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 experience (e.g., 1. AI-powered insights on training effectiveness 2. Gamified elements for trainer/learner engagement 3. Customizable dashboard layouts 4. Real-time notification system for training milestones). Add 2.5 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 components 2. Function modules unrelated to training metrics (e.g., unnecessary social media feeds) 3. Fancy effects that affect dashboard performance (e.g., excessive animations). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core dashboard 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 data fetching/processing/visualization layers), code reusability, and maintainability. Deduct 5 points if global variable pollution is found; deduct 3 points if visualization components aren't reusable; deduct 2 points if CSS isn't organized using classes/modules/variables. 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 modern design principles: 1) Consistent color scheme aligned with training industry standards 2) Clear visual hierarchy with important metrics highlighted 3) Responsive layout that works on different screen sizes 4) Proper data-to-ink ratio (minimum decorative elements). Deduct 3 points for cluttered layout, 3 points for poor color contrast affecting readability, 2 points for non-responsive design, and 2 points for excessive decoration. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dashboard optimized for usability and accessibility?",
+      "description": "Judge whether the dashboard is designed for easy use: 1) WCAG compliance with proper aria-labels and keyboard navigation 2) Intuitive information architecture 3) Loading states for data retrieval operations 4) Tool-tips and context help for complex metrics. Deduct 3 points for missing accessibility features, 3 points for confusing information organization, 2 points for missing loading indicators, and 2 points for lack of instructional elements. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "medium"
+}

package/library/data_science-data_visualization_dashboards/uniapp-ecg-drawing-fixed-data.json

@@ -0,0 +1,68 @@
+{
+  "index": 1601,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the code you generate is executable for demonstration purposes. Write a demo of an electrocardiogram (ECG) drawing using uniapp with fixed data.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the ECG waveform rendering system correctly implemented?",
+      "description": "Review whether the code accurately implements the ECG waveform visualization using canvas or other suitable rendering approaches in uniapp. Check if the waveform follows standard ECG characteristics (P wave, QRS complex, T wave). Score 0 if there's no waveform rendering, 5 if basic lines are drawn but don't resemble an ECG pattern, and 10 if the waveform accurately represents cardiac electrical activity with appropriate amplitudes and intervals.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the data structure for ECG representation properly designed?",
+      "description": "Evaluate whether the code includes an appropriate data structure to store and manage the fixed ECG data. Check if the data format is suitable for efficient rendering (time-series format, appropriate sampling rate). Deduct 5 points if the data structure is overly complex or inefficient, 3 points if data normalization is missing. Give 10 points if the data structure is optimized for ECG visualization with clear separation of data and rendering logic.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the real-time scrolling/update mechanism implemented?",
+      "description": "Check if the ECG visualization includes smooth scrolling effect that mimics a real ECG machine. Verify that the rendering loop maintains consistent frame rates without stuttering. Deduct 5 points if the animation is jerky, 3 points if the scroll speed isn't configurable. The full score is 10 points for implementations with smooth 60fps scrolling and proper timing controls.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Are ECG visualization parameters configurable and appropriately set?",
+      "description": "Assess whether the code allows configuration of key ECG parameters such as paper speed (e.g., 25mm/s), amplitude (e.g., 10mm/mV), grid sizing, and waveform colors. Check if default values align with clinical standards. Deduct 3 points for each missing essential parameter configuration. Award 10 points if all standard ECG display parameters are configurable with sensible defaults.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as different screen sizes, orientation changes, unexpected data values, etc.) and provide graceful degradation or recovery mechanisms. Code with strong robustness should 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. Heart rate calculation and display 2. Waveform zooming/panning capabilities 3. Multiple lead visualization options 4. Abnormality detection visualization). Add 2.5 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 rendering functions 2. Function modules unrelated to ECG visualization (e.g., unnecessary UI elements) 3. Fancy effects that affect performance (e.g., excessive animations or filters). Deduct 3 points for each redundancy found, and directly deduct 10 points if core functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (separating data handling, rendering, and UI components), component reusability within uniapp framework, and code organization. Deduct 5 points if global state pollution is found or proper uni-app practices aren't followed; deduct 5 points if code duplication rate is high (over 30%); deduct 5 points if performance optimization for mobile devices is missing. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional medical visualization standards?",
+      "description": "Evaluate whether the visualization follows clinical ECG display standards: 1) Appropriate grid system (1mm small squares, 5mm large squares) 2) Professional color scheme (usually red/black waveform on light background) 3) Proper scaling and proportions matching physical ECG paper. Deduct 3 points for inaccurate grid representation, 5 points for non-standard colors making interpretation difficult, and 5 points for incorrect scaling. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the cross-platform compatibility ensured within uniapp?",
+      "description": "Judge whether the implementation properly leverages uniapp's cross-platform capabilities: 1) Uses compatible canvas APIs 2) Responsive design for different device sizes 3) Considers performance implications on lower-end devices. Deduct 4 points if the implementation only works on certain platforms, 3 points for significant performance differences between platforms, and 3 points for UI inconsistencies across devices. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "medium"
+}

package/library/data_science-data_visualization_dashboards/uniapp-editable-knowledge-graph.json

@@ -0,0 +1,68 @@
+{
+  "index": 1613,
+  "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 whenever possible. uniapp, implement an editable knowledge graph.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the knowledge graph data structure properly implemented?",
+      "description": "Review whether the code accurately implements a graph data structure for knowledge representation, including nodes (concepts) and edges (relationships). Score 0 if there's no clear graph structure, 5 if basic node-edge representation exists, and 10 if it includes advanced features like node types, edge weights, and directional relationships.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are the graph editing capabilities fully functional?",
+      "description": "Check if the implementation allows CRUD operations (Create, Read, Update, Delete) for both nodes and edges. Verify the presence of node/edge selection, dragging, resizing, and content editing. Deduct 3 points if any basic operation is missing, and 5 points if multi-selection or batch operations aren't supported. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the visualization rendering optimized for uniapp?",
+      "description": "Evaluate whether the visualization leverages appropriate uniapp rendering methods (canvas vs. component-based) based on graph complexity. Check if it handles cross-platform differences (iOS/Android/H5) and applies performance optimizations like culling for off-screen elements or level-of-detail techniques. Deduct 5 points if rendering is sluggish with >50 nodes, and 3 points if platform-specific issues exist. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Does the implementation use appropriate uniapp features?",
+      "description": "Assess whether the code uses uniapp-specific components and APIs properly. Check for proper utilization of uni-app lifecycle hooks, conditional compilation for platform differences, and appropriate use of uniapp UI components. Deduct 5 points for excessive web-view usage when native components would be more appropriate, and 5 points if the code doesn't follow uniapp's development paradigm. 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 malformed graph data, user operation errors, or touch event conflicts) 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. Auto-layout algorithms for graph organization 2. Export/import functionality with standard knowledge graph formats 3. Gesture shortcuts for rapid graph manipulation). 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 graph manipulation libraries) 2. Function modules unrelated to knowledge graph editing (e.g., unneeded social features) 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 graph model/view/controller layers), 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) Touch feedback delay ≤ 100ms 2) Graph manipulation responsiveness on different devices 3) Clear visual focus guidance. Deduct 5 points for each operation without feedback, 3 points for visual lag during graph manipulation, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "easy"
+}

package/library/data_science-data_visualization_dashboards/uniapp-vue3-ts-h5-line-bar-charts-page.json

@@ -0,0 +1,68 @@
+{
+  "index": 730,
+  "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. Create a uniapp vue3 ts H5 page with simple line charts and bar charts.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the vue3 + ts UniApp project structure correctly set up?",
+      "description": "Check if the project includes essential files: pages.json, manifest.json, App.vue, main.ts and appropriate tsconfig.json. Verify proper TypeScript configuration with strict type checking and vue3 support. Ensure the project structure follows UniApp conventions with appropriate directory organization (pages/, components/, static/, etc.). Score 0 if missing critical files, 5 if basic structure exists but with configuration issues, 10 if perfectly configured with proper type declarations.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are line charts properly implemented with appropriate libraries?",
+      "description": "Evaluate if a suitable charting library compatible with UniApp is used (such as echarts, uCharts, or F2). Check if the line chart implementation includes: dynamic data binding, responsive sizing, proper axis configuration, and legend display. Examine if TypeScript interfaces/types are defined for chart data. Deduct 5 points if the chart is not responsive, 3 points if missing proper type definitions, and 5 points if lacking customization options. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Are bar charts correctly implemented with proper data visualization principles?",
+      "description": "Verify if the bar chart implementation includes appropriate scales, labels, and color encoding. Check for animations, tooltips, and interaction capabilities. Ensure data is properly bound with TypeScript interfaces. Verify if the chart handles edge cases like empty data, overflow values, and resizing. Deduct 3 points if lacking proper color contrast, 5 points if missing interactive features, and 5 points if data binding is improperly typed. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the H5 compatibility and responsiveness properly handled?",
+      "description": "Check if the page adapts to different screen sizes using UniApp's responsive design capabilities. Verify if conditional compilation (@/:#ifdef H5) is used appropriately for H5-specific code. Test if touch events are properly handled for mobile browsers. Ensure viewport meta tags are correctly set for mobile devices. Deduct 5 points if the layout breaks on common mobile dimensions, 3 points if touch interactions are missing, and 5 points if H5-specific optimizations are absent. 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 data loading failures, malformed data, network errors, etc.) and provide friendly error prompts or recovery mechanisms. Check for proper error boundaries in Vue components. Verify if charts handle edge cases gracefully (empty datasets, extreme values). 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 chart tooltips with rich content 2. Chart theme switching based on system preference 3. Gesture-based chart interactions 4. Data export capabilities 5. Animated transitions between data views). 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 chart library imports (e.g., including multiple charting libraries for similar purposes) 2. Unnecessary components or modules unrelated to visualization (e.g., complex multimedia elements) 3. Excessive animations or effects that impact performance on mobile devices. Deduct 3 points for each redundancy found, and directly deduct 10 points if the core chart functionality is interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review component organization (separating chart components from data fetching logic), TypeScript usage quality (proper interfaces, avoiding any/unknown types), and code reusability. Check if composition API is used appropriately with proper lifecycle hooks. Deduct 5 points if TypeScript is used poorly or has numerous type assertions; deduct 5 points if the code has high duplication between chart implementations; deduct 5 points if the composition API is misused or reactive references are implemented incorrectly. 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 in charts (consistent palette, appropriate contrast) 2) Proper layout spacing (chart margins, padding between elements) 3) Professional typography (readable labels, appropriate font sizing for mobile). Deduct 3 points for cluttered charts, 5 points for poor color choices that impede data interpretation, and 5 points for illegible labels or overlapping elements. 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) Chart rendering and updates within 300ms 2) Smooth animations for transitions between data states 3) Responsive touch interactions without lag. Check if the charts respond immediately to user inputs. Deduct 5 points for noticeable lag when interacting with charts, 3 points for jerky animations, and 5 points for charts that don't provide immediate visual feedback during interaction. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "easy"
+}

package/library/data_science-data_visualization_dashboards/us-population-changes-dashboard-visualization.json

@@ -0,0 +1,68 @@
+{
+  "index": 1612,
+  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Be sure to ensure that the generated code is executable for demonstration. Create a dashboard for U.S. population changes that includes visualization design and data presentation. Output in HTML format, ensuring the file is executable.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the U.S. population data visualization complete and accurate?",
+      "description": "Check whether the dashboard includes comprehensive population data visualization with appropriate metrics (total population, growth rate, demographic breakdown by age/ethnicity/gender). Verify data accuracy against reliable sources (Census Bureau, etc.). Score 0 if basic population trends are missing, 5 if only showing limited metrics, and 10 if offering comprehensive demographic insights with proper data attribution.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are multiple visualization types implemented effectively?",
+      "description": "Evaluate whether the dashboard implements diverse chart types appropriate for different data aspects (line charts for trends over time, choropleth maps for geographic distribution, bar/pie charts for comparative analysis). Check if visualizations use D3.js or other libraries effectively. Deduct 3 points if only one visualization type is used, 5 points if charts are inappropriate for the data type, and 2 points if interactive elements are missing. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the dashboard interactive with filtering and drill-down capabilities?",
+      "description": "Assess if the dashboard includes user interaction features like time period selectors, state/region filters, demographic breakdowns, and data comparison tools. Interactive elements should provide smooth transitions and clear visual feedback. Deduct 5 points if filtering capabilities are absent, 3 points if drill-down functions are limited, and 2 points if interactions lack visual confirmation. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Does the dashboard present data insights and context effectively?",
+      "description": "Review whether the dashboard goes beyond raw data display to provide meaningful context (population trends, notable migration patterns, policy implications). Check for tooltips, annotations, or narrative elements that highlight key insights. Deduct 5 points if contextual information is missing, 3 points if insights lack depth, and 2 points if annotation system is inadequate. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code handles common edge cases (missing data, loading states, browser compatibility, responsive design for different screen sizes). Code should include error handling for data fetching failures and graceful degradation. Give 10 points for comprehensive error handling and responsive design, 5 points for partial implementation, and 0 points if critical failures occur under normal usage scenarios.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the dashboard includes unique features enhancing user experience (e.g., 1. AI-powered trend predictions 2. Custom population comparison tool 3. Time-lapse visualization of demographic shifts). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Duplicate visualizations showing the same data in different formats without adding new insights 2. Unnecessary UI elements not related to population data analysis 3. Heavy animations or effects that impair dashboard performance. Deduct 3 points for each redundancy found, and directly deduct 10 points if core visualization functions are compromised by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (separation of data processing, visualization rendering, and UI components), code reusability, and performance optimization. Deduct 5 points for global variable overuse or poor encapsulation; deduct 3 points if the data loading process lacks optimization (no data caching or preloading); deduct 2 points if rendering performance drops significantly with larger datasets. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the dashboard follows data visualization best practices: 1) Color scheme is accessible and distinguishable (including for color-blind users) 2) Information hierarchy is clear with logical layout 3) Typography enhances readability (consistent font families, appropriate size hierarchy). Deduct 3 points for cluttered layout, 5 points for poor color choices that hinder data interpretation, and 2 points for inconsistent visual language across dashboard components. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether transitions and interactions feel natural: 1) Data filtering responds within 300ms 2) Chart animations have appropriate easing functions and duration 3) Loading states provide visual feedback. Deduct 5 points for laggy transitions when changing views, 3 points for abrupt visual changes without proper transitions, and 2 points for confusing interaction patterns that lack affordance cues. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "easy"
+}