@getollie/cli 0.0.1

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

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

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

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

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

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

package/library/data_science-data_visualization_dashboards/family-tree-visualization.json

@@ -0,0 +1,68 @@
+{
+  "index": 1026,
+  "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. Write a piece of code for visualizing a family tree.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the family tree data structure properly designed?",
+      "description": "Evaluate whether the code implements an appropriate data structure (e.g., tree, graph) to represent family relationships. Check for proper parent-child connections, sibling relationships, and support for complex family structures (step-relationships, multiple marriages, etc.). Score 0 if no proper structure exists, 5 if basic parent-child relationships are represented, 10 if the structure handles all complex family relationships.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the tree visualization rendering implementation complete?",
+      "description": "Review the rendering mechanism used (Canvas, SVG, HTML DOM) and assess whether it properly visualizes hierarchical relationships. Check for appropriate node spacing, branch connections, and hierarchical layout. Deduct 5 points if nodes overlap frequently, 3 points if connections between family members are unclear, and 2 points if the hierarchical structure is difficult to follow. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Are interactive features for family tree exploration provided?",
+      "description": "Check for interactive features like zooming, panning, expanding/collapsing nodes, searching, and filtering. Evaluate whether the implementation includes tooltips for additional information and node selection capabilities. Score 0 if no interactivity exists, 5 if basic interactions are implemented, and 10 if comprehensive exploration features are available with smooth transitions.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Does the implementation support data input/editing functionality?",
+      "description": "Assess whether the code includes functionality for adding, editing, and removing family members. Check for validation of input data, undo/redo capabilities, and data persistence options (local storage, export/import). Deduct 5 points if editing is not supported, 3 points if validation is missing, and 2 points if no data persistence mechanism exists. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as malformed data input, empty trees, extremely large families, circular references, 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. Timeline view of generations 2. Statistical analysis of family demographics 3. Automatic layout optimization for complex trees). 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 tree traversal algorithms doing the same thing) 2. Function modules unrelated to family tree visualization (e.g., a built-in weather widget) 3. Fancy effects that affect performance (e.g., excessive animations when displaying family members). 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 model/view/controller 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 interface vision meet professional design standards?",
+      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching (no more than 3 primary colors) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional 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) Click feedback delay ≤ 100ms 2) Transition animation duration controlled between 300-500ms 3) Clear visual focus guidance. Deduct 5 points for each operation without feedback, 3 points for visual after-images during fast navigation of large trees, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "medium"
+}

package/library/data_science-data_visualization_dashboards/four-quadrant-news-material-screening-method.json

@@ -0,0 +1,68 @@
+{
+  "index": 791,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to provide executable code when possible. Create a four-quadrant diagram and provide me with the code.\n\nSpecific requirements: (1) Establish a \"Four-Quadrant Screening Method\" to build a news material admission matrix based on \"Authenticity Index\" and \"Educational Value Index.\"\n\nFirst Quadrant (High Authenticity + High Educational Value): Materials that conform to facts and have clear educational significance can be directly incorporated into teaching or public communication.\n\nSecond Quadrant (High Authenticity + Low Educational Value): Content that is authentic but lacks educational direction requires adaptation or supplementary background information based on teaching objectives.\n\nThird Quadrant (Low Authenticity + High Educational Value): Contains factual deviations but has educational potential; requires strict verification of authenticity before use.\n\nFourth Quadrant (Low Authenticity + Low Educational Value): Exclude such materials to avoid misinformation and waste of resources.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the four-quadrant diagram correctly implemented with clear axes and quadrant divisions?",
+      "description": "Check if the code correctly implements a coordinate system with X-axis (Authenticity Index) and Y-axis (Educational Value Index) properly labeled, with clear boundaries between the four quadrants. Each quadrant should be visually distinguishable. Score 0 if quadrants are missing or axes are incorrectly labeled, 5 if basic structure exists but with alignment issues, and 10 if perfectly implemented with proper scaling.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are the four quadrants properly labeled and described according to specifications?",
+      "description": "Verify if each quadrant is correctly labeled (First through Fourth) and includes the specified descriptions (High/Low Authenticity + High/Low Educational Value) along with the appropriate action guidance for each quadrant (e.g., 'directly incorporate', 'requires adaptation', etc.). Deduct 3 points if any quadrant is mislabeled, 5 points if descriptions are incomplete or incorrect, and 10 points if no clear descriptions are provided.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Does the visualization include appropriate color coding and visual differentiation?",
+      "description": "Evaluate if the quadrants use appropriate colors to indicate their relative importance/status (e.g., green for first quadrant, red for fourth quadrant) with sufficient contrast for accessibility. Check if color choices help communicate the conceptual differences between quadrants. Deduct 3 points for poor color choices that don't reflect quadrant meaning, 5 points for insufficient contrast making it hard to distinguish quadrants, and 8 points if no meaningful color differentiation exists.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is there an interactive component allowing for practical use of the diagram?",
+      "description": "Assess whether the implementation includes practical interactive features such as: ability to plot example news materials onto the diagram, hovering effects that show detailed quadrant information, clickable regions that provide guidance, or ability to adjust threshold values. Score 10 points for comprehensive interactivity, 5 points for basic hover/click functionality, and 0 points for a completely static implementation.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as browser resizing, different screen sizes, touch vs. mouse interaction, etc.) and provide appropriate adaptations or error handling. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Ability to save/export examples 2. Animation showing how content moves between quadrants based on fact-checking 3. Integration with sample data that demonstrates the framework in action). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar visualization functions (e.g., multiple ways to render the same quadrant) 2. Function modules unrelated to the four-quadrant screening method (e.g., unnecessary animations or effects) 3. Fancy effects that affect performance (e.g., excessive transitions or hover effects). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating visualization logic/data/interaction layers), code organization, 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 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 overall design follows modern design principles: 1) Harmonious color matching (no more than 3 primary colors) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional 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) Click feedback delay ≤ 100ms 2) Transition animation duration controlled between 300-500ms 3) Clear visual focus guidance. Deduct 5 points for each operation without feedback, 3 points for visual after-images during fast sliding, 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/full-visualization-process-number-screening.json

@@ -0,0 +1,68 @@
+{
+  "index": 804,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Ensure that the generated code is executable when possible.\n\n## Block 4: Full Visualization Process\n\n### Initial Candidate Pool\n49-number base pool with 49 numbers. Through preliminary screening, usable numbers are retained and displayed above. Excluded numbers are shown below with clear reasons for exclusion.\nNumber + Five Elements Symbol + ✅Pass Mark\nExample: 01🔥❄️Ultra Cold✅Pass (01 is retained through cold state penetration)\n\nThen to the 30-number candidate pool through secondary screening using 7 major dynamic rule processors and other rules. Usable numbers are retained, excluded numbers are shown in the same format as the 49-number base pool.\n\nNext to the 20-number core pool, filtered again through quantum annealing, cold state penetration, and other rules to retain 20 numbers and exclude 10 numbers.\n\nFinally, the ultimate 10 numbers, with specific reasons noted for each number.\n\n🔮 **Usable Numbers (24):**\n01🔥❄️Ultra Cold✅Pass │ 03💰🌨️Medium Cold✅Pass │ 05⛰️🌥️Low Temp✅Pass │ 07🌳🌤️Normal Temp✅Pass │ 09🔥🌤️Normal Temp✅Pass\n11💰🌨️Medium Cold✅Pass │ 13🌊❄️Ultra Cold✅Pass │ 15🌳🌥️Low Temp✅Pass │ 17🔥🌤️Normal Temp✅Pass │ 19⛰️🌥️Low Temp✅Pass\n21🌊❄️Ultra Cold✅Pass │ 23🌳🌨️Medium Cold✅Pass │ 25💰🌥️Low Temp✅Pass │ 27⛰️🌤️Normal Temp✅Pass │ 29🌊🌨️Medium Cold✅Pass\n31🔥🌤️Normal Temp✅Pass │ 33💰🌨️Medium Cold✅Pass │ 35⛰️🌥️Low Temp✅Pass │ 37🌳🌤️Normal Temp✅Pass │ 39🔥🌤️Normal Temp✅Pass\n41💰❄️Ultra Cold✅Pass │ 43🌊🌨️Medium Cold✅Pass │ 45🌳🌥️Low Temp✅Pass │ 47⛰️🌤️Normal Temp✅Pass\n\n⚡ **Excluded Numbers (24):**\n02🔥❌Excluded【Fire Excess】 │ 04💰❌Excluded【Poultry Compression】 │ 06⛰️🔄Cold State Penetration │ 08🌳❌Excluded【Phase Lock】\n10🔥❌Excluded【Tail Number Filter】 │ 12💰⚡Conflict【Five Elements Clash】 │ 14🌊❌Excluded【Beast Exclusion】 │ 16🌳⚡Conflict【Conflict Mark】\n18🔥❌Excluded【Historical High Frequency】 │ 20⛰️⚡Conflict【Wave Color Excess】 │ 22🌊❌Excluded【Prime Number Exclusion】 │ 24🌳🔼Section Coverage\n26💰🔄Cold State Compensation │ 28⛰️⚡Conflict【Five Elements Combo】 │ 30🌊❌Excluded【Tail Number Filter】 │ 32🔥❌Excluded【Poultry Compression】\n34💰⚡Conflict【Wave Color Excess】 │ 36⛰️⚡Conflict【Conflict Mark】 │ 38🌳❌Excluded【Historical High Frequency】 │ 40🔥⚡Conflict【Five Elements Clash】\n42💰🔼Section Coverage │ 44🌊🔄Water Attribute Compensation │ 46🌳🔄Cold State Penetration │ 48🔥❌Excluded【Phase Lock】\n\n**Key Feature Restoration:**\n\n- Cold State Penetration Mark: Uses 🔄 symbol to indicate cold state penetration process\n- Status Level System:\n  - ❄️Ultra Cold (Consecutive missing ≥10 periods)\n  - 🌨️Medium Cold (Consecutive missing 6-9 periods)\n  - 🌥️Low Temperature (Consecutive missing 3-5 periods)\n  - 🌤️Normal Temperature (Consecutive missing ≤2 periods)\n- Conflict Warning System: Uses ⚡ symbol to mark five elements conflict events\n- Dynamic Compensation Mechanism: Cold state compensation, water attribute compensation, and other special process notations\n- Symbol System Standards:\n  - ✅ Final retention mark\n  - ❌ Hard exclusion mark\n  - 🔼 Section coverage operation\n  - 🔄 Dynamic adjustment process",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the number visualization system fully implemented?",
+      "description": "Review whether the code accurately implements the 49-number base pool visualization, including the five elements symbols, temperature status indicators, and retention/exclusion marks. Score 0 if the core visualization is not implemented, 5 if only basic number display is implemented, and 10 if all symbols (🔥💰⛰️🌳🌊) and status indicators (❄️🌨️🌥️🌤️) are correctly integrated with proper formatting.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the multi-stage filtering process properly visualized?",
+      "description": "Evaluate whether the code clearly displays the progression from 49-number base pool to 30-number candidate pool to 20-number core pool to the final 10 numbers. Each transition should be visually distinct with appropriate filtering animations or transitions. Deduct 3 points if any stage transition is unclear, 5 points if filtering reasons aren't visually displayed, and 5 points if the progression logic isn't evident. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Are the various status markers and symbolic systems implemented?",
+      "description": "Check implementation of all symbolic systems: cold state penetration (🔄), temperature levels (❄️🌨️🌥️🌤️), conflict warnings (⚡), retention marks (✅), exclusion marks (❌), section coverage (🔼), and dynamic adjustment process (🔄). Deduct 2 points for each missing symbol system. Score 0 if fewer than 3 symbol systems are implemented, and 10 if all systems are properly displayed with tooltips or legends explaining their meaning.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the exclusion reason display system implemented?",
+      "description": "Assess whether the code provides clear visual indicators for exclusion reasons (e.g., 【Fire Excess】, 【Poultry Compression】, etc.) that appear when hovering over or selecting excluded numbers. The system should display all specific exclusion reasons mentioned in the requirements. Deduct 2 points for each missing exclusion reason category, and 5 points if the exclusion reasons aren't interactive or visually linked to their corresponding numbers. 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, incorrect symbol formats, unsupported browsers, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Interactive filtering demonstration 2. Animated transitions between filtering stages 3. Dark/light mode toggle 4. CSV/JSON export capability). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar visualization functions (e.g., multiple ways to show the same status) 2. Function modules unrelated to number visualization (e.g., a built-in calculator) 3. Fancy effects that affect performance (e.g., excessive animations that slow down the visualization). 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), 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 interface vision meet professional design standards?",
+      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching (no more than 3 primary colors) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional 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) Click feedback delay ≤ 100ms 2) Transition animation duration controlled between 300-500ms 3) Clear visual focus guidance. Deduct 5 points for each operation without feedback, 3 points for visual after-images during fast sliding, 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": "hard"
+}