@getollie/cli 0.0.4 → 0.2.0

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

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

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

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

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

package/library/web_applications-web_visuals/online-editable-menu-image-exporter.json

@@ -1,68 +0,0 @@
-{
-  "index": 226,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Try to ensure that the generated code can be executed and displayed. Based on this HTML foundation, support online editing and exporting of menu images.\n\n<!DOCTYPE html>\n<html lang=\"zh-CN\">\n\n<head>\n    <meta charset=\"UTF-8\">\n    <title>Premium Home-style Restaurant Menu</title>\n    <style>\n        body {\n            font-family: 'Microsoft YaHei', sans-serif;\n            background-color: #f8f8f8;\n            padding: 30px;\n        }\n\n        .menu-card {\n            background: white;\n            border-radius: 12px;\n            box-shadow: 0 4px 15px rgba(0, 0, 0, 0.1);\n            padding: 25px;\n            max-width: 600px;\n            margin: 0 auto;\n        }\n\n        h1 {\n            text-align: center;\n            color: #c74a2a;\n            font-size: 28px;\n            margin-bottom: 25px;\n        }\n\n        .menu-table {\n            width: 100%;\n            border-collapse: collapse;\n            margin-bottom: 20px;\n        }\n\n        .menu-table th {\n            background-color: #f8f8f8;\n            font-weight: 600;\n            color: #333;\n            padding: 12px;\n        }\n\n        .menu-table td {\n            padding: 15px;\n            border-bottom: 1px solid #eee;\n            vertical-align: middle;\n        }\n\n        .combo-price {\n            text-align: right;\n            color: #c74a2a;\n            font-weight: bold;\n            width: 80px;\n        }\n\n        .additional {\n            background: #fff9f5;\n            padding: 15px;\n            border-radius: 8px;\n            margin-top: 25px;\n        }\n\n        .additional h3 {\n            color: #c74a2a;\n            margin: 0 0 12px 0;\n        }\n\n        .dish-item {\n            display: flex;\n            justify-content: space-between;\n            padding: 8px 0;\n            border-bottom: 1px dashed #ddd;\n        }\n\n        .price-tag {\n            color: #c74a2a;\n            font-size: 16px;\n        }\n    </style>\n</head>\n\n<body>\n    <div class=\"menu-card\">\n        <h1>Premium Home-style Restaurant</h1>\n        <p style=\"text-align: center; color: #666; margin-bottom: 25px;\">\n            March 28th Lunch Menu\n        </p>\n\n        <!-- Set Meal Combinations -->\n        <table class=\"menu-table\">\n            <thead>\n                <tr>\n                    <th>Set Meal Combinations</th>\n                    <th class=\"combo-price\">Price</th>\n                </tr>\n            </thead>\n            <tbody>\n                <tr>\n                    <td>Main Meat Dish + Small Meat Dish + Vegetable</td>\n                    <td class=\"combo-price\">¥16</td>\n                </tr>\n                <tr>\n                    <td>2 Main Meat Dishes + Small Meat Dish + Vegetable</td>\n                    <td class=\"combo-price\">¥22</td>\n                </tr>\n            </tbody>\n        </table>\n\n        <!-- Additional Options -->\n        <div class=\"additional\">\n            <h3>Additional Options</h3>\n            <ul>\n                <li>Main Meat Dish ¥8, Small Meat Dish ¥4, Vegetable ¥2</li>\n            </ul>\n        </div>\n\n    <hr></hr>\n\n        <table class=\"menu-table\">\n            <thead>\n                <tr>\n                    <th>Rice with Toppings</th>\n                    <th class=\"combo-price\">Price</th>\n                </tr>\n            </thead>\n            <tbody>\n                <tr>\n                    <td>Homestyle Stir-fried Pork</td>\n                    <td class=\"combo-price\">¥16</td>\n                </tr>\n                <tr>\n                    <td>Kung Pao Chicken</td>\n                    <td class=\"combo-price\">¥14</td>\n                </tr>\n            </tbody>\n        </table>\n    </div>\n</body>\n\n</html>",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is online menu editing functionality fully implemented?",
-      "description": "Review whether the code includes a complete editing system allowing users to modify menu items, prices, categories, and descriptions. Check for content validation, input field constraints, and real-time preview. Score 0 if no editing features exist, 5 if only basic text editing is supported, and 10 if comprehensive menu structure editing with validation is implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the menu image export functionality properly implemented?",
-      "description": "Evaluate the export functionality for converting the menu to image format (PNG/JPEG/SVG). Check for proper rendering of all elements including special characters, custom fonts, and layout preservation. Score 0 if no export feature exists, 5 if basic screenshot functionality is available but with quality/formatting issues, and 10 if high-quality image export with customization options (resolution, format, crop area) is implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the menu structure data model well-designed?",
-      "description": "Assess whether the code uses a structured data model (JSON/object) to represent menu items, categories, and pricing, enabling clean separation between data and presentation. Check if the model allows for dynamic updates and maintains data integrity. Deduct 5 points if global variables are overused; deduct 5 points if the data structure doesn't support menu hierarchy. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Are interactive UI elements properly implemented for editing?",
-      "description": "Review the implementation of UI controls (buttons, form fields, dropdowns) for editing menu content. Check for consistent interaction patterns, visual feedback on actions, and clear edit/save states. Deduct 5 points for poor accessibility (no keyboard support, missing ARIA attributes); deduct 3 points if the interface lacks clear visual indication of editable elements. 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 input data, image generation failures, browser compatibility issues) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Template gallery with different menu styles 2. QR code generation for digital menu sharing 3. Multilingual support 4. Print-optimized view). 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 export methods doing the same thing) 2. Function modules unrelated to menu editing/export (e.g., unnecessary animations) 3. Fancy effects that affect performance (e.g., heavy decorative elements that slow rendering). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating menu data/view/controller layers), browser compatibility, 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 the code doesn't handle different device screen sizes. 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 editing operations, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Web Visuals",
-  "difficulty": "hard"
-}

package/library/web_applications-web_visuals/online-network-topology-editor-antv-g6.json

@@ -1,68 +0,0 @@
-{
-  "index": 1277,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Pay attention to ensuring that the generated code is executable for demonstration. So, based on this web server and combining with AntV G6, develop an online network topology diagram editing tool.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the core graph editing functionality properly implemented?",
-      "description": "Review whether the code correctly implements node creation, edge connection, selection, and basic editing operations using AntV G6. Check if the topology editing interface includes essential operations like add/delete/move nodes, connect/disconnect edges, and group/ungroup elements. Score 0 if the core editing functions are missing, 5 if only basic operations are implemented, and 10 if a comprehensive set of topology editing features is available.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the network topology data structure well-designed?",
-      "description": "Evaluate if the code implements an appropriate data structure for representing network topology (nodes, edges, groups, attributes). Check if the structure supports topology validation, cycle detection, and maintains referential integrity. Deduct 5 points if the data structure doesn't allow for custom node/edge properties, and 3 points if it doesn't handle hierarchical relationships. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is a proper server integration implemented for topology persistence?",
-      "description": "Check if the code includes proper API integration with the web server for saving, loading, and versioning topology diagrams. Verify if the implementation handles concurrent editing conflicts, provides auto-save functionality, and includes error recovery. Deduct 5 points if server synchronization is missing, and 3 points if there's no offline editing capability. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Are advanced topology visualization features implemented?",
-      "description": "Assess whether the tool implements advanced visualization features like automatic layout algorithms, mini-map navigation, zoom/pan controls, and custom styling options. Check if it includes filtering/search capabilities for large topologies. Score 10 points for comprehensive visualization features with performance optimization, 5 points for basic functionality, and 0 if advanced features are missing.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid topology configurations, server connection failures, concurrent editing conflicts, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Real-time collaborative editing 2. Topology validation and error checking 3. Network simulation capabilities 4. AI-assisted layout suggestions). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple node creation workflows) 2. Function modules unrelated to network topology editing (e.g., unnecessary analytics) 3. Fancy effects that affect performance (e.g., excessive animations or 3D 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 data model/view/controller layers), efficient use of AntV G6 API, proper event handling, and build process automation. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the build process is not automated. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching for topology elements (distinguishable but not jarring) 2) Proper layout of toolbars and editing panels (following standard UX patterns) 3) Professional typography and iconography for network elements. Deduct 3 points for cluttered toolbars, 5 points for poor visual hierarchy, and 5 points for inconsistent node/edge styling. 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) Responsive node dragging with < 50ms latency 2) Smooth zooming and panning with proper acceleration/deceleration 3) Clear visual feedback during edge creation and connection. Deduct 5 points for laggy graph manipulation, 3 points for jumpy animations during layout changes, and 5 points for confusing interaction models. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Web Visuals",
-  "difficulty": "medium"
-}

package/library/web_applications-web_visuals/panoramic-photo-project-vue3-threejs.json

@@ -1,68 +0,0 @@
-{
-  "index": 881,
-  "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 when possible. Create a panoramic photo project using the Vue3 and Three.js technology stack.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the Three.js panoramic rendering core fully implemented?",
-      "description": "Review whether the code correctly implements panoramic image mapping using Three.js SphereGeometry or BoxGeometry, including proper texture loading, UV mapping, and camera controls for 360-degree viewing. Score 0 if basic panoramic display is not working, 5 if only static panoramic view is implemented, and 10 if full interactive panoramic rendering with proper geometry and materials is完整implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the Vue3 integration architecture properly designed?",
-      "description": "Check whether the Vue3 Composition API is correctly integrated with Three.js lifecycle, including proper reactive state management, component mounting/unmounting handling, and memory cleanup. Evaluate if ref/reactive are used appropriately for Three.js objects. Deduct 5 points if memory leaks are present, and 3 points if Vue reactivity conflicts with Three.js rendering loop. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are interactive controls and navigation mechanisms implemented?",
-      "description": "Evaluate whether mouse/touch controls for panoramic navigation are smooth and intuitive, including orbit controls, zoom functionality, and mobile device support. Check if control sensitivity is adjustable and if there are proper boundaries to prevent disorientation. Deduct 5 points if mobile touch controls are missing, and 3 points if zoom limits are not implemented. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the panoramic asset loading and optimization system complete?",
-      "description": "Check whether the code includes efficient image loading with progress indicators, supports multiple panoramic formats (equirectangular, cube maps), and implements proper error handling for failed loads. Evaluate if image preprocessing and compression are considered. Deduct 5 points if no loading states are shown, and 3 points if large images cause performance issues. Give 10 points if fully optimized with lazy loading and multiple format support.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as WebGL compatibility issues, image loading failures, browser resize events, device orientation changes, etc.) and provide friendly error prompts or fallback mechanisms. Code with strong robustness should effectively handle these edge cases, giving 10 points. If robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there innovative features that enhance the panoramic experience?",
-      "description": "Check whether the code includes advanced features that elevate the user experience (e.g., 1. Hotspot annotations with interactive tooltips 2. Multiple panoramic scene transitions 3. Mini-map navigation 4. VR mode compatibility 5. Auto-rotation with pause on interaction). Add 2-3 points for each well-implemented innovative feature (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features or unnecessary complexity?",
-      "description": "Strictly check three types of redundancy: 1. Redundant Three.js scene/renderer instances 2. Unnecessary Vue components that don't contribute to panoramic functionality 3. Over-engineered animations or effects that impact performance without adding value. Deduct 3 points for each redundancy found, and directly deduct 10 points if core panoramic functionality is compromised by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code demonstrate high engineering quality?",
-      "description": "Review modular architecture (separating Three.js logic, Vue components, and utility functions), TypeScript usage for better type safety, and proper build configuration. Deduct 5 points if global state pollution is found or if Three.js objects are not properly disposed; deduct 5 points if code organization is poor with high coupling; deduct 5 points if build process lacks optimization for 3D assets. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface design meet professional visual standards?",
-      "description": "Evaluate whether the UI overlay design follows modern principles: 1) Clean control interface that doesn't obstruct the panoramic view 2) Intuitive iconography for navigation controls 3) Proper contrast and visibility across different panoramic backgrounds 4) Responsive design for various screen sizes. Deduct 3 points for each poorly designed control element, 5 points for controls that interfere with panoramic viewing, and 5 points for poor mobile responsiveness. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Are the panoramic interactions smooth and performant?",
-      "description": "Judge whether the panoramic navigation meets performance standards: 1) Smooth 60fps rendering during navigation 2) Responsive controls with <50ms input delay 3) Smooth transitions between different viewing angles 4) Proper performance on mobile devices. Deduct 5 points for each noticeable frame drop during interaction, 3 points for laggy controls, and 5 points if mobile performance is significantly degraded. Full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Web Visuals",
-  "difficulty": "easy"
-}

package/library/web_applications-web_visuals/prize-drawing-webpage-with-admin-panel.json

@@ -1,68 +0,0 @@
-{
-  "index": 1626,
-  "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 and displayable. Help me create a prize drawing webpage with an admin panel that allows adjusting prize names and winning probabilities. The admin panel password is 123456789987654321. There should be a popup notification when a prize is won.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the prize drawing core mechanism properly implemented?",
-      "description": "Review whether the code accurately implements a weighted random selection algorithm based on configured probabilities. Check if the probability distribution is correctly calculated and if the random number generation is properly seeded. Score 0 if the core drawing mechanism is missing, 5 if basic random selection is implemented without weighting, and 10 if the weighted probability system is fully implemented with proper verification that actual results match the configured odds.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the admin panel functionality complete and secure?",
-      "description": "Evaluate whether the admin panel allows comprehensive prize management (adding, editing, deleting prizes and adjusting their probabilities). Check if the authentication mechanism is properly implemented with the specified password (123456789987654321). Deduct 5 points if the password is stored in plain text or visible in client-side code, 3 points if CSRF protection is missing, and 3 points if there's no session timeout. Give 10 points if the admin panel is fully functional and reasonably secure.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the prize notification system properly implemented?",
-      "description": "Check whether the popup notification appears when a prize is won, with appropriate animation and visibility. Evaluate if the notification includes all relevant prize details and is properly positioned. Deduct 5 points if the notification is not visually distinct, 3 points if it lacks animation, and 5 points if it disappears too quickly or doesn't have a dismissal option. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is data persistence implemented for configuration and results?",
-      "description": "Assess whether the application properly stores prize configurations and drawing history. Check if localStorage/sessionStorage is used for client-side persistence or if server-side storage is implemented. Verify if data is properly loaded when the page initializes. Deduct 5 points if prize configurations are lost on page refresh, 3 points if there's no drawing history, and 5 points if there's no export/backup functionality. 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 probability inputs, empty prize lists, concurrent admin operations, 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. Visual drawing animation with suspense 2. Confetti/celebration effects for winners 3. Statistics dashboard of historical draws). 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 implementations of similar functions (e.g., multiple prize drawing algorithms coexisting) 2. Function modules unrelated to prize drawing (e.g., unnecessary third-party widgets) 3. Fancy effects that affect performance (e.g., excessive animations that slow down the interface). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating UI/business logic/data layers), code reusability, and maintainability. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there are no comments on complex logic. 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 jarring during animations, 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"
-}