@getollie/cli 0.0.5 → 0.2.1

package/library/data_science-data_visualization_dashboards/desktop-bi-analysis-software.json

@@ -1,68 +0,0 @@
-{
-  "index": 293,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate, professional responses. Make sure the generated code is executable when possible. I want to create a desktop BI analysis software. Could you help me generate one that can import Excel files, properly map the imported fields, and automatically generate BI analysis reports?",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the Excel import functionality properly implemented?",
-      "description": "Verify that the code can handle various Excel file formats (XLS, XLSX, CSV), supports multiple sheets, and properly manages data types during import (numbers, dates, text, etc.). Check for error handling for corrupted files, large datasets, and character encoding issues. Score 0 if import is not implemented, 5 if basic import exists with limitations, and 10 if the implementation is robust with comprehensive error handling.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the data field mapping system fully developed?",
-      "description": "Evaluate whether the code implements an intelligent field mapping system that can auto-detect data types, suggest appropriate mappings, and allow manual overrides. Check for data cleansing capabilities, handling of missing values, and validation of mapped fields. Deduct 3 points if automatic field type detection is missing, 3 points if there's no data preview functionality, and 4 points if field relationship detection is absent. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are the BI analysis functions comprehensive and appropriate?",
-      "description": "Check whether the code includes essential BI analysis capabilities: descriptive statistics, trend analysis, correlation analysis, outlier detection, and predictive modeling. Verify that the analysis methods match the data types (categorical vs. numerical). Deduct 2 points for each missing core analysis function. Give 10 points if all essential analyses are implemented with appropriate algorithms and statistical validations.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Does the report generation system provide meaningful insights?",
-      "description": "Assess whether the automatic report generation system produces actionable insights rather than just raw data. Check if it includes anomaly highlighting, trend identification, key metric summaries, and comparative analysis. Verify that reports can be customized and saved in multiple formats (PDF, HTML, etc.). Deduct 3 points if insights are not highlighted, 3 points if export options are limited, and 4 points if report templates are missing. 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 out-of-memory errors with large datasets, unexpected input values, application crashes). Check for proper exception handling, graceful degradation, and data recovery mechanisms. Code with strong robustness should provide meaningful error messages and recovery paths, 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-powered insight generation 2. Natural language query interface 3. Automatic dashboard recommendations based on data patterns 4. Real-time collaboration features). 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 analysis calculations that could be optimized 2. Function modules unrelated to BI analytics (e.g., unnecessary multimedia features) 3. Resource-intensive visualizations that don't contribute to data understanding. 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/analysis/visualization layers), unit test coverage, and performance optimization techniques. Deduct 5 points if global state management is poorly implemented; deduct 3 points if the code lacks comments and documentation; deduct 2 points if there's no consideration for memory management with 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 UI follows modern data visualization principles: 1) Consistent data visualization style 2) Clear information hierarchy with proper emphasis on key metrics 3) Appropriate use of white space and grid alignment 4) Color schemes that account for data types and accessibility. Deduct 3 points for cluttered dashboards, 3 points for improper chart selection for data types, and 4 points for poor readability of data labels and values. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the interactive elements enhance data exploration: 1) Filtering and drill-down capabilities respond within 300ms 2) Smooth transitions between different views and analyses 3) Intuitive interactions for data selection and comparison. Deduct 3 points for laggy visualizations with large datasets, 3 points for unintuitive interaction patterns, and 4 points if essential interactions (zoom, filter, details-on-demand) are missing. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Data Science-Data Visualization Dashboards",
-  "difficulty": "medium"
-}

package/library/data_science-data_visualization_dashboards/drowning-victim-behavior-dashboard.json

@@ -1,68 +0,0 @@
-{
-  "index": 850,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable for demonstration. Create a comprehensive dashboard for drowning victim behavior description data, which should include a comparison of data between witnesses, rescuers, and drowning victims, visualization design, and detailed data presentation. Output in HTML format to ensure it's executable.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the dashboard data structure and model properly implemented?",
-      "description": "Review whether the code correctly implements data models for the three subject types (witnesses, rescuers, and drowning victims). Check if the data structure allows for comparison across these groups. The implementation should include data normalization and proper typing. Score 0 if data models are missing, 5 if basic models exist but lack comparative capabilities, and 10 if comprehensive models with comparison functionality are implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are appropriate visualization components selected and implemented?",
-      "description": "Evaluate the selection and implementation of visualization components (charts, graphs, heatmaps, etc.) for drowning behavior data. Components should match the data type being displayed (e.g., timeline charts for temporal data, spatial visualizations for location data). Deduct 5 points if visualizations are inappropriate for the data type, 3 points if they lack interactivity. The visualizations must effectively communicate differences between the three stakeholder groups. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the comparative analysis functionality comprehensive?",
-      "description": "Check whether the dashboard effectively enables comparison between witness, rescuer, and victim data. Look for side-by-side visualizations, differential metrics, and highlighting of discrepancies. The system should provide both quantitative and qualitative comparison mechanisms. Deduct 5 points if comparison is limited to basic metrics, and 8 points if no meaningful comparison functionality exists. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Does the dashboard implement effective filtering and drill-down capabilities?",
-      "description": "Assess whether the code includes robust filtering mechanisms that allow users to focus on specific aspects of drowning behavior data. Check for time-based filters, demographic filters, environmental condition filters, and the ability to drill down into specific incidents. The implementation should maintain context during exploration. Deduct 5 points if filtering is basic, and 8 points if drill-down capabilities are absent. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as missing data fields, malformed data, empty datasets, 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. Machine learning-based pattern detection in drowning behavior 2. Augmented reality visualization of drowning scenarios 3. Multi-language support for international incident comparison). 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 similar charts showing the same data) 2. Function modules unrelated to drowning behavior analysis (e.g., weather forecasting) 3. Fancy effects that affect performance (e.g., excessive animations that distract from data interpretation). 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), reusable components, and responsive design implementation. 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 dashboard is not responsive across device sizes. 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 (consideration for colorblind users) 2) Proper layout spacing with clear information hierarchy 3) Professional typography system (clear labels, legible data points, consistent styling). Deduct 3 points for each cluttered visualization, 5 points for poor color choices that hinder data interpretation, and 5 points for inconsistent layout that disrupts the analytical flow. 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 filtering response time ≤ 200ms 2) Smooth transitions between different views/filters 3) Clear visual feedback for user interactions with data points. Deduct 5 points for laggy transitions between visualization states, 3 points for lack of hover/selection states on interactive elements, and 5 points for unintuitive 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/dual-curve-backtest-stock-returns-visualization.json

@@ -1,68 +0,0 @@
-{
-  "index": 987,
-  "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 for demonstration. Include visualization with dual curves showing backtest returns and stock returns.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the backtesting system properly implemented?",
-      "description": "Review whether the code accurately implements the backtesting framework with proper time series handling, transaction cost modeling, and performance calculation. Score 0 if the backtesting logic is missing, 5 if only basic backtesting is implemented without accounting for market frictions, and 10 if slippage, commission, and other market mechanics are fully modeled.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the dual curve visualization correctly implemented?",
-      "description": "Evaluate whether the code includes a proper visualization component that clearly displays both backtest returns and stock returns on the same chart. Check for proper labeling, legends, time axis handling, and scaling methods. Deduct 5 points if curves lack proper scaling, 3 points if legends or axes are missing/unclear, and 2 points if the visualization is not interactive when it should be. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are the data handling and financial calculations accurate?",
-      "description": "Assess the correctness of financial calculations such as returns, drawdowns, Sharpe ratio, and other performance metrics. Check if data preprocessing handles missing values, adjusts for splits/dividends, and maintains point-in-time integrity. Deduct 5 points for look-ahead bias, 3 points for incorrect return calculations, and 5 points for improper handling of financial time series data. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the code modular and reusable for different strategy implementations?",
-      "description": "Check whether the code architecture separates data handling, strategy logic, execution, and visualization components. The design should allow for easy swapping of different strategies or stocks while maintaining the same backtesting framework. Deduct 5 points if components are tightly coupled, 3 points if strategy parameters cannot be easily modified, and 2 points if the code doesn't support multiple asset types. 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, outliers, API failures, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Interactive drill-down into specific time periods 2. Risk attribution analysis 3. Automated strategy parameter optimization). 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 calculations (e.g., multiple ways to calculate returns) 2. Function modules unrelated to financial analysis (e.g., excessive decorative elements) 3. Computationally expensive operations that don't add analytical value. 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 acquisition/processing/visualization layers), unit test coverage, and build process automation. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the build process is not automated. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the visualization meet professional financial charting standards?",
-      "description": "Evaluate whether the charts follow financial industry standards: 1) Proper color scheme for gains/losses (typically green/red) 2) Clear labeling of key events and metrics 3) Appropriate scale for returns (log scale or percentage) 4) Inclusion of benchmark comparison. Deduct 3 points for each misleading visual element, 5 points for improper scaling that distorts performance perception, and 3 points for missing critical information like drawdowns or volatility. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the chart interaction smooth and informative?",
-      "description": "Judge whether the chart interactions enhance financial analysis: 1) Tooltips showing precise values on hover 2) Ability to zoom into specific time periods 3) Toggle visibility of different metrics 4) Export functionality for research purposes. Deduct 3 points for each missing key interaction, 5 points for laggy/unresponsive charts with large datasets, and 3 points for interactions that don't add analytical value. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Data Science-Data Visualization Dashboards",
-  "difficulty": "easy"
-}

package/library/data_science-data_visualization_dashboards/dupont-analysis-chart-html.json

@@ -1,68 +0,0 @@
-{
-  "index": 1206,
-  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Make sure that the generated code can be executed for demonstration purposes. Please design a DuPont analysis chart for this enterprise, with the DuPont chart in HTML format.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the DuPont analysis structure correctly implemented?",
-      "description": "Verify that the chart includes the three main components of DuPont analysis: Return on Equity (ROE), Return on Assets (ROA), and Financial Leverage. Check if the decomposition logic is accurate (ROE = Net Profit Margin × Asset Turnover × Equity Multiplier). Deduct 5 points if any main component is missing, deduct 3 points if the calculation relationships are incorrect. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are the financial metrics and ratios calculated correctly?",
-      "description": "Examine whether all financial metrics (such as Net Profit Margin, Asset Turnover, Equity Multiplier) are correctly calculated and displayed with appropriate formulas. Check for mathematical accuracy in ratio calculations. Deduct 5 points for each incorrectly calculated major ratio, 3 points for minor calculation errors. Give 10 points if all calculations are accurate and properly documented.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the hierarchical structure of the DuPont chart properly visualized?",
-      "description": "Evaluate if the chart clearly shows the hierarchical breakdown of ROE into its components and sub-components. The visualization should demonstrate the parent-child relationships between financial metrics. Deduct 5 points if the hierarchy is flat or confusing, 3 points if some relationships are unclear. Full implementation with clear hierarchical visualization earns 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Does the implementation allow for data input or modification?",
-      "description": "Check if the chart provides functionality for users to input or modify financial data, with the chart updating accordingly. Deduct 5 points if data cannot be modified at all, 3 points if only basic modification is supported without validation. Award 10 points for a complete implementation with data validation and real-time updates.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid inputs, missing data, division by zero, 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. Comparative analysis with industry benchmarks 2. Historical trend visualization 3. Interactive tooltips with explanations of financial metrics). 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 calculation methods for the same ratio) 2. Function modules unrelated to DuPont analysis (e.g., irrelevant financial calculators) 3. Fancy effects that affect performance (e.g., unnecessary 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 calculation logic/visualization/user interaction layers), code reusability, and maintainability. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there's no clear separation of concerns. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the DuPont chart follows professional financial visualization standards: 1) Clean and professional color scheme appropriate for financial data 2) Proper spacing between chart elements 3) Professional typography with consistent font hierarchy (headings vs. data). Deduct 3 points for each visual clutter issue, 5 points for inappropriate color choices, and 5 points for poor text formatting. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and informative?",
-      "description": "Judge whether the chart provides meaningful interactive elements: 1) Hover tooltips with detailed metric explanations 2) Smooth transitions when data changes 3) Clear visual indication of calculation flow. Deduct 5 points for static charts with no interactivity, 3 points for interactions that don't enhance understanding, and 5 points for confusing or non-intuitive interactions. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Data Science-Data Visualization Dashboards",
-  "difficulty": "easy"
-}

package/library/data_science-data_visualization_dashboards/dynamic-data-dashboard-charts-visualizations.json

@@ -1,68 +0,0 @@
-{
-  "index": 1629,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Ensure the code you generate is executable for display. Based on all the data in the table, create a dynamic comprehensive data dashboard with charts and visualizations, outputting the content in .html format.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Are all appropriate chart types selected based on the data characteristics?",
-      "description": "Evaluate whether the most suitable chart types are chosen based on data attributes and relationships (e.g., line charts for trends, bar charts for comparisons, pie charts for proportions, heatmaps for correlation). Deduct 3 points for each inappropriate chart selection that obscures rather than clarifies data insights. Award 10 points for perfect chart selection with clear rationale, 5 points for adequate but not optimal choices, 0 points if charts actively misrepresent data.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the dashboard layout logically organized with proper information hierarchy?",
-      "description": "Check whether the dashboard follows a strategic layout with clear information hierarchy, placing critical KPIs prominently while maintaining logical grouping of related metrics. Examine if the dashboard uses grid systems for alignment and if it implements responsive design principles. Award 10 points for excellent organization with clear visual hierarchy, 5 points if layout is functional but sub-optimal, 0 points if chaotic arrangement impedes data interpretation.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are interactive filtering and drill-down capabilities implemented effectively?",
-      "description": "Assess implementation of user controls (filters, sliders, date pickers) that allow exploration of different data segments and time periods. Verify that interactions provide meaningful context changes and cross-filtering between charts. Award full 10 points if comprehensive interactive elements are implemented with smooth state transitions, 5 points for basic filtering only, 0 points if no interactivity exists.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is data loading, processing, and rendering optimized?",
-      "description": "Evaluate how efficiently the dashboard handles data - check for appropriate data transformation methods, lazy loading strategies for large datasets, and caching mechanisms. Examine if charts render progressively and if performance degrades with increasing data volume. Deduct 3 points for each second of initial load time beyond 3 seconds, 5 points if rendering flickers during interactions. Award 10 points for seamless performance.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code handles edge cases (empty datasets, null values, outliers, browser compatibility issues) and provides graceful error handling with user-friendly messages. Code with strong robustness should prevent dashboard crashes even with unexpected inputs. Award 10 points for comprehensive error handling with recovery mechanisms, 5 points for basic error checks, 0 points if dashboard breaks easily.",
-      "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. Intelligent insight generation highlighting anomalies 2. Custom theme switching with saved preferences 3. Dashboard state sharing via URL parameters). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Duplicate visualizations showing the same insights 2. Excessive decorative elements that don't convey information 3. Heavy animations or effects that impact performance or distract from data comprehension. Deduct 3 points for each redundancy found, and directly deduct 10 points if core visualization clarity is compromised by unnecessary elements.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (separation of data processing logic from visualization rendering), code reusability for chart components, and appropriate use of visualization libraries. Deduct 5 points if global variables are overused; deduct 5 points if there's significant code duplication across chart creation functions; deduct 5 points if there's no error handling for data loading failures. 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) Consistent color palette with clear data encoding 2) Proper white space and alignment (8px grid system) 3) Typography hierarchy with readable font sizes (≥14px for data points). Deduct 3 points for each inconsistent design element, 5 points for poor accessibility (e.g., low contrast), 5 points for overlapping elements. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether user interactions feel natural and responsive: 1) Chart transitions under 300ms 2) Hovering tooltips appear within 100ms 3) Filter applications reflect immediately with appropriate loading indicators for longer operations. Deduct 5 points for each interaction that lacks visual feedback, 3 points for jerky animations, 5 points for confusing interaction patterns that don't follow standard dashboard conventions. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Data Science-Data Visualization Dashboards",
-  "difficulty": "easy"
-}

package/library/data_science-data_visualization_dashboards/echarts-bubble-chart-engine-displacement-price-market-share.json

@@ -1,68 +0,0 @@
-{
-  "index": 1322,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable for display. Create a bubble chart from table data, with engine displacement as the x-axis, price as the y-axis, and market share as the bubble size. Please generate the Echarts code.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the data transformation from table to chart properly implemented?",
-      "description": "Check if the code extracts and processes tabular data correctly to feed into the ECharts bubble chart. Verify if it handles data types properly (numbers for displacement, price, and market share). Deduct 5 points if data types aren't converted correctly, 3 points if there's no error handling for missing data, and 5 points if the data structure doesn't match ECharts requirements. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the bubble chart implementation complete and accurate?",
-      "description": "Evaluate whether the ECharts bubble chart correctly visualizes the three variables: engine displacement (x-axis), price (y-axis), and market share (bubble size). Review if the axis definitions, series type, and bubble size scaling are properly configured. Give 10 points for a fully functioning bubble chart with appropriate scaling, 5 points if basic visualization works but with scaling issues, and 0 points if the chart doesn't display or uses incorrect chart type.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are appropriate scales and ranges used for the axes?",
-      "description": "Check if the x-axis (engine displacement) and y-axis (price) use appropriate scales and ranges. Verify if the axis minimums are set properly (e.g., starting from 0 or data minimum), whether logarithmic scales are used if there's large data variance, and if axis labels are formatted appropriately (e.g., currency for price, L/cc for displacement). Deduct 5 points for inappropriate scales, 3 points for poor label formatting, and 3 points for missing units. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the bubble size representation appropriate and meaningful?",
-      "description": "Assess whether the bubble size (market share) is appropriately scaled to be visually meaningful. Check if very small market shares are still visible and large shares don't overwhelm the chart. Verify if a symbolSize function is used to properly map data values to visual sizes. Deduct 5 points if bubble sizes are poorly scaled (too small/large), 3 points if the scaling is linear when logarithmic would be better (or vice versa), and 3 points if there's no legend to indicate what bubble sizes represent. 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, negative values, or extremely large/small values) and provide appropriate fallbacks or error handling. 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 experience (e.g., 1. Interactive tooltips with additional information 2. Color coding by categories 3. Animation on load or data updates). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant chart components (e.g., unnecessary legends or grids) 2. Function modules unrelated to bubble chart visualization 3. Fancy effects that affect performance or clarity (e.g., excessive animations or 3D effects when not needed). 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/chart configuration/event handling), code reusability, and maintainability. Deduct 5 points if global variable pollution is found or proper encapsulation is not used; deduct 5 points if the code duplication rate is too high; deduct 5 points if there are no comments for complex logic. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the visualization meet professional design standards?",
-      "description": "Evaluate whether the chart follows data visualization best practices: 1) Appropriate color scheme (colorblind-friendly, meaningful use of colors) 2) Clear and legible labels and tooltips 3) Proper use of grid lines and axis ticks. Deduct 3 points for poor color choices, 5 points for illegible labels, and 5 points for missing or misleading legends/tooltips. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the interaction experience smooth and informative?",
-      "description": "Judge whether the interactive features enhance data understanding: 1) Responsive tooltips that show precise values 2) Zoom/pan capabilities for exploring dense data 3) Highlighting or filtering options for data exploration. Deduct 5 points for missing tooltips, 3 points for slow or jerky interactions, and 5 points for insufficient information in interactive elements. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Data Science-Data Visualization Dashboards",
-  "difficulty": "easy"
-}

package/library/data_science-data_visualization_dashboards/echarts-uniapp-vue3-example.json

@@ -1,68 +0,0 @@
-{
-  "index": 805,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be careful to ensure that the code you generate is executable for demonstration. Please provide me with a complete example of using ECharts in UniApp, using Vue 3 syntax.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "ECharts component integration quality",
-      "description": "Check if the code properly integrates ECharts in UniApp with Vue 3. Verify the implementation includes proper lifecycle management (import, initialization, rendering, resizing, and destruction). Score 0 if ECharts is not properly initialized, 5 if basic initialization exists but lifecycle hooks are incomplete, and 10 if ECharts initialization is fully integrated with Vue 3 lifecycle methods.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "UniApp cross-platform compatibility",
-      "description": "Evaluate how the code handles platform differences between H5, WeChat Mini Program, App (iOS/Android), etc. Check for platform-specific adaptations (like using canvas-id for mini program and ref for H5). Deduct 3 points for each major platform not supported. Deduct 5 points if no platform detection or adaptation is implemented. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Vue 3 Composition API implementation",
-      "description": "Verify that the code properly uses Vue 3 Composition API (setup(), ref, reactive, computed, etc.) rather than Options API. Check for proper reactivity handling with ECharts data. Score 0 if no Vue 3 features are used, 5 if basic setup() is used but reactivity is poorly handled, and 10 if the code demonstrates excellent use of Composition API with proper reactivity for chart data.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Chart data update mechanism",
-      "description": "Evaluate how chart data updates are handled. Check if the code implements proper watchers for reactive data, debouncing for frequent updates, and optimized rendering. Deduct 5 points if charts need full reinitialization on data changes. Deduct 3 points if updates cause visible flickering. 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 component unmounting during chart rendering, network data loading failures, resize events, 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. Touch gesture interactions 2. Smooth animation transitions between data updates 3. Theme switching capability 4. Chart state persistence). 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 initialization logic (e.g., multiple chart instances for the same data) 2. Unnecessary or duplicated data transformation 3. Excessive options configuration unrelated to the demonstrated chart. Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating chart configurations, data handling, and component logic), reusability, and performance considerations. Deduct 5 points if chart options are hardcoded instead of modularized; deduct 5 points if there's no separation between data fetching and visualization logic; deduct 5 points if performance optimizations like debouncing window resize events 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 chart design follows modern visualization principles: 1) Appropriate color scheme for data visualization (colorblind-friendly) 2) Proper spacing and sizing of chart elements 3) Clear labels and legends. Deduct 3 points for cluttered visualization, 5 points for poor color choices that hinder data interpretation, and 5 points for missing or confusing labels/legends. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the chart interactions conform to expected behavior: 1) Responsive tooltips appearing within 100ms 2) Smooth zoom/pan/drill-down animations 3) Touch-friendly interaction areas for mobile. Deduct 5 points for laggy rendering on data updates, 3 points for jerky animations, and 5 points for non-intuitive interaction patterns. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Data Science-Data Visualization Dashboards",
-  "difficulty": "medium"
-}

package/library/data_science-data_visualization_dashboards/embroidery-products-economic-environmental-dashboard.json

@@ -1,68 +0,0 @@
-{
-  "index": 339,
-  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable for demonstration. Create a comprehensive dashboard for the economic and environmental benefits of embroidery products (in economic benefits, achieve 30% growth in overseas market sales by 2025, help intangible cultural heritage inheritors increase order volume by 20%, and raise average order value from $200 to $800). Requirements include visualization design and detailed data presentation. Please output in HTML format to ensure it's executable.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the dashboard visualization for economic benefits fully implemented?",
-      "description": "Review whether the code accurately implements charts/graphs showing economic metrics (30% growth in overseas market, 20% increase in order volume, and average order value increase from $200 to $800). Verify if the visualization includes trend analysis, comparative views, and forecasting elements.Score 0 if economic visualizations are missing, 5 points if basic charts are implemented without interactivity, and 10 points if comprehensive interactive visualizations with forecasting capabilities through 2025 are included.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the environmental benefits visualization component properly implemented?",
-      "description": "Evaluate whether the code implements visualizations for environmental impact metrics related to embroidery products (such as sustainable materials usage, carbon footprint reduction, water conservation, etc.). Check if the environmental data is properly contextualized with industry benchmarks.Score 0 if environmental visualizations are absent, 5 points if basic environmental metrics are shown without context, and 10 points if comprehensive environmental impact analysis with comparative industry benchmarks is included.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the intangible cultural heritage data presentation component implemented?",
-      "description": "Check whether the dashboard includes specific visualizations for intangible cultural heritage inheritors' data (number of artisans, geographical distribution, skill categories, etc.) and how their order volumes have changed. Verify if the visualization connects cultural preservation with economic outcomes.Score 0 if cultural heritage data is missing, 5 points if basic inheritor data is shown without economic correlation, and 10 points if comprehensive visualization of cultural-economic relationships is implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the overseas market analysis component properly implemented?",
-      "description": "Assess whether the code implements geographical market visualization showing the 30% growth target in overseas markets. Check if the visualization includes market segmentation, regional performance comparison, and growth trajectory toward the 2025 goal.Score 0 if overseas market visualization is missing, 5 points if basic geographical data is presented without growth projections, and 10 points if comprehensive market analysis with interactive geographic elements and clear growth pathways is included.",
-      "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, responsive design requirements, 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 market prediction model 2. Interactive embroidery pattern explorer tied to sales data 3. Virtual tour of artisan workshops with economic impact indicators).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. Function modules unrelated to embroidery economics/environmental impact (e.g., general textile industry data) 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/interaction layers), code reusability for different chart types, and implementation of design patterns.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 the visualization library implementation is inconsistent. 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 (no more than 3 primary colors with appropriate accent 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) 4) Clear visual hierarchy between economic and environmental data sections.Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic chart-text layout. 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 human perception characteristics: 1) Filter/selection feedback delay ≤ 100ms 2) Chart transition animation duration controlled between 300-500ms 3) Clear visual focus guidance between economic and environmental sections. 4) Intuitive drill-down capabilities from summary to detailed data views.Deduct 5 points for each interaction without feedback, 3 points for visual lag during data filtering/sorting, and 5 points for hard-to-find key data comparison functions. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Data Science-Data Visualization Dashboards",
-  "difficulty": "medium"
-}