@getollie/cli 0.0.5 → 0.2.1

package/library/data_science-data_visualization_dashboards/stock-trading-volume-bar-charts.json

@@ -1,68 +0,0 @@
-{
-  "index": 1508,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable and presentable. How do I write a program for stock trading volume bar charts?",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core functionality of the stock trading volume bar chart fully implemented?",
-      "description": "Review whether the code accurately implements the visualization of trading volume data through bars, including proper scaling, axis representation, and data binding. Score 0 if the core visualization logic is not implemented, 5 if only basic bars are shown without proper scaling, and 10 if the implementation includes proper data normalization, axis labeling, and responsive sizing.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the data processing mechanism robust and efficient?",
-      "description": "Evaluate how the code processes stock data, including parsing, filtering, and aggregation for visualization. Check for date/time handling, handling of missing values, and proper data normalization. Deduct 5 points if there's no data validation, 3 points if performance optimizations for large datasets are missing, and 3 points if time-based aggregation options (daily/weekly/monthly) are absent. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are interactive features included for data exploration?",
-      "description": "Assess whether the chart includes essential interactive features like tooltips showing detailed volume information, zoom/pan capabilities for exploring different time periods, and clickable elements for drill-down analysis. Deduct 5 points if tooltips are missing, 3 points for lack of zoom/pan functionality, and 3 points if there's no way to interact with individual bars. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is there integration with complementary stock metrics/visualizations?",
-      "description": "Check if the volume chart is integrated or can work alongside other stock metrics like price movement, moving averages, or technical indicators. Volume-price relationship visualization is crucial for trading analysis. Deduct 5 points if there's no price data correlation, 3 points if comparison with historical volume averages is missing, and 3 points if volume-based indicators (e.g., OBV) are not included. 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 points, extremely high volume spikes, API failures, 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 visualization on the side, 2. Automatic pattern recognition for volume spikes, 3. Color coding based on price-volume divergence). 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 (e.g., multiple ways to render the same bars) 2. Function modules unrelated to trading volume visualization (e.g., unrelated social media integration) 3. Fancy effects that affect performance (e.g., excessive animations that hinder chart readability). 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), reusability of chart components, and performance optimization. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there's no consideration for rendering performance with large datasets. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional financial visualization standards?",
-      "description": "Evaluate whether the overall design follows financial charting principles: 1) Appropriate color scheme (using green/red for up/down volume or neutral colors with clear contrast) 2) Clean layout with proper data-ink ratio (minimal chartjunk) 3) Professional typography (readable numbers, proper axis labels, clear title). Deduct 3 points for cluttered visuals, 5 points for misleading visual encoding, and 5 points for poor readability of critical information. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and responsive?",
-      "description": "Judge whether the chart interactions conform to user expectations: 1) Hover/tooltip response within 100ms 2) Smooth transitions when updating data or changing time frames 3) Responsive design that works across device sizes. Deduct 5 points for laggy interactions with large datasets, 3 points for jarring visual updates when changing parameters, and 5 points for non-responsive design that breaks on different screen sizes. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Data Science-Data Visualization Dashboards",
-  "difficulty": "medium"
-}

package/library/data_science-data_visualization_dashboards/team-capability-matrix-chart.json

@@ -1,68 +0,0 @@
-{
-  "index": 1123,
-  "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. Please create a runnable HTML file for a team capability matrix chart and render it.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the team capability matrix data structure properly designed and implemented?",
-      "description": "Review whether the code accurately implements a comprehensive data model for team members and their capabilities through JavaScript objects/arrays. Check if it includes proper data validation, supports multiple skill levels (e.g., beginner/intermediate/expert), and handles dynamic data updates. Score 0 if no structured data model exists, 5 if only basic member-skill mapping is implemented, and 10 if a complete hierarchical capability framework with validation is included.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the matrix visualization rendering fully functional?",
-      "description": "Evaluate whether the HTML/CSS/JavaScript implementation creates a proper matrix layout with clear row/column headers, capability indicators (colors/icons/numbers), and responsive grid structure. Check if it supports different visualization modes (heatmap, bubble chart, or traditional grid). Deduct 5 points if the matrix layout is not properly aligned, and 3 points if capability levels are not visually distinguishable. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are interactive features and filtering mechanisms implemented?",
-      "description": "Check whether the code includes interactive capabilities such as sorting by team member or skill, filtering by capability level, search functionality, and hover effects showing detailed information. Evaluate if click interactions provide drill-down details or editing capabilities. Deduct 5 points if no interactive features exist, and 3 points if interactions lack visual feedback. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the chart scalable and handles large datasets efficiently?",
-      "description": "Assess whether the implementation can handle teams with 20+ members and 15+ skills without performance degradation. Check if virtual scrolling, pagination, or data chunking is implemented for large datasets. Evaluate if the rendering performance remains smooth during interactions. Deduct 5 points if the chart becomes unresponsive with large data, and 3 points if loading states are not handled properly. Give 10 points if fully optimized for scalability.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as missing data fields, invalid capability values, empty team lists, malformed input data, etc.) and provide friendly error prompts or fallback mechanisms. Code with strong robustness should gracefully handle edge cases and provide meaningful error messages, 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 user experience (e.g., 1. Export to PDF/Excel functionality 2. Skill gap analysis with recommendations 3. Team composition optimizer 4. Historical capability tracking 5. Integration with external HR systems). 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 chart rendering methods coexisting) 2. Function modules unrelated to capability matrix (e.g., built-in chat system) 3. Excessive animations that affect readability (e.g., constantly moving elements). Deduct 3 points for each redundancy found, and directly deduct 10 points if core matrix 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 layer/visualization layer/interaction layer), code organization, and maintainability. Deduct 5 points if global variables pollute the namespace or no clear separation of concerns; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the code lacks proper documentation or comments. 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 scheme for capability levels (using consistent color theory) 2) Proper spacing and alignment (grid elements follow consistent padding/margin rules) 3) Professional typography (readable font sizes ≥ 12px, appropriate contrast ratios). Deduct 3 points for each visually cluttered element, 5 points for poor color accessibility, and 5 points for inconsistent visual hierarchy. 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) Hover effects respond within 100ms 2) Sorting/filtering animations are smooth and under 400ms 3) Clear visual feedback for all interactive elements 4) Intuitive navigation and selection states. Deduct 5 points for each interaction without proper feedback, 3 points for laggy animations during data updates, and 5 points for confusing or hidden interactive elements. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Data Science-Data Visualization Dashboards",
-  "difficulty": "medium"
-}

package/library/data_science-data_visualization_dashboards/team-training-duration-win-rate-line-chart.json

@@ -1,68 +0,0 @@
-{
-  "index": 1088,
-  "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. Please provide code for a line chart comparing each team's weekly training duration and win rate.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the data visualization implementation complete?",
-      "description": "Review whether the code accurately implements a line chart with clear data representation of both weekly training duration and win rate for each team. Score 0 if the visualization is not implemented, 5 if only one metric is displayed or multiple metrics are poorly differentiated, and 10 if both metrics are properly visualized with clear distinction between teams.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the dual-axis representation handled correctly?",
-      "description": "Evaluate whether the code properly implements a dual-axis system (one for training duration in hours and one for win rate in percentage) with appropriate scales for each metric. Deduct 5 points if axes are missing labels or units, 3 points if scales are inappropriate for the data ranges, and 5 points if a dual-axis system is not implemented at all. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is proper data handling and preprocessing implemented?",
-      "description": "Check whether the code includes mechanisms for data input, validation, and preprocessing (handling missing values, data normalization if needed). Score 10 points if there's robust data handling with error checking, 5 points if basic data processing exists but lacks validation, and 0 points if data is hardcoded without any processing logic.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Are interactive features incorporated in the visualization?",
-      "description": "Assess whether the code includes interactive elements like tooltips showing exact values, ability to toggle teams' visibility, zoom/pan functionality, or highlighting data points on hover. Award 2.5 points for each meaningful interactive feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as varying data sizes, missing data points, extremely high/low values, browser resizing, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Animated transitions when data updates 2. Smart insights highlighting significant trends or correlations 3. Customizable color schemes or themes). 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 tooltip systems) 2. Function modules unrelated to the line chart comparison (e.g., unrelated animations) 3. Fancy effects that affect performance (e.g., excessive animations or gradients). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core 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, 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 code lacks comments or documentation. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the chart design follows modern data visualization principles: 1) Harmonious color scheme that differentiates teams clearly 2) Proper use of space with sufficient margins and padding 3) Professional typography with readable labels and legends. Deduct 3 points for cluttered visualizations, 5 points for poor color choices that hinder data interpretation, and 5 points for illegible text or overlapping elements. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the chart responsive and cross-browser compatible?",
-      "description": "Judge whether the chart adapts to different screen sizes and browsers: 1) Responsive design that adapts to container width 2) Proper handling of touch interactions for mobile devices 3) Cross-browser compatibility with major browsers. Deduct 5 points for fixed-size charts that don't adapt to containers, 5 points for lack of mobile considerations, and 3 points for browser-specific issues. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Data Science-Data Visualization Dashboards",
-  "difficulty": "easy"
-}

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

@@ -1,68 +0,0 @@
-{
-  "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

@@ -1,68 +0,0 @@
-{
-  "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

@@ -1,68 +0,0 @@
-{
-  "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

@@ -1,68 +0,0 @@
-{
-  "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

@@ -1,68 +0,0 @@
-{
-  "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"
-}