@getollie/cli 0.0.1

package/library/data_science-data_visualization_dashboards/shaanxi-elderly-care-data-dashboard.json

@@ -0,0 +1,68 @@
+{
+  "index": 1439,
+  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Make sure that the code you generate is executable for display. Create a comprehensive data dashboard for innovative elderly care models in Shaanxi Province, including visualization design and detailed data presentation. Output should be in HTML format to ensure executability.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the elderly care data dashboard structure properly implemented?",
+      "description": "Review whether the code accurately implements a complete dashboard structure with proper HTML5 semantic layout (header, main content areas, sidebar, footer) and responsive design. Check if CSS Grid/Flexbox is used for layout management and if the dashboard includes necessary navigation components. Score 0 if the basic structure is missing, 5 if only basic layout is implemented without semantic HTML, and 10 if a complete, semantic, and responsive dashboard framework is implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are the data visualization components properly implemented?",
+      "description": "Verify implementation of essential charts for elderly care data (demographic trends, service distribution, facility locations, etc.) using appropriate visualization libraries (D3.js, Chart.js, ECharts, etc.). Charts should include proper axes, legends, tooltips, and interactive elements. Deduct 3 points if charts lack proper legends/tooltips, 5 points if visualizations are static without interactivity, and 5 points if inappropriate chart types are chosen for the data. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is Shaanxi-specific geographical data visualization implemented?",
+      "description": "Check if the dashboard includes a map visualization of Shaanxi Province with accurate regional boundaries, showing elderly care facility distribution, coverage areas, or regional statistics. Verify if the map is interactive (zoom, pan, click for details) and uses appropriate geographical encoding (colors, symbols). Deduct 5 points if the map is static, 3 points if it lacks proper legends, and 5 points if geographical data is inaccurate. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the elderly care innovation model comparison feature implemented?",
+      "description": "Evaluate if the dashboard provides visual comparisons between traditional and innovative elderly care models in Shaanxi (e.g., service efficiency, cost analysis, satisfaction rates, health outcomes). Check for implementation of comparative charts, before/after views, or innovation impact metrics. Deduct 5 points if comparison metrics are missing, 3 points if data lacks context explanations, and 5 points if innovative models aren't clearly distinguished. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as missing data, browser compatibility issues, screen size variations, 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. AI-driven insights and predictions 2. Elderly user persona profiles 3. Time-series animation of demographic changes 4. Voice-controlled dashboard navigation for accessibility). 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 charts showing the same data differently) 2. Feature modules unrelated to elderly care in Shaanxi (e.g., irrelevant statistics from other regions) 3. Fancy effects that affect performance (e.g., unnecessary 3D effects or animations). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core 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 maintainability. Deduct 5 points if global variable pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there's no data loading 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 dashboard design follows modern design principles: 1) Harmonious color matching suitable for elderly care theme (no more than 3 primary colors) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional font system (body font size ≥ 14px, line height over 1.5 times). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic text-image layout. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Data filter/selection feedback delay ≤ 100ms 2) Chart transition animation duration controlled between 300-500ms 3) Clear visual focus guidance for elderly care insights. Deduct 5 points for each operation without feedback, 3 points for visual stuttering during interactions, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "easy"
+}

package/library/data_science-data_visualization_dashboards/shanxi-gdp-growth-chart.json

@@ -0,0 +1,68 @@
+{
+  "index": 1701,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Ensure that the code generated is executable for display purposes. Please use HTML and Chart.js to help me create a comparison table showing Shanxi Province's GDP, Shanxi Province's GDP growth rate, and the national GDP growth rate from 2010-2024 based on data compiled from the National Bureau of Statistics and Shanxi Provincial Statistical Yearbook (Note: 2023-2024 are predicted values). Note: Both sets of data should be presented in a single table.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the data visualization properly implemented with Chart.js?",
+      "description": "Evaluate whether the Chart.js library is correctly imported, initialized, and configured. Check if appropriate chart types are selected for GDP values (bar chart) and growth rates (line chart). The chart should use the mixed chart type capability of Chart.js to display both values simultaneously. Deduct 5 points if library integration is incorrect, 3 points if chart types are inappropriate for the data types, and 5 points if the mixed chart functionality isn't utilized. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the complete dataset for Shanxi and national GDP accurately represented?",
+      "description": "Verify that the code includes all required data points from 2010-2024 (including predicted values for 2023-2024). The data should include Shanxi Province's GDP absolute values, Shanxi Province's GDP growth rates, and national GDP growth rates. All 15 years must be represented with clear labeling of predicted values. Deduct 5 points for incomplete data, 3 points if predicted values aren't clearly distinguished, and 5 points if any data category is missing. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Does the visualization include appropriate labels, legends, and annotations?",
+      "description": "Check if the chart includes proper title, axis labels (years on x-axis, GDP values on primary y-axis, growth rates on secondary y-axis), and a legend clearly identifying each data series. The visualization should also include annotations indicating predicted values for 2023-2024. Deduct 3 points for missing title, 2 points for unclear or missing axis labels, 2 points for missing legend, and 3 points if predictions aren't annotated. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the chart responsive and properly scaled for different displays?",
+      "description": "Evaluate if the chart implements responsive design principles using Chart.js options like 'responsive: true' and 'maintainAspectRatio'. Test if the visualization adapts to different screen sizes without distortion or overflow. Proper scaling of y-axes is required to accommodate both the GDP values and percentage growth rates. Deduct 5 points if no responsiveness is implemented, 3 points if the chart overflows on mobile screens, and 2 points if axes scaling creates visual confusion. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as data loading errors, missing values, browser compatibility issues) and provide friendly error prompts or fallback mechanisms. Code with strong robustness should include error handling for Chart.js initialization and data processing. Give 10 points if fully implemented with try-catch blocks and data validation, 5 points if basic error handling is present, and 0 points if exceptions are not handled at all.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Interactive tooltips with additional economic context 2. Toggle functionality to show/hide specific data series 3. Animation effects for data presentation 4. Trend line or correlation analysis). 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. Unrelated data or chart elements that don't contribute to the GDP comparison 3. Excessive decorative elements that distract from the data presentation. 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, chart configuration, and rendering logic), code organization, and maintainability. Deduct 5 points if global variables are excessively used; deduct 5 points if the code structure is monolithic with no separation of concerns; deduct 5 points if hardcoded values are used instead of configuration options. 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 data visualization best practices: 1) Professional color scheme with sufficient contrast between data series 2) Proper spacing and layout with clear visual hierarchy 3) Appropriate font choices and sizing for readability. Deduct 3 points for poor color choices that make data series indistinguishable, 5 points for cluttered layout with overlapping elements, and 5 points for illegible text or numbers. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the chart provides appropriate interactive features: 1) Responsive hover tooltips showing precise data values 2) Smooth animations when initializing or updating the chart 3) Intuitive controls if interactive elements are included. Deduct 5 points for missing tooltips on data points, 3 points for jerky or distracting animations, and 5 points for interactive elements that lack visual feedback. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "easy"
+}

package/library/data_science-data_visualization_dashboards/smart-restaurant-data-dashboard-visualization.json

@@ -0,0 +1,68 @@
+{
+  "index": 1593,
+  "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 display. Based on the following data: \"There are 748 users in total. 407 users who visited last year did not visit this year; among these 407 people, 129 made purchases last year and 278 did not make any purchases. 341 people visited this year; among these 341 people, 24 made purchases last year, 139 have never made a purchase, and 178 made purchases recently. Overall purchase frequency: 417 people made 0 purchases, 197 people made 1 purchase, 60 people made 2 purchases, 59 people made 3 to 8 purchases, and 15 people made 9 or more purchases.\" Please create a comprehensive data dashboard for the smart restaurant industry, with visualization design and data presentation, output in HTML format, ensuring the file is executable.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the data analysis and calculation accuracy verified?",
+      "description": "Review whether the code accurately processes the given statistical data (748 total users, visit patterns, purchase behaviors). Check if all numerical relationships are correctly calculated and cross-validated (e.g., 407 non-visitors + 341 visitors = 748, purchase frequency totals match user counts). Score 0 if basic data parsing is incorrect, 5 if minor calculation discrepancies exist, and 10 if all data relationships are mathematically consistent and verifiable.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are multiple professional visualization charts implemented effectively?",
+      "description": "Evaluate whether the dashboard includes diverse and appropriate chart types for restaurant analytics: user segmentation (pie/donut charts), purchase behavior flow (sankey/funnel), time-based trends (line/area charts), and distribution analysis (histograms/heatmaps). Each chart must use proper data binding and interactive legends. Deduct 3 points for each inappropriate chart type selection, 5 points if charts lack proper data labels or scales. Full score requires 5+ distinct visualization types.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the dashboard interactivity and filtering system comprehensive?",
+      "description": "Check whether the dashboard provides professional-grade interactive features: cross-chart filtering, drill-down capabilities, date range selectors, user segment toggles, and real-time data updates. Interactive elements should support brush selection, hover tooltips with detailed metrics, and synchronized highlighting across multiple charts. Deduct 5 points if filtering doesn't work across all charts, 3 points for missing hover interactions, 5 points if no drill-down functionality exists.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Are restaurant industry KPIs and insights properly integrated?",
+      "description": "Assess whether the dashboard includes restaurant-specific metrics and actionable insights: customer lifetime value calculations, retention rate analysis, purchase frequency segmentation, churn risk indicators, and revenue impact projections. Must include calculated metrics like repeat customer rate, average order patterns, and seasonal trend indicators. Deduct 5 points if generic metrics are used instead of restaurant-specific KPIs, 5 points if no predictive or actionable insights are provided.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust and error-handling comprehensive?",
+      "description": "Evaluate whether the code can handle edge cases like missing data points, invalid user inputs, chart rendering failures, and browser compatibility issues. Should include data validation, graceful degradation for unsupported features, and meaningful error messages. Code should handle scenarios like zero-value datasets, extreme outliers, and dynamic data updates without breaking. Give 10 points for comprehensive error handling, 5 points for basic validation, 0 points if no exception handling exists.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there innovative dashboard features that enhance business value?",
+      "description": "Check for advanced features that distinguish this from basic dashboards: predictive analytics overlays, automated insight generation, comparative benchmarking, export functionality with custom reports, mobile-responsive design, or real-time collaboration features. Each innovative feature should provide tangible business value for restaurant decision-making. Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant or irrelevant dashboard elements?",
+      "description": "Strictly identify three types of redundancy: 1. Duplicate visualizations showing identical data patterns 2. Non-essential decorative elements that don't support decision-making 3. Over-complicated animations or transitions that slow down analysis workflow. Dashboard should maintain focus on actionable restaurant insights without visual clutter. Deduct 3 points for each redundant element found, and directly deduct 10 points if core analytical functions are hindered by unnecessary features.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code demonstrate professional engineering standards?",
+      "description": "Review code architecture including separation of data processing, visualization rendering, and interaction handling. Check for modular JavaScript structure, proper use of visualization libraries (D3.js, Chart.js, etc.), performance optimization for large datasets, and maintainable CSS organization. Deduct 5 points for monolithic code structure, 5 points for inefficient DOM manipulation, 5 points for missing performance optimizations in data processing. Full score requires clean, scalable code architecture.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the visual design meet professional dashboard standards?",
+      "description": "Evaluate adherence to dashboard design principles: 1) Consistent color scheme with semantic meaning (success/warning/danger states) 2) Proper information hierarchy with clear visual grouping 3) Professional typography with readable font sizes (≥12px for data labels, ≥14px for body text) 4) Adequate whitespace and grid alignment. Deduct 3 points for each visual inconsistency, 5 points for poor color contrast or accessibility issues, 5 points for cluttered layout that impedes data comprehension.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Are interactions smooth with optimal user experience flow?",
+      "description": "Judge whether dashboard interactions follow UX best practices: 1) Chart transitions and updates complete within 300-800ms 2) Loading states for data processing operations 3) Intuitive navigation between different analytical views 4) Clear visual feedback for all interactive elements 5) Responsive behavior across different screen sizes. Deduct 5 points for each laggy interaction, 3 points for missing loading indicators, 5 points for non-intuitive user flow that requires explanation.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "easy"
+}

package/library/data_science-data_visualization_dashboards/stock-limit-up-monitoring-display.json

@@ -0,0 +1,68 @@
+{
+  "index": 963,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure the code you generate is executable when displayed. Help me create a real-time data display for stock limit-up monitoring in a TongHuaShun-style format. It should be in HTML format with a window interface and have an attractive design.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the real-time stock data display system fully implemented?",
+      "description": "Review whether the code accurately implements real-time stock data fetching and display through HTML/JavaScript, including stock price updates, percentage changes, volume data, and limit-up detection logic. Score 0 if core data display is not implemented, 5 if only basic price display is shown, and 10 if comprehensive stock metrics including limit-up alerts are fully integrated.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the TongHuaShun-style interface design authentically replicated?",
+      "description": "Check whether the interface design follows TongHuaShun's characteristic layout including: data grid tables, color-coded price changes (red for up, green for down), professional financial dashboard appearance, and appropriate use of financial industry UI conventions. Deduct 5 points if the visual style doesn't match professional trading platforms, and 3 points if color coding doesn't follow market standards. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the limit-up monitoring mechanism properly designed with alert functionality?",
+      "description": "Evaluate whether the system includes accurate limit-up detection (typically 10% increase for most stocks, 20% for ST stocks), real-time monitoring with visual/audio alerts, and filtering capabilities for limit-up stocks. Deduct 5 points if limit-up calculation is incorrect, 3 points if no alert mechanism exists, and 2 points if filtering is not implemented. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the window interface system complete with proper interaction controls?",
+      "description": "Check whether the code implements a complete windowed interface with resizable panels, sortable columns, search/filter functionality, and proper window management (minimize, maximize, close). Deduct 5 points if window controls are missing, 3 points if tables are not sortable, and 2 points if search functionality is absent. Give 10 points if fully implemented with smooth window operations.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as API failures, network interruption, invalid stock data, real-time data feed errors, 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 trading experience (e.g., 1. Real-time candlestick mini-charts 2. Sound alerts for limit-up events 3. Historical limit-up statistics 4. Custom watchlist management 5. Export functionality for limit-up data). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple data fetching mechanisms coexisting) 2. Function modules unrelated to stock monitoring (e.g., built-in games or social features) 3. Fancy effects that affect performance (e.g., excessive animations during data updates). Deduct 3 points for each redundancy found, and directly deduct 10 points if core financial data display is interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating data fetching/display/alert logic), proper error handling, and clean code structure. 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 data processing is inefficient for real-time updates. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional financial design standards?",
+      "description": "Evaluate whether the overall design follows professional trading platform principles: 1) Appropriate use of financial industry colors (red/green for gains/losses) 2) Clear data hierarchy with proper spacing (follows 8px grid system) 3) Professional typography (monospace fonts for numbers, readable font sizes ≥ 12px for data tables). Deduct 3 points for each unclear data presentation, 5 points for unprofessional color schemes, and 5 points for poor data table formatting. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the real-time data update smooth and performant?",
+      "description": "Judge whether the real-time updates are optimized for performance: 1) Data refresh rate appropriate for stock monitoring (1-3 seconds) 2) Smooth transitions without flickering during updates 3) Efficient DOM manipulation to prevent lag 4) Proper handling of high-frequency data streams. Deduct 5 points for each performance bottleneck, 3 points for visual glitches during updates, and 5 points for slow response to limit-up events. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "hard"
+}

package/library/data_science-data_visualization_dashboards/stock-price-k-line-charts-app.json

@@ -0,0 +1,68 @@
+{
+  "index": 1679,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to ensure that the code you generate is executable for demonstration. Create an application software for analyzing and displaying historical stock price amplitude data with K-line charts.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the stock data retrieval and processing system fully implemented?",
+      "description": "Review whether the code effectively retrieves historical stock price data from a reliable source (like Yahoo Finance, Alpha Vantage API), processes it correctly (handles missing data points, adjusts for splits/dividends), and converts it to proper OHLC (Open, High, Low, Close) format for K-line visualization. Score 0 if data retrieval is not implemented, 5 if basic data fetching exists but lacks error handling or preprocessing, and 10 if a complete data pipeline with caching and refresh mechanisms is implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the K-line chart rendering accurate and complete?",
+      "description": "Evaluate whether the K-line chart correctly implements standard candlestick visualization with proper color coding (e.g., green for bullish, red for bearish candles), accurate price scaling, and correct time-axis representation. Check if volume bars are included below the main chart. Deduct 5 points if candle bodies or shadows are incorrectly rendered, 3 points if time scale is inconsistent, and 3 points if volume representation is missing. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Are technical analysis indicators and overlays implemented?",
+      "description": "Check whether the application includes common technical indicators (e.g., Moving Averages, RSI, MACD, Bollinger Bands) with correct mathematical implementation and visual representation. Score 3 points for each properly implemented indicator category (moving averages, oscillators, volatility indicators, volume indicators) up to a maximum of 10 points. Implementation should include accurate calculations and appropriate visual distinction from price data.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Does the application provide interactive analysis features?",
+      "description": "Assess whether the application allows users to interact with the chart through zooming, panning, selecting time ranges, comparing multiple stocks, or drawing trend lines/Fibonacci retracements. Score 2 points for each well-implemented interactive feature. Check if values are displayed on hover/selection and if selection events provide detailed information about specific candles. 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 failures, malformed data, network interruption, extreme market conditions like circuit breakers) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should gracefully degrade functionality rather than crash. Give 10 points if robust error handling exists throughout the application, 5 points if only basic error handling is implemented, and 0 points if exceptions are unhandled.",
+      "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. Pattern recognition algorithms to identify chart patterns 2. AI-based price prediction overlays 3. Social sentiment analysis integration 4. Automated technical signal alerts). 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. Multiple implementations of similar visualization methods 2. Excessive indicators that clutter the chart or duplicate information 3. Heavy animations or visual effects that impair chart clarity or performance. Deduct 3 points for each redundancy found, and directly deduct 10 points if core functionality is compromised by unnecessary features.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (separation of data retrieval, processing, and visualization layers), use of appropriate design patterns for financial data handling, and implementation of state management. Deduct 5 points if global state pollution exists or if the application has poor component architecture; deduct 5 points if there's significant code duplication across similar indicators; deduct 5 points if there's no test coverage for critical calculations. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional trading platform standards?",
+      "description": "Evaluate whether the design follows financial application conventions: 1) Appropriate color scheme that reduces eye strain for extended viewing (dark mode option) 2) Clear visual hierarchy with proper contrast between chart elements 3) Professional typography with legible data labels even at small sizes 4) Efficient use of screen real estate. Deduct 3 points for each usability issue like overlapping labels, 5 points for poor color choices that make data interpretation difficult, and 5 points for inefficient layout that requires excessive scrolling. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the chart performance optimized for large datasets?",
+      "description": "Judge whether the application can handle large historical datasets (5+ years of daily data) without significant performance degradation. Check for: 1) Data downsampling techniques when zoomed out 2) Efficient canvas/SVG rendering with element reuse 3) Asynchronous loading of extended historical data 4) Smooth transitions when changing timeframes. Deduct 5 points if charts noticeably lag when panning/zooming, 5 points if rendering more than 1000 candles causes visible performance issues, and 5 points if the application freezes during data loading. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "medium"
+}

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

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

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

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

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

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