@getollie/cli 0.0.5 → 0.2.0

package/library/web_applications-communication/gradio-dynamic-dark-mode-themes.json

@@ -1,68 +0,0 @@
-{
-  "index": 415,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to ensure that the code you generate can be executed and displayed. How can I add two menu items in Gradio, one for dynamically switching dark mode, and another for dynamically switching themes?",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Are the menu items correctly implemented in Gradio?",
-      "description": "Review whether the code properly implements menu items using Gradio's API components. Check for correct use of gr.Dropdown, gr.Radio, or custom components for theme selection. Score 0 if no menu implementation, 5 if basic implementation without proper styling, 10 if fully implemented with proper Gradio component integration.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the dark mode switching functionality working correctly?",
-      "description": "Verify the dark mode toggle functionality works dynamically without page refresh. Check for proper event handling that applies CSS changes or theme classes. Examine if the implementation uses Gradio's built-in theme methods or custom JavaScript. Score 0 if not implemented, 5 if implemented but requires page refresh, 10 if fully dynamic with smooth transition effects.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the theme switching functionality implemented properly?",
-      "description": "Evaluate if multiple themes can be selected and applied dynamically. Check if the code includes proper theme definitions or uses Gradio's built-in themes. Verify the theme switcher updates all UI elements consistently. Score 0 if theme switching is missing, 5 if only basic theme changes work, 10 if comprehensive theme switching with consistent application across the interface.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is there proper state management for persistent theme preferences?",
-      "description": "Check if the code maintains user theme preferences across sessions using local storage, cookies, or server-side storage. Verify if theme state is properly synchronized between client and server components. Score 0 if no state persistence, 5 if basic persistence without synchronization, 10 if complete persistence mechanism with proper synchronization.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as browser incompatibilities, CSS conflicts, theme application failures) and provide friendly error handling or fallback 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. Theme preview thumbnails 2. Automatic time-based theme switching 3. Custom theme creation interface). 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 theme switching methods) 2. Function modules unrelated to theming (e.g., unnecessary UI components) 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 from theme logic), code reusability, and maintainability. Deduct 5 points if global variable pollution is found or proper encapsulation is not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the code is not structured logically for easy maintenance. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the menu items follow modern design principles: 1) Visually distinguishable from other UI elements 2) Proper spacing and positioning in the interface 3) Professional typography and iconography. Deduct 3 points for poor visual hierarchy, 5 points for inconsistent styling with the rest of the interface, and 5 points for poor accessibility (e.g., low contrast). The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the theme switching conforms to human perception characteristics: 1) Theme changes apply without visible flickering 2) Transition effects between themes are smooth (200-400ms) 3) Clear visual feedback when selecting themes. Deduct 5 points for jarring theme transitions, 3 points for delayed application of theme changes, and 5 points for lack of visual feedback during selection. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Communication",
-  "difficulty": "medium"
-}

package/library/web_applications-communication/h5-java-user-login-interface.json

@@ -1,68 +0,0 @@
-{
-  "index": 899,
-  "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. I need a user login interface based on H5 and Java interaction.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the front-end login interface fully implemented with HTML5?",
-      "description": "Review whether the code properly implements a responsive login form with HTML5 features (such as form validation, placeholder attributes, and semantic elements). Check if it includes essential login fields (username/email, password) and appropriate input types with attributes for validation. Score 0 if there's no HTML5 implementation, 5 if basic login fields exist but lack proper validation, and 10 if the implementation is complete with modern HTML5 features.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the CSS styling professional and responsive?",
-      "description": "Evaluate if the CSS implementation follows responsive design principles with media queries for different devices. Check if it includes modern styling techniques (flexbox/grid, transitions, etc.) and handles different screen sizes properly. Deduct 5 points if the interface doesn't adapt to mobile screens, 3 points if there are clear styling inconsistencies, and 2 points if accessibility features (focus states, contrast ratios) are missing. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the client-side validation logic properly implemented?",
-      "description": "Check whether JavaScript validation is implemented for all form inputs before submission. Verify that it includes real-time validation feedback, password strength indicators, and proper error handling. Deduct 5 points if validation only happens on submission without real-time feedback, 3 points if error messages are not specific or helpful, and 2 points if password strength requirements aren't enforced. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the Java backend authentication system properly designed and secured?",
-      "description": "Evaluate the Java backend code for secure authentication practices including password hashing (using algorithms like bcrypt/PBKDF2), protection against SQL injection, and proper session management. Check if it implements token-based authentication (JWT/OAuth). Deduct 5 points if passwords are stored in plaintext/weak hashing, 5 points if there's no protection against brute force attacks, and 3 points if secure session handling is missing. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as network failures during login, invalid inputs, system unavailability, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should handle connection timeouts, server errors, and input validation gracefully. Give 10 points if all edge cases are handled, 5 points if only basic error handling exists, and 0 points if errors cause the system to crash.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the login system includes surprise features that enhance the experience (e.g., 1. Biometric authentication options 2. Social login integration 3. Two-factor authentication 4. Remember me functionality with secure cookie handling 5. Passwordless login options). 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 validation logic (e.g., duplicate validation in both HTML5 attributes and JavaScript) 2. Unnecessary API calls or data processing unrelated to authentication 3. Excessive animations or effects that slow down the login process. Deduct 3 points for each redundancy found, and directly deduct 10 points if the core authentication function is compromised by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating UI/business logic/API layers), appropriate design patterns, consistent error handling, and proper documentation. On the Java side, check for proper dependency injection, service-repository pattern, and exception handling. Deduct 5 points if global variables are overused; deduct 5 points if there's significant code duplication; deduct 5 points if logging is insufficient for debugging. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the login UI follows modern design principles: 1) Cohesive color scheme (no more than 3 primary colors) 2) Proper layout with adequate white space (following the 8px grid system) 3) Professional typography (readable font sizes ≥ 14px, line height over 1.5 times) 4) Clear visual hierarchy guiding users through the login flow. Deduct 3 points for cluttered design, 5 points for jarring color combinations, and 5 points for poor form layout. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the login interaction conforms to user expectations: 1) Login button shows loading state within 100ms of click 2) Form validation feedback appears immediately after input 3) Error messages are clearly displayed near the relevant fields 4) Successful login provides visual confirmation before redirect. Deduct 5 points for each interaction without feedback, 3 points for delayed responses over 300ms, and 5 points for confusing navigation after failed login attempts. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Communication",
-  "difficulty": "medium"
-}

package/library/web_applications-communication/h5-qr-code-chat-room.json

@@ -1,68 +0,0 @@
-{
-  "index": 238,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate, professional responses. Be sure to make the generated code executable for demonstration. Help me create an H5 open chat room where anyone can scan a QR code to enter and chat by sending text messages and images.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the HTML5 chat room interface fully implemented?",
-      "description": "Review whether the code implements a complete chat interface with message display area, input field, send button, and image upload functionality. Check if messages are properly formatted and displayed with timestamps and user identifiers. Score 0 if the core interface elements are missing, 5 if basic messaging UI is implemented, and 10 if all chat features including text, images, timestamps, and user identification are fully included.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the QR code entry mechanism properly implemented?",
-      "description": "Evaluate whether the code generates a proper QR code that contains the room URL, can be displayed clearly on various devices, and handles scanning properly. Check if the QR code generation uses a reliable library and if the generated code scales without degradation. Deduct 5 points if the QR code doesn't work across different devices, and 3 points if there's no validation mechanism to ensure the QR code contains proper data. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is real-time communication properly implemented?",
-      "description": "Check whether the implementation uses WebSockets or a similar technology for real-time messaging. Verify that messages appear instantly for all users without manual refresh and that the connection handles disconnections gracefully. Deduct 5 points if there's noticeable delay (>500ms), 3 points if reconnection logic is missing, and 5 points if the system doesn't handle multiple concurrent users properly. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the image sharing functionality complete and secure?",
-      "description": "Evaluate the image upload and display features, including preview before sending, proper sizing/compression of images, supported formats, and security measures. Check if the code includes validation for file types and sizes, and if images are displayed properly in the chat. Deduct 5 points if there's no file type validation, 3 points if images aren't properly resized for mobile, and 5 points if there's no progress indicator for uploads. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as network interruption, invalid file uploads, XSS attacks, 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. Message reactions/emojis 2. Read receipts 3. Typing indicators 4. Voice messages 5. Custom themes). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple message sending mechanisms) 2. Function modules unrelated to chat (e.g., a built-in game) 3. Fancy effects that affect performance (e.g., excessive animations that slow down messaging). 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/messaging logic/networking layers), code organization, and proper error handling. 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 security considerations (like sanitizing inputs) are missing. 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) 4) Mobile-responsive design that works on various screen sizes. 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) Message sending feedback delay ≤ 100ms 2) Smooth scrolling when new messages appear 3) Clear visual focus guidance 4) Intuitive image upload process. Deduct 5 points for each operation without feedback, 3 points for jerky animations when messages arrive, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Communication",
-  "difficulty": "medium"
-}

package/library/web_applications-communication/hikvision-vue-realtime-monitoring-video-page.json

@@ -1,68 +0,0 @@
-{
-  "index": 763,
-  "question": "You are a code expert, please utilize your professional knowledge to generate accurate and professional responses. Make sure the code you generate is executable for demonstration purposes. Develop a real-time monitoring video page with Hikvision based on the PDF development documentation in conjunction with Vue.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the Hikvision SDK integration correctly implemented?",
-      "description": "Review whether the code correctly integrates Hikvision Web SDK according to the official PDF documentation, including proper initialization of video plugins, camera connection establishment, and stream decoding capabilities. Check if the implementation handles different video formats (H.264/H.265) and supports multiple resolution options. Score 0 if SDK is not properly integrated, 5 if basic video display works but lacks format support, and 10 if all streaming protocols and formats are fully supported with proper error handling.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the real-time video streaming functionality fully operational?",
-      "description": "Evaluate whether the real-time video streaming maintains stable connection with minimal latency (<500ms), includes proper buffer management to prevent video freezing, and implements automatic stream quality adjustment based on network conditions. Check if the system supports multiple concurrent video streams and handles stream switching seamlessly. Deduct 5 points if latency exceeds 1 second, deduct 3 points if buffer overflow occurs during network fluctuations. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the Vue.js architecture properly designed with component modularity?",
-      "description": "Check whether the Vue.js implementation follows best practices with proper component separation (video player, control panel, device management), state management using Vuex/Pinia, and reactive data binding for real-time status updates. Evaluate if the component lifecycle methods properly handle video resource allocation and cleanup. Deduct 5 points if components are tightly coupled, deduct 3 points if memory leaks occur during component destruction. Award 10 points for clean modular architecture.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Are the monitoring control features comprehensively implemented?",
-      "description": "Assess whether essential monitoring controls are implemented including PTZ (Pan-Tilt-Zoom) operations, video recording start/stop, snapshot capture, playback functionality, and device status monitoring. Check if the interface provides intuitive controls for brightness/contrast adjustment and supports preset position management. Deduct 3 points for each missing core control feature, deduct 5 points if PTZ operations have noticeable delays. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as network disconnection, device offline, authentication failures, browser compatibility issues, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should implement automatic reconnection, graceful degradation, and clear error messaging, 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 monitoring experience (e.g., 1. AI-powered motion detection alerts 2. Multi-screen video wall layout 3. Real-time video analytics overlay 4. Mobile-responsive touch controls 5. Video export with timestamp watermarks). 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 video player instances for same stream) 2. Function modules unrelated to video monitoring (e.g., built-in chat system) 3. Heavy visual effects that impact video performance (e.g., complex CSS animations during streaming). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core video functionality is interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (separating video streaming/UI components/API layers), TypeScript usage for type safety, proper error boundaries, and build optimization for video streaming performance. Deduct 5 points if global state pollution is found or Vue composition API is not properly utilized; deduct 5 points if bundle size is not optimized for video streaming; deduct 5 points if no proper testing setup for video components. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional monitoring system standards?",
-      "description": "Evaluate whether the design follows professional monitoring interface principles: 1) Dark theme optimized for long-term viewing 2) High contrast elements for critical controls 3) Proper video aspect ratio maintenance 4) Professional control panel layout with logical grouping. Deduct 3 points for each poorly positioned control element, 5 points for eye-straining color schemes inappropriate for monitoring, and 5 points for video distortion or improper scaling. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the video controls and interactions meet professional monitoring standards: 1) PTZ control response time ≤ 200ms 2) Video switching without black screen flicker 3) Control panel overlay without interfering video viewing 4) Smooth zoom and pan operations without stuttering. Deduct 5 points for each laggy control response, 3 points for video artifacts during operation transitions, and 5 points for unresponsive touch/click areas in video player. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Communication",
-  "difficulty": "hard"
-}

package/library/web_applications-communication/homepage-appointment-booking-store-management.json

@@ -1,68 +0,0 @@
-{
-  "index": 927,
-  "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 display purposes. Help me create code for a homepage that includes immediate appointment booking, store projects, package management, as well as store information, address, and phone number.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the appointment booking system fully implemented?",
-      "description": "Review whether the code accurately implements an appointment booking form with date/time selection, service type options, and validation. Check if the system includes confirmation emails or SMS notifications for appointments. Score 0 if booking functionality is missing, 5 if basic form exists without validation, and 10 if complete with server-side validation and confirmation system.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the project/portfolio showcase feature properly implemented?",
-      "description": "Evaluate whether the project display includes filtering options, detailed view functionality, and responsive image galleries. Check if projects can be categorized and if there's pagination or infinite scroll for large collections. Deduct 5 points if images aren't optimized, 3 points if filtering is missing. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the package management system comprehensive?",
-      "description": "Check whether the system allows browsing different service packages, with clear pricing, feature comparison, and the ability to select/customize packages before booking. Deduct 5 points if pricing information is static/non-interactive, 3 points if package comparison is missing. Award 10 points for a fully interactive system with package customization options.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the store information section complete and accessible?",
-      "description": "Assess if the code implements store details (name, description, hours), contact information (phone, email), address with interactive map integration, and possibly social media links. Deduct 5 points if the map is static/missing, 3 points if business hours are not clearly displayed. 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 form validation errors, failed API calls, slow network connections, 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 availability indicators 2. Virtual tour of facilities 3. AI-powered chat assistance for booking). 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 contact forms) 2. Function modules unrelated to the store's services (e.g., a built-in game) 3. Fancy effects that affect performance (e.g., excessive animations that slow page loading). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating UI/business logic/data layers), component reusability, and build process 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 build process is not automated or lacks optimization. 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-Communication",
-  "difficulty": "medium"
-}

package/library/web_applications-communication/html-javascript-real-time-chat-system.json

@@ -1,68 +0,0 @@
-{
-  "index": 61,
-  "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.\n\nPlease implement a real-time chat system using HTML and JavaScript.\n\n**Task**: Create a real-time chat system where players can chat and communicate with other players in the game.\n\n**Hint**: Use WebSocket or other real-time communication technologies to implement the chat functionality, and set up a chat interface with message filtering.\n\nInclude comments in your code so other developers can understand your implementation process.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the real-time chat system fully implemented?",
-      "description": "Review whether the code implements a complete chat system with message sending and receiving functionality. Check if the interface includes message input, display area, and send button. Score 0 if core chat functionality is missing, 5 if basic messaging works but lacks real-time updates, and 10 if messages appear instantly without page refresh.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the WebSocket or real-time communication implementation correct?",
-      "description": "Verify if WebSocket or alternative real-time technologies (e.g., Socket.io, Server-Sent Events) are properly implemented. Check connection establishment, message handling, reconnection logic, and error handling. Deduct 5 points if the connection isn't maintained properly, 3 points if reconnection logic is missing, and 2 points if there's no error handling. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the message filtering functionality implemented?",
-      "description": "Examine whether the code includes message filtering capabilities such as profanity filters, spam prevention, or content moderation. Check if users can filter messages by type/sender. Deduct 5 points if no filtering exists, 3 points if basic filtering lacks customization options. Give 10 points if comprehensive filtering with multiple options is implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the chat interface user-friendly and functional?",
-      "description": "Evaluate if the chat interface includes essential elements like message history, timestamps, user identification, and message status indicators. Check for features like message formatting, emoji support, or file sharing. Deduct 3 points for each missing essential element, and award up to 10 points for a complete, intuitive interface.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as network disconnections, message delivery failures, invalid 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. Message reactions/emojis 2. Read receipts 3. Typing indicators 4. Voice/video messaging 5. Chat rooms/channels). Add 2 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 message sending logics) 2. Function modules unrelated to chat (e.g., a built-in game within the chat) 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/network/message handling layers), code organization, comment quality, and variable naming. 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 comments are insufficient or misleading. 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) Message sending feedback delay ≤ 100ms 2) New message notification animation duration controlled between 300-500ms 3) Clear visual focus guidance. Deduct 5 points for operations without feedback, 3 points for messages appearing without smooth transitions, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Game Development-Casual",
-  "difficulty": "easy"
-}

package/library/web_applications-communication/html-simple-login-page.json

@@ -1,68 +0,0 @@
-{
-  "index": 1819,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to provide executable code whenever possible. Write a simple login page using HTML.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the basic login form structure properly implemented?",
-      "description": "Check if the HTML contains a proper form element with method and action attributes, input fields for username/email and password, and a submit button. Form must have appropriate semantic structure. Deduct 3 points for missing form tags, 2 points for missing method/action attributes, and 2 points for using non-semantic elements. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are all essential input fields and their attributes correctly implemented?",
-      "description": "Verify that username/email and password fields use appropriate input types (text/email and password), have name attributes, placeholder text, and required attributes. Each field should also have proper labels associated through 'for' attributes or nested structure. Deduct 2 points for each missing input type, 2 points for missing labels, and 2 points for missing required attributes. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is form validation implemented?",
-      "description": "Assess if client-side validation is implemented using HTML5 attributes (required, pattern, minlength, etc.) or JavaScript. Check for email format validation and password complexity requirements. Score 10 points for comprehensive validation with error messages, 5 points for basic HTML5 validation attributes only, and 0 points if validation is completely missing. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Are CSRF protection and secure form submission implemented?",
-      "description": "Check for CSRF token implementation, secure form submission using HTTPS (action starts with 'https://'), and proper method (POST for login forms). Also check for autocomplete attributes and prevention of credential exposure. Deduct 3 points for missing CSRF protection, 3 points for insecure HTTP submission, and 4 points for using GET method. 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 form validation failures, network errors, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Social login options 2. Remember me functionality 3. Password strength indicator 4. Two-factor authentication option). 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. Redundant form fields not needed for login 2. Excessive script imports unrelated to login functionality 3. Unnecessary complex structures that could be simplified. Deduct 3 points for each redundancy found, and directly deduct 10 points if the core login function is complicated by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review code organization (HTML structure, script, and style separation), naming conventions, and overall code cleanliness. Deduct 3 points if inline styles are excessively used; deduct 3 points if JavaScript is not properly separated or organized; deduct 4 points if the HTML structure lacks semantic meaning or proper indentation. 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) Clean, well-spaced form layout 2) Consistent form styling (input sizes, button styles) 3) Readable typography (font size ≥ 14px, sufficient contrast). Deduct 3 points for inconsistent styling, 3 points for poor spacing/alignment, and 4 points for accessibility issues (contrast, focus indicators). The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the user experience well-considered?",
-      "description": "Judge whether the login page considers UX best practices: 1) Clear error messages that appear near the relevant field 2) Logical tab order for keyboard navigation 3) 'Forgot password' link 4) Visual feedback on form submission. Deduct 2.5 points for each missing UX element. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Communication",
-  "difficulty": "easy"
-}

package/library/web_applications-communication/html-springboot-login-registration-button.json

@@ -1,68 +0,0 @@
-{
-  "index": 253,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure that the code you generate is executable and demonstrable. Implement HTML for a button that interacts with SpringBoot for login and registration.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the HTML for login/registration forms properly structured?",
-      "description": "Review whether the HTML implements proper semantic structure with appropriate form elements (input fields, labels, buttons), validation attributes (required, pattern, etc.), and accessibility features (aria-labels, tab indexes). Score 0 if forms are missing, 5 if basic forms exist but lack validation/accessibility, and 10 if forms are complete with all necessary elements and attributes.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are the client-side validation mechanisms implemented correctly?",
-      "description": "Check if JavaScript implements client-side validation for both login and registration forms (e.g., email format validation, password strength checks, matching password confirmation). Deduct 3 points if basic validations are missing, 3 points if real-time feedback is not provided, and 2 points if error messages are not user-friendly. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the API communication with SpringBoot properly implemented?",
-      "description": "Evaluate whether the JavaScript properly handles AJAX/fetch calls to SpringBoot endpoints, includes appropriate headers (Content-Type, CSRF tokens), handles responses correctly, and implements proper error handling. Deduct 5 points if no error handling exists, 3 points if CSRF protection is missing, and 2 points if response handling is inadequate. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the authentication flow and session management properly designed?",
-      "description": "Check whether the code implements proper authentication flow (JWT or session-based), handles login persistence, provides logout functionality, and manages authentication state. Deduct 3 points if token storage is insecure, 4 points if session expiration is not handled, and 3 points if authentication state updates are not reflected in the UI. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as network errors, server timeouts, validation failures, 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. Social login integration 2. Remember-me functionality 3. Multi-factor authentication). 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 validation implementations) 2. Function modules unrelated to authentication (e.g., unnecessary widgets) 3. Fancy effects that affect performance (e.g., heavy animations on form submission). 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/validation/API communication), code reusability, and implementation of design patterns. 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 error handling is 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 form design (consistent input sizes, clear focus states, proper alignment). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for inconsistent form element styling. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the form interactions conform to human perception characteristics: 1) Submit button feedback delay ≤ 100ms 2) Form state transitions (success/error) provide clear visual feedback 3) Loading states are properly indicated. Deduct 5 points for each operation without feedback, 3 points for jarring state transitions, and 5 points for no loading indicators during server communication. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Web Applications-Communication",
-  "difficulty": "hard"
-}