@getollie/cli 0.0.1

package/library/data_science-data_visualization_dashboards/china-3d-map-new-energy-vehicle-sales.json

@@ -0,0 +1,68 @@
+{
+  "index": 1667,
+  "question": "You are a coding expert. Please use your professional knowledge to generate accurate and professional responses. Make sure that the code you generate is executable and can be demonstrated. Create a 3D map of China showing city outlines, where the height of each city's outline represents the sales volume of new energy vehicles in that city.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the 3D map of China correctly implemented?",
+      "description": "Examine whether the code accurately renders China's geographical boundaries with appropriate GeoJSON data, including provincial and city outlines. Check if the map projection is appropriate (preferably a conformal projection like Mercator or Albers for China). Deduct 5 points if provincial boundaries are missing, 3 points if city boundaries are inaccurate, and 5 points if the projection distorts China's shape significantly. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the 3D extrusion of city outlines correctly implemented based on sales data?",
+      "description": "Verify that each city's outline is extruded in 3D space proportionally to its new energy vehicle sales data. Check if the height mapping function is appropriate (linear, logarithmic, etc.) given the potential large variance in sales volumes across cities. Deduct 5 points if the height calculation is incorrect, 3 points if there's no normalization for extreme values, and 5 points if the extrusion method creates visual artifacts. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the data visualization accompanied by appropriate legends and annotations?",
+      "description": "Evaluate whether the visualization includes clear legends explaining the height-to-sales mapping, city labels for at least major cities, and annotations that help interpret the data. Check for a color scale or height scale indicator. Deduct 3 points for missing legends, 3 points for absent city labels, and 4 points if there's no way to determine actual sales figures from the visualization. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is there interactivity allowing users to explore the data?",
+      "description": "Assess the implementation of interactive features such as zooming, panning, rotating the 3D view, hovering for city information tooltips, and clicking for detailed sales data. Deduct 2 points for each missing core interaction (zoom/pan/rotate), 3 points for missing tooltips, and 3 points if there's no way to view specific sales figures. 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, mobile responsiveness, etc.) and provide graceful fallbacks or error handling. Code with strong robustness should load fallback data if the main dataset fails, handle WebGL/3D rendering limitations, and adapt to different screen sizes. Give 10 points for comprehensive error handling, 5 points for basic error checks, and 0 points if errors crash the application.",
+      "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. Time-series animation showing sales growth 2. Comparative visualization with traditional vehicle sales 3. Weather or environmental overlay showing correlation with EV adoption). 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 data processing methods 2. Visualization elements unrelated to the city sales data (e.g., unnecessary decorative elements) 3. Heavy effects that affect performance (e.g., excessive particle systems or shaders). 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/interaction layers), code reusability, and performance optimization. Deduct 5 points if global namespace pollution is found; deduct 3 points if the code doesn't implement proper asset loading strategies for large GeoJSON files; deduct 5 points if there's no optimization for the 3D rendering performance. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the overall design follows modern data visualization principles: 1) Appropriate color scheme that aids data interpretation (not just aesthetics) 2) Clear visual hierarchy distinguishing map, data, and controls 3) Professional typography with readable labels even on complex 3D terrain. Deduct 3 points for poor color choices that hinder data interpretation, 5 points for cluttered interface elements, and 5 points for illegible labels or legends. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and responsive?",
+      "description": "Judge whether the 3D visualization performs well: 1) Smooth rotation/zoom with frame rate ≥30fps 2) Responsive tooltips appearing within 100ms of hover 3) Efficient rendering that handles all city polygons without significant lag. Deduct 5 points for jittery camera movements, 3 points for delayed data loading affecting interactivity, and 5 points if the visualization becomes unresponsive with full data. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "medium"
+}

package/library/data_science-data_visualization_dashboards/china-real-estate-prices-rose-chart.json

@@ -0,0 +1,68 @@
+{
+  "index": 1767,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to ensure the generated code is executable for demonstration. You are a data analysis expert, please help create a rose chart for China's 100-city real estate prices in HTML format.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the rose chart data structure and rendering correctly implemented?",
+      "description": "Review whether the code accurately implements rose chart (polar area chart) using HTML/JavaScript/SVG, including proper polar coordinate system transformation, data binding, and sector area calculations proportional to real estate price values. Score 0 if basic chart structure is missing, 5 if only simple polar rendering is implemented, and 10 if complete rose chart with accurate data mapping and sector proportions is fully implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the 100-city real estate data properly structured and processed?",
+      "description": "Check whether the implementation includes realistic Chinese city real estate price data (at least 50+ cities), proper data validation, normalization algorithms, and handling of missing/invalid data points. Evaluate data source credibility and whether price ranges reflect realistic market conditions. Deduct 5 points if data is clearly fabricated or unrealistic, 3 points if data structure lacks proper validation. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Are interactive features and data exploration capabilities implemented?",
+      "description": "Evaluate whether the rose chart includes essential interactive features such as hover tooltips showing city names and exact prices, click-to-highlight functionality, zoom/pan capabilities, and filtering options (by region, price range, or city tier). Deduct 5 points if no hover interactions exist, 3 points if tooltip information is incomplete. Full score requires smooth interactive experience with comprehensive data exploration tools.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the chart legend, labeling, and data annotation system complete?",
+      "description": "Check whether the implementation includes proper legend system, city name labels (readable without overlap), price scale indicators, color coding explanation, and data source attribution. Evaluate label positioning algorithms to avoid overlap and ensure readability. Deduct 5 points if legend is missing, 3 points if labels are overlapping or unreadable, 2 points if no data source is mentioned. 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 data, browser compatibility issues, rendering errors, division by zero in calculations, etc.) and provide friendly error prompts or fallback mechanisms. Code with strong robustness should gracefully handle edge cases like empty datasets or extreme price values, giving 10 points. If 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 analysis experience (e.g., 1. Real-time price trend indicators 2. Comparative analysis with historical data 3. Geographic clustering visualization 4. Export functionality for charts 5. Responsive design adaptation). 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 chart types (e.g., multiple visualization libraries coexisting) 2. Function modules unrelated to real estate data visualization (e.g., built-in games) 3. Excessive animations that affect performance (e.g., continuous particle effects). Deduct 3 points for each redundancy found, and directly deduct 10 points if 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), code organization, reusability, and maintainability. Deduct 5 points if global state pollution is found or proper separation of concerns is missing; deduct 5 points if the code duplication rate is too high (over 30%); deduct 3 points if no error handling or data validation is implemented. 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 suitable for data representation (no more than 5 primary colors) 2) Proper spacing and layout (adequate margins, non-overlapping elements) 3) Professional typography (readable font sizes ≥ 12px, appropriate contrast ratios) 4) Consistent visual hierarchy. Deduct 3 points for each crowded visual element, 5 points for poor color choices that hinder data reading, and 5 points for chaotic layout. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the interactive effects conform to user experience standards: 1) Hover feedback delay ≤ 100ms 2) Smooth transitions when filtering or updating data (300-500ms duration) 3) Clear visual feedback for all interactive elements 4) Responsive performance with large datasets. Deduct 5 points for each interaction without proper feedback, 3 points for laggy animations or slow rendering, and 5 points for unclear interaction affordances. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "easy"
+}

package/library/data_science-data_visualization_dashboards/china-unicom-data-transformation-stages.json

@@ -0,0 +1,68 @@
+{
+  "index": 441,
+  "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 display.\n\n1. Data Resourceization: Building a Trustworthy Data Foundation\nChina Unicom transforms raw data into high-value resource pools through \"governance + technology\" dual drivers:\n\nGovernance System Upgrade:\n• Implemented metadata-driven governance covering 12 core data categories including 5G network logs and industrial equipment data, establishing a three-dimensional tagging system (classification, quality, security) with 97.3% data lineage traceability.\n• Deployed \"Unicom Chain\" blockchain platform, processing 150,000+ daily data transaction certifications, improving audit efficiency by 60% and ensuring trustworthiness throughout the data lifecycle.\n\nResource Integration Innovation:\n• Created a \"lake-warehouse integration\" architecture, consolidating enterprise customer data (5TB+ daily increase) with data streams from 20+ industrial sectors and 5G factory equipment, reducing storage costs by 35%.\n• Built provincial-park two-tier edge computing network, compressing industrial data collection latency to ≤50ms, supporting concurrent real-time processing of 2000+ devices.\n\n2. Data Productization: Creating Scenario-Based Service Matrix\nConverting data resources into tradable products through \"technology + ecosystem\" integration:\n\nStandardized Product Output:\n• Developed 300+ data API interfaces, providing industry databases, analytical reports and solutions (such as the smart healthcare \"Metascape Model\" and industrial internet AI energy consumption prediction model).\n• Launched \"155SN\" digital capability system, including Unicom Cloud infrastructure, five middle platforms and N scenario-based applications supporting capability reuse.\n\nDeep Industry Integration:\n• Implemented 20,000+ \"5G + Industrial Internet\" projects across 41 industrial categories, helping 6000+ factories reduce costs and increase efficiency.\n• Built \"Five Unified\" capability system in smart cities, enabling holographic data perception and intelligent decision-making.\n\n3. Data Assetization: Achieving Value Quantification Management\nPromoting transformation of data resources into assets through \"rights confirmation + valuation\" system:\n\nAccounting Innovation:\n• Incorporated data resources (industry databases, models, etc.) into development expenditure, with data resource book value reaching 84.7639 million yuan in H1 2024, a 28% increase from 2023.\n• Explored fair value assessment models for data assets, establishing multi-dimensional value measurement systems integrated with blockchain certification.\n\nManagement System Improvement:\n• Formulated \"Data Asset Classification and Coding Standards,\" clarifying data ownership rules and completing registration of 200+ core data assets.\n• Implemented \"Mokong\" security operations platform to achieve full-chain risk monitoring of data assets, ensuring asset security.\n\n4. Data Capitalization: Unleashing Financial Leverage\nActivating data asset liquidity through \"finance + ecosystem\" innovation:\n\nSecuritization Exploration:\n• Piloted data income rights pledge financing, issuing the first 500 million yuan asset-backed security in 2024 based on industrial internet platform data traffic.\n• Co-established data element joint venture platforms with strategic investors (like Tencent and Alibaba) to promote data equity operations.\n\nCapital Operation Synergy:\n• Maintained double-digit growth in R&D investment for 8 consecutive years (up 23% year-on-year in H1 2024), developing high-value technological achievements like computing power smart networks to attract strategic capital.\n• Enhanced capital market recognition of data value premium through dividend policy optimization (2024 interim dividend up 20.5% year-on-year).\n\nBased on the above text, please generate a chart showing China Unicom's four-stage data resource value transformation in HTML format.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the four-stage data resource value transformation architecture correctly visualized?",
+      "description": "Check whether the visualization clearly illustrates the four stages (Data Resourceization, Data Productization, Data Assetization, Data Capitalization) as a coherent transformation flow. Each stage should be visually distinct yet connected, showing progression. Verify that the hierarchical relationship between stages is properly communicated. Score 0 if stages are missing or incorrectly ordered, 5 if basic stages are shown but relationships are unclear, and 10 if the complete transformation journey is well articulated with clear connections.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are the key components and sub-elements of each stage accurately represented?",
+      "description": "Evaluate whether each stage contains its essential components: Resourceization (Governance System, Resource Integration), Productization (Standardized Products, Industry Integration), Assetization (Accounting Innovation, Management System), and Capitalization (Securitization, Capital Operation). Check if each component shows its respective sub-elements with quantitative metrics where applicable (e.g., 97.3% data lineage traceability, 84.7639 million yuan book value). Deduct 2 points for each major component missing and 1 point for missing key metrics. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Does the visualization incorporate the dual-driver mechanisms for each stage?",
+      "description": "Review whether the chart effectively shows the dual drivers for each stage: 'governance + technology' for Resourceization, 'technology + ecosystem' for Productization, 'rights confirmation + valuation' for Assetization, and 'finance + ecosystem' for Capitalization. Deduct 2.5 points for each missing dual-driver mechanism. Each driver should be visually connected to its respective outcomes or implementations. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the progression of value creation effectively communicated?",
+      "description": "Assess whether the visualization demonstrates the incremental value creation across stages - from raw data to resources to products to assets to capital returns. Value indicators should be included (cost reduction metrics, growth percentages, financial figures). The chart should convey how each stage builds upon the previous one to create higher forms of value. Deduct 3 points if value progression is unclear, 5 points if value metrics are absent, and 7 points if the visualization fails to show the relationship between stages in value creation. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common display scenarios (different screen sizes, browsers) and includes fallbacks for unsupported features. Check if the visualization remains functional and readable on mobile devices through responsive design. Deduct 3 points if the chart breaks on smaller screens, 2 points if text becomes illegible at certain viewport sizes, and 5 points if browser compatibility issues exist for major browsers. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Interactive elements showing detailed metrics on hover/click 2. Animation effects visualizing the transformation flow 3. Toggleable views to focus on different aspects of the framework). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant visual elements that don't add informational value 2. Excessive decoration that distracts from the core data transformation concept 3. Animated effects that slow rendering or impede comprehension. Deduct 3 points for each redundancy found, and directly deduct 10 points if core information is obscured by unnecessary elements.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (separation of data, styling, and interaction logic), code reusability, and optimization techniques. Check if the code uses appropriate HTML semantic elements, CSS best practices, and JavaScript performance patterns. Deduct 3 points for global scope pollution, 3 points for excessive inline styles, 2 points for unmaintainable code structure, and 2 points for lack of comments on complex logic. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the overall design follows modern data visualization principles: 1) Harmonious color scheme appropriate for corporate/business context 2) Proper information hierarchy with clear visual distinction between levels 3) Professional typography system with appropriate font sizes for headings and data points. Deduct 3 points for clashing colors, 3 points for poor layout balance, and 4 points for unclear visual hierarchy. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether any interactive elements function naturally: 1) Immediate visual feedback for user actions 2) Smooth transitions between states (300-500ms duration) 3) Clear affordances indicating interactive elements. Check if interactions enhance understanding rather than complicate it. Deduct 3 points for laggy animations, 3 points for confusing interaction patterns, and 4 points for interactions that don't meaningfully improve data comprehension. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "easy"
+}

package/library/data_science-data_visualization_dashboards/code-expert-html-visualizations-data-presentations.json

@@ -0,0 +1,68 @@
+{
+  "index": 708,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Take care to ensure that the code you generate is executable for demonstration purposes. Complement your charts with visualizations and data presentations, outputting in HTML format to ensure executability.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the visual data presentation component properly implemented?",
+      "description": "Check whether the code effectively implements data visualization using appropriate JavaScript libraries (D3.js, Chart.js, Highcharts, etc.) and HTML5 elements (Canvas, SVG). Score 0 if no visualization is implemented, 5 if basic charts are present but lack interactivity, and 10 if responsive, interactive visualizations with proper data binding are fully implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the data processing and transformation logic robust?",
+      "description": "Evaluate whether the code includes proper data sanitization, transformation pipelines, and error handling for different data formats. Check for presence of data validation, normalization techniques, and effective handling of edge cases (null values, outliers, etc.). Deduct 5 points if data validation is missing, and 3 points if the code doesn't handle incomplete data. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Are the visualization components responsive and cross-browser compatible?",
+      "description": "Review whether the code implements responsive design principles (viewport meta tags, CSS media queries, fluid containers) and maintains compatibility across major browsers. Test for proper rendering in different screen sizes and device types. Deduct 5 points for non-responsive visualizations and 5 points for browser-specific implementations without fallbacks. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the visualization accessibility implemented according to standards?",
+      "description": "Check if the code follows WCAG guidelines including proper color contrast ratios (minimum 4.5:1), alternative text for visual elements, keyboard navigation support, and ARIA attributes where necessary. Deduct 3 points for each missing major accessibility feature, and 2 points for each minor issue. Give 10 points if fully accessible.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as malformed data inputs, network 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. Interactive data exploration capabilities 2. Animated transitions between data states 3. Integration with external data sources or APIs). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar visualization functions 2. Unnecessary script imports or dependencies 3. Fancy effects that affect performance (e.g., excessive animations or transitions). 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), code reusability, and build process optimization. Deduct 5 points if global namespace pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if performance optimization techniques are not implemented. 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 visualization 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 typography system (body font size ≥ 14px, line height over 1.5 times). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic text-image layout. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Click feedback delay ≤ 100ms 2) Transition animation duration controlled between 300-500ms 3) Clear visual focus guidance. Deduct 5 points for each operation without feedback, 3 points for visual after-images during fast data transitions, 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": "medium"
+}

package/library/data_science-data_visualization_dashboards/comprehensive-analysis-report-table-data-visualization-design.json

@@ -0,0 +1,68 @@
+{
+  "index": 1310,
+  "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. Help me create a comprehensive analysis report based on the table data, including visualization design and data presentation. Output in HTML format, ensuring the file is executable.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the data parsing and analysis correctly implemented?",
+      "description": "Check whether the code properly handles data input, processes raw data, and performs appropriate statistical analysis. Evaluate if the code handles different data formats (CSV, JSON, etc.) and performs data cleaning operations like handling missing values, outliers, and type conversions. Score 0 if no data processing is implemented, 5 if basic parsing is present but with flaws, and 10 if comprehensive data analysis including validation and error handling is implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are appropriate visualization libraries and techniques utilized?",
+      "description": "Evaluate the choice and implementation of visualization libraries (D3.js, Chart.js, Plotly, etc.). Check whether the code leverages library capabilities effectively and uses appropriate chart types for the specific data characteristics. Deduct 3 points if inappropriate chart types are used, 5 points if visualizations are static when interactivity would be beneficial, and 2 points if there's no responsive design implementation. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Does the report provide comprehensive data insights?",
+      "description": "Review whether the analysis report includes essential statistics (mean, median, variance, etc.), identifies trends, correlations, and anomalies in the data. Check if comparative analysis is included where appropriate. Score 3 points for basic summary statistics, add 3 points for trend analysis, add 2 points for correlation analysis, and 2 points for anomaly detection. Deduct 5 points if critical insights are missing given the data context.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the visualization design effectively communicating data stories?",
+      "description": "Assess whether the visualizations follow data storytelling principles, with an appropriate narrative flow from simple to complex insights. Check if visualizations include proper titles, axis labels, legends, and annotations to explain key findings. Deduct 3 points if there's no clear narrative structure, 3 points for missing context or explanations, and 4 points if visualizations fail to highlight key insights. 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 data, browser compatibility issues, responsive layout problems, 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 filtering mechanisms 2. Animated transitions between views 3. Drill-down capabilities 4. Custom tooltips with rich information). 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 of the same data points 2. Unnecessary UI elements that don't contribute to data understanding 3. Heavy animations or effects that distract from data insights. 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/UI layers), code reusability, and performance optimization. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 3 points if the code duplication rate is too high (over 30%); deduct 2 points if there are no performance considerations for large datasets. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color palette suitable for data visualization (accessible, distinguishable, and following convention where appropriate) 2) Proper layout spacing with appropriate white space 3) Professional typography (readable font size ≥ 14px, proper hierarchy). Deduct 3 points for each accessibility issue, 5 points for poor color choices that make data hard to interpret, and 2 points for cluttered layout. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the interaction design user-friendly and helpful?",
+      "description": "Judge whether the interactive elements enhance data exploration: 1) Intuitive controls with clear affordances 2) Responsive feedback within 100ms 3) Helpful tooltips and annotations 4) Smooth transitions when data or views change. Deduct 3 points for each confusing interaction pattern, 2 points for missing tooltips on complex visualizations, and 5 points if filter controls are implemented but don't update visualizations properly. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "easy"
+}

package/library/data_science-data_visualization_dashboards/construction-task-gantt-chart-generator.json

@@ -0,0 +1,68 @@
+{
+  "index": 1357,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to ensure the generated code is executable for display. \n\nNumber | Construction Task | Start Date | End Date | Duration (Days)\n--- | --- | --- | --- | ---\n1 | Site Leveling and Enclosure Setup | XXXX/XX/XX | XXXX/XX/XX | XX\n2 | Foundation Excavation and Pouring | XXXX/XX/XX | XXXX/XX/XX | XX\n3 | Main Structure Construction | XXXX/XX/XX | XXXX/XX/XX | XX\n4 | Roof and Wall Construction | XXXX/XX/XX | XXXX/XX/XX | XX\n5 | Interior Finishing and Decoration | XXXX/XX/XX | XXXX/XX/XX | XX\n6 | Exterior Engineering and Landscaping | XXXX/XX/XX | XXXX/XX/XX | XX\n\nPlease provide me with the code to output a Gantt chart.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the basic Gantt chart structure correctly implemented?",
+      "description": "Evaluate whether the code properly creates a visual timeline representation with horizontal bars for each construction task. Check if the chart includes a timeline axis, task labels, and proper date formatting. Score 0 if the basic structure is missing, 5 points if the structure is present but with deficiencies, and 10 points for a complete and properly structured Gantt chart.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are the tasks and date ranges accurately displayed?",
+      "description": "Verify that all 6 construction tasks are correctly represented with their respective start and end dates. The bars should be proportionally sized according to the duration and correctly positioned on the timeline. Deduct 2 points for each incorrectly displayed task or date conversion error. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the time axis implementation complete and accurate?",
+      "description": "Check if the time axis is properly scaled, with clear interval markings, appropriate date labels, and consistent spacing. The axis should accommodate the full project timeline from the earliest start date to the latest end date. Deduct 5 points if the time scale is inconsistent or if date calculations are incorrect, and 3 points if the axis lacks proper labeling. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Does the Gantt chart include visual indicators for progress tracking or milestones?",
+      "description": "Assess whether the implementation includes features for tracking progress (like percent complete indicators, today's date marker) or milestone markers. Give 3 points for basic progress indicators, 3 points for milestone visualization, and 4 points for interactive progress updating capabilities. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid dates, missing data, browser compatibility issues) and provide appropriate error handling. Code with strong robustness should validate inputs and gracefully handle edge cases, giving 10 points. If the robustness is average, give 5 points, and if no error handling is implemented, give 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Task dependency visualization 2. Critical path highlighting 3. Interactive tooltips with detailed information 4. Zoom and pan capabilities). 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 functions (e.g., multiple date parsing methods) 2. Function modules unrelated to Gantt charts (e.g., unnecessary animations) 3. Fancy effects that affect performance (e.g., excessive animations or renderings). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating data processing/rendering/interaction layers), reusability, and maintainability. Deduct 5 points if global variables are excessively used; deduct 3 points if the code is not properly commented; deduct 3 points if there's significant code duplication. Check if the implementation follows modern development practices. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the chart follows data visualization best practices: 1) Clear visual hierarchy with task labels aligned properly 2) Appropriate color coding (consistent, accessible, meaningful) 3) Sufficient contrast between elements and background. Deduct 3 points for poor alignment, 3 points for inappropriate color choices, and 4 points for cluttered or hard-to-read visual presentation. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and responsive?",
+      "description": "Judge whether the chart provides appropriate interaction capabilities: 1) Hovering effects for additional information 2) Smooth transitions when updating data or filtering 3) Responsive design that adapts to different screen sizes. Deduct 3 points for lack of hover states, 4 points for jarring transitions or no transitions, and 3 points for poor responsiveness across devices. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "easy"
+}

package/library/data_science-data_visualization_dashboards/consumption-willingness-by-city-type-bar-chart.json

@@ -0,0 +1,68 @@
+{
+  "index": 812,
+  "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. Create a bar chart where the x-axis represents consumption willingness, including \"Very willing\", \"Somewhat willing\", \"Somewhat unwilling\", and \"Very unwilling\", and the y-axis represents city types, including \"First-tier cities\", \"New first-tier cities\", \"Second-tier cities\", \"Third-tier cities\", and \"Others\" (each x-coordinate corresponds to five bars).",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the bar chart correctly implemented with the specified axes?",
+      "description": "Check whether the code correctly implements a bar chart with consumption willingness on the x-axis ('Very willing', 'Somewhat willing', 'Somewhat unwilling', 'Very unwilling') and city types on the y-axis ('First-tier cities', 'New first-tier cities', 'Second-tier cities', 'Third-tier cities', 'Others'). Verify that each x-coordinate has 5 bars representing different city types. Score 0 if axes are reversed or missing, 5 if partially implemented, 10 if fully and correctly implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the data structure appropriate for the visualization?",
+      "description": "Evaluate if the data structure efficiently organizes the relationship between consumption willingness categories and city types. Check if the data format allows for easy updating and scaling. Deduct 5 points if the structure requires complex transformations before visualization, 3 points if it's not optimized for performance with larger datasets. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Are appropriate visual differentiation techniques used?",
+      "description": "Assess whether the visualization uses appropriate techniques (colors, patterns, spacing) to differentiate between the 5 city types within each consumption willingness category. Check if a legend is included to identify each city type. Deduct 5 points if bars are not visually distinguishable, 3 points if the legend is missing or unclear. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Does the chart include proper labels and annotations?",
+      "description": "Verify if the chart includes clear axis titles, value labels, and a meaningful chart title. Check whether tooltips or data labels show exact values when hovering/clicking. Deduct 3 points for missing axis titles, 3 points for missing value labels, and 4 points for missing tooltips/interactive elements. 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, different data scales, browser resizing, etc.) and provide graceful fallbacks or error handling. 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 filtering options 2. Animation when loading data or hovering 3. Responsive design that works on mobile devices). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar visualization functions 2. Function modules unrelated to the bar chart (e.g., unnecessary widgets) 3. Fancy effects that affect performance (e.g., excessive animations). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating data processing/visualization/interaction layers), reusability, and code organization. Deduct 5 points if global namespace 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 is not organized in logical sections with 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 data visualization principles: 1) Harmonious color matching (color-blind friendly, consistent palette) 2) Proper layout spacing (sufficient margin around the chart, appropriate bar width and spacing) 3) Professional typography (readable font sizes, proper text alignment). 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) Hover/click feedback delay ≤ 100ms 2) Transition animation duration controlled between 300-500ms 3) Clear visual feedback on interaction. Deduct 5 points for each operation without feedback, 3 points for laggy transitions, 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/create-pie-chart-from-table-data-html.json

@@ -0,0 +1,68 @@
+{
+  "index": 720,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to provide executable code whenever possible. I have a table - could you help me create a pie chart based on the data in the table and generate an HTML file?",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the data extraction and processing logic properly implemented?",
+      "description": "Evaluate if the code correctly extracts data from the table input and processes it for chart visualization. Check if the code handles various table formats (HTML tables, CSV strings, JSON data) and applies appropriate data transformations. Deduct 5 points if the code only handles one specific format, deduct 10 points if data extraction fails for complex tables.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the pie chart visualization correctly implemented with proper layout?",
+      "description": "Verify that the pie chart is correctly rendered with properly calculated sectors based on data values. Check that the chart uses appropriate angles, radii, and center points. Deduct 5 points if the chart has incorrect proportions, 3 points for minor rendering issues, and 10 points if the chart fails to represent data accurately.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the chart enhanced with proper labeling and legend?",
+      "description": "Check if the pie chart includes clear labels for each sector, a comprehensive legend, and meaningful title. Labels should show category names and values/percentages. Deduct 3 points for missing labels, 3 points for missing legend, and 4 points for poor placement that obstructs readability.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Are appropriate visualization libraries utilized effectively?",
+      "description": "Evaluate if the implementation makes appropriate use of chart libraries (like Chart.js, D3.js, or Google Charts) or implements custom SVG/Canvas rendering when needed. Check correct configuration of library-specific options. Deduct 5 points for inappropriate library choice, 3 points for inefficient implementation, and 10 points for library misuse.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as empty data, single-value datasets, very large or small values, text values mixed with numbers, etc.) and provide friendly error prompts or graceful fallbacks. Deduct 3 points for each unhandled edge case, and 10 points if the chart breaks completely on atypical inputs.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Interactive tooltips showing more details 2. Animation on hover/load 3. Ability to toggle between pie and donut chart 4. Export to image functionality). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar visualization methods 2. Function modules unrelated to chart visualization 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 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), code reusability, and maintainability. Deduct 5 points if global state pollution is found; deduct 3 points if the code is not organized into logical functions; deduct 2 points if there's no error handling. 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 visualization best practices: 1) Harmonious color scheme with good contrast 2) Proper proportions and layout 3) Professional typography (legible fonts, proper sizing). Deduct 3 points for poor color choices that hinder data perception, 4 points for cluttered design, and 3 points for illegible labels or text. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and responsive?",
+      "description": "Judge whether the chart provides appropriate interactive elements: 1) Responsive design that works across device sizes 2) Smooth transitions when data changes 3) Clear interactive elements (e.g., hover effects, clickable segments). Deduct 3 points for lack of responsiveness, 3 points for missing hover states, and 4 points for jerky transitions or poor performance with larger datasets. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "easy"
+}