@getollie/cli 0.0.1

package/library/web_applications-web_visuals/rural-courtyard-six-bedrooms-html-design.json

@@ -0,0 +1,68 @@
+{
+  "index": 1776,
+  "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 display. Design a rural courtyard with six bedrooms, two living rooms, and one kitchen, and draw it using HTML.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the rural courtyard layout completely implemented?",
+      "description": "Verify whether the HTML code properly implements the required layout with six bedrooms, two living rooms, and one kitchen in a rural courtyard style. Score 0 if the core layout is missing elements, 5 if all required rooms are present but poorly arranged, and 10 if the layout is complete and logically arranged in a courtyard formation.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the architectural structure accurately represented?",
+      "description": "Examine whether the courtyard design includes appropriate structural elements (walls, doors, windows, roofs) with correct proportions and rural characteristics. Deduct 3 points if structural elements are missing, 3 points if proportions are unrealistic, and 4 points if the rural style is not evident. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Are the room relationships and connections logically designed?",
+      "description": "Evaluate whether the connections between rooms make architectural sense (e.g., bedrooms with proper privacy, kitchen accessible from living areas, logical doorways and pathways). Deduct 5 points for illogical room arrangements, 3 points for missing critical pathways, and 2 points for poor flow between spaces. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the courtyard component appropriately incorporated?",
+      "description": "Check if the design includes a proper courtyard element that integrates well with the building structure in rural style. Deduct 5 points if the courtyard is missing or poorly defined, 3 points if it lacks rural characteristics, and 2 points if its relationship with surrounding rooms is poorly conceived. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle different screen sizes, browser compatibility issues, and ensures proper rendering across devices. Code with strong robustness should use responsive design principles and fallback options, giving 10 points. If the robustness is average with partial responsiveness, give 5 points, and if the design breaks on different screen sizes, 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 room exploration 2. Day/night lighting simulation 3. Rural-appropriate decorative elements). 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 HTML elements or CSS styles that serve the same purpose 2. Excessive decorative elements that distract from the main layout 3. Fancy effects that affect loading performance. Deduct 3 points for each redundancy found, and directly deduct 10 points if the core layout is interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review HTML structure (semantic HTML usage), CSS organization (systematic class naming, separation of concerns), and code maintainability. Deduct 5 points if non-semantic div-soup is prevalent; deduct 5 points if styles are inline rather than properly organized; deduct 5 points if the code lacks comments or organization. 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 appropriate for a rural setting 2) Proper layout proportions reflecting architectural reality 3) Consistent visual style throughout the courtyard. Deduct 3 points for jarring visual elements, 5 points for unrealistic architectural representations, and 5 points for inconsistent visual styling. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the visual representation clear and intuitive?",
+      "description": "Judge whether the visual representation clearly communicates the rural courtyard design: 1) Clear distinction between different room types 2) Intuitive understanding of the floor plan 3) Visual hierarchy that prioritizes important elements. Deduct 5 points for confusing room identification, 3 points for unclear boundaries between spaces, and 5 points for poor visual differentiation of architectural elements. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Web Visuals",
+  "difficulty": "medium"
+}

package/library/web_applications-web_visuals/traffic-light-web-interface.json

@@ -0,0 +1,68 @@
+{
+  "index": 992,
+  "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. You only need to create a simple web interface that can display traffic light timing, vehicle speed, and video.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the traffic light timing system fully implemented?",
+      "description": "Review whether the code accurately implements traffic light state management with proper timing sequences (red/yellow/green cycles). Check if the timing display shows countdown or elapsed time, and whether the light transitions follow realistic traffic patterns. Score 0 if no timing logic is implemented, 5 if only basic color switching exists, and 10 if complete timing control with configurable intervals is included.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the vehicle speed monitoring functionality implemented?",
+      "description": "Check whether the speed display includes real-time updates, proper unit conversion (mph/kmh), and realistic speed simulation or input mechanisms. Evaluate if speed data is presented clearly with appropriate formatting and decimal precision. Deduct 5 points if speed updates are jerky or unrealistic, and 3 points if unit display is unclear. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the video display component properly integrated?",
+      "description": "Evaluate whether the video element is properly embedded with standard HTML5 video controls, appropriate sizing, and fallback mechanisms for unsupported formats. Check if video loading states are handled gracefully and if the video integrates well with other interface elements. Deduct 5 points if video fails to load or has no error handling, and 3 points if controls are poorly positioned. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the integrated traffic monitoring interface cohesive?",
+      "description": "Check whether all three components (traffic light, speed display, video) work together as a unified traffic monitoring system. Evaluate if the interface provides logical grouping, consistent data refresh rates, and synchronized updates. Deduct 5 points if components appear disconnected or have conflicting update cycles, and 3 points if the overall system lacks coherent workflow. Give 10 points if fully integrated with cross-component interactions.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as video loading failures, invalid speed values, timing interruptions, 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 traffic monitoring experience (e.g., 1. Speed limit violation alerts 2. Traffic flow statistics 3. Emergency mode with flashing lights 4. Historical data charts). 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 timer mechanisms coexisting) 2. Function modules unrelated to traffic monitoring (e.g., a built-in music player or social features) 3. Fancy effects that affect performance (e.g., excessive particle animations on traffic lights). 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 traffic light logic/speed monitoring/video handling), proper variable naming, and code organization. Deduct 5 points if global state pollution is found or no separation of concerns; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if no proper event handling or DOM manipulation patterns are used. 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 UI principles: 1) Harmonious color matching with appropriate traffic light colors 2) Proper layout spacing with clear visual hierarchy 3) Professional typography with readable font sizes (≥14px) and appropriate contrast ratios. Deduct 3 points for each crowded visual element, 5 points for poor color contrast or confusing traffic light representation, and 5 points for chaotic 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 user expectations: 1) Traffic light transitions are smooth with appropriate timing 2) Speed updates are fluid without jarring jumps 3) Video controls respond immediately to user input 4) Overall interface updates are synchronized and performant. Deduct 5 points for each laggy interaction, 3 points for choppy animations, and 5 points for unresponsive controls. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Web Visuals",
+  "difficulty": "easy"
+}

package/library/web_applications-web_visuals/unity-cloud-rendering-html-interaction.json

@@ -0,0 +1,68 @@
+{
+  "index": 772,
+  "question": "You are a code expert. Please utilize your professional knowledge to generate accurate and professional responses. Be sure to provide executable code for demonstration. Help me write an HTML page where I need to embed a Unity cloud rendering URL and interact with it.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the HTML page correctly structured for embedding a Unity WebGL application?",
+      "description": "Check whether the HTML document has proper DOCTYPE declaration, meta tags, and follows HTML5 standards. Verify if the Unity iframe or container div is structured correctly with appropriate dimensions and responsive design considerations. Deduct 5 points if responsive design is missing, 3 points if incomplete meta tags, and 2 points if semantic HTML elements are not used. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the Unity cloud rendering URL properly integrated?",
+      "description": "Evaluate whether the code uses the correct embedding technique (iframe, WebGL container, etc.) for the Unity cloud rendering URL. Check for proper URL handling, loading states, and error handling when the Unity content is unavailable. Deduct 5 points if the embedding approach is incorrect, 3 points if loading indicators are missing, and 2 points if error states aren't handled. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the communication between HTML and Unity implemented?",
+      "description": "Review whether the code includes proper JavaScript bridge functions for bi-directional communication between the webpage and Unity application. Check if the implementation uses standard Unity external call patterns (e.g., SendMessage, JSLib) and properly handles asynchronous messaging. Deduct 5 points if bidirectional communication is missing, 3 points if event listeners are improperly implemented, and 2 points if security considerations are ignored. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Are the Unity interaction controls well-designed?",
+      "description": "Assess whether external UI controls for Unity interaction are implemented (like buttons, sliders, input fields) that can trigger actions in the Unity application. Check if the controls follow a consistent design pattern and provide visual feedback when interacting with Unity. Deduct 3 points if controls are inconsistently designed, 5 points if there's no visual feedback for interactions, and 2 points if control labeling is unclear. 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 Unity failing to load, network interruptions, browser compatibility issues, etc.) and provides 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. Custom loading animations while Unity initializes 2. Fullscreen toggle with proper UI adaptation 3. Performance monitoring with visual indicators). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple ways to perform the same Unity interaction) 2. Function modules unrelated to Unity integration (e.g., unnecessary animations or effects) 3. Fancy effects that affect performance (e.g., heavy background animations competing with Unity 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 UI logic/Unity communication/error handling), maintainability, and documentation quality. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 3 points if the code duplication rate is too high (over 30%); deduct 2 points if comments and documentation are insufficient. 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 between HTML UI and Unity content 2) Proper layout with clear separation between controls and Unity viewport 3) Professional font system and consistent styling. 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 for Unity communication 2) Proper loading and transition states when interacting with Unity 3) Clear visual guidance for available interactions. Deduct 5 points for each operation without feedback, 3 points for delayed Unity responses without indicators, and 5 points for confusing interaction patterns. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Web Visuals",
+  "difficulty": "easy"
+}

package/library/web_applications-web_visuals/vue-3-amap-autonavi-3d-map-building-blocks.json

@@ -0,0 +1,68 @@
+{
+  "index": 1346,
+  "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. Implement Amap (AutoNavi) API using Vue 3 to create a 3D map and draw building blocks.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the Vue 3 application structure correctly set up?",
+      "description": "Check if the code properly initializes a Vue 3 application with appropriate component architecture. Verify the presence of Vue 3 specific features like Composition API, proper lifecycle hooks, and reactive data management. Score 0 if Vue 3 is not used, 5 if basic implementation exists but with improper structure, and 10 if properly structured with clean component design patterns.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the Amap (AutoNavi) API integration complete?",
+      "description": "Assess whether the Amap API is correctly loaded, initialized with valid keys, and properly integrated. Check for error handling in API loading process and key validation. Deduct 5 points if the API key management is insecure, 3 points if version compatibility issues exist. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the 3D map functionality properly implemented?",
+      "description": "Evaluate if the code correctly initializes a 3D map view with proper view settings (pitch, rotation, zoom levels). Check if the 3D buildings layer is enabled and correctly configured. Score 0 if 3D view is missing, 5 if basic 3D functionality exists but with incorrect parameters, and 10 if fully implemented with optimized 3D rendering settings.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the building block drawing functionality complete?",
+      "description": "Verify if the code includes methods to draw custom building blocks with appropriate geometry (polygons, extrusions), proper height calculations, and styling options. Check if it includes options for custom colors, textures and opacity. Deduct 5 points if custom building geometry lacks precision, 5 points if height calculations are not dynamic or configurable. 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 loading failures, invalid coordinates, rendering 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. Dynamic building highlighting on hover 2. Custom building information popups 3. Animation of building creation/modification). 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 initializations or map instances 2. Unnecessary feature loading unrelated to 3D buildings or map functionality 3. Excessive effects that impact map performance. 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 handling), component reusability, and performance optimization techniques. Deduct 5 points if global state pollution is found; deduct 5 points if the code lacks proper documentation for API parameters; deduct 5 points if there's no optimization for large building datasets. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the map visualization follows modern design principles: 1) Appropriate map style selection for 3D buildings 2) Clean UI controls for map navigation 3) Professional color scheme for building representation (avoiding visual clutter). Deduct 3 points for cluttered controls, 5 points for poor color contrast between buildings and base map, and 5 points for illegible labels or building information. 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) Smooth camera transitions during navigation ≤ 500ms 2) Responsive building selection and information display ≤ 100ms 3) Efficient rendering during zoom/pan operations without jank. Deduct 5 points for laggy camera movements, 3 points for delayed building highlighting, and 5 points for freezes during building data updates. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Web Visuals",
+  "difficulty": "easy"
+}

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

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

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

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

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