@getollie/cli 0.0.4 → 0.2.0

package/library/web_applications-web_visuals/vue-3-canvas-2.5d-effect-button-click.json

@@ -1,68 +0,0 @@
-{
-  "index": 1394,
-  "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. For a Vue 3 project, write a canvas flat graphic that transforms into a 2.5D effect after clicking a button.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the 2D to 2.5D transformation effect properly implemented?",
-      "description": "Review whether the code accurately implements transformation from a flat 2D shape to a 2.5D perspective view using canvas manipulation and matrix transformations. Score 0 if no transformation is implemented, 5 if there's basic transformation but lacks depth perception, and 10 if the transformation includes proper perspective, shading, and visual depth cues.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the Vue 3 integration well-executed?",
-      "description": "Evaluate whether the code properly leverages Vue 3 features (Composition API, reactive refs, computed properties, lifecycle hooks) to manage the canvas and transformation state. Deduct 3 points if not using Vue 3's reactive system effectively, 3 points if not properly handling component lifecycle, and 3 points if missing proper component structure. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the canvas drawing implementation correct and efficient?",
-      "description": "Check whether the canvas API is used correctly for both 2D and transformed states. Look for proper context management, efficient redrawing strategy, and correct handling of canvas dimensions. Deduct 5 points if using inefficient redraw methods (like clearing the entire canvas unnecessarily), 3 points if canvas dimensions are not responsive, and 3 points if transformations cause visual artifacts. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the animation smooth and visually appealing?",
-      "description": "Evaluate whether the transformation between 2D and 2.5D states is animated smoothly. Check for use of requestAnimationFrame, proper easing functions, and consistent frame rates. Deduct 5 points if animation is jerky or has frame drops, 3 points if transition timing is unnatural, and 2 points if visual artifacts appear during animation. 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 window resizing, device pixel ratio differences, interaction during animation, etc.) and provide 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. User-controlled camera angle in 2.5D mode 2. Dynamic lighting effects 3. Interactive manipulation of the transformed object). 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 drawing functions 2. Function modules unrelated to the 2D-to-2.5D transformation 3. Fancy effects that affect performance without adding value to the core functionality. 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 rendering logic/transformation logic/interaction handling), reusability of components, and maintainability. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the code lacks proper documentation or comments. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching for both 2D and 2.5D states 2) Proper layout spacing for controls and canvas 3) Professional transitions between states. Deduct 3 points for each visually unappealing element, 5 points for poorly chosen colors that detract from the effect, and 5 points for chaotic button/control placement. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the interactions conform to human perception characteristics: 1) Click feedback delay ≤ 100ms 2) Transformation animation duration controlled between 300-800ms 3) Clear visual indication of interactive elements. Deduct 5 points for each operation without feedback, 3 points for laggy response during transformation, and 5 points for confusing or hard-to-find controls. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Web Visuals",
-  "difficulty": "easy"
-}

package/library/web_applications-web_visuals/vue-amap-realtime-location-monitor.json

@@ -1,68 +0,0 @@
-{
-  "index": 1149,
-  "question": "You are a code expert. Please utilize your professional knowledge to generate accurate and professional responses. Make sure that the code you generate is executable for demonstration purposes. Work on the project from requirements to finished product, based on the approach of a Huawei expert-led team developing from zero to one... Develop a real-time location monitoring module based on Vue.js, integrating the Amap (AutoNavi/Gaode Maps) API.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the Amap API integration complete and functional?",
-      "description": "Review whether the code properly integrates Amap JavaScript API with correct key authentication, map initialization, and essential map controls. Check if the implementation includes proper error handling for API failures, coordinate system conversion (WGS84/GCJ02), and map style customization. Score 0 if API integration fails or key functions are missing, 5 if basic map display works but lacks essential features, and 10 if all core Amap functionalities are properly implemented with robust error handling.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the real-time location tracking mechanism properly implemented?",
-      "description": "Evaluate whether the code implements accurate geolocation acquisition using HTML5 Geolocation API or device GPS, includes position accuracy validation, and handles location permission requests gracefully. Check for real-time coordinate updates with appropriate frequency control (avoid battery drain), location smoothing algorithms, and fallback mechanisms when GPS is unavailable. Deduct 5 points if permission handling is missing, 3 points if location accuracy is poor, and 5 points if no battery optimization is considered. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the Vue.js architecture and component design well-structured?",
-      "description": "Check whether the Vue.js implementation follows best practices including proper component decomposition (map component, location service, control panels), reactive data management using Vuex or Composition API, and lifecycle management for map initialization/destruction. Evaluate if the code uses Vue 3 features appropriately and maintains clean separation between map logic and Vue components. Deduct 5 points for poor component structure, 3 points for improper state management, and 5 points for memory leaks in component lifecycle. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Are the monitoring features comprehensive and enterprise-ready?",
-      "description": "Assess whether the module includes professional monitoring capabilities such as: location history tracking with timestamps, geofencing alerts, multi-target monitoring dashboard, location data export functionality, and real-time notification system. Check for admin panel features, user permission management, and monitoring analytics. Deduct 5 points if core monitoring features are missing, 3 points if data persistence is not implemented, and 5 points if the interface lacks professional monitoring tools. 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 network interruption, GPS signal loss, API rate limiting, browser compatibility issues, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should effectively handle edge cases including offline scenarios, location permission denial, and API quota exhaustion. Give 10 points if fully robust, 5 points if average robustness, and 0 points if no exception handling.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes impressive features that enhance the monitoring experience (e.g., 1. Predictive location analytics with AI 2. Custom heatmap visualization for location density 3. Voice alerts for geofencing 4. Real-time collaboration features 5. Advanced data visualization dashboards). 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 location service instances) 2. Function modules unrelated to location monitoring (e.g., built-in weather widget) 3. Fancy effects that affect map performance (e.g., excessive marker animations). Deduct 3 points for each redundancy found, and directly deduct 10 points if core location functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (separating map service/location service/UI components), TypeScript usage, unit test coverage, and build process automation. Check for proper Vue.js project structure, ESLint configuration, and deployment scripts. Deduct 5 points if global state pollution is found or Vue best practices are not followed; deduct 5 points if code duplication rate is too high (over 30%); deduct 5 points if build process is not automated. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface design meet professional monitoring system standards?",
-      "description": "Evaluate whether the monitoring interface follows enterprise dashboard design principles: 1) Professional color scheme suitable for monitoring (dark theme support) 2) Clear information hierarchy with proper spacing (8px grid system) 3) Readable typography system (minimum 14px font, 1.5x line height) 4) Intuitive iconography for location states. Deduct 3 points for each cluttered visual element, 5 points for unprofessional color choices, and 5 points for poor information architecture. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the real-time interaction smooth and responsive?",
-      "description": "Judge whether the real-time features perform smoothly: 1) Map rendering and zoom operations ≤ 100ms response time 2) Location updates with smooth marker transitions (300-500ms) 3) Real-time data refresh without UI blocking 4) Clear visual feedback for all monitoring actions. Deduct 5 points for each laggy interaction, 3 points for choppy map animations, and 5 points for unclear system status indicators. Full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Web Visuals",
-  "difficulty": "hard"
-}

package/library/web_applications-web_visuals/vue2-offline-map-cesium-zhengzhou.json

@@ -1,68 +0,0 @@
-{
-  "index": 1083,
-  "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. Implement a Vue2 offline map component using Cesium (covering only Zhengzhou city).",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the Cesium map initialization and configuration properly implemented?",
-      "description": "Check whether the Cesium map instance is correctly initialized with proper viewport configuration, appropriate default camera position targeting Zhengzhou (coordinates approximately 34.7°N, 113.6°E), and essential Cesium widgets. Score 0 if map initialization fails, 5 if basic initialization exists but with incorrect Zhengzhou positioning, and 10 if initialization includes proper Zhengzhou focus with appropriate altitude and angle settings.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is offline map data for Zhengzhou city correctly implemented?",
-      "description": "Evaluate whether the code includes proper configuration for offline tile sets, with correct paths to local terrain and imagery assets specific to Zhengzhou boundaries. Check if there's proper tile caching mechanism and local resource management. Deduct 5 points if only partial offline capabilities are implemented, 8 points if offline mode is mentioned but not functionally implemented. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the Vue2 component structure properly designed?",
-      "description": "Assess whether the code follows Vue2 best practices with proper component lifecycle methods (especially for Cesium resource management in mounted/beforeDestroy hooks), proper prop validation, emitted events, and a cleanly encapsulated component structure. Check for memory leak prevention with proper destruction of Cesium entities. Deduct 3 points for each missing critical lifecycle management aspect, and 5 points if Vue reactivity is not properly integrated with Cesium. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Are essential map navigation controls and user interactions implemented?",
-      "description": "Review whether the component includes necessary map interactions such as zoom, pan, rotation, and provides a user-friendly UI for these controls specific to the Zhengzhou area. Check for proper event handling of user interactions and appropriate visual feedback. Score 0 if no controls are implemented, 5 if only basic map navigation exists, and 10 if comprehensive controls with Zhengzhou-specific features (like district selection) are included.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as missing offline tiles, initialization failures, plugin loading errors, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Offline POI search within Zhengzhou 2. Custom 3D landmarks for Zhengzhou attractions 3. District-based data visualization layers). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant initialization of Cesium resources (e.g., multiple viewer instances) 2. Function modules unrelated to Zhengzhou mapping (e.g., support for other cities without proper abstraction) 3. Heavy features that affect offline performance (e.g., unnecessary high-resolution textures). 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 map services/UI components/data handlers), unit test coverage, and build process optimization for offline assets. Deduct 5 points if global state pollution is found or Cesium instances are not properly encapsulated; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if offline resources are not properly managed in the build process. 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 controls and UI elements 2) Proper layout spacing for control panels and information displays 3) Professional typography for labels and POIs (legible at various zoom levels). Deduct 3 points for each cluttered control group, 5 points for poor contrast between map and UI elements, and 5 points for illegible labels at standard zoom levels. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the map rendering performance optimized for offline use?",
-      "description": "Judge whether the implementation addresses performance concerns: 1) Efficient tile loading strategy for offline use 2) Proper level-of-detail management 3) Frame rate above 30fps during navigation. Deduct 5 points for noticeable stuttering during pan/zoom operations, 3 points for excessive memory usage leading to slowdowns, and 5 points for missing optimization techniques specific to Cesium (like entity clustering or fog). The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Web Visuals",
-  "difficulty": "medium"
-}

package/library/web_applications-web_visuals/vue3-cabinet-topology-diagram-demo.json

@@ -1,68 +0,0 @@
-{
-  "index": 294,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to ensure that the code you generate can be executed and demonstrated. Vue3 cabinet topology diagram demo",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the Vue3 cabinet topology diagram core rendering functionality fully implemented?",
-      "description": "Review whether the code accurately implements cabinet topology visualization using Vue3 composition API, including cabinet node rendering, connection line drawing, and interactive selection mechanisms. Score 0 if basic topology structure is not displayed, 5 if only static cabinet nodes are shown, and 10 if complete interactive topology with dynamic connections and real-time updates is implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the cabinet hierarchy and relationship management properly structured?",
-      "description": "Check whether the implementation includes proper data modeling for cabinet relationships (parent-child, peer connections), supports multi-level topology nesting, and provides real-time topology state management. Deduct 5 points if cabinet relationship data structure is poorly designed, and 3 points if topology updates don't reflect in real-time. Full score requires complete hierarchy management with bidirectional relationship tracking.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are cabinet interaction features and operations comprehensively implemented?",
-      "description": "Evaluate whether the topology supports essential cabinet operations including drag-and-drop positioning, zoom in/out functionality, cabinet detail inspection, and connection line management. Two-way data binding between cabinet properties and visual representation is required. Deduct 5 points if drag-and-drop is not smooth, and 3 points if zoom operations cause layout distortion.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the topology layout algorithm and responsive design optimized?",
-      "description": "Check whether the code implements intelligent cabinet positioning algorithms (such as force-directed layout or hierarchical layout), supports automatic layout adjustment, and provides responsive design for different screen sizes. Deduct 5 points if cabinet overlapping occurs frequently, and 3 points if mobile compatibility is poor. Full score requires adaptive layout with collision avoidance.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid cabinet data, network interruption, large dataset rendering, browser compatibility issues, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should effectively handle edge cases including empty data states and performance degradation scenarios, 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 any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the topology experience (e.g., 1. Real-time cabinet status monitoring with color coding 2. Cabinet path finding and route highlighting 3. Interactive cabinet grouping and filtering 4. Export topology as image/PDF 5. Cabinet search and auto-navigation). 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 topology functions (e.g., multiple layout algorithms running simultaneously) 2. Function modules unrelated to cabinet topology (e.g., built-in chat system) 3. Fancy effects that affect topology performance (e.g., excessive particle animations on connections). Deduct 3 points for each redundancy found, and directly deduct 10 points if core topology functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review Vue3 best practices including proper composition API usage, component modularity (topology view/data layer/interaction layer separation), TypeScript integration, and build process optimization. Deduct 5 points if reactive data management is poorly implemented or Vue3 patterns are not followed; deduct 5 points if component reusability is low (over 30% code duplication); deduct 5 points if build configuration lacks optimization. Full score requires professional Vue3 architecture.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the topology visual design meet professional standards?",
-      "description": "Evaluate whether the topology design follows modern UI principles: 1) Consistent cabinet node styling with clear visual hierarchy 2) Appropriate color coding for different cabinet types/states (maximum 5 primary colors) 3) Professional typography for labels and annotations (minimum 12px font size) 4) Proper spacing and alignment following grid principles. Deduct 3 points for each visual inconsistency, 5 points for poor color contrast or accessibility issues, and 5 points for cluttered layout affecting readability.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the topology interaction smooth and seamless?",
-      "description": "Judge whether the topology interactions conform to user experience standards: 1) Cabinet selection feedback delay ≤ 100ms 2) Smooth pan/zoom operations with proper easing (300-500ms transitions) 3) Clear visual feedback for hover states and active selections 4) Intuitive connection line rendering without performance lag. Deduct 5 points for each laggy interaction, 3 points for unclear visual states during operations, and 5 points for difficult-to-access topology controls or navigation.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Web Visuals",
-  "difficulty": "hard"
-}

package/library/web_applications-web_visuals/vue3-categorized-video-platform-with-upload.json

@@ -1,68 +0,0 @@
-{
-  "index": 821,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. I am a code expert. Please let me use my professional knowledge to generate accurate and professional responses. I'll make sure the code I provide is executable. Can you help me create a website that can preview videos? The website should include directory categories, where users can view video lists under each category and click to watch videos. It should also have video upload functionality. The directory categories are created by administrators, while others can upload and preview videos. Let's use the Vue3.js framework for the frontend.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the Vue3 application structure properly implemented?",
-      "description": "Examine whether the code correctly implements Vue3 component architecture, including proper use of Composition API, reactive state management, and component lifecycle hooks. Check for proper directory structure (views, components, services, etc.). Score 0 if Vue3 is not used, 5 if basic implementation exists but lacks optimization, and 10 if fully implements Vue3 best practices including proper component composition and script setup syntax.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the video category directory system fully implemented?",
-      "description": "Verify that the directory category system supports hierarchical structure, proper navigation between categories, and displays category-specific video lists. Check for admin-only category management features (create, edit, delete, reorder). Deduct 5 points if the hierarchy is limited to one level, 3 points if search/filter functionality within categories is missing, and 5 points if category metadata (description, thumbnail, etc.) is not supported. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the video preview functionality properly implemented?",
-      "description": "Evaluate whether the video player component includes essential features like play/pause, volume control, progress bar, full screen, and playback speed. Check for preview thumbnails on hover, custom video controls, and adaptive bitrate streaming support. Deduct 5 points if the player lacks responsive design, 5 points if it doesn't handle different video formats, and 3 points if it doesn't support keyboard shortcuts. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the video upload function complete and secure?",
-      "description": "Assess whether the upload functionality includes progress indicators, file type validation, size limitations, chunk upload for large files, and proper error handling. Check for security features like MIME type verification and virus scanning integration. Deduct 5 points if resume upload capability is missing, 5 points if preview generation doesn't happen during upload, and 3 points if metadata editing (title, description, tags) is not available. 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 network interruption, video loading failures, invalid file uploads, 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-powered video recommendations 2. Automated video chaptering 3. Interactive comments with timestamps 4. Picture-in-picture mode while browsing). 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 video players coexisting) 2. Function modules unrelated to video preview/upload (e.g., a built-in game) 3. Fancy effects that affect performance (e.g., excessive animations during browsing). 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 API/state/view layers), unit test coverage, and build process automation. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the build process is not automated. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching (no more than 3 primary colors) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional font system (body font size ≥ 14px, line height over 1.5 times). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic text-image layout. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Click feedback delay ≤ 100ms 2) Transition animation duration controlled between 300-500ms 3) Clear visual focus guidance. Deduct 5 points for each operation without feedback, 3 points for visual after-images during fast scrolling of video lists, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Web Visuals",
-  "difficulty": "hard"
-}

package/library/web_applications-web_visuals/vue3-creating-openlayers.json

@@ -1,68 +0,0 @@
-{
-  "index": 863,
-  "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 purposes. Vue3 creating OpenLayers",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the OpenLayers map initialization fully implemented with Vue3?",
-      "description": "Check if the code properly initializes an OpenLayers map within the Vue3 component lifecycle (mounted/onMounted). Verify that the map instance is correctly created with proper viewport size, initial center coordinates, and zoom level. The map should be properly destroyed when the component is unmounted. Score 0 if map initialization is missing, 5 if basic initialization exists but lacks proper lifecycle management, and 10 if fully implemented with reactive properties.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are Vue3 Composition API features properly utilized for OpenLayers integration?",
-      "description": "Evaluate whether the code makes appropriate use of Vue3's Composition API (ref, reactive, computed, watch) to manage OpenLayers objects and their states. Check for proper reactive wrappers around map objects, map layers, and map controls. Deduct 5 points if only Options API is used, deduct 3 points if reactivity is not properly implemented with map state changes. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is there a comprehensive layer management system implemented?",
-      "description": "Review if the code implements a flexible layer management system that allows adding/removing different types of layers (Vector, Tile, WMS, etc.). Check if layer visibility and properties can be controlled reactively through Vue components. Deduct 5 points if only basic layers are implemented without customization options, deduct 3 points if layer management lacks reactivity. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Are OpenLayers events properly integrated with the Vue3 event system?",
-      "description": "Assess if OpenLayers events (click, pointermove, etc.) are properly connected to Vue3's event handling system. Check for proper event listeners setup and cleanup in component lifecycle hooks. Map interactions should update Vue reactive state, and Vue state changes should be reflected in the map. Deduct 5 points if events are not properly cleaned up, and deduct 3 points if there's no bidirectional synchronization. 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 failed map loading, layer loading errors, invalid coordinates, etc.) and provide friendly error prompts or recovery mechanisms. Check for proper null checks before accessing properties, try-catch blocks for error-prone operations, and graceful fallbacks. 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. Custom Vue3 composables for map features 2. Transition animations for layer switching 3. Integration with Vue3's Teleport for map controls). 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 OpenLayers functionality already available through API (e.g., reimplementing zoom controls) 2. Unnecessary wrapper components that add complexity without value 3. Heavy visual effects that impair map performance. Deduct 3 points for each redundancy found, and directly deduct 10 points if the core map functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (separation of map service, component logic, and UI elements), TypeScript usage for OpenLayers types, and proper project structure. Deduct 5 points if global state pollution is found; deduct 5 points if OpenLayers instances are not properly typed; deduct 5 points if the code lacks reusable composables for common map operations. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the map UI follows modern design principles: 1) Clean map controls with proper spacing and sizing 2) Consistent styling between Vue components and map elements 3) Responsive design that adapts to different viewport sizes. Deduct 3 points for each overlapping control element, 5 points for inconsistent styling between Vue components and map elements, and 5 points for non-responsive map layout. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the map interaction smooth and seamless?",
-      "description": "Judge whether the map interactions perform well: 1) Map pan/zoom operations respond within 100ms 2) Layer switching animations complete within 300-500ms 3) Clear visual feedback for user interactions with map features. Deduct 5 points for noticeable lag in map operations, 3 points for jerky animations during transitions, and 5 points if the map becomes unresponsive during data loading operations. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Web Visuals",
-  "difficulty": "medium"
-}

package/library/web_applications-web_visuals/vue3-element-ui-weather-app.json

@@ -1,68 +0,0 @@
-{
-  "index": 1217,
-  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Make sure to ensure that the code you generate is executable for demonstration. Please provide me with a free weather service application for a frontend using Vue 3 + Element UI JavaScript.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the weather service API integration complete and properly implemented?",
-      "description": "Check if the code includes appropriate API calls to a free weather service (such as OpenWeatherMap, WeatherAPI, etc.) with proper error handling and rate limiting considerations. The implementation should include API key management, proper request formatting, and response parsing. Deduct 5 points if error handling is missing, 3 points if there's no loading state during API calls, and 5 points if the API integration is incomplete. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Does the Vue 3 application properly utilize Composition API?",
-      "description": "Evaluate whether the implementation leverages Vue 3's Composition API effectively with reactive state management, computed properties, and lifecycle hooks. Check for proper use of ref(), reactive(), watch(), watchEffect(), and onMounted(). Deduct 3 points for using Options API instead of Composition API, 5 points for global state management issues, and 3 points for improper reactivity management. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is Element UI integration complete with appropriate weather visualization components?",
-      "description": "Review the implementation of Element UI components such as cards, sliders, dropdowns, and tables to display weather data. The components should be properly themed and responsive. Look for customized weather icons, temperature displays, and forecast layouts. Deduct 5 points if basic Element UI components aren't used, 3 points for inconsistent styling, and 5 points if the components aren't properly responsive. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Are key weather application features implemented and functional?",
-      "description": "Check if the application includes essential weather features: current conditions, forecasts (hourly and multi-day), location search/geolocation, unit conversion (°C/°F), and weather alerts if available. Deduct 3 points for each missing core feature, 2 points for incomplete implementation of features, and 5 points if the data 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 API failures, network interruption, invalid location inputs, 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. Weather-based theme adaptation 2. Historical weather data visualization 3. Weather alerts with push notifications 4. Weather impact on daily activities suggestions). 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 API calls for the same data 2. Function modules unrelated to weather (e.g., a built-in calculator) 3. Fancy effects that affect performance (e.g., excessive animations that slow down the interface). 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 API services, components, composables), proper folder structure, code comments, and build process setup. Deduct 5 points if global state management is poorly implemented; deduct 5 points if the code lacks reusable components; deduct 5 points if there is no proper build configuration or environment variable management. 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 weather app design principles: 1) Weather-appropriate color scheme (cool blues for rain, warm yellows for sun) 2) Proper layout spacing with responsive design 3) Professional typography for temperature and condition displays (clear temperature numbers ≥ 18px). Deduct 3 points for each cluttered section, 5 points for a visually jarring interface, and 5 points for poor information hierarchy. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the dynamic effects conform to modern web app standards: 1) Smooth location transitions 2) Responsive weather data updates 3) Intuitive interactions for changing views/settings. Deduct 5 points for laggy transitions between views, 3 points for jerky animations, and 5 points for confusing navigation patterns. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Web Visuals",
-  "difficulty": "easy"
-}

package/library/web_applications-web_visuals/vue3-openlayers-gcj02-tile-coordinate-display.json

@@ -1,68 +0,0 @@
-{
-  "index": 1480,
-  "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. Using vue3/ts/OpenLayers 10 + proj4js with the gcj02 coordinate system, load gcj02 tiles and display gcj02 coordinate points. Please provide a real, usable example with custom deployed tiles.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the Vue3/TypeScript setup properly configured?",
-      "description": "Verify that the project correctly sets up Vue3 with TypeScript, including proper tsconfig.json configuration, Vue SFCs with TypeScript, and proper type definitions. Check if the component structure follows Vue3 composition API best practices with proper setup() function or <script setup> syntax. Score 0 if Vue3/TS is not used, 5 if basic setup exists but with type issues, and 10 if properly configured with strict typing.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is OpenLayers 10 correctly integrated with the GCJ02 coordinate system?",
-      "description": "Evaluate whether OpenLayers is properly initialized and configured to work with the GCJ02 coordinate system. Check if the correct versions of dependencies are used (OpenLayers 10+). Verify that the map projection is properly set up and the transformation between coordinate systems is correctly implemented. Score 0 if OpenLayers is missing or incompatible version, 5 if basic integration exists but with projection issues, and 10 if fully functional with proper GCJ02 support.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is Proj4js correctly implemented for coordinate transformations?",
-      "description": "Check if proj4js is properly imported and configured with the correct definition for GCJ02. Verify that the transformation functions between different coordinate systems (e.g., WGS84, GCJ02) are implemented correctly. Test if coordinate conversions work accurately at different locations in China. Deduct 5 points if transformation accuracy is off by more than 2 meters, and 3 points if the proj4 definition is incomplete.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Are custom GCJ02 tiles properly loaded and displayed?",
-      "description": "Evaluate whether the code successfully loads and displays custom GCJ02 tiles. Check if the tile source is correctly configured with proper URL template, appropriate zoom levels, and tile size. Verify that the code includes configuration for a custom tile server deployment rather than just using public tile services. Deduct 5 points if tiles don't load properly, 3 points if zoom levels are improperly configured, and 5 points if no custom deployment example is provided.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as tile loading failures, network interruption, incorrect coordinate inputs, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Interactive coordinate conversion tool 2. Visual comparison between WGS84 and GCJ02 3. Performance optimization for tile loading). 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 ways to perform coordinate transformations) 2. Function modules unrelated to the mapping requirement (e.g., unnecessary UI components) 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 map services/UI components/coordinate utilities), type safety with TypeScript, and build process configuration. 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 properly configured for Vue3/TS. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the map UI follows modern design principles: 1) Clean control layout (zoom buttons, layer switchers, etc.) 2) Proper information hierarchy for displaying coordinates 3) Responsive design that works across device sizes. Deduct 3 points for each misaligned map control, 5 points for poorly contrasting markers against the map background, and 5 points for non-responsive layouts. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the map interaction smooth and seamless?",
-      "description": "Judge whether the map interactions conform to user expectations: 1) Responsive pan/zoom without lag (≤ 100ms) 2) Smooth transitions when changing layers or zoom levels 3) Clear visual feedback when selecting points or features. Deduct 5 points for jerky map movements, 3 points for delayed tile loading without placeholders, and 5 points for unresponsive point clicking. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Web Visuals",
-  "difficulty": "hard"
-}