@getollie/cli 0.0.1

package/README.md

@@ -0,0 +1,3 @@
+# Ollie
+
+Ollie is an generic "Prompting" framework for Pochi to evaluate a website, it accepts a URL, and generates a report

package/library/data_science-data_visualization_dashboards/air-quality-realtime-monitoring-system.json

@@ -0,0 +1,68 @@
+{
+  "index": 1117,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Air Quality Real-time Monitoring System\n\n1. Air Quality Real-time Monitoring\nDisplay online air quality monitoring data through charts, including hourly data and daily cumulative data for various cities and monitoring stations.\n\n2. Air Quality Ranking Display\nThe system ranks cities nationwide using AQI/composite index as evaluation criteria, displaying daily, monthly cumulative, and annual cumulative rankings for 74 cities, 168 cities, 337 cities, and various cities/counties in the Fenwei Plain. This helps users understand regional air quality conditions and their rankings among major cities nationwide.\n\n3. City Comparison Analysis Display\nSummarizes and displays analysis results for cities within a region. The system supports selecting any number of cities of interest to view trends in their hourly, daily, monthly, and annual data.\n\n4. Historical Data Query Display\nConsolidates historical monitoring data for cities, districts, counties, and monitoring stations within a region. Provides query functionality based on conditions (including city selection and date selection) for various pollutant values (AQI, PM2.5, PM10, O3, NO2, SO2, CO), pollution levels, and primary pollutants. Supports data export.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the real-time air quality monitoring visualization fully implemented?",
+      "description": "Review whether the code implements comprehensive chart visualizations for both hourly and daily cumulative air quality data across multiple cities and monitoring stations. Charts should include time series data, appropriate scales, legends, and tooltips. Score 0 if core visualization is missing, 5 if basic charts are implemented without real-time updates, and 10 if fully implemented with dynamic data refreshing (≤60s intervals) and smooth transitions between data points.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the air quality ranking display system properly implemented?",
+      "description": "Evaluate whether the code properly implements ranking visualizations for all required city groupings (74 cities, 168 cities, 337 cities, Fenwei Plain cities/counties) with correct sorting based on AQI/composite index. Check if daily, monthly, and annual cumulative ranking views are available with appropriate UI controls to switch between them. Deduct 3 points if any city grouping is missing, 2 points if ranking calculation is incorrect, and 3 points if visual representation lacks clarity (e.g., no color coding for pollution levels).",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the city comparison analysis functionality complete?",
+      "description": "Assess whether the code implements multi-city selection and comparison features, allowing users to select any number of cities and view comparative trends across different time periods (hourly, daily, monthly, annual). Check if the visualization uses appropriate chart types for comparison (line charts, bar charts, or radar charts), includes proper legends to distinguish cities, and allows for easy addition/removal of cities from comparison. Deduct 5 points if multi-city selection is limited or broken, and 5 points if time period switching is not implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the historical data query system fully functional?",
+      "description": "Verify whether the code implements a comprehensive query interface for historical data that includes all filtering capabilities (city selection, date range selection, pollutant selection) and displays all required metrics (AQI, PM2.5, PM10, O3, NO2, SO2, CO, pollution levels, primary pollutants). Check if query results are properly visualized and if data export functionality is implemented. Deduct 3 points for each missing filter type, 3 points for missing export functionality, and 4 points if query performance is poor (>2s response time for typical queries).",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as missing data points, API failures, network interruptions, invalid user inputs) and provide friendly error prompts or recovery mechanisms. Check for proper loading states, error boundaries, and fallback content. 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. AI-based pollution forecasting 2. Geospatial heatmap visualizations 3. Air quality alerts/notifications 4. Custom dashboard creation for users). 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 visualizations (e.g., multiple chart libraries used for the same purpose) 2. Function modules unrelated to air quality monitoring (e.g., unrelated weather features) 3. Fancy effects that affect performance (e.g., excessive animations or 3D effects 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 fetching/processing/visualization layers), component reusability, state management approach, and performance optimization techniques. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if no performance optimizations (like virtualization for large data sets, memoization, or lazy loading) are 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 design principles: 1) Harmonious color matching (using appropriate color schemes for air quality levels following standards like US EPA or China MEE) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional font system (body font size ≥ 14px, line height over 1.5 times). Deduct 3 points for each crowded visual element, 5 points for misleading color representation of pollution levels, and 5 points for chaotic dashboard 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) Filter application response time ≤ 300ms 2) Chart transition animations controlled between 300-500ms 3) Clear visual indicators for selected cities/time periods. Deduct 5 points for each major interaction without feedback, 3 points for jerky transitions between data views, and 5 points for hard-to-find filtering controls or comparison tools. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "hard"
+}

package/library/data_science-data_visualization_dashboards/analyze-file-data-dashboard-html.json

@@ -0,0 +1,68 @@
+{
+  "index": 1530,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate, professional responses. Be sure to provide executable code where possible. Analyze file data and create a data dashboard in HTML format.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the data parsing and processing logic fully implemented?",
+      "description": "Review whether the code accurately implements file parsing functions (CSV, JSON, Excel, etc.), data cleaning procedures, and proper error handling for malformed data. Score 0 if no parsing logic exists, 5 if basic parsing is implemented but lacks error handling, and 10 if comprehensive data processing with validation and sanitization is included.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are appropriate data visualization components implemented?",
+      "description": "Check whether the code includes effective visualization components (charts, graphs, tables) relevant to the data being analyzed. Evaluate if appropriate visualization libraries (D3.js, Chart.js, Highcharts, etc.) are properly integrated. Deduct 5 points if visualizations are basic or don't match the data characteristics, and 3 points if interactive features are missing. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the dashboard layout well-designed with proper responsiveness?",
+      "description": "Evaluate whether the dashboard implements responsive design principles using flexbox/grid layouts for different screen sizes. Check if the layout adapts appropriately from desktop to mobile views. Deduct 5 points if there's no responsive design implementation, and 3 points if there are layout inconsistencies across devices. Give 10 points if fully implemented with proper breakpoints.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Does the dashboard include filtering, sorting, and data manipulation capabilities?",
+      "description": "Check whether users can interact with the data through filters, sorting options, and other data manipulation tools. Verify if real-time data updates are reflected in visualizations when filters are applied. Deduct 5 points if only basic sorting is available, and 3 points if filter operations cause performance issues. 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 files, missing values, network interruption when loading external resources, 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. Dynamic data refresh capabilities 2. Export/download options for visualizations 3. Custom theming or dark/light mode toggle). 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 libraries doing the same job) 2. Function modules unrelated to data visualization (e.g., unnecessary animations) 3. Fancy effects that affect performance (e.g., excessive DOM manipulation). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating data processing/visualization/UI components), code organization, and performance optimization. Deduct 5 points if global variable pollution is found; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if no performance optimizations are implemented 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 dashboard follows modern design principles: 1) Harmonious color matching with consistent data visualization colors 2) Proper layout spacing and information hierarchy 3) Professional typography with readable font sizes and sufficient contrast. Deduct 3 points for each crowded visual element, 5 points for inconsistent or inaccessible color schemes, and 5 points for poor information organization. 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) Dashboard loads within 3 seconds 2) Chart transitions are smooth between 300-500ms 3) Interactive elements provide clear feedback. Deduct 5 points for slow initial loading (>5s), 3 points for jerky transitions when filtering/sorting data, and 5 points for unresponsive UI elements. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "easy"
+}

package/library/data_science-data_visualization_dashboards/annual-air-quality-analysis-page.json

@@ -0,0 +1,68 @@
+{
+  "index": 1615,
+  "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 as much as possible. Alright, now I need to build an annual air quality analysis page, please provide the code for HTML, CSS, and JavaScript files.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the air quality data visualization fully implemented?",
+      "description": "Review whether the code implements appropriate visualization methods (charts, maps, etc.) to display annual air quality data. Check if key metrics like AQI, PM2.5, PM10, O3, NO2, SO2 are included. Score 0 if visualizations are missing, 5 if only basic charts are implemented, and 10 if multiple interactive visualization types are provided with clear data representation.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is temporal analysis functionality implemented?",
+      "description": "Evaluate whether the code includes features for analyzing air quality trends over time (monthly patterns, seasonal variations, year-over-year comparisons). Check if time-series charts have proper date formatting, zoom/pan capabilities, and period selection options. Deduct 5 points if only static time views are available, and 3 points if comparative analysis is missing. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Are filtering and data manipulation features properly implemented?",
+      "description": "Check whether users can filter the air quality data by different parameters (location, pollutant type, time period, threshold values). Validate if the filtering is responsive and properly updates the visualizations. Deduct 5 points if filtering options are limited, and 3 points if there's no visual feedback during filtering. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the data loading and processing mechanism designed appropriately?",
+      "description": "Assess how the code handles data loading, parsing, and processing. Check for proper error handling during data fetching, loading indicators, and data caching strategies. Validate if the code can handle large datasets efficiently through techniques like data aggregation or lazy loading. Deduct 5 points if loading states aren't handled, and 3 points if data processing is inefficient. 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, API failures, invalid user inputs, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Predictive air quality forecasting 2. Correlation analysis with weather data 3. Interactive health impact indicators based on AQI). 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 visualizations (e.g., multiple line charts showing the same data) 2. Function modules unrelated to air quality analysis (e.g., unrelated weather widgets) 3. Fancy effects that affect performance (e.g., excessive animations or 3D effects). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating data processing/visualization/UI layers), code organization, and optimization techniques. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if performance optimization techniques (like debouncing for filters) are missing. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching for different air quality levels (using standardized AQI color schemes) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional font system (body font size ≥ 14px, line height over 1.5 times). Deduct 3 points for each crowded visual element, 5 points for misleading color representations of air quality data, and 5 points for chaotic dashboard 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) Chart transitions respond within 300ms 2) Tooltips and data popups appear within 100ms of hover 3) Clear visual feedback for selection states. Deduct 5 points for laggy chart updates, 3 points for jumpy transitions between data views, and 5 points for confusing interaction patterns when exploring the data. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "medium"
+}

package/library/data_science-data_visualization_dashboards/aquaculture-dashboard-html-chartjs.json

@@ -0,0 +1,68 @@
+{
+  "index": 725,
+  "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. Help me create an aquaculture sector digital dashboard display using HTML and Chart.js.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is a complete aquaculture dashboard layout implemented?",
+      "description": "Evaluate whether the code creates a comprehensive dashboard structure with proper sections for key aquaculture metrics (water quality parameters, fish growth data, feed conversion ratios, mortality rates, etc.). Score 0 if there's no dashboard structure, 5 if only a basic layout exists, and 10 if a complete, well-organized dashboard with all essential aquaculture KPIs is implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are appropriate chart visualizations used for aquaculture data?",
+      "description": "Check if the code utilizes Chart.js to create suitable visualization types for different aquaculture metrics: line charts for time-series data (oxygen levels, temperature), bar charts for comparative data (harvest volumes, feed consumption), pie/doughnut charts for distribution data (species breakdown, cost allocation), and gauge charts for critical parameters with threshold limits. Deduct 3 points for each inappropriate chart type selection or missing essential visualization. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is real-time or simulated data monitoring implemented?",
+      "description": "Assess if the dashboard includes functionality for real-time data updates or simulated data streams that mimic actual aquaculture monitoring systems. Check for WebSocket connections, polling mechanisms, or timer-based updates. Score 0 if no data refresh mechanism exists, 5 if basic simulation is implemented, and 10 if a comprehensive real-time monitoring system with appropriate update frequencies for different metrics is included (e.g., critical parameters updating more frequently).",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Are aquaculture-specific alert systems and thresholds implemented?",
+      "description": "Evaluate whether the code implements critical threshold alerts for key parameters such as dissolved oxygen, temperature, pH, ammonia levels, etc. Check if visual indicators (color changes, flashing elements) and notification systems are present when parameters breach safe ranges. Deduct 3 points for each missing critical parameter alert, and 5 points if no threshold system exists 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 points, sensor failures, extreme outlier values) and provide appropriate fallback mechanisms or error handling. Check for data validation before visualization and graceful degradation. Code with strong robustness should handle these edge cases effectively, 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 aquaculture monitoring experience (e.g., 1. Predictive analytics for harvest timing 2. Weather data integration affecting water parameters 3. Interactive pond/tank selection map 4. Cross-parameter correlation visualization). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant visualization of the same metrics in multiple formats 2. Excessive dashboard elements unrelated to aquaculture management 3. Fancy effects that affect performance or distract from critical data (e.g., unnecessary animations on critical alerts). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core monitoring functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (separation of data handling, visualization logic, and UI components), reusability of chart components, and maintainability. Check for proper Chart.js configuration with options appropriate for aquaculture data visualization. Deduct 5 points if global variables are excessively used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there's no organized structure for different dashboard sections. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the dashboard follows professional design principles: 1) Appropriate color scheme for data visualization (using blue tones for water parameters, red for alerts, etc.) 2) Proper layout with logical grouping of related metrics 3) Consistent typography with adequate contrast for legibility in control room environments. Deduct 3 points for cluttered visuals, 5 points for color schemes that make data interpretation difficult, and 5 points for poor information hierarchy. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dashboard responsive and optimized for operational use?",
+      "description": "Judge whether the dashboard is optimized for practical use in aquaculture facilities: 1) Responsive design that works on different devices (control room monitors, tablets for on-site inspections) 2) Loading optimizations to handle large datasets 3) Appropriate data density that prioritizes critical information. Deduct 5 points if the dashboard is unusable on mobile devices, 3 points if charts render slowly with moderate data amounts, and 5 points if critical alerts aren't immediately visible. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "medium"
+}

package/library/data_science-data_visualization_dashboards/armored-transport-industry-data-dashboard.json

@@ -0,0 +1,68 @@
+{
+  "index": 1391,
+  "question": "You are a coding expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable for display. Create a comprehensive data dashboard for the armored transport industry, including visualizations and data presentation. Output in HTML format, ensuring the file is executable.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Dashboard layout and structure implementation",
+      "description": "Review whether the dashboard has a well-structured layout with proper organization of key components (header, sidebar, content area, footer) and responsive design. Check for a grid system implementation that adapts to different screen sizes. Score 0 if there's no clear structure, 5 if basic layout exists but isn't responsive, and 10 if the dashboard has a professional, responsive layout with proper component hierarchy.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Data visualization quality and variety",
+      "description": "Evaluate the implemented visualizations for the armored transport industry. Check for diverse chart types (line charts, bar charts, maps for route tracking, etc.) appropriate for displaying relevant metrics like security incidents, delivery times, and vehicle status. Assess whether D3.js or other libraries are used effectively. Deduct 3 points for each missing essential visualization type, and 5 points if visualizations aren't interactive. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Industry-specific KPI implementation",
+      "description": "Check whether the dashboard displays armored transport industry-specific KPIs such as on-time delivery rate, security breach incidents, vehicle fleet status, route efficiency, and money handling accuracy. Verify if the metrics are calculated correctly and displayed prominently with proper visual hierarchy. Deduct 2 points for each missing critical KPI and 5 points if the calculation logic is flawed or absent. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Data filtering and interactivity features",
+      "description": "Assess whether the dashboard provides interactive elements for data exploration, including date range selectors, vehicle/route filters, and drill-down capabilities for detailed analysis. Check for proper implementation of dynamic updates when filters change. Deduct 3 points if filter controls are missing, 3 points if the filters don't affect visualization updates, and 4 points if there's no drill-down functionality. 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, 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. Real-time alerts for security incidents 2. Predictive analytics for route optimization 3. Interactive map with vehicle tracking 4. Custom reporting tools). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple filtering mechanisms that accomplish the same task) 2. Function modules unrelated to armored transport industry (e.g., irrelevant visualizations) 3. Fancy effects that affect performance (e.g., excessive animations that slow down the dashboard). 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/user interaction layers), code reusability for visualization components, and efficient data handling. 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 data caching or optimization 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 matching suitable for data visualization (no more than 3 primary colors, with appropriate use of alarm colors for critical metrics) 2) Proper layout spacing (dashboard elements follow consistent grid spacing) 3) Professional typography system (clear hierarchy in headings and metrics). Deduct 3 points for each cluttered dashboard section, 5 points for poor color choices that hinder data interpretation, and 5 points for inconsistent visual design across components. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the dashboard interactions conform to user expectations: 1) Chart tooltips appear within 100ms 2) Filter changes update visualizations within 500ms 3) Smooth transitions between different dashboard views. Deduct 5 points for each interaction without visual feedback, 3 points for jerky or laggy transitions, and 5 points for confusing navigation between dashboard sections. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "medium"
+}

package/library/data_science-data_visualization_dashboards/bar-chart-consumption-savings-comparison.json

@@ -0,0 +1,68 @@
+{
+  "index": 1489,
+  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Pay attention to ensuring that the generated code is executable for display. Please help me generate a bar chart comparison diagram based on the given content:\n\n┌───────────────┬─────────────┬─────────────┐  \n│       Item             │   Traditional Mode Consumption   │   Circular Mode Savings       │  \n├───────────────┼─────────────┼─────────────┤  \n│ Raw Wood Consumption   │ Equivalent to destroying 20 mu of forest | Recycled paper raw materials: 800 tons │  \n│ Carbon Dioxide Emissions│ Equal to annual emissions of 160 cars | Equivalent to planting 7000 fir trees │  \n│ Student Economic Burden │ Reduction of 35,000 bubble tea drinks | Convertible to 25,000 cups of campus benefits │  \n└───────────────┴─────────────┴─────────────┘",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the bar chart properly implemented with HTML/CSS/JavaScript?",
+      "description": "Evaluate whether the code uses appropriate web technologies (SVG, Canvas, or CSS) to render the bar chart. Check for proper initialization, scaling, and rendering of bars. Score 0 if no functional chart is created, 5 if basic bars are displayed but with issues, and 10 if the implementation is complete and visually correct.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the data from the table correctly represented in the visualization?",
+      "description": "Verify that all data points from the provided table (Raw Wood, Carbon Dioxide, Student Economic Burden) are accurately represented in the chart. All 3 categories and their corresponding values for both Traditional Mode and Circular Mode must be visualized. Deduct 3 points for each missing or incorrectly represented data point. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Are appropriate scales and units used for the different metrics?",
+      "description": "Check if the visualization handles the different units (forest area, tons, car emissions, trees, bubble tea drinks, campus benefits) appropriately. The visualization should normalize these different metrics for comparison or provide clear unit indicators. Deduct 4 points if units are misrepresented, 3 points if scales are inappropriate for comparison, and 3 points if no unit indicators are provided. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Does the chart effectively communicate the comparison between Traditional Mode and Circular Mode?",
+      "description": "Assess whether the visualization clearly shows the contrast between consumption and savings. The chart should visually distinguish between the two modes (e.g., through color coding, positioning, or labels) and make the comparison intuitive. Deduct 5 points if modes are not visually differentiated, 3 points if the comparison is unclear, and 2 points if labels don't clearly indicate which mode is which. 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 window resizing, different screen sizes, browser compatibility issues, etc.) and provide appropriate fallbacks. Code with strong robustness should have responsive design considerations and graceful degradation. Give 10 points for comprehensive error handling and responsiveness, 5 points for average robustness, and 0 points if these considerations are absent.",
+      "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 visualization experience (e.g., 1. Interactive tooltips showing detailed information 2. Animation transitions when switching views 3. Additional data visualization like percentage comparisons). 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. Visualization elements unrelated to the data comparison 3. Fancy effects that affect performance or clarity (e.g., excessive animations). 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 logic), code reusability, and maintainability. Deduct 5 points if global variables are overused or proper encapsulation is missing; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there are no 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 overall design follows modern data visualization principles: 1) Harmonious color matching (no more than 3 primary colors with appropriate contrast) 2) Proper layout spacing and positioning 3) Professional typography (readable font size ≥ 12px, appropriate font choices). Deduct 3 points for each visual clutter element, 5 points for poor color choices that hinder data interpretation, and 5 points for illegible text or improper labeling. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the chart interactive and user-friendly?",
+      "description": "Judge whether the chart provides appropriate interactivity: 1) Responsive tooltips or information on hover/click 2) Smooth transitions if data views can be changed 3) Clear visual cues for interactive elements. Deduct 5 points if there's no interactivity when it would benefit understanding, 3 points for laggy interactions, and 5 points if interactive elements aren't intuitive or accessible. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "easy"
+}

package/library/data_science-data_visualization_dashboards/candlestick-charts-patterns-buy-sell-resistance.json

@@ -0,0 +1,68 @@
+{
+  "index": 917,
+  "question": "You are a coding expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to ensure that the generated code is executable for demonstration. Create a visualization that draws candlestick charts and labels patterns, strokes, segments, pivots, buy/sell points, and resistance levels.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the candlestick chart visualization properly implemented?",
+      "description": "Review whether the code accurately renders candlestick charts with correct OHLC (Open, High, Low, Close) data representation. Check if the candlesticks properly show bullish (typically green/white) and bearish (typically red/black) price movements. Score 0 if the basic candlestick rendering is missing, 5 if only basic candlesticks are displayed without proper styling, and 10 if candlesticks are fully implemented with proper color coding and proportional scaling.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are chart patterns properly identified and labeled?",
+      "description": "Evaluate how well the code identifies and labels common chart patterns (e.g., head and shoulders, double tops/bottoms, triangles, flags). Check if the pattern recognition algorithm uses proper technical analysis principles rather than simplistic shape matching. Deduct 5 points if pattern detection is rudimentary, 3 points if the visual labeling is unclear, and give full marks if patterns are correctly identified with confidence levels and clear visual indicators.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Are the strokes, segments, and pivots correctly identified and visualized?",
+      "description": "Check whether the code identifies price movements as strokes (directional price movements), segments (collections of strokes), and pivots (significant reversal points). The visualization should clearly differentiate between these elements with distinct visual styling. Deduct 5 points if the algorithm doesn't properly identify swing highs/lows, 5 points if the visual representation is confusing, and give full points if both the algorithm and visualization are technically accurate.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Are buy/sell signals and resistance/support levels clearly marked?",
+      "description": "Examine if the code implements algorithms to identify potential buy/sell signals based on technical analysis principles and marks support/resistance levels. The visualization should prominently highlight these critical trading points. Deduct 5 points if the signals aren't based on established technical indicators, 3 points if they lack visual prominence, and give full marks if signals include both entry and exit points with risk management annotations.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as missing data points, outliers, different data formats, or zoom levels) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Interactive tooltips showing pattern confidence levels 2. Ability to toggle between different timeframes 3. Visual backtesting of identified patterns). 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 indicators (e.g., multiple versions of the same resistance level detection) 2. Function modules unrelated to technical analysis (e.g., unnecessary animations) 3. Elements that clutter the visualization and reduce clarity. 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/user interaction layers), reusability of components, and performance optimization for large datasets. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the visualization performs poorly with larger datasets. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the overall design follows financial visualization best practices: 1) Appropriate color scheme for financial data (distinguishing up/down movements) 2) Clear grid lines and axis labeling 3) Proper information hierarchy with the most important data being most visually prominent. Deduct 3 points for each crowded visual element, 5 points for poor color choices that hinder data interpretation, and 5 points for chaotic pattern/indicator labeling. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and responsive?",
+      "description": "Judge whether the chart provides essential interactive capabilities: 1) Smooth zooming and panning without visual lag 2) Responsive tooltips appearing within 100ms 3) Clear visual feedback when hovering over significant elements like patterns or signals. Deduct 5 points if zooming/panning is jerky, 3 points if tooltips are delayed or poorly positioned, and 5 points if the visualization lacks basic interactivity expected in modern financial charts. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "medium"
+}

package/library/data_science-data_visualization_dashboards/cdn-monitoring-tool-global-speed-availability.json

@@ -0,0 +1,68 @@
+{
+  "index": 515,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the code you provide is executable whenever possible. Develop a CDN distribution monitoring tool that checks website access speed and availability across different global regions. Display loading times and error rates for various regions on a map, with support for setting detection frequency and alert conditions. Provide historical data comparison and trend analysis, as well as CDN node switching recommendations.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the global CDN monitoring system fully implemented?",
+      "description": "Review whether the code implements a comprehensive global CDN monitoring system with multiple geographic test points, parallel request handling, and proper timeout management. Check if it supports various HTTP methods and header configurations for accurate simulation of real user requests. Score 0 if the core monitoring functionality is missing, 5 if only basic single-region monitoring is implemented, and 10 if it includes at least 8 global regions with configurable test parameters.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the map visualization properly implemented?",
+      "description": "Evaluate whether the code implements an interactive map (using libraries like Leaflet, Mapbox, or D3.js) that accurately displays global CDN performance metrics. Check if the map includes color-coded performance indicators, proper tooltips showing detailed metrics, and responsive design that works across different screen sizes. Deduct 5 points if the map lacks interactive elements, 3 points if region identification is unclear, and 3 points if performance data is not visually distinguished (e.g., through color gradients or sized markers). The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Are the detection frequency and alert mechanisms properly implemented?",
+      "description": "Check if the code provides configurable monitoring intervals (from seconds to days) with proper throttling to prevent API abuse. Verify that the alert system includes threshold configuration, multiple notification channels (email, SMS, webhook), and alert escalation logic. Deduct 5 points if the monitoring frequency is hardcoded, 3 points if alerts lack severity levels, and 5 points if there's no mechanism to prevent alert storms. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the historical data comparison and trend analysis feature implemented?",
+      "description": "Review whether the solution includes data persistence (database or structured file storage), time-series visualization (charts showing performance trends), and statistical analysis functions (calculating percentiles, detecting anomalies). Check if it supports comparing current performance against historical baselines and can identify seasonal patterns. Deduct 5 points if data retention is limited to less than 7 days, 3 points if trend visualization is missing, and 3 points if there's no anomaly detection. 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 API rate limiting, network timeouts, data corruption, etc.) and provide friendly error prompts or recovery mechanisms. Check for proper error handling when testing endpoints are unavailable or return unexpected responses. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Real-time protocol performance comparison (HTTP/1.1 vs HTTP/2 vs HTTP/3) 2. Synthetic transaction monitoring beyond simple pings 3. AI-powered prediction of potential CDN issues). 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 monitoring functions (e.g., multiple HTTP client libraries doing the same job) 2. Function modules unrelated to CDN monitoring (e.g., a built-in weather widget) 3. Fancy effects that affect performance (e.g., excessive animations that consume CPU). 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 monitoring logic/visualization/data storage layers), unit test coverage, and build process automation. Check if the code follows proper architecture patterns for monitoring applications (e.g., observer pattern, pub/sub for alerts). Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the build process is not automated. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional monitoring dashboard standards?",
+      "description": "Evaluate whether the dashboard design follows monitoring-specific design principles: 1) Appropriate use of color for severity indication (red for critical, yellow for warnings, etc.) 2) Clear information hierarchy with most important metrics prominently displayed 3) Proper density of information without overwhelming the user. Deduct 3 points for each confusing visual element, 5 points for misleading color usage (e.g., using red for normal status), and 5 points for cluttered dashboards that hinder quick issue identification. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and informative for monitoring purposes?",
+      "description": "Judge whether the interactive elements serve monitoring needs: 1) Quick filters to isolate problem regions/nodes 2) Drill-down capabilities from overview to detailed metrics 3) Clear visual indications when data is being refreshed or is stale. Deduct 5 points for missing real-time update indicators, 3 points for unclear data timestamp information, and 5 points for interactions that interrupt the monitoring workflow (e.g., modal dialogs that block the view of critical alerts). The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "hard"
+}