@getollie/cli 0.0.4 → 0.2.0

package/library/data_science-data_visualization_dashboards/vue3-leaflet-temperature-data-visualization.json

@@ -1,68 +0,0 @@
-{
-  "index": 1464,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the code you generate is executable for demonstration. Implement temperature data visualization using Vue 3 and Leaflet.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the Vue 3 + Leaflet integration properly implemented?",
-      "description": "Evaluate whether the Vue 3 component structure correctly integrates with the Leaflet library. Check for proper lifecycle hooks management (onMounted, onBeforeUnmount), Leaflet map initialization, and proper cleanup. Score 0 if the integration is broken, 5 if basic integration exists but with issues, and 10 if the integration is seamless with proper Vue 3 Composition API usage.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the temperature data visualization effectively implemented?",
-      "description": "Examine how temperature data is visualized on the map. Check for appropriate visualization techniques (heatmap, colored markers, chloropleth, etc.) that accurately represent temperature variations. Assess if color scales are intuitive and if legends are provided. Score 0 if visualization is missing, 5 if basic visualization exists but lacks clarity, and 10 if visualization is comprehensive with proper color mapping and clear visual cues.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the data fetching and processing mechanism well-designed?",
-      "description": "Review the implementation of data retrieval (API calls, static data imports) and processing logic. Check for error handling during data fetching, data transformation for visualization compatibility, and caching strategies. Deduct 5 points if error states aren't handled, 3 points if there's no loading state, and 3 points if data processing is inefficient. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Are interactive map features properly implemented?",
-      "description": "Assess the implementation of map interactions such as zooming, panning, tooltips on hover, and click events on temperature data points. Check if interaction with temperature layers is intuitive and responsive. Deduct 5 points if essential map interactions are broken, 3 points if temperature data isn't interactive, and 2 points if interactions lack smooth transitions. 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 empty data, API failures, incorrect data formats, 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. Time-based animation of temperature changes 2. Multiple visualization modes (heatmap/isolines/colored markers) 3. Comparison tools for different time periods). 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 map library imports or duplicate visualization layers 2. Unnecessary UI components that don't contribute to temperature visualization 3. Heavy animations or effects that slow down map rendering. Deduct 3 points for each redundancy found, and directly deduct 10 points if the core visualization functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating map configuration/data handling/UI components), reusability of components, and proper Vue 3 best practices. Deduct 5 points if global state management is messy or Composition API is misused; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there's no separation of concerns between visualization logic and UI. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching for both UI and temperature visualization (color scales should be scientifically appropriate) 2) Proper layout spacing for controls and legends 3) Professional font system for temperature indicators and map labels. Deduct 3 points for each crowded visual element, 5 points for confusing temperature color scales, and 5 points for poorly positioned legends or controls. 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) Map loading and rendering performance (should complete within 2 seconds) 2) Smooth transitions when changing temperature visualization settings 3) Responsive tooltip displays when interacting with temperature data. Deduct 5 points for laggy map performance, 3 points for jarring transitions between data views, and 5 points for delayed response when interacting with temperature points. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Data Science-Data Visualization Dashboards",
-  "difficulty": "easy"
-}

package/library/data_science-data_visualization_dashboards/vue3-threejs-dynamic-map-dashboard-visualization.json

@@ -1,68 +0,0 @@
-{
-  "index": 1587,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the code you generate is executable. Implement a visualization dashboard using Vue 3 and Three.js to import a map model, where information at a specific point on the map continuously changes and updates.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the Vue 3 integration with Three.js properly implemented?",
-      "description": "Check whether the code correctly integrates Vue 3 with Three.js using proper lifecycle hooks (onMounted, onBeforeUnmount) and reactive data management. Verify that component structure follows Vue 3 composition API best practices, with clear separation of concerns. Score 0 if Three.js isn't integrated with Vue at all, 5 if basic integration exists but has lifecycle issues, and 10 if integration is seamless with proper reactivity.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the map model import functionality complete?",
-      "description": "Evaluate whether the code includes comprehensive map model loading capabilities: supports multiple 3D formats (GLTF/GLB, OBJ, FBX), implements proper loading progress indicators, handles loading errors gracefully, and optimizes large model performance. Score 0 if map loading is missing, 5 if only basic loading exists without error handling, and 10 if a robust map import system with optimization is implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the point-specific data update mechanism implemented effectively?",
-      "description": "Assess whether the code implements a system for specific map points to receive and visualize real-time data updates. Check for raycasting implementation to select points, data binding between map points and information sources, and visualization of changing data. The update mechanism should handle high-frequency updates (>1 update/second) without performance degradation. Score 0 if this core feature is missing, 5 if implemented but with performance issues, and 10 if fully functional with optimized performance.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the real-time data visualization system comprehensive?",
-      "description": "Review whether the dashboard includes various visualization methods for the changing data (e.g., color changes, size animations, particle effects, floating panels with charts). Check if the visualization adapts to different data types and ranges. Verify that transitions between data states are smooth and meaningful. Deduct 5 points if visualizations are basic or limited to text only; deduct 3 points if animations are jerky or distracting. Full score requires at least 3 different visualization techniques with smooth transitions.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as model loading failures, WebGL context loss, data feed interruptions, 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. GPU-based data filtering 2. VR/AR view mode 3. Advanced shader effects for data emphasis). 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 camera control systems coexisting) 2. Function modules unrelated to the dashboard visualization (e.g., unnecessary social features) 3. Fancy effects that affect performance (e.g., excessive post-processing filters). 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 3D rendering logic/Vue components/data services), 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 frame rate drops below 30fps during interactions, and 5 points for camera controls that cause disorientation or motion sickness. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Data Science-Data Visualization Dashboards",
-  "difficulty": "medium"
-}

package/library/data_science-data_visualization_dashboards/water-margin-character-relationship-diagram.json

@@ -1,68 +0,0 @@
-{
-  "index": 1579,
-  "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. Based on the character relationships in the novel \"Water Margin\" (also known as \"Outlaws of the Marsh\"), please generate code for a character relationship diagram.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the character relationship graph data structure well-designed?",
-      "description": "Evaluate whether the code properly represents the complex character relationships from 'Water Margin' using an appropriate graph data structure. Check if nodes represent characters with proper attributes (e.g., name, rank, skills) and edges represent different relationship types (e.g., brotherhood, mentorship, rivalry, family). Score 0 if no clear data structure is defined, 5 if only basic node-edge relationships exist, and 10 if rich relationship types with attributes are implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Does the visualization accurately represent the 'Water Margin' character relationships?",
-      "description": "Assess whether the visualization includes the main characters (at least the 36 heavenly spirits and 72 earthly fiends) and their key relationships. Check if the visualization distinguishes between different types of relationships through visual cues (colors, line styles, etc.). Deduct 5 points if fewer than 30 key characters are included, 3 points if relationship types aren't visually distinct, and 2 points if historically inaccurate relationships are depicted.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are interactive features implemented for exploring the character network?",
-      "description": "Verify if the visualization includes interactive features like zooming, panning, highlighting connections on hover, filtering by relationship type, or character search. Score 0 if no interactivity exists, 5 if only basic hover/click interactions are implemented, and 10 if multiple advanced interactive features are available for deep exploration of the character network.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the layout algorithm appropriate for displaying complex character networks?",
-      "description": "Examine whether the code implements an appropriate layout algorithm (force-directed, hierarchical, etc.) that effectively visualizes the complex network without excessive edge crossings or node overlaps. Check if the layout considers character groupings (e.g., Liangshan bandits, imperial officials). Deduct 5 points if the visualization is cluttered with many crossing edges, and 3 points if no consideration is given to logical character groupings.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle edge cases such as missing character data, connection errors, browser compatibility issues, or varying screen sizes. Code with strong robustness should include error handling, responsive design principles, and graceful degradation. Give 10 points for comprehensive error handling and responsiveness, 5 points for average robustness, and 0 points if errors break the visualization.",
-      "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. Historical context annotations 2. Character story snippets on interaction 3. Timeline view of character appearances 4. Filtering by story arcs). 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 techniques 2. Unnecessary features unrelated to character relationships 3. Fancy effects that affect performance without adding informational value. Deduct 3 points for each redundancy found, and directly deduct 10 points if core visualization functionality is compromised by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (separation of data processing, visualization logic, and UI controls), 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 between data and visualization layers. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the visualization follows modern design principles: 1) Harmonious color scheme appropriate for the historical theme 2) Proper layout with clear node labels and legible text 3) Balanced visual hierarchy emphasizing important characters/relationships. Deduct 3 points for cluttered node arrangements, 5 points for poor color choices that make relationships hard to distinguish, and 5 points for illegible character names or information. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the dynamic effects enhance understanding of the complex network: 1) Smooth transitions when filtering or rearranging nodes 2) Appropriate animation speed (300-500ms) for state changes 3) Responsive feedback when interacting with characters. Deduct 5 points for jerky animations during network exploration, 3 points for delayed response (>200ms) to user interactions, and 5 points for animations that obscure the understanding of relationships. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Data Science-Data Visualization Dashboards",
-  "difficulty": "medium"
-}

package/library/data_science-data_visualization_dashboards/web-data-monitoring-excel-import.json

@@ -1,68 +0,0 @@
-{
-  "index": 1374,
-  "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. I want to create a web-based big data monitoring platform that sources data from Excel spreadsheets stored on my local computer.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Excel data import and parsing functionality",
-      "description": "Review whether the code properly implements Excel file import functionality using appropriate libraries (SheetJS/xlsx, Papa Parse, etc.). Check if the implementation can handle different Excel formats (.xlsx, .csv) and whether it includes robust data validation. Score 0 if file import is not implemented, 5 if only basic parsing without validation is included, and 10 if it handles multiple formats with error handling and validation.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Data processing and transformation pipeline",
-      "description": "Evaluate the data processing pipeline from raw Excel data to visualization-ready formats. Check for proper data cleaning, normalization, aggregation functions, and handling of missing/invalid values. Deduct 5 points if no data transformation logic exists, 3 points if transformations are inefficient (e.g., multiple iterations over large datasets), and 2 points if edge cases (null values, non-numeric data) are not handled. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Visualization components and dashboard design",
-      "description": "Check if appropriate visualization libraries (D3.js, Chart.js, Highcharts, etc.) are used to create dynamic, interactive visualizations. Verify if the dashboard includes essential big data visualizations (time series, distributions, correlations, etc.) and allows for custom view configurations. Deduct 5 points if visualizations are static, 3 points if interactivity is limited, and 5 points if the visualizations are not appropriate for the data types. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Real-time monitoring and automatic refresh",
-      "description": "Assess if the platform implements file watching/monitoring to detect changes in source Excel files and provides real-time or scheduled data refresh functionality. Check for WebSocket implementation or polling mechanisms with configurable intervals. Give 0 points if no refresh capability exists, 5 points for basic manual refresh, and 10 points for automatic detection with configurable refresh rates and change highlighting.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as corrupted Excel files, network interruption, 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. AI-driven anomaly detection in data 2. Natural language queries for data exploration 3. Automated insights generation 4. Custom alert thresholds with notifications). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple data parsing methods coexisting) 2. Function modules unrelated to data monitoring (e.g., a built-in game) 3. Fancy effects that affect performance (e.g., excessive animations that slow down rendering of critical data). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating data processing/visualization/user interface 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 dashboard design principles: 1) Harmonious color matching optimized for data visualization (no more than 3 primary colors) 2) Proper layout spacing with logical grouping of related metrics 3) Professional typography system (body font size ≥ 14px, clear hierarchy between titles and data). Deduct 3 points for each crowded visual element, 5 points for a color scheme that makes data hard to interpret, and 5 points for chaotic dashboard organization. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the dynamic effects conform to data dashboard best practices: 1) Filter/selection feedback delay ≤ 100ms 2) Smooth transitions when switching between views or applying filters 3) Clear visual indicators for loading states and data freshness. Deduct 5 points for operations without loading feedback, 3 points for jerky transitions when navigating between views, and 5 points if key metrics or controls are hidden behind unintuitive menus. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Data Science-Data Visualization Dashboards",
-  "difficulty": "medium"
-}

package/library/data_science-data_visualization_dashboards/web-page-excel-upload-charts-display.json

@@ -1,68 +0,0 @@
-{
-  "index": 1766,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the code you generate is executable. Create a web page using HTML+CSS+Java that can upload Excel files and display charts on the web page.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the Excel file upload function fully implemented?",
-      "description": "Review whether the code accurately implements file upload through HTML input and JavaScript, including file type validation (only Excel formats like .xlsx, .xls), file size restrictions, and proper error handling for invalid files. Check if drag-and-drop upload is supported. Score 0 if basic upload is not working, 5 if only basic upload without validation is implemented, and 10 if comprehensive upload with all validations and user feedback is included.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the Excel data parsing and processing correctly implemented?",
-      "description": "Evaluate whether the code properly parses Excel files using appropriate libraries (such as SheetJS/xlsx.js), handles different data types (numbers, strings, dates), manages empty cells, and converts data into usable JavaScript objects/arrays. Check if multiple sheets are supported. Deduct 5 points if date formatting is incorrect, 3 points if special characters cause parsing errors. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are comprehensive and interactive charts implemented?",
-      "description": "Check whether the code generates meaningful charts from Excel data using proper charting libraries (Chart.js, D3.js, etc.), supports multiple chart types (bar, line, pie, scatter), includes interactive features (hover tooltips, zoom, legend toggles), and handles dynamic data updates. Deduct 5 points if charts are static without interaction, 3 points if chart types are limited to basic ones only. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the data visualization workflow and user experience well-designed?",
-      "description": "Evaluate whether the application provides a smooth user journey from file upload to chart display, includes data preview before visualization, allows users to select which columns/rows to chart, provides chart customization options (colors, titles, axis labels), and handles large datasets efficiently. Deduct 5 points if no data preview is provided, 3 points if chart customization is limited. Give 10 points if fully implemented with excellent UX flow.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as corrupted Excel files, network interruption, oversized files, malformed data, browser compatibility issues, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Real-time chart animation during data loading 2. Export charts as images/PDF 3. Multiple file comparison views 4. Data filtering and search capabilities 5. Chart template gallery). 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 file parsing libraries loaded simultaneously) 2. Function modules unrelated to Excel processing and charting (e.g., built-in games or social features) 3. Excessive animations that slow down data processing. 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 (separating file handling/data processing/visualization layers), proper error handling patterns, and clean code structure. Deduct 5 points if global variables pollute the namespace or no proper design patterns are used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if no proper dependency management or code organization is implemented. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface design meet professional standards?",
-      "description": "Evaluate whether the overall design follows modern web design principles: 1) Harmonious color scheme (no more than 3 primary colors) 2) Proper spacing and layout (consistent margins and padding) 3) Professional typography (readable font sizes ≥ 14px, proper line height) 4) Clear visual hierarchy for upload area, data preview, and charts. Deduct 3 points for each cluttered visual element, 5 points for poor color combinations, and 5 points for inconsistent layout patterns. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Are the interactions smooth and provide clear feedback?",
-      "description": "Judge whether the user interactions are intuitive and responsive: 1) File upload progress indicators 2) Loading states during Excel parsing 3) Smooth chart rendering transitions 4) Clear success/error messages 5) Responsive design for different screen sizes. Deduct 5 points for each operation without proper feedback, 3 points for slow response times (>2 seconds for file processing), and 5 points for unclear navigation or confusing interface states. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Data Science-Data Visualization Dashboards",
-  "difficulty": "easy"
-}

package/library/data_science-data_visualization_dashboards/wechat-mini-program-data-analysis-page.json

@@ -1,68 +0,0 @@
-{
-  "index": 1245,
-  "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 purposes. Next, write a data analysis page in a WeChat Mini Program that visually displays the obtained data.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the basic WeChat Mini Program structure implemented correctly?",
-      "description": "Verify if the code contains the essential WXML, WXSS, JS files with proper structure, page registration in app.json, and follows Mini Program development specifications. Check if it includes proper page lifecycle hooks (onLoad, onShow, etc.) and follows the correct directory structure. Score 0 if the core Mini Program structure is missing, 5 if basic structure exists with minor issues, and 10 if fully compliant with WeChat specification.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the data acquisition and processing logic complete?",
-      "description": "Examine whether the code includes proper data fetching mechanisms (wx.request or equivalent), data transformation functions, error handling for API calls, and caching strategies. Check for loading states and retry mechanisms. Deduct 5 points if API error handling is absent, 3 points if there's no loading state management, and 3 points if data transformation logic is incomplete. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are appropriate visualization components implemented?",
-      "description": "Assess if the code uses appropriate visualization libraries (like ec-canvas for ECharts, wx-chart, or Canvas API) with proper chart types matching the data characteristics. Check if the visualizations include proper labels, legends, tooltips, and responsive sizing. Deduct 5 points if chart types don't match the data nature, 3 points for missing interactive elements, and 5 points for poor responsiveness. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Does the solution include user interaction for data analysis?",
-      "description": "Evaluate whether the code implements filtering options, time range selection, category toggles, data drill-down capabilities, and other interactive analysis features. Check if the interactions update the visualizations in real-time. Score 0 if no data interaction exists, 5 if only basic filters are present, and 10 if comprehensive analysis interactions are implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as empty data sets, network errors, unexpected data formats, 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 data insights 2. Custom gesture controls for analysis 3. Social sharing of analysis results). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple chart libraries for the same purpose) 2. Function modules unrelated to data analysis (e.g., a built-in game) 3. Fancy effects that affect performance (e.g., excessive animations). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating data/view/controller layers), component reusability, and Mini Program optimization practices. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if performance optimization measures are absent. 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 WeChat Mini Program 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 chart layouts. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Chart transitions occur within 300ms 2) Touch feedback delay ≤ 100ms 3) Clear visual focus guidance when switching between analysis views. Deduct 5 points for each operation without feedback, 3 points for laggy chart rendering, and 5 points for awkward gesture recognition. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Data Science-Data Visualization Dashboards",
-  "difficulty": "easy"
-}

package/library/data_science-data_visualization_dashboards/world-empires-gantt-chart.json

@@ -1,68 +0,0 @@
-{
-  "index": 1426,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the code you generate is executable when possible. Write an HTML file that draws a Gantt chart depicting the rise and fall of world empires spanning across Europe, Asia, and Africa.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the Gantt chart visualization fully implemented?",
-      "description": "Review whether the HTML file correctly implements a Gantt chart structure with proper timeline representation of empires. Check if it includes time scales, empire names, and duration bars. Score 0 if visualization is missing, 5 if basic chart is implemented but lacks detail, and 10 if the chart clearly depicts multiple empires with accurate time periods.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are historical empires of Europe, Asia, and Africa accurately represented?",
-      "description": "Evaluate the historical accuracy and comprehensiveness of the empires included. The visualization should include major empires from all three continents (at least 5 from each continent) with reasonably accurate time periods. Deduct 2 points for each continent underrepresented (fewer than 5 empires), and 5 points if historical dates have significant inaccuracies (>50 years for ancient empires, >20 years for more recent ones).",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the timeline implementation effective and well-scaled?",
-      "description": "Check if the timeline handles the vast historical span appropriately (potentially covering 3000+ years). Assess if the scale is consistent, if important historical periods are highlighted, and if overlapping empires are clearly distinguished. Deduct 5 points if the timeline scale is distorted or inconsistent, and 3 points if overlapping empires are difficult to distinguish.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Does the visualization include interactive features for better understanding?",
-      "description": "Evaluate implementation of interactive features such as zooming, panning, filtering by region/period, tooltips with additional information, or highlighting related empires. Award 2 points for each well-implemented interactive feature (max 10 points), with particular attention to features that enhance historical understanding and exploration.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as browser compatibility issues, missing data handling, responsive design for different screen sizes, etc.) and provide fallback 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. Visual representation of empire expansion/contraction 2. Integration of important historical events as markers 3. Comparative visualization of empire territories/population/influence). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar visualization functions 2. Feature modules unrelated to historical empires visualization 3. Fancy effects that affect performance without adding historical context. Deduct 3 points for each redundancy found, and directly deduct 10 points if the core visualization functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating data/visualization/interaction layers), code organization, and optimization techniques. Deduct 5 points if global state pollution is found or if appropriate design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the visualization performance is poor with noticeable lag. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern data visualization principles: 1) Clear visual hierarchy with appropriate emphasis on important empires 2) Harmonious color coding system that helps distinguish between regions/continents 3) Professional typography with readable labels (even for small empires). Deduct 3 points for each cluttered visual element, 5 points for poor color scheme that makes empire distinction difficult, and 5 points for illegible labels. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the dynamic effects enhance historical understanding: 1) Smooth transitions when filtering/sorting empires 2) Responsive tooltips appearing within 100ms 3) Clear visual cues for interactive elements. Deduct 5 points for jerky animations, 3 points for delayed responses to user interactions, and 5 points for confusing or hidden interactive controls. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Data Science-Data Visualization Dashboards",
-  "difficulty": "medium"
-}

package/library/data_science-machine_learning/ai-quant-trading-digital-currency-product.json

@@ -1,68 +0,0 @@
-{
-  "index": 1627,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Take care to ensure the generated code is executable for demonstration. Help create an AI quantitative trading product in the digital currency field that integrates multi-factor models, basic trading indicators, risk control mechanisms, position management, data statistics, and dashboard functionality. The requirements are a monthly return of 15% with risk lower than 5%. Please provide complete executable code.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the multi-factor model for crypto trading fully implemented?",
-      "description": "Review whether the code implements comprehensive multi-factor analysis, including at minimum: momentum factors, value factors, sentiment analysis, and on-chain metrics. Score 0 if no factors are implemented, 5 if only basic factors (like simple moving averages) are used, and 10 if the model incorporates at least 4 distinct factor categories with proper normalization and weighting mechanisms.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are standard trading indicators and their integration implemented?",
-      "description": "Evaluate the implementation of at least 5 essential trading indicators (e.g., MACD, RSI, Bollinger Bands, OBV, Stochastic) and how they're combined into trading signals. Verify that the indicators are properly parameterized and that signal conflicts are resolved through a clear decision framework. Deduct 2 points for each missing core indicator, and 3 points if there's no signal aggregation logic.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the risk control mechanism robust and comprehensive?",
-      "description": "Check if the system includes stop-loss mechanisms, volatility-based position sizing, drawdown controls, and market regime detection. The code must implement at least two layers of risk control (trade level and portfolio level) with clear risk metrics calculation (VaR, maximum drawdown). Deduct 5 points if there's no volatility adjustment logic, and 3 points if maximum loss limits aren't enforced. Full score requires all these elements plus backtesting of the risk controls.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is position management and sizing algorithm implemented?",
-      "description": "Assess whether the code handles dynamic position sizing based on account equity, market conditions, and signal strength. Check for implementation of Kelly criterion or similar mathematical position sizing, diversification logic across multiple assets, and correlation-aware allocation. Deduct 5 points if position sizing is static, 3 points if rebalancing logic is missing, and 2 points if there's no consideration for trading costs in the position calculations.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as market data gaps, API failures, extreme volatility events, etc.) and provide error handling or recovery mechanisms. Code with strong robustness should include retry mechanisms, data validation, exception handling for API calls, and graceful degradation in adverse conditions. If robust error handling exists across all modules, give 10 points. If error handling is inconsistent, give 5 points. If critical operations lack error handling, 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 system (e.g., 1. Auto-adaptation to market regimes 2. Machine learning for parameter optimization 3. Sentiment analysis from social media integration 4. Advanced order execution algorithms). 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 position sizing algorithms running in parallel) 2. Function modules unrelated to trading (e.g., unnecessary data visualization) 3. Computationally expensive operations that don't contribute to performance (e.g., excessive resampling of data). 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/signal generation/execution/risk management layers), unit test coverage, and configuration management. 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 configuration separation from the code. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the dashboard and visualization meet professional standards?",
-      "description": "Evaluate whether the trading dashboard follows financial visualization best practices: 1) Clear performance metrics display (CAGR, Sharpe ratio, drawdown) 2) Proper equity curve and drawdown visualization 3) Trade distribution analysis 4) Risk exposure charts. Deduct 3 points for each missing critical visualization, 5 points for misleading performance representation, and 5 points for poor data-to-ink ratio. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Does the system meet the performance requirements?",
-      "description": "Judge whether the backtesting results demonstrate the required 15% monthly return with risk under 5%. Check if the performance is consistent across different market conditions and time periods. Deduct 5 points if backtesting doesn't include transaction costs and slippage, 3 points if there's no out-of-sample testing, and 5 points if the Sharpe ratio is below 2.0. The full score is 10 points if all requirements are met with convincing statistical significance.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Data Science-Machine Learning",
-  "difficulty": "hard"
-}