@getollie/cli 0.0.5 → 0.2.0

package/library/web_applications-web_visuals/homepage-spinning-animation-loading-popup.json

@@ -1,68 +0,0 @@
-{
-  "index": 1528,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Ensure that the code you generate is executable when possible. I want to design a homepage where there's a popup window in the center of the screen with a spinning animation when it loads, including a prompt that says \"Loading...",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the popup window implementation complete?",
-      "description": "Review whether the code correctly positions a popup window in the center of the screen using proper CSS positioning techniques (absolute positioning with top/left 50% and transform translate). Check if the window has proper styling (borders, background, shadow effects) and is responsive on different screen sizes. Score 0 if no popup is implemented, 5 if it's basic but fixed-size, and 10 if it's fully responsive and properly styled.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the spinning animation correctly implemented?",
-      "description": "Evaluate the spinning animation implementation - check for CSS animation/transition properties with keyframes or JavaScript-based animation. The animation should be smooth (60fps), have appropriate duration (1-3s per rotation), and proper easing. Animations should use hardware acceleration (transform instead of position changes). Deduct 5 points if the animation is jerky, 3 points if it lacks easing, and 2 points if it's CPU-intensive.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the 'Loading...' prompt properly displayed?",
-      "description": "Check if the loading text is visible, properly formatted, and positioned relative to the spinner. Text should have sufficient contrast ratio (minimum 4.5:1), appropriate font size (16px+), and should indicate loading progress clearly. Deduct 5 points if the text is hard to read, 3 points if poorly positioned relative to the spinner, and 2 points if it doesn't visually connect with the loading action.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is there a proper loading state management?",
-      "description": "Verify if the code includes logic to display the loading popup during actual loading operations (fetch requests, large asset loading) and properly hides it when loading completes. Check for timeout handling (showing error message after excessive loading time), ability to cancel loading, and smooth transition when loading completes. Give 10 points for comprehensive loading state management, 5 for basic show/hide functionality, and 0 if no real loading logic exists.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as slow network, missing assets, script 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. Progressive loading indicators 2. Customized themed spinner 3. Subtle background animations during 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 animations (e.g., multiple spinners running simultaneously) 2. Unnecessary decorative elements that distract from the loading state 3. Heavy effects that affect performance (e.g., complex particle effects during loading). 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 components/animation logic/loading state management), code reusability, and performance optimization. Deduct 5 points if global scope pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if no performance considerations exist (like requestAnimationFrame for animations). 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) Animation timing appears natural (not too fast or slow) 2) Transition between loading and loaded states is smooth without jarring changes 3) Visual hierarchy guides user attention appropriately. Deduct 5 points for abrupt appearance/disappearance without transitions, 3 points for animations that cause layout shifts, and 5 points for distracting animations that compete with the main content. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Web Visuals",
-  "difficulty": "easy"
-}

package/library/web_applications-web_visuals/horror-game-official-website-html.json

@@ -1,68 +0,0 @@
-{
-  "index": 1162,
-  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable for display. Create an HTML code for a horror game official website with 2000 lines of code, including customer service information on the right side that can be collapsed/expanded, download links, game introduction, image showcase, a horror website background, scary background music, and dynamic background effects.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the horror game official website structure fully implemented?",
-      "description": "Review whether the HTML code implements a complete website structure with proper semantic HTML5 tags (header, nav, main, footer), responsive layout (using CSS Grid/Flexbox), and organized sections for all required components (game intro, image showcase, download links, etc). Score 0 if basic structure is missing, 5 if structure exists but with improper semantics, and 10 if properly structured with semantic HTML.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the customer service feature implemented as specified?",
-      "description": "Check whether the collapsible/expandable customer service component is fully functional on the right side of the website. It should include proper animation transitions, accessibility features (ARIA attributes, keyboard navigation), and contact information. Deduct 5 points if the component doesn't collapse/expand properly, 3 points if it lacks responsive behavior on mobile devices. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are the dynamic horror background effects properly implemented?",
-      "description": "Evaluate the quality and performance of background effects. Check for WebGL/Canvas/CSS animations that create horror atmosphere (fog, flickering lights, floating elements, etc.). Effects should be optimized for performance (using requestAnimationFrame, proper canvas rendering). Deduct 5 points if effects cause visible performance issues, 3 points if animations are basic/generic. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the scary background music functionality properly implemented?",
-      "description": "Check whether the audio implementation includes: auto-play with user consent mechanism, volume control, mute option, and proper looping without gaps. Audio should preload for seamless playback and include fallback formats. Deduct 5 points if audio controls are missing, 3 points if there's no user consent mechanism for autoplay, and 5 points if mobile implementation is broken. 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 image loading failures, audio playback issues, browser compatibility issues, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Interactive horror elements that respond to user actions 2. Randomized jumpscares or events 3. Parallax scrolling with horror themes). 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 animation systems doing the same thing) 2. Function modules unrelated to a horror game website (e.g., unrelated social media features) 3. Fancy effects that affect performance (e.g., excessive particle effects that slow down the page). 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 structure/styles/scripts), code organization, use of appropriate design patterns, and browser compatibility. Deduct 5 points if global scope pollution is found; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there's no progressive enhancement or graceful degradation for older browsers. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional horror design standards?",
-      "description": "Evaluate whether the overall design follows horror genre design principles: 1) Dark color scheme with appropriate accent colors for emphasis 2) Typography that enhances the horror theme (gothic/distressed fonts for headings, readable fonts for content) 3) Proper use of negative space to create tension. Deduct 3 points for each visual element that breaks the horror atmosphere, 5 points for overly bright/cheerful color combinations, and 5 points for cluttered layouts that diminish the horror experience. 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 horror genre expectations: 1) Subtle hover effects that create unease 2) Transition animations that build suspense (300-800ms duration) 3) Clear visual hierarchy guiding users to key elements. Deduct 5 points for each interaction without appropriate feedback, 3 points for animations that break immersion, and 5 points for confusing navigation that frustrates users. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Web Visuals",
-  "difficulty": "easy"
-}

package/library/web_applications-web_visuals/html-3d-street-view-renderer.json

@@ -1,68 +0,0 @@
-{
-  "index": 278,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate, professional responses. Make sure that the code you generate is executable for demonstration purposes. Help me write an HTML that can render a 3D street view.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the 3D street view rendering system properly implemented?",
-      "description": "Check if the code properly implements a 3D street view using appropriate technology (WebGL, Three.js, Babylon.js, etc.). Evaluate if it includes camera controls, perspective projection, and proper scene setup. Score 0 if no 3D rendering is implemented, 5 if basic scene rendering is present, and 10 if a complete street environment with proper depth and perspective is achieved.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are interactive navigation controls implemented?",
-      "description": "Verify if the code includes intuitive navigation controls (pan, tilt, zoom, street movement) with keyboard/mouse/touch support. Check for smooth camera transitions between positions and proper collision detection to prevent going through buildings/objects. Deduct 5 points if navigation is limited to basic rotation only, 3 points if movement feels jerky or unnatural. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Does the street view include realistic environment elements?",
-      "description": "Evaluate the presence and quality of urban environment elements (buildings, roads, sidewalks, street furniture, vehicles, etc.). Check if textures are properly applied and if lighting creates realistic shadows. Deduct 3 points for missing essential street elements, 5 points for unrealistic textures, and 3 points for poor lighting implementation. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is performance optimization implemented for 3D rendering?",
-      "description": "Assess whether the code includes optimization techniques like level-of-detail rendering, texture compression, object instancing, frustum culling, or occlusion culling. Check for frame rate stability during navigation. Deduct 5 points if frame rate drops below 30fps on standard hardware, 3 points if no asset loading strategies are implemented. 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 WebGL not supported, texture loading failures, window resizing, 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 time-of-day lighting 2. Weather effects like rain or snow 3. Interactive storefronts or landmarks 4. Procedurally generated building facades). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple camera control systems) 2. Function modules unrelated to street view (e.g., a built-in mini-game) 3. Fancy effects that affect performance (e.g., excessive particle systems or post-processing effects). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating 3D rendering/controls/asset management layers), code organization, 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 shader code is mixed with application logic. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the UI overlay elements follow 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) Clear navigation indicators and controls. Deduct 3 points for each cluttered UI element, 5 points for poor contrast between UI and 3D scene, and 5 points for control elements that block the view. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the 3D navigation conforms to human perception characteristics: 1) Camera movement inertia feels natural 2) Transition animations between positions last 300-500ms 3) Movement speed is appropriate for exploring a street. Deduct 5 points for jerky camera movements, 3 points for disorienting rotations or transitions, and 5 points for navigation controls that are difficult to use. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Web Visuals",
-  "difficulty": "easy"
-}

package/library/web_applications-web_visuals/html-button-new-page-esp32-arduino.json

@@ -1,68 +0,0 @@
-{
-  "index": 1588,
-  "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 when possible. I am using Arduino IDE to develop for ESP32. I want to develop an HTML page with a button in the middle. When the button is clicked, it should open a new page. When opening the page, it should call function A(), and when closing the page, it should call function B().",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the HTML page correctly structured with a centered button?",
-      "description": "Examine if the HTML document has proper DOCTYPE, head, body sections, and if the button is accurately centered using CSS (flex, grid, or absolute positioning). Button should be properly styled with appropriate size (at least 44x44px for touch targets), contrast ratio (at least 4.5:1 for AA compliance), and hover/active states. Deduct 5 points if button styling is minimal or non-existent, 3 points if centering is approximate rather than precise. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the navigation functionality properly implemented?",
-      "description": "Check if the button click handler correctly navigates to a new page using appropriate methods (window.location, <a> tag with href, or history API). Assess whether the navigation maintains proper browser history state. Deduct 5 points if navigation occurs but breaks browser back button functionality, 7 points if navigation is implemented incorrectly or incompletely. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are functions A() and B() correctly implemented and called at appropriate lifecycle events?",
-      "description": "Verify that function A() is properly called when the new page loads (using window.onload, DOMContentLoaded, or equivalent ESP32 approach) and function B() is called when closing/navigating away (using beforeunload, pagehide, or equivalent). Examine if both functions are defined with proper scoping. Deduct 5 points if only one function works correctly, 10 points if neither function works. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the ESP32 integration correctly implemented?",
-      "description": "Evaluate whether the code includes proper ESP32 server setup using ESP32WebServer or equivalent library. Check if the HTML is served correctly from SPIFFS or embedded strings, and if any required ESP32-specific configurations are present (like CORS settings for local development). Deduct 5 points if the implementation works but has inefficient memory usage patterns for an embedded system, 10 points if ESP32 integration is missing or fundamentally flawed. 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, page reload, rapid button clicking, etc.) and provide friendly error handling. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Smooth transition animations between pages 2. Persistent state management across navigation 3. Offline functionality with service workers). 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 event listeners or multiple ways to trigger the same action 2. Unnecessary libraries or frameworks for a simple ESP32 application 3. Overly complex solutions for simple requirements that may impact ESP32 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 HTML/CSS/JS, using appropriate ESP32 file structure), error handling, and code readability. Deduct 5 points if global scope is polluted; deduct 5 points if the code is not optimized for ESP32's memory constraints; deduct 5 points if variable/function naming is unclear. 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 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 jarring transitions, and 5 points for unclear interactive elements. Consider ESP32's processing limitations when evaluating animation smoothness. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Web Visuals",
-  "difficulty": "easy"
-}

package/library/web_applications-web_visuals/html-code-minecraft-theme.json

@@ -1,68 +0,0 @@
-{
-  "index": 1046,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate, professional responses. Be sure to provide executable code for demonstration whenever possible. Help me create an HTML code with the theme of Minecraft.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the Minecraft visual style accurately reproduced?",
-      "description": "Review whether the HTML/CSS implementation accurately captures the distinctive blocky, pixelated aesthetic of Minecraft. Score 0 if there's no visual resemblance to Minecraft, 5 if basic blocky elements are present but lack authenticity, and 10 if the implementation convincingly recreates the game's iconic visual style including textures, colors, and proportions.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are Minecraft-specific elements included?",
-      "description": "Evaluate the presence of recognizable Minecraft elements such as blocks (dirt, stone, wood), characters (Steve, creepers, endermen), items (pickaxe, sword), or environments (biomes). Score 3 points for each category of elements properly implemented (blocks, characters, items, environments) with a maximum of 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is there any interactive functionality that reflects Minecraft gameplay?",
-      "description": "Check whether the implementation includes interactive elements like block placement/breaking, character movement, crafting mechanics, or day/night cycles. Award 3 points for each interactive Minecraft-like feature that works properly, with basic interaction receiving 5 points and complex gameplay mechanics earning the full 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the Minecraft audio experience incorporated?",
-      "description": "Assess whether the code implements Minecraft-style sound effects (block breaking sounds, background music, mob noises) or music that enhances the Minecraft theme. Score 0 if no audio is included, 5 if basic sound effects are implemented, and 10 if there's a comprehensive audio experience that authentically reproduces the Minecraft soundscape.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as window resizing, different screen sizes, browser compatibility issues) and provide appropriate 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. Procedural terrain generation 2. Weather effects 3. Mob AI simulation). 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 render the same block type) 2. Function modules unrelated to Minecraft (e.g., non-thematic elements) 3. Fancy effects that affect performance (e.g., excessive particle systems). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core Minecraft theme is 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 from game mechanics), code organization, and performance optimization. Deduct 5 points if global variable pollution is found; deduct 5 points if the code is not organized into logical components; deduct 5 points if there are significant performance issues. 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 while maintaining Minecraft aesthetics: 1) Faithful color palette matching the game 2) Proper layout spacing for UI elements 3) Consistent pixelated styling. Deduct 3 points for each inconsistently styled element, 5 points for colors that don't match Minecraft's palette, and 5 points for mixing pixel art with high-resolution elements. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether any animations or transitions feel appropriate to Minecraft: 1) Block breaking/placement animations 2) Character movement fluidity 3) UI responsiveness. Deduct 5 points for each choppy animation, 3 points for inconsistent movement speed, and 5 points for laggy interactions. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Web Visuals",
-  "difficulty": "medium"
-}

package/library/web_applications-web_visuals/html-display-local-media.json

@@ -1,68 +0,0 @@
-{
-  "index": 1434,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable and can be displayed. Help me write a web page code for a local HTML file that will display all image and video files from a folder located in the same directory as the HTML file when opened.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the local file system access implementation correct?",
-      "description": "Evaluate whether the code properly implements the File System Access API or an alternative method to access local files. Check if it handles browser security restrictions correctly. Score 0 if no file system access is implemented, 5 if basic access is implemented but with limitations, and 10 if it handles all edge cases including file permissions and browser compatibility.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Does the file filtering mechanism work correctly?",
-      "description": "Check if the code correctly identifies and filters image and video files by extension or MIME types. It should recognize common formats (JPG, PNG, GIF, WebP, MP4, WebM, etc.). Deduct 3 points if some common formats are missing, 5 points if the filtering logic has errors, and 7 points if there's no filtering at all.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the gallery rendering implementation complete?",
-      "description": "Evaluate whether the code properly renders the discovered files in a gallery format. Check for proper image/video element creation, source setting, and container organization. Deduct 5 points if media doesn't display correctly, 3 points if there are rendering issues with certain file types, and 2 points if the display logic isn't optimized.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is there proper error handling and user feedback?",
-      "description": "Assess whether the code includes comprehensive error handling for cases like permission denied, unsupported files, or empty directories. Check if clear feedback is provided to users when issues occur. Deduct 5 points if critical errors aren't handled, 3 points if error messages are unclear, and 2 points if minor edge cases are unhandled.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid file formats, large files, many files, 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. Thumbnail generation 2. Sorting options 3. Lightbox preview 4. Lazy loading for better performance). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple file loading methods) 2. Function modules unrelated to file display (e.g., a built-in editing tool) 3. Fancy effects that affect performance (e.g., unnecessary animations). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating file access/rendering/UI components), code organization, and maintainability. Deduct 5 points if global scope pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there's no clear separation of concerns. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the 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 gallery design (consistent thumbnail sizes, proper margins). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic media 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) Image loading indicators 2) Smooth transitions when browsing through media 3) Clear visual feedback for user actions. Deduct 5 points for each operation without feedback, 3 points for jarring transitions between media items, and 5 points for unresponsive UI when loading large files. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Management Systems-File Management",
-  "difficulty": "easy"
-}

package/library/web_applications-web_visuals/html-iphone-image-video-viewer-interface.json

@@ -1,68 +0,0 @@
-{
-  "index": 1437,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure that the code you generate is executable for demonstration. HTML code to simulate iPhone interface for viewing images or videos - source code",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Does the simulated iPhone interface accurately mimic the real iOS design?",
-      "description": "Evaluate if the interface includes key iPhone elements (status bar, home indicator, correct screen dimensions). Check if it uses accurate iOS design system (SF Pro font, iOS color palette, correct corner radius). Score 0 if it looks nothing like iOS, 5 if it has basic resemblance, 10 if it's nearly indistinguishable from real iOS.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the image/video viewing functionality properly implemented?",
-      "description": "Check if the code provides smooth viewing experience with proper loading states and error handling. Evaluate support for both images and videos with appropriate format compatibility (JPEG, PNG, MP4, WebM). Test for zoom/pinch functionality and rotation support. Deduct 5 points if missing video support, 3 points if missing zoom functionality, 5 points if lacking proper media controls.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are iOS-specific gestures and interactions implemented?",
-      "description": "Review implementation of standard iOS photo/video viewing gestures: pinch-to-zoom, swipe-to-dismiss, double-tap to zoom in/out, swipe between media items. Test for smooth animations with proper physics (deceleration, bounce effects). Score 0 if no gesture support, 5 if basic gestures work, 10 if all gestures work with proper iOS-like physics.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the media gallery functionality robust and complete?",
-      "description": "Evaluate if the code includes gallery view with thumbnails, transitions between gallery/detail views, proper handling of portrait/landscape orientations. Check if it includes media metadata display, sharing options, and deletion functionality. Deduct 3 points for missing transitions, 3 points for poor orientation support, 4 points for missing metadata/actions.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as broken image links, unsupported media formats, network issues during loading, touch events on non-touchscreen devices). 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. Live Photo support with force touch simulation 2. Memory-efficient lazy loading of high-resolution images 3. Custom filters or editing tools 4. Intelligent face detection for improved cropping). 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 image loading libraries coexisting) 2. Function modules unrelated to image/video viewing (e.g., unnecessary social media integration) 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 UI/logic/data layers), code reusability, and performance optimization. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there are no performance optimizations for image/video loading. 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 iOS design principles: 1) Consistent color matching with iOS system colors 2) Proper layout spacing according to iOS guidelines 3) Correct typography using SF Pro font family. Deduct 3 points for each non-iOS visual element, 5 points for incorrect color schemes, and 5 points for improper spacing or font usage. 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 iOS interaction patterns: 1) Response to touch within 100ms 2) Smooth animations at 60fps 3) Proper haptic feedback simulation 4) Spring animations for bounces and transitions. Deduct 5 points for janky scrolling/zooming, 3 points for non-standard transition animations, and 5 points for significant UI freezing during operations. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Web Visuals",
-  "difficulty": "hard"
-}

package/library/web_applications-web_visuals/html-upload-image-analyze-results.json

@@ -1,68 +0,0 @@
-{
-  "index": 372,
-  "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 is executable for demonstration. Based on the image content, write a similar HTML code that can upload images and analyze results.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the image upload functionality fully implemented?",
-      "description": "Check if the HTML/JavaScript code provides a complete image upload mechanism including: file input control, drag-and-drop support, preview functionality, and validation for file types (images only) and sizes. Score 0 if no upload functionality exists, 5 if only basic file input is implemented, and 10 if it includes multiple upload methods with proper validation.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the image analysis functionality implemented?",
-      "description": "Evaluate whether the code includes client-side or server-side image analysis capabilities such as basic properties extraction (dimensions, format, size) or more advanced features (object detection, color analysis, etc.). Deduct 5 points if only metadata display is implemented without actual analysis, and 3 points if the analysis lacks depth. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the result visualization properly implemented?",
-      "description": "Assess how the analysis results are presented to users - through text descriptions, charts, overlays on the image, or other visual methods. Check if the visualization is clear, informative and interactive. Deduct 5 points if results are only displayed as plain text, and 3 points if visualizations lack interactivity. Full score requires comprehensive and interactive visualizations.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is there appropriate feedback during the upload and analysis process?",
-      "description": "Verify if the code implements loading indicators, progress bars, or other feedback mechanisms during file upload and processing. Check for proper error handling and user notifications. Deduct 5 points if there's no visual feedback during processing, and 3 points if error states are not properly communicated. 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 invalid file uploads, failed analysis, browser compatibility issues, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Batch processing multiple images 2. Comparison views between original and analyzed images 3. Exportable analysis reports). 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 image processing pipelines) 2. Function modules unrelated to image upload and analysis 3. Fancy effects that affect performance (e.g., unnecessary animations). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating UI/processing/visualization logic), error handling patterns, and code organization. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the code lacks comments or documentation. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching (no more than 3 primary colors) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional font system (body font size ≥ 14px, line height over 1.5 times). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic text-image layout. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Immediate feedback after upload action 2) Transition animation during analysis process 3) Clear visual indication of completed analysis. Deduct 5 points for each operation without feedback, 3 points for jarring transitions between states, and 5 points for confusing workflow that doesn't guide users. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Web Visuals",
-  "difficulty": "easy"
-}