@getollie/cli 0.0.1

package/library/web_applications-web_visuals/interstellar-black-hole-html-drawing.json

@@ -0,0 +1,68 @@
+{
+  "index": 242,
+  "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. Help me draw a black hole from the movie \"Interstellar\" using HTML code. It should be a single file and match the appearance of the black hole as seen in the movie.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the core visual representation of the black hole implemented accurately?",
+      "description": "Evaluate whether the code successfully creates a realistic visual representation of the black hole from 'Interstellar', including the accretion disk, event horizon, and gravitational lensing effects. Score 0 if the core elements are missing, 5 if basic elements are present but lack detail, and 10 if the visualization closely resembles Gargantua from the movie.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are the key visual components of Gargantua properly implemented?",
+      "description": "Check if the code includes the specific visual characteristics of the 'Interstellar' black hole: the thin, bright accretion disk with its asymmetric brightness (brighter on the approaching side due to relativistic beaming), the dark event horizon in the center, and the distinctive halo effect. Deduct 3 points for each missing element. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the gravitational lensing effect properly simulated?",
+      "description": "Assess whether the code implements the critical gravitational lensing effect that creates the distinctive appearance of light bending around the black hole. This should include the visualization of how the accretion disk appears both above and below the black hole due to extreme light bending. Score 0 if no lensing is implemented, 5 if basic warping is present, and 10 if the effect accurately mimics the movie's physics-based representation.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the simulation interactive or animated to enhance the visual experience?",
+      "description": "Evaluate whether the code includes animation or interactive elements that enhance the black hole visualization, such as disk rotation, perspective changes, or user controls. Score 0 if static only, 5 if basic animation is implemented, and 10 if comprehensive interactive elements are included that allow viewers to experience the black hole from different perspectives.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle different viewport sizes, browser compatibility issues, and potential rendering challenges. Code should degrade gracefully if certain features are not supported. Full implementation with fallbacks and responsive design earns 10 points, average implementation with some responsiveness earns 5 points, and implementations that break on different devices earn 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Time dilation visualization effects 2. Sound elements reminiscent of Hans Zimmer's score 3. Interactive educational elements explaining black hole physics). 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 rendering methods that accomplish the same visual effect 2. Unnecessary elements unrelated to the black hole visualization 3. Excessive effects that impact performance without enhancing the core representation. Deduct 3 points for each redundancy found, and directly deduct 10 points if redundant code interferes with the core visualization.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review the structure of the HTML/CSS/JS implementation, looking for clean separation of concerns, efficient rendering techniques, and appropriate use of canvas/WebGL/SVG based on the visualization needs. Deduct 5 points if global scope pollution is found; deduct 5 points if there is significant code duplication; deduct 5 points if the implementation uses inappropriate technologies for the task. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the visual presentation meet professional design standards?",
+      "description": "Evaluate whether the black hole visualization follows cinematic design principles: 1) Appropriate color gradient for the accretion disk (orange/red/blue spectrum as in the film) 2) Proper contrast ratio between the event horizon and surrounding elements 3) Clean implementation without visual artifacts or pixelation. Deduct 3 points for each inaccuracy in color representation, 5 points for poor contrast that makes elements difficult to distinguish, and 5 points for visible rendering artifacts. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the visual experience smooth and immersive?",
+      "description": "Judge whether the rendering maintains consistent frame rates (minimum 30fps) during animations, transitions occur smoothly, and the overall experience creates the sense of cosmic scale and awe that the film conveyed. Deduct 5 points for stuttering animations, 3 points for jarring transitions, and 5 points if the scale and proportions fail to create immersion. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Web Visuals",
+  "difficulty": "medium"
+}

package/library/web_applications-web_visuals/javascript-showcase-artwork-dynamic-webpages.json

@@ -0,0 +1,68 @@
+{
+  "index": 1436,
+  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Take care to ensure that the code you provide is executable and can be demonstrated. How can one create dynamic web pages using JavaScript to showcase artwork?",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is a proper HTML5 canvas implementation included?",
+      "description": "Verify whether the code includes a correctly configured HTML5 canvas element with appropriate dimensions, responsive design considerations, and proper initialization. Check if the canvas context (2D or WebGL) is properly obtained and utilized. Score 0 if canvas is missing, 5 if basic implementation exists, and 10 if it includes advanced features like resolution scaling and browser compatibility solutions.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are dynamic drawing techniques implemented effectively?",
+      "description": "Evaluate the implementation of dynamic drawing techniques such as animation loops (requestAnimationFrame), procedural generation, or interactive elements. Check for smooth frame rates (60fps target), efficient redrawing strategies, and proper timing mechanisms. Deduct 5 points if animations are jerky, 3 points if there's no frame rate control, and 5 points if there are no dynamic elements at all.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is there proper user interaction with the artwork?",
+      "description": "Assess whether the code implements meaningful user interactions such as mouse/touch events, keyboard controls, or gesture recognition that allow users to engage with the artwork. Check for event delegation, proper event listener cleanup, and accessible interaction patterns. Deduct 5 points for missing interaction, 3 points for poor event handling, and 5 points for inaccessible controls.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Does the implementation offer artistic customization options?",
+      "description": "Review whether the code provides ways to customize the artwork through parameters, controls, or settings that affect visual appearance. Look for color pickers, sliders for visual parameters, or theme options. Score 0 if no customization exists, 5 points for basic controls, and 10 for comprehensive artistic customization options.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code handles common edge cases (such as browser inconsistencies, window resizing, device orientation changes, etc.) and provides graceful fallbacks or recovery mechanisms. Code with strong robustness should handle these edge cases effectively, 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. Generative art algorithms 2. Physics-based interactions 3. Audio-visual integration 4. AR/VR capabilities). 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. Unused visual effects or abandoned code paths 3. Overly complex animations that harm performance without adding artistic value. Deduct 3 points for each redundancy found, and directly deduct 10 points if the core artwork display 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/UI controls/data management), code reusability, and performance optimization techniques. Deduct 5 points if global namespace pollution is found; deduct 5 points if there's excessive code duplication; deduct 5 points if no performance considerations (like debouncing/throttling for intensive operations) exist. 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 artistic presentation principles: 1) Clean artwork display area without visual clutter 2) Harmonious control panel design that doesn't distract from the artwork 3) Appropriate use of negative space and composition. Deduct 3 points for each visually distracting element, 5 points for poor artwork framing, and 5 points for chaotic UI layout. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and responsive?",
+      "description": "Judge whether the dynamic effects and artistic animations conform to human perception: 1) Immediate visual feedback for user interactions 2) Smooth transitions between states or visual changes 3) Appropriate animation timing that enhances rather than detracts from the artwork. Deduct 5 points for laggy responses, 3 points for jarring transitions, and 5 points for animations that distract from appreciating the artwork. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Web Visuals",
+  "difficulty": "medium"
+}

package/library/web_applications-web_visuals/jquery-floating-text-website.json

@@ -0,0 +1,68 @@
+{
+  "index": 1318,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the code you provide is executable for demonstration purposes. Create a floating text website using jQuery.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the floating text functionality properly implemented?",
+      "description": "Review whether the code uses jQuery to create elements that float across the screen with smooth animation. Check if the text moves in different directions, speeds, or patterns. Score 0 if no animation exists, 5 if only basic linear movement is implemented, and 10 if there are multiple floating patterns (e.g., sine wave, circular, bounce) with configurable parameters.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the text generation and management system complete?",
+      "description": "Evaluate whether the code includes mechanisms to generate texts dynamically, manage their lifecycle (creation, animation, removal), and handle text overlap. Deduct 3 points if text elements pile up without being removed after leaving the viewport. Deduct 4 points if there's no system to prevent excessive DOM elements. Score 10 if the implementation includes efficient object pooling or equivalent performance optimizations.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the interaction with the floating text implemented?",
+      "description": "Check whether users can interact with floating text (e.g., click to remove, hover to pause, drag to reposition). Deduct 5 points if no interaction is implemented. Score full 10 points if multiple intuitive interaction methods are available with appropriate visual feedback (e.g., color change on hover, subtle animation on click).",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is there customization functionality for the floating text?",
+      "description": "Assess whether the code allows customization of text appearance (color, size, font, opacity) and behavior (speed, direction, rotation). Score 3 points for basic customization options, 7 points if users can adjust settings through UI controls, and 10 points if there's a complete settings panel with real-time preview functionality.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as rapid user interactions, browser resize, mobile device orientation changes) and provide graceful degradation. 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. Physics-based interactions like gravity 2. Text that reacts to mouse movement 3. Themed text groups with different behaviors). 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 handlers causing memory leaks 2. Unnecessary DOM manipulations that could be handled with CSS 3. Complex animations that could be simplified with CSS transitions/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 jQuery usage best practices (like proper selectors, event delegation, chain operations), code organization (namespacing, modular structure), and performance considerations (animation frame management, DOM manipulation efficiency). Deduct 5 points for excessive direct DOM manipulations; deduct 5 points if jQuery selectors are inefficient; deduct 5 points if event handlers aren't properly cleaned up. 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 text and background 2) Proper contrast ensuring readability of floating text 3) Thoughtful typography choices (appropriate font families, sizes, and weights). Deduct 3 points for poor color combinations affecting readability, 5 points for inconsistent text styling, and 5 points for cluttered visual presentation. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the animation performance optimized?",
+      "description": "Judge whether the animation implementation follows performance best practices: 1) Using requestAnimationFrame instead of setInterval/setTimeout 2) Applying hardware acceleration where appropriate (transform/opacity) 3) Properly handling large numbers of elements without frame drops. Deduct 5 points for noticeable jank during animation, 3 points for excessive reflows/repaints, and 5 points for significant performance degradation with multiple texts. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Web Visuals",
+  "difficulty": "medium"
+}

package/library/web_applications-web_visuals/mobile-wallpaper-webpage.json

@@ -0,0 +1,68 @@
+{
+  "index": 1812,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate, professional responses. Be sure to provide executable code when possible. Help me create a mobile wallpaper webpage.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the core wallpaper display and browsing functionality implemented?",
+      "description": "Review whether the code properly implements a responsive grid/layout for displaying wallpapers and includes navigation controls for browsing through the collection. Score 0 if no display mechanism exists, 5 if basic display is implemented but lacks organization, and 10 if it includes proper thumbnails, categories, and smooth navigation.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are wallpaper preview and download functions properly implemented?",
+      "description": "Check if the code includes functionality for users to preview wallpapers in full-screen mode before downloading, and whether it implements proper download functionality with appropriate file formats (JPG/PNG) and resolution options for different mobile devices. Deduct 5 points if preview is missing, and 3 points if download options are limited. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is mobile responsiveness properly implemented?",
+      "description": "Evaluate whether the webpage is fully responsive across different mobile device sizes (from small phones to tablets), with appropriate media queries, flexible grid layouts, and touch-friendly UI elements. Deduct 5 points if the layout breaks on specific screen sizes and 5 points if touch interactions are poorly implemented. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Are wallpaper filtering and search features implemented?",
+      "description": "Check if the code includes functionality for users to filter wallpapers by categories, colors, resolution, or tags, and whether there's a search feature with proper indexing. Deduct 3 points if filtering is limited, 3 points if search doesn't support partial matching, and 4 points if there's no visual feedback during search/filter operations. 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, network interruption, unsupported device orientations, 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. Live wallpaper support with subtle animations 2. Dark/light mode toggle that affects UI and wallpaper suggestions 3. Wallpaper cropping/customization tools). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple image loading libraries) 2. Function modules unrelated to wallpapers (e.g., a built-in calculator) 3. Fancy effects that affect performance (e.g., unnecessary parallax 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 UI components/services/state management), asset optimization (image compression, lazy loading), and performance optimization. Deduct 5 points if global state pollution is found; deduct 5 points if unoptimized images cause slow loading; deduct 5 points if there's no code organization or bundling strategy. 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 mobile design principles: 1) Harmonious color matching (no more than 3 primary colors) 2) Proper layout spacing (touch targets at least 44x44px, consistent margins) 3) Professional typography (readable fonts, proper contrast ratios). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for elements that extend beyond screen boundaries. 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 mobile interaction standards: 1) Touch feedback delay ≤ 100ms 2) Smooth scrolling without jank 3) Appropriate loading indicators for network operations. Deduct 5 points for each operation without feedback, 3 points for choppy animations, and 5 points for interactions that don't follow platform conventions (iOS/Android). The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Web Visuals",
+  "difficulty": "easy"
+}

package/library/web_applications-web_visuals/nested-webpage-clickable-expandable-sections.json

@@ -0,0 +1,68 @@
+{
+  "index": 1698,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and expert responses. Be sure to ensure that the code you generate is executable for demonstration. Please create in markdown a nested webpage with clickable expandable sections.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the nested webpage structure properly implemented?",
+      "description": "Review whether the HTML implements a clean nested structure with properly defined sections. Check if the code uses appropriate semantic HTML5 elements (like `<section>`, `<article>`, `<details>`, etc.) rather than just generic `<div>` tags. Score 0 if there's no nested structure, 5 if basic nesting is implemented but with poor semantics, and 10 if the structure is both semantic and properly organized.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are the expandable sections fully functional?",
+      "description": "Evaluate the implementation of expandable/collapsible sections. Check if the implementation uses native HTML (`<details>` and `<summary>`) or JavaScript-driven toggles. Test if clicking works properly to expand/collapse content without page reloads. Full 10 points requires smooth transitions, proper state management (remembering open/closed states), and accessible controls. Deduct 5 points if implementation only works in certain browsers or has accessibility issues.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the markdown properly rendered to HTML?",
+      "description": "Check if Markdown syntax is correctly transformed into HTML elements. Verify that all Markdown features (headers, lists, code blocks, emphasis, links, etc.) render properly. Score 0 if Markdown isn't converted at all, 5 if basic conversion is done but with formatting errors, and 10 if all Markdown elements are rendered correctly including nested Markdown elements within expandable sections.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is proper event handling implemented for interactions?",
+      "description": "Analyze the JavaScript event handling for the clickable components. Check for event delegation rather than individual listeners, proper stopping of event propagation where needed, and performance considerations for nested elements. Deduct 4 points if events cause unnecessary re-renders, 3 points if there are memory leaks from unremoved listeners, and 5 points if mobile touch events aren't properly supported. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code handles edge cases such as deeply nested content, special characters in content, browser compatibility issues, and potential script errors. Code with strong robustness should gracefully degrade in older browsers and handle content loading failures. Score 10 points for comprehensive error handling and fallbacks, 5 points for basic error handling, and 0 points if no error handling exists.",
+      "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 animations for expanding/collapsing, 2. Search functionality within nested content, 3. Breadcrumb navigation for deep nesting, 4. Keyboard shortcuts for navigation). Add 2.5 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Duplicate implementations of the same functionality, 2. Unnecessary libraries for simple tasks (e.g., using full jQuery just for toggles), 3. Overly complex solutions for straightforward requirements. Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functionality is obscured by unnecessary code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review code organization (separation of HTML, CSS, and JavaScript), modularity, use of modern practices (like ES6+ features), and maintainability. Deduct 5 points for inline styles or scripts that should be separated; deduct 5 points for unmaintainable spaghetti code; deduct 5 points for lack of comments on complex functions. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the design follows modern principles: 1) Consistent visual hierarchy for nested elements, 2) Proper indentation and visual cues for depth, 3) Clear indicators for expandable content, 4) Responsive design that works on different screen sizes. Deduct 3 points for inconsistent visual indicators, 5 points for poor readability at different nesting levels, and 5 points for designs that break on mobile devices. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the interactions feel natural: 1) Expand/collapse animations under 300ms, 2) No layout shifts when toggling content, 3) Clear visual feedback for interactive elements, 4) Smooth scrolling to expanded content. Deduct 5 points for jarring animations, 3 points for layout jumps during interactions, and 5 points for latency over 200ms when responding to clicks. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Web Visuals",
+  "difficulty": "easy"
+}

package/library/web_applications-web_visuals/new-year-wishes-program-interface.json

@@ -0,0 +1,68 @@
+{
+  "index": 889,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure that any code you generate is executable for demonstration. Design a small program interface for New Year's wishes.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the New Year's wishes core functionality implemented?",
+      "description": "Review whether the code implements the essential elements of a New Year's wishes interface, including input fields for entering wishes, submission functionality, and display of wishes. Score 0 if the core interaction logic is missing, 5 if only basic wish submission is implemented, and 10 if the solution includes rich text formatting, wish categorization, or filtering capabilities.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the New Year theme aesthetically represented?",
+      "description": "Evaluate whether the interface incorporates appropriate New Year elements (such as fireworks, countdowns, festive colors, seasonal imagery) that match cultural expectations. Deduct 3 points if theming is minimal, 5 points if theme elements are inappropriate or missing entirely. Full score requires thoughtful integration of New Year visuals that enhance rather than distract from the core functionality.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Are interactive New Year elements implemented?",
+      "description": "Check for interactive elements that enhance the New Year's experience, such as animations (fireworks, confetti, etc.), sound effects, countdown timers, or transition effects when submitting wishes. Score 0 if no interactive elements exist, 5 if basic animations are implemented, and 10 if multiple well-integrated, performant interactive elements are present.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the data management for wishes properly implemented?",
+      "description": "Assess how wishes are stored, retrieved, and managed. Look for appropriate data structures, local storage implementation, or simple backend integration. Deduct 5 points if wishes disappear on page reload, 3 points if there's no validation for inputs. Full score requires data persistence and proper handling of wish data lifecycle.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as empty inputs, special characters in wishes, rapid clicking, handling many wishes, 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. Wish sharing to social media 2. Personalized digital greeting cards 3. AR wishes viewing). 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 wish submission methods) 2. Function modules unrelated to New Year wishes (e.g., a built-in calculator) 3. Fancy effects that affect performance (e.g., excessive particle 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 organization, and reusability. 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) Click feedback delay ≤ 100ms 2) Transition animation duration controlled between 300-500ms 3) Clear visual focus guidance. Deduct 5 points for each operation without feedback, 3 points for visual after-images during fast interactions, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Web Visuals",
+  "difficulty": "easy"
+}

package/library/web_applications-web_visuals/nezha-character-description-css-preprocessing.json

@@ -0,0 +1,68 @@
+{
+  "index": 1621,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Try to ensure that the generated code is executable for demonstration purposes. Nezha is the protagonist in the animated films \"Ne Zha: Birth of the Demon Child\" and \"Ne Zha: The Devil Child Returns to the Sea\" directed by Jiaozi, as well as related works.\n\nNezha is the third son of Li Jing and Lady Yin. He has a rebellious, mischievous, and impulsive personality, yet remains kind and just. Because he was reincarnated from a demon pill, he is misunderstood by people, feels lonely inside, and craves acceptance.\n\nHe has straight bangs, two small buns on top of his head, large panda eyes with heavy eye makeup, and somewhat frightening rows of teeth. He often displays a wicked smile with a hint of cuteness. He wears a golden collar around his neck, a red vest with lotus patterns, brown three-quarter length pants with flame patterns, and a yellow belt. He is a chaotic \"demon child\" who mistakenly came to the mortal world causing endless trouble. At birth, because the spirit pearl was stolen by Shen Gongbao, he became the reincarnation of the demon pill. Initially, Nezha faced discrimination, rejection, mockery, and hostility from the people of Chentang Pass because he was a demon pill, but as the story progresses, he gradually gains acceptance from the people.\n\nPlease use CSS preprocessing to create two files based on the text above: one HTML file and one LESS file.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the Nezha character visualization implemented in HTML/CSS?",
+      "description": "Check if the code creates a visual representation of Nezha with the specific characteristics mentioned: straight bangs, two small buns, panda eyes with heavy makeup, teeth showing in a wicked smile, golden collar, red vest with lotus patterns, brown pants with flame patterns, and yellow belt. Score 0 if the character is not implemented at all, 5 if only basic features are included, and 10 if all detailed characteristics are present with artistic quality.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the LESS preprocessing properly utilized for the styling?",
+      "description": "Evaluate whether the code leverages LESS features effectively: using variables for color schemes related to Nezha (red, gold, brown), implementing nesting for better organization, utilizing mixins for repeated styling patterns, and employing other LESS-specific functionalities like operations or functions. Deduct 3 points if only basic LESS features are used, 5 points if it's mostly just CSS with minimal LESS advantages, and 10 points for comprehensive LESS implementation with clear organization.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Does the implementation include animations that reflect Nezha's character?",
+      "description": "Assess whether the code implements animations that represent Nezha's rebellious and mischievous yet kind personality. Look for animations like flame effects, hovering or movement animations that suggest impulsiveness, and transitions that reflect his character development. Score 0 if no animations are present, 5 if basic animations exist, and 10 if thoughtful animations that meaningfully represent the character's traits are implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the implementation responsive and adaptable?",
+      "description": "Check if the code uses responsive design techniques to ensure the Nezha visualization works across different screen sizes. Verify if media queries are implemented, if relative units are used appropriately, and if the layout adapts well without breaking. Deduct 5 points if major responsive features are missing, and 3 points if adaptation is limited to only certain screen sizes. 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 slow loading, missing assets, browser compatibility issues, etc.) and provides fallbacks or graceful degradation. 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 elements that respond to user input 2. Creative visualization techniques beyond standard CSS 3. Storytelling elements that reflect Nezha's journey). 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 CSS properties or LESS variables that serve the same purpose 2. Unnecessary elements or styling unrelated to Nezha's character 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 visualization is 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/animations), LESS organization (proper use of imports, variables, and mixins), and optimization techniques. Deduct 5 points if global style pollution is found; deduct 5 points if the code structure is overly complex or difficult to maintain; deduct 5 points if best practices for CSS/LESS organization are not followed. 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 that aligns with Nezha's character palette 2) Proper layout spacing and visual hierarchy 3) Professional typography that enhances readability and character representation. Deduct 3 points for each visual element that feels out of place with the character, 5 points for clashing colors that don't match the description, and 5 points for poor visual composition. 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) Hover/click feedback delay ≤ 100ms 2) Transition animation duration controlled between 300-500ms 3) Clear visual indication of interactive elements. Deduct 5 points for each interaction without feedback, 3 points for stuttering animations or performance issues, and 5 points for confusing or misleading interactive elements. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Web Visuals",
+  "difficulty": "medium"
+}

package/library/web_applications-web_visuals/nezha-sea-dragon-anime-style.json

@@ -0,0 +1,68 @@
+{
+  "index": 380,
+  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Make sure to ensure the generated code is executable for display. Please create a webpage about \"Nezha: The Sea Dragon\" in anime style.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the Nezha character accurately represented in anime style?",
+      "description": "Review if the code creates a visual representation of Nezha that authentically reflects anime aesthetics (big eyes, distinctive hairstyle, exaggerated expressions) and incorporates his mythological elements (fire wheels, red ribbon, cosmic ring, fire-tipped spear). Score 0 if Nezha is absent, 5 if basic representation exists but lacks anime style details, and 10 if the character is fully realized with anime style elements and mythological accuracy.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the \"Sea Dragon\" theme integrated effectively?",
+      "description": "Evaluate whether the code implements visual elements representing the sea dragon antagonist and the water/ocean environment. Check for animations or illustrations showing the conflict between Nezha and the dragon. Deduct 5 points if the sea dragon is completely missing, 3 points if water elements are minimal, and give full marks if both the dragon and dynamic water elements are implemented creatively. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Are interactive anime-style animations implemented?",
+      "description": "Check for CSS/JavaScript animations that reflect anime visual language (speed lines, impact frames, particle effects, smooth transitions). Score 0 if no animations exist, 5 if only basic transitions are present, and 10 if the page includes multiple anime-style animations that enhance the storytelling (e.g., Nezha's fire wheel spinning, water splash effects, dragon movements). Deduct 3 points if animations are jerky or cause performance issues.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is responsive design properly implemented for the anime webpage?",
+      "description": "Test if the webpage maintains its anime aesthetic across different screen sizes (desktop, tablet, mobile). Check if media queries adjust layout, font sizes, and image scaling appropriately. Deduct 5 points if the page breaks on mobile, 3 points if some elements overflow or become misaligned, and give 10 points if the responsive design preserves the anime style experience across all common device sizes.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (image loading failures, browser compatibility issues, user interaction errors) and provide fallback mechanisms. Code with strong robustness should gracefully 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 anime experience (e.g., 1. Interactive character poses that change on click 2. Dynamic weather/water effects 3. Voice clips or sound effects on interaction). 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 effects (e.g., multiple parallax libraries) 2. Function modules unrelated to Nezha or anime (e.g., unnecessary form elements) 3. Fancy effects that affect performance (e.g., excessive particle systems that cause lag). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core anime presentation is interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (separation of HTML structure, CSS styling, and JavaScript interaction), code readability, and maintainability. Deduct 5 points if global CSS/JS conflicts are found; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if best practices for web development are not followed. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional anime design standards?",
+      "description": "Evaluate whether the design follows anime aesthetic principles: 1) Vibrant color palette typical of anime 2) Character designs with proper proportions and style 3) Typography that complements the anime theme (possibly including some Japanese-inspired fonts). Deduct 3 points for each visually inconsistent element, 5 points for color combinations that don't match anime aesthetics, and 5 points for non-complementary typography. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the interactive elements follow anime conventions: 1) Smooth transitions between states 2) Appropriately timed animations (300-800ms for character movements) 3) Clear visual feedback for user interactions. Deduct 5 points for each operation without feedback, 3 points for choppy animations, and 5 points for confusing navigation or interaction patterns. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Web Visuals",
+  "difficulty": "easy"
+}