@getollie/cli 0.0.5 → 0.2.1

package/library/data_science-data_visualization_dashboards/uniapp-editable-knowledge-graph.json

@@ -1,68 +0,0 @@
-{
-  "index": 1613,
-  "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 whenever possible. uniapp, implement an editable knowledge graph.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the knowledge graph data structure properly implemented?",
-      "description": "Review whether the code accurately implements a graph data structure for knowledge representation, including nodes (concepts) and edges (relationships). Score 0 if there's no clear graph structure, 5 if basic node-edge representation exists, and 10 if it includes advanced features like node types, edge weights, and directional relationships.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are the graph editing capabilities fully functional?",
-      "description": "Check if the implementation allows CRUD operations (Create, Read, Update, Delete) for both nodes and edges. Verify the presence of node/edge selection, dragging, resizing, and content editing. Deduct 3 points if any basic operation is missing, and 5 points if multi-selection or batch operations aren't supported. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the visualization rendering optimized for uniapp?",
-      "description": "Evaluate whether the visualization leverages appropriate uniapp rendering methods (canvas vs. component-based) based on graph complexity. Check if it handles cross-platform differences (iOS/Android/H5) and applies performance optimizations like culling for off-screen elements or level-of-detail techniques. Deduct 5 points if rendering is sluggish with >50 nodes, and 3 points if platform-specific issues exist. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Does the implementation use appropriate uniapp features?",
-      "description": "Assess whether the code uses uniapp-specific components and APIs properly. Check for proper utilization of uni-app lifecycle hooks, conditional compilation for platform differences, and appropriate use of uniapp UI components. Deduct 5 points for excessive web-view usage when native components would be more appropriate, and 5 points if the code doesn't follow uniapp's development paradigm. 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 graph data, user operation errors, or touch event conflicts) 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. Auto-layout algorithms for graph organization 2. Export/import functionality with standard knowledge graph formats 3. Gesture shortcuts for rapid graph manipulation). 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 graph manipulation libraries) 2. Function modules unrelated to knowledge graph editing (e.g., unneeded social features) 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 graph 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) Touch feedback delay ≤ 100ms 2) Graph manipulation responsiveness on different devices 3) Clear visual focus guidance. Deduct 5 points for each operation without feedback, 3 points for visual lag during graph manipulation, 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/uniapp-vue3-ts-h5-line-bar-charts-page.json

@@ -1,68 +0,0 @@
-{
-  "index": 730,
-  "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. Create a uniapp vue3 ts H5 page with simple line charts and bar charts.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the vue3 + ts UniApp project structure correctly set up?",
-      "description": "Check if the project includes essential files: pages.json, manifest.json, App.vue, main.ts and appropriate tsconfig.json. Verify proper TypeScript configuration with strict type checking and vue3 support. Ensure the project structure follows UniApp conventions with appropriate directory organization (pages/, components/, static/, etc.). Score 0 if missing critical files, 5 if basic structure exists but with configuration issues, 10 if perfectly configured with proper type declarations.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are line charts properly implemented with appropriate libraries?",
-      "description": "Evaluate if a suitable charting library compatible with UniApp is used (such as echarts, uCharts, or F2). Check if the line chart implementation includes: dynamic data binding, responsive sizing, proper axis configuration, and legend display. Examine if TypeScript interfaces/types are defined for chart data. Deduct 5 points if the chart is not responsive, 3 points if missing proper type definitions, and 5 points if lacking customization options. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are bar charts correctly implemented with proper data visualization principles?",
-      "description": "Verify if the bar chart implementation includes appropriate scales, labels, and color encoding. Check for animations, tooltips, and interaction capabilities. Ensure data is properly bound with TypeScript interfaces. Verify if the chart handles edge cases like empty data, overflow values, and resizing. Deduct 3 points if lacking proper color contrast, 5 points if missing interactive features, and 5 points if data binding is improperly typed. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the H5 compatibility and responsiveness properly handled?",
-      "description": "Check if the page adapts to different screen sizes using UniApp's responsive design capabilities. Verify if conditional compilation (@/:#ifdef H5) is used appropriately for H5-specific code. Test if touch events are properly handled for mobile browsers. Ensure viewport meta tags are correctly set for mobile devices. Deduct 5 points if the layout breaks on common mobile dimensions, 3 points if touch interactions are missing, and 5 points if H5-specific optimizations are absent. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as data loading failures, malformed data, network errors, etc.) and provide friendly error prompts or recovery mechanisms. Check for proper error boundaries in Vue components. Verify if charts handle edge cases gracefully (empty datasets, extreme values). 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 chart tooltips with rich content 2. Chart theme switching based on system preference 3. Gesture-based chart interactions 4. Data export capabilities 5. Animated transitions between data views). 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 library imports (e.g., including multiple charting libraries for similar purposes) 2. Unnecessary components or modules unrelated to visualization (e.g., complex multimedia elements) 3. Excessive animations or effects that impact performance on mobile devices. Deduct 3 points for each redundancy found, and directly deduct 10 points if the core chart functionality is interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review component organization (separating chart components from data fetching logic), TypeScript usage quality (proper interfaces, avoiding any/unknown types), and code reusability. Check if composition API is used appropriately with proper lifecycle hooks. Deduct 5 points if TypeScript is used poorly or has numerous type assertions; deduct 5 points if the code has high duplication between chart implementations; deduct 5 points if the composition API is misused or reactive references are implemented incorrectly. 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 in charts (consistent palette, appropriate contrast) 2) Proper layout spacing (chart margins, padding between elements) 3) Professional typography (readable labels, appropriate font sizing for mobile). Deduct 3 points for cluttered charts, 5 points for poor color choices that impede data interpretation, and 5 points for illegible labels or overlapping elements. 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 rendering and updates within 300ms 2) Smooth animations for transitions between data states 3) Responsive touch interactions without lag. Check if the charts respond immediately to user inputs. Deduct 5 points for noticeable lag when interacting with charts, 3 points for jerky animations, and 5 points for charts that don't provide immediate visual feedback during interaction. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Data Science-Data Visualization Dashboards",
-  "difficulty": "easy"
-}

package/library/data_science-data_visualization_dashboards/us-population-changes-dashboard-visualization.json

@@ -1,68 +0,0 @@
-{
-  "index": 1612,
-  "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. Create a dashboard for U.S. population changes that includes visualization design and data presentation. Output in HTML format, ensuring the file is executable.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the U.S. population data visualization complete and accurate?",
-      "description": "Check whether the dashboard includes comprehensive population data visualization with appropriate metrics (total population, growth rate, demographic breakdown by age/ethnicity/gender). Verify data accuracy against reliable sources (Census Bureau, etc.). Score 0 if basic population trends are missing, 5 if only showing limited metrics, and 10 if offering comprehensive demographic insights with proper data attribution.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are multiple visualization types implemented effectively?",
-      "description": "Evaluate whether the dashboard implements diverse chart types appropriate for different data aspects (line charts for trends over time, choropleth maps for geographic distribution, bar/pie charts for comparative analysis). Check if visualizations use D3.js or other libraries effectively. Deduct 3 points if only one visualization type is used, 5 points if charts are inappropriate for the data type, and 2 points if interactive elements are missing. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the dashboard interactive with filtering and drill-down capabilities?",
-      "description": "Assess if the dashboard includes user interaction features like time period selectors, state/region filters, demographic breakdowns, and data comparison tools. Interactive elements should provide smooth transitions and clear visual feedback. Deduct 5 points if filtering capabilities are absent, 3 points if drill-down functions are limited, and 2 points if interactions lack visual confirmation. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Does the dashboard present data insights and context effectively?",
-      "description": "Review whether the dashboard goes beyond raw data display to provide meaningful context (population trends, notable migration patterns, policy implications). Check for tooltips, annotations, or narrative elements that highlight key insights. Deduct 5 points if contextual information is missing, 3 points if insights lack depth, and 2 points if annotation system is inadequate. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code handles common edge cases (missing data, loading states, browser compatibility, responsive design for different screen sizes). Code should include error handling for data fetching failures and graceful degradation. Give 10 points for comprehensive error handling and responsive design, 5 points for partial implementation, and 0 points if critical failures occur under normal usage scenarios.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the dashboard includes unique features enhancing user experience (e.g., 1. AI-powered trend predictions 2. Custom population comparison tool 3. Time-lapse visualization of demographic shifts). 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 data in different formats without adding new insights 2. Unnecessary UI elements not related to population data analysis 3. Heavy animations or effects that impair dashboard performance. Deduct 3 points for each redundancy found, and directly deduct 10 points if core visualization functions are compromised by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (separation of data processing, visualization rendering, and UI components), code reusability, and performance optimization. Deduct 5 points for global variable overuse or poor encapsulation; deduct 3 points if the data loading process lacks optimization (no data caching or preloading); deduct 2 points if rendering performance drops significantly with larger datasets. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the dashboard follows data visualization best practices: 1) Color scheme is accessible and distinguishable (including for color-blind users) 2) Information hierarchy is clear with logical layout 3) Typography enhances readability (consistent font families, appropriate size hierarchy). Deduct 3 points for cluttered layout, 5 points for poor color choices that hinder data interpretation, and 2 points for inconsistent visual language across dashboard components. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether transitions and interactions feel natural: 1) Data filtering responds within 300ms 2) Chart animations have appropriate easing functions and duration 3) Loading states provide visual feedback. Deduct 5 points for laggy transitions when changing views, 3 points for abrupt visual changes without proper transitions, and 2 points for confusing interaction patterns that lack affordance cues. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Data Science-Data Visualization Dashboards",
-  "difficulty": "easy"
-}

package/library/data_science-data_visualization_dashboards/visitor-flow-analysis-xinzhou-vue-implementation.json

@@ -1,68 +0,0 @@
-{
-  "index": 1024,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure that the code you generate is executable for demonstration. The thesis title is \"Visitor Flow Analysis of Xinzhou Ancient City Based on Vue Implementation\".",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the Vue.js architecture and component system properly implemented?",
-      "description": "Review whether the code correctly implements Vue.js framework with proper component hierarchy, state management (Vuex/Pinia), and routing (Vue Router). Check if components are properly structured with data flow, props validation, and lifecycle management. Score 0 if basic Vue structure is missing, 5 if only basic components are implemented without state management, and 10 if complete Vue ecosystem with proper architecture is implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the visitor flow data visualization comprehensively implemented?",
-      "description": "Evaluate whether the system includes multiple visualization methods for visitor flow analysis such as heat maps, flow direction charts, time-series analysis, and statistical dashboards. Check if data binding is reactive and supports real-time updates. Deduct 5 points if only basic charts are provided, 3 points if interactive filtering is missing. Full score requires comprehensive multi-dimensional visualization with smooth data transitions.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the ancient city geographic mapping and spatial analysis accurately implemented?",
-      "description": "Check whether the code includes accurate geographic mapping of Xinzhou Ancient City with proper coordinate systems, landmark positioning, and spatial relationship analysis. Evaluate if visitor flow paths are correctly mapped to actual geographic locations with proper scaling and orientation. Deduct 5 points if geographic accuracy is poor, 3 points if spatial relationships are not properly represented. Full score requires precise geographic implementation with detailed spatial analysis.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the data processing and analysis algorithm properly implemented?",
-      "description": "Review whether the system includes proper data preprocessing, filtering, aggregation, and statistical analysis algorithms for visitor flow patterns. Check if temporal analysis, peak detection, and trend analysis are implemented. Evaluate data validation and cleansing mechanisms. Deduct 5 points if data processing is superficial, 3 points if statistical analysis is incomplete. Full score requires comprehensive data analysis with multiple algorithmic approaches.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust and handles edge cases effectively?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as missing data, network interruption, invalid coordinates, empty datasets, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should effectively handle these edge cases and maintain system stability, giving 10 points. If robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there innovative features that enhance the analysis experience?",
-      "description": "Check whether the code includes valuable features that enhance visitor flow analysis (e.g., 1. Predictive flow modeling 2. Comparative analysis across time periods 3. Interactive 3D visualization 4. Real-time monitoring dashboard 5. Export functionality for reports). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant or unnecessary features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar visualization functions 2. Feature modules unrelated to visitor flow analysis 3. Excessive animations or effects that impact performance and distract from data analysis. Deduct 3 points for each redundancy found, and directly deduct 10 points if core analytical functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code demonstrate high engineering quality?",
-      "description": "Review modular design (separation of data layer/visualization layer/business logic), component reusability, and code organization. Deduct 5 points if global state pollution is found or Vue best practices are not followed; deduct 5 points if code duplication rate exceeds 30%; deduct 5 points if proper build configuration and optimization are missing. Full score requires excellent code structure and maintainability.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface design meet professional academic presentation standards?",
-      "description": "Evaluate whether the design follows academic and professional standards: 1) Clear information hierarchy with proper data visualization principles 2) Consistent color scheme suitable for data analysis (colorblind-friendly palettes) 3) Professional typography with readable font sizes and proper contrast 4) Clean layout without visual clutter. Deduct 3 points for each poorly designed visualization element, 5 points for unprofessional color choices, and 5 points for cluttered or confusing layout.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Are the interactive elements smooth and intuitive for data exploration?",
-      "description": "Judge whether interactions support effective data exploration: 1) Responsive filtering and selection with immediate feedback 2) Smooth transitions between different views and time periods 3) Intuitive navigation and zoom controls 4) Clear visual indicators for interactive elements. Deduct 5 points for each unresponsive interaction, 3 points for confusing navigation, and 5 points for slow rendering that impacts user experience during data exploration.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Data Science-Data Visualization Dashboards",
-  "difficulty": "hard"
-}

package/library/data_science-data_visualization_dashboards/visualization-dashboard-word-cloud-code-with-npm.json

@@ -1,68 +0,0 @@
-{
-  "index": 416,
-  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Pay attention to ensure the generated code is executable for demonstration. Visualization dashboard word cloud code, created with npm.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the word cloud visualization core functionality implemented correctly?",
-      "description": "Check if the code implements a proper word cloud visualization using appropriate npm packages (e.g., d3-cloud, react-wordcloud). The implementation should handle text processing, word frequency calculation, and visual rendering. Score 0 if no word cloud is generated, 5 if basic functionality exists with flaws, and 10 if the implementation is complete with proper text processing and visualization.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Does the code handle data input and processing appropriately?",
-      "description": "Evaluate how the code handles text input (from files, APIs, or user input), processes it (tokenization, stopword removal, stemming/lemmatization), and calculates word frequencies. Check if it handles different languages, special characters, and case sensitivity. Deduct 3 points if stopwords aren't handled, 3 points if no text preprocessing exists, and 2 points if it only works with English text. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the dashboard integration complete and functional?",
-      "description": "Assess if the word cloud is properly integrated into a dashboard context with appropriate layout structure. The dashboard should include controls for customization, data refresh mechanisms, and possibly other complementary visualizations. Deduct 5 points if the word cloud exists in isolation without dashboard elements, and 3 points if integration exists but with limited functionality. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Are word cloud customization options implemented?",
-      "description": "Check if the code allows customization of the word cloud appearance and behavior: font styles/sizes, color schemes, layout options (shape, orientation), minimum/maximum word count, and animation settings. Deduct 2 points for each major customization category missing. The full score is 10 points if comprehensive customization is available with intuitive controls.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as empty input, extremely large texts, malformed data, browser compatibility issues) 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 hovering effects with additional word information 2. Real-time word cloud updates based on streaming data 3. Exportable word cloud as SVG/PNG with custom branding). 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 functionality (e.g., multiple text processing pipelines) 2. Function modules unrelated to the word cloud dashboard (e.g., unnecessary analytics) 3. Fancy effects that affect performance (e.g., excessive animations that slow rendering). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating data processing/visualization/UI components), code organization, dependency management, and build configuration. Deduct 5 points if global state pollution is found; deduct 3 points if npm dependencies are not properly managed; deduct 5 points if the code lacks comments or documentation. Check if the project has a proper structure with 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 overall design follows modern dashboard design principles: 1) Harmonious color matching with consistent palette 2) Proper layout with appropriate use of space and grid systems 3) Professional typography with readable fonts and proper contrast ratios. Deduct 3 points for cluttered layout, 5 points for poor color choices affecting readability, and 5 points for inconsistent styling across components. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and responsive?",
-      "description": "Judge whether the word cloud and dashboard interactions are fluid and responsive: 1) Smooth transitions when filtering or updating data 2) Responsive design that works across device sizes 3) Performance optimization for large datasets without UI freezing. Deduct 5 points for laggy rendering with large word sets, 3 points for missing loading states during data processing, and 3 points for non-responsive design on different screen sizes. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Data Science-Data Visualization Dashboards",
-  "difficulty": "medium"
-}

package/library/data_science-data_visualization_dashboards/visualize-excel-pois-clustering-on-map-html.json

@@ -1,68 +0,0 @@
-{
-  "index": 1307,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to provide executable code that can be demonstrated. Read from Excel, display POIs and clustering situations on a map, and visualize through HTML.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the Excel data reading functionality properly implemented?",
-      "description": "Evaluate whether the code correctly reads data from Excel files (XLSX/XLS) including error handling for missing files, incorrect formats, and large datasets. Check if the code uses appropriate libraries (e.g., SheetJS, xlsx, pandas) and maintains data integrity. Score 0 if there's no Excel reading implementation, 5 if basic reading is implemented but with limitations, and 10 if robust Excel processing with error handling is fully implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the POI data extraction and processing properly implemented?",
-      "description": "Review whether the code correctly extracts Point of Interest (POI) data from the Excel file, validates geographic coordinates (latitude/longitude), handles missing or invalid POI data, and transforms data into an appropriate format for mapping. Deduct 5 points if coordinate validation is missing, 3 points if there's no handling for incomplete data, and 2 points if data transformation is inefficient. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the clustering algorithm implementation effective?",
-      "description": "Assess the clustering algorithm implementation (e.g., K-means, DBSCAN, hierarchical clustering) for grouping POIs. Check if the algorithm is appropriate for geospatial data, includes proper parameter selection, and has optimization for performance with larger datasets. Deduct 5 points if the clustering doesn't account for geographic distance properly, 3 points if parameter tuning options are missing, and 2 points if performance issues exist with larger datasets. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the map visualization implementation complete?",
-      "description": "Evaluate whether the map implementation includes proper initialization (using libraries like Leaflet, Google Maps API, or OpenLayers), correct POI placement, appropriate zoom levels, distinguishable cluster visualizations, and interactive elements. Deduct 5 points if the map lacks proper initialization or responsive design, 3 points if POI markers lack clarity or distinction, and 3 points if clustering visualization is not intuitive. 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 Excel data, invalid coordinates, 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. Heatmap visualization as an alternative view 2. Time-series animation for temporal POI data 3. Advanced filtering options for clusters 4. Custom cluster inspection tools). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple mapping libraries used simultaneously) 2. Function modules unrelated to POI visualization (e.g., unnecessary analytics tools) 3. Fancy effects that affect performance (e.g., excessive animations that slow down map rendering). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating data loading/processing/visualization layers), unit test coverage, and build process automation. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the build process is not automated. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching for map elements and clusters (distinguishable but not jarring) 2) Proper layout spacing for controls and information panels 3) Professional font system for labels and information displays (readable at various zoom levels). Deduct 3 points for cluttered map controls, 5 points for indistinguishable cluster/POI markers, and 5 points for illegible text elements. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the map interactions conform to user expectations: 1) Responsive zooming and panning without lag 2) Clear visual feedback when selecting POIs or clusters 3) Smooth transitions when switching between cluster views and individual POIs. Deduct 5 points for laggy map rendering, 3 points for unresponsive POI selection, and 5 points for abrupt transitions between clustering levels. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Data Science-Data Visualization Dashboards",
-  "difficulty": "easy"
-}

package/library/data_science-data_visualization_dashboards/visualize-temperature-data-from-serial-monitor-web-interface.json

@@ -1,68 +0,0 @@
-{
-  "index": 1305,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the code you provide is executable for demonstration. How can I visualize temperature data from a serial monitor on a web interface, using USB as the communication method?",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the serial communication implementation complete?",
-      "description": "Check whether the code properly implements the Web Serial API or an alternative method for USB communication. Verify that it handles connection setup, disconnection handling, and error recovery. Score 0 if no serial communication code is implemented, 5 if basic connection is established but lacks error handling, and 10 if the implementation includes proper connection management, data buffering, and error handling.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the temperature data parsing logic robust?",
-      "description": "Evaluate whether the code correctly parses temperature data from the serial stream, handling different formats (JSON, CSV, plain text), corrupted data, and partial messages. Check for validation of reasonable temperature ranges and units conversion if needed. Score 3 if basic parsing is implemented, 7 if validation and error handling are included, and 10 if the parsing is comprehensive with support for multiple formats and robust against transmission errors.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is real-time visualization effectively implemented?",
-      "description": "Assess whether the visualization updates in real-time with minimal latency (< 500ms), uses appropriate charts/graphs (line charts, gauges, etc.) for temperature data, and handles continuous data streams without performance degradation. Score 3 for static visualization, 7 for basic real-time updates, and 10 for smooth visualization with proper time scaling and performance optimization.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is data history and management functionality provided?",
-      "description": "Check if the implementation includes data history storage, allows viewing historical data trends, provides zoom/pan capabilities for exploring the data timeline, and includes options for exporting/saving temperature logs. Score 0 if no history is maintained, 5 if basic history is shown but lacks interaction features, and 10 if comprehensive history management with time navigation controls is implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as device unplugging, buffer overflows, malformed data, browser compatibility issues) 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. Temperature anomaly detection with alerts 2. Multi-sensor comparison visualization 3. Responsive design for mobile/desktop). 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 data processing steps (e.g., multiple parsing of the same data) 2. Function modules unrelated to temperature visualization (e.g., irrelevant UI components) 3. Fancy effects that affect performance (e.g., excessive animations that slow down real-time updates). 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 communication/data processing/visualization layers), use of appropriate design patterns, error handling, and code 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 is no 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 visualization dashboard follows modern design principles: 1) Harmonious color scheme appropriate for data visualization (clear distinction between data series) 2) Proper layout with intuitive organization of components 3) Professional typography with clear legends and axis labels. Deduct 3 points for cluttered visualization, 5 points for poor color choices that make data hard to interpret, and 5 points for missing critical information like units or timestamp. 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 user expectations: 1) Data updates without visual jarring 2) Smooth transitions when new data arrives 3) Intuitive controls for adjusting view parameters (timeframe, scale, etc.). Deduct 5 points for each interaction without visual feedback, 3 points for choppy animations during updates, and 5 points for unintuitive interface controls. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Data Science-Data Visualization Dashboards",
-  "difficulty": "easy"
-}

package/library/data_science-data_visualization_dashboards/visualize-trajectories-code-segment.json

@@ -1,68 +0,0 @@
-{
-  "index": 997,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the code you generate is executable for demonstration purposes. Please create a complete code segment for visualizing trajectories, including the data reading portion, so I can try it out.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the trajectory data reading implementation correct and flexible?",
-      "description": "Check whether the code provides robust methods for reading trajectory data from common formats (CSV, JSON, etc.) and handles different data structures appropriately. Score 0 if no data reading is implemented, 5 if only basic file loading is included, and 10 if it supports multiple data formats with error handling and validation.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the trajectory visualization core rendering complete?",
-      "description": "Evaluate whether the visualization leverages appropriate technology (Canvas, SVG, WebGL, etc.) based on the data scale. Check if it properly implements features like path drawing, data point plotting, and coordinate mapping. Deduct 5 points if the visualization is static only, 3 points if there are rendering artifacts. Score 10 if the visualization is smooth with proper scaling and coordination transformations.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are interactive elements properly implemented?",
-      "description": "Review whether the code includes essential interactive features like zooming, panning, selection of specific trajectories, and time-based filtering/playback. Deduct 5 points if basic interactions are missing, 3 points if interactions have noticeable lag. Give 10 points if all interactions feel responsive and intuitive.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is there appropriate temporal representation in the visualization?",
-      "description": "Assess if the code handles the temporal aspect of trajectory data effectively, including features like timeline controls, color/opacity gradient for time progression, or animation capabilities. Score 0 if time is not represented, 5 if basic time representation exists but isn't interactive, and 10 if comprehensive temporal navigation and visualization are implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as malformed data, empty datasets, browser compatibility issues, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Real-time statistical analysis of trajectories 2. Pattern recognition for similar paths 3. Heat map overlay of trajectory densities). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar visualization methods 2. Function modules unrelated to trajectory visualization (e.g., unnecessary UI elements) 3. Fancy effects that affect performance (e.g., excessive animations or effects that obscure the data). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core visualization functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating data processing/visualization/interaction layers), code reusability, and performance optimization. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if no performance considerations are implemented for large datasets. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional data visualization standards?",
-      "description": "Evaluate whether the visualization follows effective data visualization principles: 1) Appropriate color schemes for data clarity 2) Clear visual hierarchy with proper labels and legends 3) Balanced information density without chart junk. Deduct 3 points for poor color choices that hinder data interpretation, 5 points for missing essential contextual elements (axes, legends, etc.), and 5 points for cluttered visuals that obscure the data narrative. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the visualization responsive and performant?",
-      "description": "Judge whether the implementation maintains smooth performance across different data loads: 1) Renders trajectories with minimal latency 2) Efficiently handles large datasets with appropriate optimizations (data sampling, WebWorkers, etc.) 3) Adapts gracefully to different screen sizes. Deduct 5 points for noticeable lag with moderate data sizes, 3 points for poor mobile/responsive behavior, and 5 points if the visualization breaks under larger datasets. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Data Science-Data Visualization Dashboards",
-  "difficulty": "easy"
-}