@getollie/cli 0.0.1

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

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

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

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

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

package/library/web_applications-communication/html-text-to-speech-with-rich-voice-features.json

@@ -0,0 +1,68 @@
+{
+  "index": 398,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Ensure that the code you generate is executable. Write an HTML text-to-speech program that categorizes voices by language, with a rich variety of voice options. Include support for downloading audio, pausing and resuming playback, and provide a good user interface and interaction experience. Use responsive design to adapt to different screen sizes.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the text-to-speech core functionality fully implemented?",
+      "description": "Evaluate whether the code correctly implements the Web Speech API or a similar TTS library to convert text to speech. Check if the speech synthesis includes essential controls (start, pause, resume, stop) and proper error handling. Score 0 if speech synthesis is not implemented, 5 if only basic functionality exists without proper controls, and 10 if all core TTS features work correctly.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Does the solution categorize voices by language effectively?",
+      "description": "Check if the implementation organizes available voices by language/locale and displays them in a user-friendly way. Evaluate whether users can easily filter and select voices by language group. Deduct 5 points if languages are not categorized at all, 3 points if categorization exists but is difficult to navigate. Full score requires clear language grouping with proper localized display names.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is voice variety and selection implemented correctly?",
+      "description": "Review if the code properly retrieves all available system voices and provides sufficient details about each voice (name, language, gender if available). Check if the selection mechanism allows easy switching between voices with immediate feedback. Deduct 5 points if voice options are limited without technical reason, 3 points if voice details are insufficient for informed selection.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is audio download functionality properly implemented?",
+      "description": "Assess whether the code includes a working mechanism to download the synthesized speech as an audio file (typically MP3 or WAV). Check if it handles longer texts by providing progress indicators during conversion and if filenames are appropriate. Deduct 5 points if download sometimes fails on longer texts, 3 points if the download exists but without proper file naming or format options.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as unsupported voices, browser compatibility issues, network interruptions, 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. Visualizing speech with waveforms 2. Speech rate/pitch adjustment sliders 3. Saving favorite voice settings 4. Text preprocessing for better pronunciation). 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 audio processing chains) 2. Function modules unrelated to text-to-speech (e.g., a built-in video player) 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 TTS logic/UI components/audio processing), error handling coverage, and cross-browser compatibility. 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 browser compatibility is not addressed. 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 responsive design properly implemented?",
+      "description": "Judge whether the interface adapts smoothly to different screen sizes: 1) Controls remain accessible and usable on mobile devices 2) No horizontal scrolling on standard screen sizes 3) Media queries properly handle breakpoints for desktop, tablet, and mobile. Deduct 5 points for each major responsive failure (e.g., unusable on mobile), 3 points for layout shifts during resize, and 3 points for touch targets smaller than 44px on mobile. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Communication",
+  "difficulty": "easy"
+}

package/library/web_applications-communication/implement-sso-page-auth-automatic-login-vue-router-vuex.json

@@ -0,0 +1,68 @@
+{
+  "index": 1158,
+  "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. Implement single sign-on (SSO), page authentication, and automatic login functionality based on Vue Router + Vuex.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the SSO authentication system properly implemented?",
+      "description": "Review the implementation of the Single Sign-On system. Check if it includes proper token management (JWT or OAuth), cross-domain authentication handling, and secure communication protocols (HTTPS). Verify if the code includes authentication endpoints integration, token validation logic, and proper error handling for authentication failures. Score 0 if SSO isn't implemented, 5 if basic authentication is present but lacks security features, and 10 if a complete, secure SSO implementation is provided.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the Vue Router authentication guard mechanism comprehensive?",
+      "description": "Evaluate the implementation of route guards (beforeEach, beforeResolve, etc.) to protect routes requiring authentication. Check if the code implements proper redirection logic for unauthenticated access attempts, handles role-based access control, and preserves the original navigation target after successful authentication. The implementation should prevent direct URL access to protected routes. Deduct 5 points if only basic route protection exists without proper redirection, 3 points if role-based permissions are missing. Full score for a complete navigation guard system with proper meta fields in route definitions.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the automatic login functionality correctly implemented?",
+      "description": "Check if the code implements persistent authentication through secure storage mechanisms (localStorage, cookies with proper flags, etc.). Verify the presence of token refresh logic, automatic login on page reload/revisit, and proper session timeout handling. The implementation should include initial auth state detection on application start. Deduct 5 points if token storage is insecure, 3 points if refresh tokens are not implemented, and 3 points if session expiration handling is absent. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the Vuex state management for authentication well-designed?",
+      "description": "Review the Vuex store implementation for authentication. Check if it includes proper authentication state management (user info, token storage, authentication status), dedicated mutations/actions for login/logout operations, and proper error state handling. Verify that the store integrates with the Vue Router for protected route navigation. Deduct 5 points if state management is incomplete, 3 points if authentication actions lack proper error handling, and 3 points if the store doesn't properly persist authentication state. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common authentication edge cases (token expiration during active use, network errors during authentication, concurrent login attempts, etc.) and provide friendly error prompts or recovery mechanisms. Check if error boundaries exist to prevent authentication failures from crashing the application. Code with strong robustness should handle these scenarios elegantly, 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 authentication experience (e.g., 1. Biometric authentication integration 2. Progressive authentication levels based on activity sensitivity 3. Transparent background token refresh without disrupting user experience). 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 authentication implementations (e.g., multiple token validation methods coexisting) 2. Function modules unrelated to authentication (e.g., excessive analytics in auth flow) 3. Unnecessary state updates that affect performance (e.g., excessive Vuex commits during authentication). 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 authentication services/store modules/UI components), unit test coverage for authentication logic, and proper code organization. Deduct 5 points if global state pollution is found or authentication logic is not properly encapsulated; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if proper security practices for authentication are not followed (e.g., storing sensitive data in plain text). The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the authentication UI meet professional design standards?",
+      "description": "Evaluate whether the authentication-related interfaces follow modern design principles: 1) Clean and focused login forms (minimal distractions) 2) Proper visual feedback for authentication states (loading, errors, success) 3) Professional form validation with clear error messages. Deduct 3 points for cluttered authentication forms, 5 points for confusing error messages, and 5 points for inconsistent visual feedback during authentication flows. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the authentication user experience smooth and seamless?",
+      "description": "Judge whether the authentication flow conforms to user expectations: 1) Login process completable within 3 steps maximum 2) Authentication state transitions are visually clear without jarring redirects 3) Appropriate loading indicators during authentication operations. Deduct 5 points for authentication flows requiring excessive steps, 3 points for abrupt page transitions during login/logout, and 5 points for missing feedback during authentication processes. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Communication",
+  "difficulty": "medium"
+}

package/library/web_applications-communication/intelligent-email-template-generator-with-ab-testing.json

@@ -0,0 +1,68 @@
+{
+  "index": 686,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate, professional responses. Make sure the code you generate is executable and displayable. Build an intelligent email template generator that supports variable interpolation (such as {name}), conditional logic blocks, and multi-topic A/B testing. Requirements include providing a visual editing interface, sending record tracking, and open rate statistics with chart displays.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the email template generator core functionality implemented?",
+      "description": "Evaluate whether the code correctly implements variable interpolation (e.g., {name}, {company}), conditional logic blocks (if-else statements for content customization), and template storage/retrieval. Score 0 if the core functionality is missing, 5 if only basic interpolation is implemented, and 10 if all required template features (interpolation, conditionals, and multi-topic A/B testing logic) are fully functional.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the visual editing interface well-designed and functional?",
+      "description": "Check if the interface provides intuitive WYSIWYG editing capabilities, with clear separation between editing mode and preview mode. Verify that users can easily insert variables, add conditional blocks, and set up A/B testing variants. Deduct 5 points if drag-and-drop functionality is missing, 3 points if real-time preview isn't available, and 2 points if the UI doesn't provide clear visual indicators for dynamic elements (variables, conditionals). The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the A/B testing mechanism properly implemented?",
+      "description": "Evaluate whether the code includes a complete A/B testing system that can randomly select content variants for different recipients, track which variant was sent to whom, and analyze performance differences. Check for proper audience segmentation capabilities and statistical significance calculation. Deduct 5 points if variant distribution isn't randomized properly, and 5 points if there's no mechanism to declare a winning variant. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Are the email tracking and analytics features functioning?",
+      "description": "Assess whether the system can track email opens, link clicks, and display this data in charts/graphs with proper visualization. Verify that tracking pixels/codes are correctly implemented, and data collection respects privacy regulations. Check if the analytics dashboard provides meaningful metrics (open rates, click rates, conversion rates). Deduct 5 points if tracking implementation has security flaws, and 5 points if visualization lacks filtering or comparison capabilities. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common edge cases (such as missing variables, malformed templates, large data sets, concurrent users) and provides friendly error handling with appropriate feedback. Code with strong robustness should validate all inputs, handle template parsing exceptions gracefully, and implement appropriate timeouts. Give 10 points for comprehensive error handling, 5 points for partial implementation, and 0 points if no exception handling exists.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. AI-assisted content suggestions 2. Sentiment analysis of email content 3. Automated send-time optimization based on recipient behavior 4. Responsive preview across multiple device types). 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 template engines coexisting) 2. Function modules unrelated to email generation (e.g., a built-in social media manager) 3. Fancy effects that affect performance (e.g., unnecessary animations in the dashboard). 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 template engine/UI/analytics layers), unit test coverage, and build process automation. Check for proper dependency management and secure handling of email content (sanitization, encoding). Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the build process is not automated. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching (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). Check if the template editor provides clear visual hierarchy and if the analytics dashboard presents data clearly without visual clutter. 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) Template editor updates preview within 500ms 2) Transition animations controlled between 300-500ms 3) Clear visual feedback when saving templates or running A/B tests. Assess if the interface provides appropriate loading states when fetching analytics data or sending test emails. Deduct 5 points for each operation without feedback, 3 points for visual stutter during template editing, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Communication",
+  "difficulty": "hard"
+}

package/library/web_applications-communication/java-wechat-chat-window-ui.json

@@ -0,0 +1,68 @@
+{
+  "index": 427,
+  "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. Create a window in Java 1.8 that resembles a WeChat chat window. It should look nice and match the recent WeChat interface appearance.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the core WeChat chat window UI layout properly implemented?",
+      "description": "Evaluate whether the code implements a proper layout resembling the WeChat chat window, including the main conversation area, input area, message bubbles, and navigation elements. Score 0 if the basic layout is missing, 5 if only a basic structure is implemented, and 10 if the layout closely resembles the authentic WeChat interface with proper proportions and organization.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are the WeChat-specific UI components accurately represented?",
+      "description": "Check whether the code includes accurate representations of WeChat's distinctive UI elements such as green/white message bubbles with proper rounded corners, profile pictures, timestamps, message status indicators, and emoji support. Deduct 2 points for each major WeChat UI component missing, and 1 point for each inaccurate styling. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the navigation and control system properly implemented?",
+      "description": "Review whether the code implements WeChat's navigation system including back button, menu options, and navigation between different sections (chats, contacts, discover, me). Evaluate if proper listeners and event handling are implemented for these controls. Score 0 if navigation is missing, 5 if basic navigation exists but lacks some elements, and 10 if the complete navigation system is fully implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Are the chat functionality demonstrations implemented?",
+      "description": "Assess whether the code demonstrates basic chat functionalities like sending messages, displaying message history, showing typing indicators, and message timestamps. Deduct 3 points if sending/receiving messages isn't functional, 2 points if message history isn't persistent within the session, and 2 points if timestamps or read receipts are 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 empty messages, window resizing, very long messages, and special characters) and provide friendly error handling. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Message animation effects 2. Dark mode support 3. Custom themes 4. Voice message simulation). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple ways to handle messages) 2. Function modules unrelated to WeChat chat (e.g., unnecessary games or utilities) 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), proper Java conventions, design patterns, and code organization. Deduct 5 points if global state pollution is found or MVC/MVP patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if proper OOP principles aren't followed. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the design follows WeChat's design language: 1) Correct color scheme (main WeChat green #7BB32E, background gray #EBEBEB, etc.) 2) Proper layout spacing and alignment 3) Professional font system (matching WeChat's typography). Deduct 3 points for each visual inconsistency with WeChat's design, 5 points for incorrect color palette, and 5 points for improper spacing or alignment. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the UI interactions match WeChat's behavior: 1) Immediate message sending feedback 2) Smooth message bubble animations 3) Responsive controls with appropriate hover/click effects. Deduct 3 points for each laggy animation, 3 points for missing interaction feedback, and 5 points for jerky scrolling or unresponsive UI elements. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Communication",
+  "difficulty": "medium"
+}