@getollie/cli 0.0.1

package/library/web_applications-education_learning/campus-technology-festival-robot-showcase-website.json

@@ -0,0 +1,68 @@
+{
+  "index": 847,
+  "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. Please help me write HTML code for a science and technology festival website with the theme of campus technology festival. The content is divided into three sections: robot dogs, industrial robots, and humanoid robots. Each section should have three images scrolling on the left side and text on the right side introducing their current development status.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the three-section structure for robot categories properly implemented?",
+      "description": "Check whether the HTML correctly separates the content into three distinct sections for robot dogs, industrial robots, and humanoid robots. Each section should be clearly demarcated with appropriate semantic HTML5 tags (e.g., <section>, <article>). Deduct 5 points if sections blend together visually, 5 points if semantic HTML is not used, and 5 points if the sections are not equally prominent. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the image scrolling mechanism properly implemented for each section?",
+      "description": "Evaluate if each of the three sections contains a functional image carousel/slider with exactly three images per section. The scrolling should work automatically and/or through user interaction. Check for proper image transitions, navigation controls, and responsive design. Score 0 if scrolling is not implemented, 5 if basic scrolling exists but with flaws (e.g., no navigation controls, jerky transitions), and 10 if the scrolling is smooth, intuitive, and fully functional across device sizes.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the section layout correctly implemented with images on the left and text on the right?",
+      "description": "Review whether each section strictly follows the required layout specification with images scrolling on the left side and descriptive text positioned on the right side. The layout should maintain this structure at appropriate breakpoints. Deduct 5 points if even one section has incorrect layout, 3 points if the layout breaks on common device sizes, and 2 points if there are significant spacing issues between the image and text areas. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Does the content effectively introduce the current development status of each robot category?",
+      "description": "Assess whether the text for each section provides substantive information about the current development status of robot dogs, industrial robots, and humanoid robots. The content should be informative, relevant to a technology festival context, and include key technical details or advancements. Deduct 3 points per section if content is generic/placeholder text, 2 points per section if content lacks technical depth, and 5 points if content is completely unrelated to robot technology. 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, varying screen sizes, text overflow, etc.) and provide appropriate fallbacks or responsive solutions. Code with strong robustness should include alt text for images, handle text overflow gracefully, and adapt to different viewport sizes. Give 10 points for comprehensive error handling and responsiveness, 5 points for partial implementation, and 0 points if no robustness measures are implemented.",
+      "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 robot demonstrations 2. Animated technology illustrations 3. Theme toggle between light/dark mode 4. Accessibility features beyond basic requirements). 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 carousel scripts) 2. Function modules unrelated to the science and technology festival theme 3. Fancy effects that affect performance (e.g., excessive animations or effects that slow page loading). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core presentation is interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating HTML structure, CSS styling, and JavaScript functionality), code organization, and best practices. Deduct 5 points if inline styles are overused; deduct 5 points if JavaScript is not externalized or properly structured; deduct 5 points if the HTML structure is not semantic or contains deprecated elements. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching appropriate for a tech festival (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) Image scrolling timing is appropriate (not too fast or slow) 2) Transition animations are controlled between 300-500ms 3) Clear visual indicators for interactive elements. Deduct 5 points for abrupt transitions between images, 3 points for lack of loading states, and 5 points for confusing navigation controls. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Education/Learning",
+  "difficulty": "easy"
+}

package/library/web_applications-education_learning/chinese-chess-commentary-journey-west-style.json

@@ -0,0 +1,68 @@
+{
+  "index": 410,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to make the generated code executable for display. Write me a Chinese Chess commentary mini-program in HTML that can interpret input move notations with a colloquial language style inspired by \"Journey to the West.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Chinese Chess board visualization implementation",
+      "description": "Evaluate whether the HTML/CSS implementation accurately renders a standard xiangqi (Chinese Chess) board with proper piece representations. Check if the board follows the traditional 9×10 grid with river boundary, and if pieces are visually distinguishable (red vs. black sides). Score 0 if the board is missing or fundamentally incorrect, 5 if basic structure exists with minor issues, and 10 if the board is professionally implemented with proper Chinese characters for pieces.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Move notation parsing accuracy",
+      "description": "Review the code's ability to interpret standard Chinese Chess algebraic notation (e.g., '炮二平五', '马八进七'). Test with various move types including special cases like piece captures. Deduct 3 points if it only handles basic moves, 5 points if it fails on ambiguous notations (when two identical pieces could make the same move), and 7 points if it cannot interpret traditional Chinese notation formats. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "'Journey to the West' commentary style implementation",
+      "description": "Assess whether the commentary system successfully incorporates the colloquial style and character references from 'Journey to the West'. Check for varied commentary that includes recognizable phrases from characters like Sun Wukong, Zhu Bajie, and Tang Sanzang. Score 0 if no stylistic elements are present, 5 if style appears but is inconsistent or repetitive, and 10 if the commentary cleverly integrates authentic character voices with chess strategy observations.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Move validation and game rules enforcement",
+      "description": "Evaluate whether the code properly validates moves according to Chinese Chess rules (including piece-specific movement patterns, check conditions, and illegal moves). Test with edge cases like flying generals or restricted palace movements. Deduct 5 points if basic movement validation is missing, 3 points if special rules are not enforced, and 2 points if the checking mechanism is incomplete. 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 move notations, illegal moves, out-of-sequence inputs, etc.) and provide friendly error messages in the 'Journey to the West' style. 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. Animation of pieces with 'Journey to the West' character resemblances 2. Sound effects matching the commentary style 3. Special visual effects for important moves like checkmate). 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 move validation methods) 2. Function modules unrelated to Chinese Chess or 'Journey to the West' theme 3. Fancy effects that affect performance (e.g., excessive animations that slow down the program). 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 game logic/view/commentary generation 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 the code lacks proper commenting 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 traditional Chinese aesthetic principles while remaining functional: 1) Appropriate use of colors (red and black theme with complementary accents) 2) Proper layout spacing (clear separation between board and commentary) 3) Professional font system (traditional Chinese calligraphy for pieces, readable font for commentary). Deduct 3 points for each crowded visual element, 5 points for inconsistent visual theme, and 5 points for poor readability. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the interaction design meets user expectations: 1) Commentary updates immediately after move input 2) Clear visual feedback when moves are executed or rejected 3) Intuitive input method for move notation. Deduct 5 points if commentary delays exceed 300ms, 3 points if move execution lacks visual feedback, and 5 points if the input mechanism is confusing or counterintuitive. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Education/Learning",
+  "difficulty": "medium"
+}

package/library/web_applications-education_learning/class-schedule-draggable-courses.json

@@ -0,0 +1,68 @@
+{
+  "index": 1738,
+  "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. Design a webpage for my class schedule.\n\nRequirements: Courses should be draggable to corresponding time slots. If a time slot already contains a course, the existing course should be replaced.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the drag-and-drop functionality for courses fully implemented?",
+      "description": "Review whether the code accurately implements drag-and-drop interactions through HTML/JavaScript, including drag start/end events, visual feedback during dragging, and proper drop zone detection. Check if courses can be successfully moved from source to target time slots with smooth visual transitions. Score 0 if drag-and-drop is not implemented, 5 if only basic dragging works without proper drop handling, and 10 if all drag-and-drop interactions are fully functional with visual feedback.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the time slot replacement logic correctly implemented?",
+      "description": "Evaluate whether the replacement mechanism works correctly when dropping a course onto an occupied time slot. The existing course should be properly replaced without causing data loss or visual glitches. Check if the DOM updates correctly and state management handles replacements properly. Deduct 5 points if replacement causes visual artifacts, and 3 points if state inconsistencies occur. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the class schedule structure and layout properly designed?",
+      "description": "Check whether the schedule grid structure uses proper HTML semantic elements (table or CSS grid) with clear time slots and day columns. Evaluate if the layout is responsive and maintains proper proportions across different screen sizes. The schedule should display weekdays, time periods, and provide clear visual boundaries for each slot. Deduct 5 points if the grid structure is poorly implemented, and 3 points if responsiveness is lacking. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is comprehensive course data management implemented?",
+      "description": "Review whether the code includes proper course data structure with essential information (course name, instructor, duration, etc.) and provides mechanisms for adding, editing, or removing courses. Check if course data persists correctly during drag operations and maintains data integrity. Deduct 5 points if course data structure is incomplete, and 3 points if data persistence is not handled properly. Give 10 points if fully implemented with robust data management.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid drop targets, rapid consecutive drags, browser compatibility issues, etc.) and provide friendly error handling or recovery mechanisms. Code with strong robustness should effectively handle edge cases like dragging outside valid zones or handling touch events on mobile devices. Give 10 points for excellent robustness, 5 points for average handling, and 0 points if no exception handling exists.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that enhance user experience?",
+      "description": "Check whether the code includes thoughtful features that improve usability (e.g., 1. Auto-save schedule changes to localStorage 2. Color-coding courses by subject/priority 3. Time conflict warnings 4. Schedule export functionality 5. Undo/redo operations). Add 2-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 drag handlers for the same functionality) 2. Function modules unrelated to schedule management (e.g., built-in calculator or weather widget) 3. Overly complex animations that affect drag performance. Deduct 3 points for each redundancy found, and directly deduct 10 points if core schedule functionality is compromised by unnecessary features.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (separating drag logic, schedule rendering, and data management), code organization, and maintainability. Check for proper event listener management, memory leak prevention, and clean separation of concerns. Deduct 5 points if global state pollution is found or no design patterns are used; deduct 5 points if code duplication rate is high (over 30%); deduct 3 points if event listeners are not properly cleaned up. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface design meet professional standards?",
+      "description": "Evaluate whether the schedule design follows modern UI principles: 1) Clear visual hierarchy with proper contrast between time slots and courses 2) Consistent spacing following 8px grid system 3) Professional typography (readable font sizes ≥ 12px for course text) 4) Intuitive color scheme distinguishing different course types. Deduct 3 points for each cramped visual element, 5 points for poor color contrast affecting readability, and 5 points for inconsistent styling. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Are the drag interactions smooth and intuitive?",
+      "description": "Judge whether drag interactions provide excellent user feedback: 1) Immediate visual response on drag start (≤50ms) 2) Clear drop zone highlighting during drag-over 3) Smooth animation transitions (200-300ms) 4) Proper cursor changes and visual cues 5) Touch device compatibility. Deduct 5 points for each missing interaction feedback, 3 points for choppy animations during dragging, and 5 points if drag operations feel unresponsive or confusing. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Education/Learning",
+  "difficulty": "easy"
+}

package/library/web_applications-education_learning/classroom-info-maintenance-interface.json

@@ -0,0 +1,68 @@
+{
+  "index": 897,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate, professional responses. Be careful to ensure that the generated code is executable for demonstration. Create a classroom information maintenance interface, including classroom name, description, class occupancy times (various time slots each week), names of occupying courses, and teacher information. Include functions such as adding, modifying, list viewing, detailed viewing, etc., forming several HTML pages.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the classroom information data model well-designed?",
+      "description": "Review whether the code implements a comprehensive data model for classrooms that includes all required fields (name, description, weekly time slots, course names, teacher information). Check for proper data types, validation rules, and relationships. Score 0 if missing critical fields, 5 if basic structure is there but incomplete, 10 if the model is complete with proper validation and relationships.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are all CRUD operations fully implemented?",
+      "description": "Evaluate whether the code properly implements all required functions: adding new classrooms, modifying existing ones, listing all classrooms, and viewing classroom details. Check if each operation includes proper form validation, error handling, and success feedback. Deduct 3 points for each missing operation, 2 points for incomplete implementation per operation. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the time slot management system properly implemented?",
+      "description": "Examine the implementation of the weekly time slot system. Check for proper handling of time conflicts, overlapping schedules, visual representation of occupied vs. available times, and intuitive time selection UI. Deduct 5 points if conflict detection is missing, 3 points if the time representation is confusing, and 5 points if bulk time slot operations aren't supported. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the multi-page navigation and flow logical?",
+      "description": "Assess whether the multiple HTML pages work together as a cohesive system. Check for consistent navigation between pages, proper state preservation when moving between pages, breadcrumbs or other navigation aids, and logical workflow for common tasks. Deduct 5 points if navigation is confusing/missing, 3 points if state is lost between pages, and 3 points if the workflow requires excessive clicks. 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 form input, duplicate classroom names, conflicting time slots, 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. Calendar visualization of classroom usage 2. Export to PDF/Excel functionality 3. Search/filter capabilities for finding available classrooms). 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 forms for the same operation) 2. Function modules unrelated to classroom management (e.g., a built-in chat system) 3. Fancy effects that affect performance (e.g., excessive animations). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating data/view/controller layers), code organization, reusable components, and maintainability. Deduct 5 points if global variables are overused or appropriate design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there's no separation of concerns. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching (no more than 3 primary colors) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional 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-Education/Learning",
+  "difficulty": "medium"
+}

package/library/web_applications-education_learning/classroom-random-name-calling-website.json

@@ -0,0 +1,68 @@
+{
+  "index": 744,
+  "question": "You are a coding expert. Please use your professional knowledge to generate accurate and professional responses. Ensure that the generated code can be executed and displayed. Help me create a classroom random name-calling website in HTML format. Double-click to run. After completion, self-check the code to make sure it can still run when saved as an HTML file on the desktop.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the random name-calling core functionality properly implemented?",
+      "description": "Check if the code implements the fundamental random selection mechanism including proper randomization algorithm (e.g., Fisher-Yates shuffle), handling edge cases like empty lists, and preventing repetitive selections in consecutive calls. Score 0 if core randomization is missing, 5 if basic randomization exists but with flaws, and 10 if it includes advanced features like weighted selection or history tracking.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Does the application provide complete name management functionality?",
+      "description": "Evaluate whether the code includes features for adding, editing, removing names, and saving the name list (using localStorage or other persistence methods). Score 3 points for basic addition/removal, 3 points for editing capabilities, and 4 points for proper persistence between sessions. Deduct all points if names cannot be managed at all.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the classroom context appropriately represented in the interface?",
+      "description": "Assess whether the UI reflects a classroom environment with relevant elements (e.g., student roster visualization, classroom theme, teacher controls). Score 0 if there's no classroom context at all, 5 if basic theming exists, and 10 if the interface thoughtfully incorporates classroom metaphors and educational design principles.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Does the application work in a standalone HTML file as required?",
+      "description": "Verify that the code is self-contained in a single HTML file with inline JavaScript and CSS, with no external dependencies that would prevent it from running locally. Check for proper script loading sequence and DOM-ready handlers. Deduct all 10 points if external resources are required; deduct 5 points if the code runs only in specific environments.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as empty name lists, invalid inputs, 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. Animation when selecting names 2. Sound effects for selection 3. Statistics tracking of selection frequency). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple ways to select random names) 2. Function modules unrelated to classroom name-calling (e.g., a built-in calculator) 3. Fancy effects that affect performance (e.g., excessive animations that slow down the page). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating UI/logic/data management), code readability, and appropriate use of JavaScript patterns. Deduct 5 points if global namespace pollution is found; deduct 3 points if the code duplication rate is too high; deduct 2 points if variable/function naming is unclear or inconsistent. 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 animations, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Education/Learning",
+  "difficulty": "easy"
+}

package/library/web_applications-education_learning/classroom-roll-call-program-html.json

@@ -0,0 +1,68 @@
+{
+  "index": 1341,
+  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable and displayable. Please write a classroom roll call program in HTML language, which includes features such as flashing name display, roll call, and \"next\" function.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the basic roll call function fully implemented?",
+      "description": "Review whether the code implements the core roll call functionality, including student name storage, random selection, and display mechanism. Score 0 if the roll call system is not implemented, 5 if only basic name display is available, and 10 if complete with student management and random selection algorithms.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the flashing name display feature properly implemented?",
+      "description": "Check if the code includes a visually engaging flashing effect for displaying selected names. Evaluate the animation timing (should be between 200-600ms for optimal visibility), contrast ratio (minimum 4.5:1 for accessibility), and whether it gracefully handles different name lengths. Score 3 points for basic animation, 7 points for proper timing and accessibility, and 10 points for fully optimized implementation.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the 'next' function properly implemented?",
+      "description": "Assess whether the 'next' function correctly selects a new student without repetition until all students have been called. Check if it has proper state management to track called students, handles edge cases (empty list, last student), and provides clear feedback when the list is exhausted. Deduct 5 points if it allows immediate repetitions, 3 points if it lacks proper completion indication.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is class roster management functionality included?",
+      "description": "Evaluate whether the program allows adding, editing, and removing students from the roll call list. Check if it includes data persistence (localStorage or similar), input validation, and duplicate prevention. Score 3 points for basic list editing, 7 points for validation and proper UI integration, 10 points for complete management with persistence.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as empty roster, rapid clicking, browser refresh, 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. Attendance tracking statistics 2. Customizable roll call animations/sounds 3. Timer for student response). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple ways to select students) 2. Function modules unrelated to roll call (e.g., a built-in calculator) 3. Fancy effects that affect performance (e.g., excessive animations). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating UI/logic/data layers), code reusability, and maintainability. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the code lacks 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 clicking, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Education/Learning",
+  "difficulty": "easy"
+}

package/library/web_applications-education_learning/classroom-seating-chart-performance-groups.json

@@ -0,0 +1,68 @@
+{
+  "index": 1289,
+  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable for demonstration. I am a teacher, please help me write an HTML program that can create a classroom seating chart, divided into 4 groups based on performance levels: Excellent, Good, Satisfactory, and Unsatisfactory. Each group has two rows, with 10 people on the right side, and 12 people each in the other three groups.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the classroom seating chart correctly implemented with the required group structure?",
+      "description": "Examine if the code creates a classroom layout with 4 distinct performance groups (Excellent, Good, Satisfactory, Unsatisfactory), where Excellent has 10 students (two rows of 5), and the other three groups have 12 students each (two rows of 6), totaling 46 students. Check if groups are visually distinct. Score 0 if structure is incorrect, 5 if basic structure exists but with count/arrangement errors, 10 if perfectly implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Does the code implement performance level differentiation?",
+      "description": "Evaluate whether students in different performance levels are clearly distinguished visually (through colors, borders, icons, or labels). Check if the performance level grouping is easily identifiable. Deduct 5 points if the visual distinction between groups is minimal or confusing, and 3 points if the performance level indicators are not intuitive. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the student identification system well-implemented?",
+      "description": "Assess whether each seat has a unique identifier or student representation. Check if the identifiers are easily readable, whether there's a way to add student names or IDs, and whether the student data structure is well-designed. Deduct 5 points if students cannot be uniquely identified, and 3 points if the identification system is rudimentary. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is there an interactive component for managing the seating arrangement?",
+      "description": "Verify if the code includes features for interactivity, such as drag-and-drop functionality to rearrange seats, editing student information, swapping seats, or saving/loading configurations. Deduct 5 points if there's no interactivity at all, 3 points if interactivity is limited to basic functions. 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 browser resizing, missing student data, improper user inputs, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Attendance tracking functionality 2. Performance statistics visualization 3. Randomized seating generator). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple ways to edit student information) 2. Function modules unrelated to seating charts (e.g., a built-in calculator) 3. Fancy effects that affect performance (e.g., unnecessary animations). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating data/view/control layers), code organization, and reusable components. Deduct 5 points if global variable pollution is found or if proper event handling is absent; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if CSS/HTML/JS are not properly separated. 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 manipulation, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Education/Learning",
+  "difficulty": "medium"
+}

package/library/web_applications-education_learning/code-editor-with-live-preview.json

@@ -0,0 +1,68 @@
+{
+  "index": 785,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure that any code you provide is executable for demonstration purposes. I need a webpage with the following functionality: an input box where I can enter code, and after confirmation, a preview area below the input box that displays the functionality of my code, such as CSS styling, JavaScript interactions, etc.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the code input mechanism properly implemented?",
+      "description": "Check if the code implements a robust text input area that can handle various programming languages (HTML, CSS, JavaScript) with proper sizing and scrolling capabilities. The input area should preserve code formatting, offer ample space (minimum 15 lines visible), and maintain cursor position after actions. Score 0 if no input mechanism exists, 5 if basic textarea is implemented without code formatting, and 10 if a fully-featured code editor (with syntax highlighting or code formatting) is implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the preview rendering system functional and secure?",
+      "description": "Evaluate whether the preview system can properly render HTML/CSS/JavaScript without security vulnerabilities. It should use proper sandboxing techniques (iframe with sandbox attributes or CSP restrictions) to prevent XSS attacks. Preview should update dynamically or have a clear execution trigger. Deduct 5 points if no sandboxing is implemented, 3 points if only partial code types are supported. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is there proper error handling and feedback?",
+      "description": "Analyze whether the application provides clear error messages for syntax errors, execution errors, or other issues. The system should catch errors gracefully without crashing the main page and display meaningful error messages that help identify the problem location. Deduct 5 points if errors crash the entire application, 3 points if errors are caught but with generic messages. Give 10 points for comprehensive error catching with detailed feedback.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Does the preview update mechanism work efficiently?",
+      "description": "Check whether the preview updates in a sensible manner - either automatically with appropriate debouncing (300-500ms delay) or via an explicit 'Run/Preview' button that's clearly visible. The update process should not cause page jumps or loss of user input focus. Deduct 5 points if updates cause visible page reloads, 3 points if there's significant delay (>1s) for simple code. 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 extremely large inputs, infinite loops, memory-intensive 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. Multiple tabs for different code examples 2. Code saving/sharing functionality 3. Theme switching for the editor/preview). 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 preview mechanisms) 2. Function modules unrelated to code editing/preview (e.g., unrelated tools or widgets) 3. Fancy effects that affect performance (e.g., excessive animations). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating editor/preview/control logic), event handling patterns, and code organization. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there's no clear separation between UI and business 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 after-images during fast sliding, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Education/Learning",
+  "difficulty": "easy"
+}