@getollie/cli 0.0.1

package/library/web_applications-communication/vue-login-navigation-system.json

@@ -0,0 +1,68 @@
+{
+  "index": 858,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to provide executable code where possible. Create a login and navigation system in Vue.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the Vue login component properly implemented?",
+      "description": "Review whether the login component includes proper form validation, password masking, error handling for authentication failures, and controlled inputs. Check for v-model usage, form submission prevention, and validation feedback. Score 0 if core login functionality is missing, 5 if basic functionality exists without validation, and 10 if comprehensive validation and security features are implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the authentication system securely designed?",
+      "description": "Evaluate the authentication implementation including token storage (preferably using HttpOnly cookies or secure localStorage), CSRF protection, proper handling of authentication errors, and timeout/refresh mechanisms. Deduct 5 points if tokens are stored insecurely, 3 points if no token expiration handling exists, and 3 points if authentication state is not properly maintained across page reloads. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the navigation system responsive and properly implemented?",
+      "description": "Check if the navigation component adapts to different screen sizes (mobile, tablet, desktop), handles active route highlighting, and includes responsive collapse/expand functionality. Evaluate Vue Router integration, navigation guards for protected routes, and route transitions. Deduct 3 points for each missing responsiveness feature, 5 points if route guards aren't implemented, and 3 points if navigation state isn't preserved. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the Vuex state management properly utilized?",
+      "description": "Assess whether Vuex (or Pinia) is correctly integrated for state management, with proper separation of concerns (mutations, actions, getters), namespaced modules for auth and navigation, and consistent state access patterns. Deduct 5 points for direct state mutations, 3 points for inadequate error handling in actions, and 5 points if authentication state is not properly maintained in the store. 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 during login, invalid inputs, token expiration, unauthorized access attempts, 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. Biometric authentication options 2. Multi-factor authentication 3. Customizable navigation themes/layouts 4. Animated route transitions). 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 authentication methods with overlapping code) 2. Function modules unrelated to login/navigation (e.g., a built-in calculator) 3. Fancy effects that affect performance (e.g., excessive animations or transitions). 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 components, services, and store modules), component reusability, proper use of Vue best practices, and testing setup. Deduct 5 points if global state pollution is found; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if proper Vue lifecycle hooks aren't used appropriately. 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 labeling, visible focus states). Deduct 3 points for each accessibility issue, 5 points for inconsistent styling across components, and 5 points for poor form layout or feedback. 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) Login button feedback delay ≤ 100ms 2) Navigation transition animation duration controlled between 300-500ms 3) Loading indicators for asynchronous operations. Deduct 5 points for each operation without feedback, 3 points for jarring navigation transitions, and 5 points for missing loading states during authentication. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Communication",
+  "difficulty": "medium"
+}

package/library/web_applications-communication/vue-nodejs-express-mysql-xiaohongshu-webpage.json

@@ -0,0 +1,68 @@
+{
+  "index": 1403,
+  "question": "You are a code expert, please use your professional knowledge to generate accurate, professional responses. Ensure that the code you generate is executable. Create a webpage using Vue 3 + Node.js with Express.js framework + MySQL, styled to mimic Xiaohongshu (Little Red Book). Use a user database called 'user'. Please tell me all the necessary plugins that must be installed, and the commands to automatically generate the file directory structure.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the Vue 3 front-end structure properly implemented?",
+      "description": "Review whether the code correctly implements Vue 3's Composition API, component structure, and reactive state management. Check for proper use of setup(), ref(), reactive(), and other Vue 3 specific features. Score 0 if Vue 3 is not implemented correctly, 5 if basic Vue 3 structure exists but lacks optimization, and 10 if it fully utilizes Vue 3's capabilities including proper component hierarchy, lifecycle hooks, and performance optimizations.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the Express.js backend properly configured with necessary middleware?",
+      "description": "Evaluate whether the Express.js server is properly set up with essential middleware like cors, body-parser, cookie-parser, helmet for security, morgan for logging, and proper route organization. Check if the server handles errors appropriately and implements proper API versioning. Deduct 3 points if security middleware is missing, 3 points if request validation is absent, and 2 points if route organization is chaotic. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the MySQL database connection and schema design appropriate?",
+      "description": "Check if the MySQL connection is properly established with connection pooling and error handling. Evaluate the 'user' table schema design for appropriate fields, data types, indexes, and constraints. Look for proper SQL query construction with parameterized queries to prevent SQL injection. Deduct 5 points if no connection pooling is implemented, 3 points if queries are vulnerable to SQL injection, and 2 points if the schema design is inefficient. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Does the application successfully mimic Xiaohongshu's UI and features?",
+      "description": "Assess how closely the application resembles Xiaohongshu's design and functionality: waterfall layout for content display, discovery feed, user profiles, post creation with image upload, like/comment/collect features, and the signature red theme. Deduct 3 points for each missing core feature and 2 points if the visual styling significantly deviates from Xiaohongshu. 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 database connection failures, network errors, invalid user inputs, etc.) and provide friendly error prompts or recovery mechanisms. Check for form validation, API error handling, and graceful degradation. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. AI-powered content recommendations 2. Real-time notifications 3. Interactive image filters mimicking Xiaohongshu). 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 authentication systems coexisting) 2. Function modules unrelated to a social media platform like Xiaohongshu 3. Fancy effects that affect performance (e.g., excessive animations that slow 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 API/business logic/view layers), unit test coverage, and build process automation. Check for proper use of .env files for configuration, proper error logging, and documentation. 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 (with Xiaohongshu's signature red accents) 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. Check for infinite scroll implementation, lazy loading of images, and smooth transitions between pages. Deduct 5 points for each operation without feedback, 3 points for visual after-images during fast scrolling, 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/vue-three-section-social-website.json

@@ -0,0 +1,68 @@
+{
+  "index": 1693,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to make the generated code executable for demonstration when possible. I am designing a website using Vue, divided into three parts: left, middle, and right. The left section contains the logo and navigation bar, followed by navigation options and functional options including Sports, Food, Travel, Culture, Technology, Leisure, as well as Message Notifications, Settings Center, and Logout. The middle section has a search box and profile picture, below which is an area for editing and publishing posts. Before editing a post, users need to select one of the same 6 categories that appear in the left navigation bar. Below this is where users' posts of various types are displayed. The right section of the website contains a friends list and an area for sending messages and chatting.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the Vue component structure properly organized?",
+      "description": "Evaluate the project structure and component hierarchy. Check if components are properly segregated (e.g., NavigationBar, PostEditor, FriendsList), follow single responsibility principle, and use proper Vue best practices like props/emits for communication. Analyze if the layout is implemented with appropriate Vue directives, CSS Grid/Flexbox for the three-column layout. Deduct 5 points for monolithic components, 3 points for prop drilling beyond 2 levels, and 5 points if reactive data management is poorly implemented. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the navigation system in the left section fully implemented?",
+      "description": "Review the left navigation implementation including logo, category navigation (Sports, Food, Travel, Culture, Technology, Leisure), and utility functions (Message Notifications, Settings Center, Logout). Check for active state styling, proper routing configuration, and visual hierarchy. Award 10 points for complete implementation with proper Vue Router integration, responsive design, and visual feedback. Deduct 3 points if navigation state persistence is missing, 3 points for accessibility issues, and 5 points if navigation items aren't properly linked to their corresponding views.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the post editing and publishing functionality in the middle section complete?",
+      "description": "Assess the implementation of the post creation workflow: category selection (matching the 6 navigation categories), content editing interface, and publishing mechanism. Check for form validation, error handling, and state management during the post creation process. Give 10 points for a fully functional editor with appropriate input fields, category selection UI, real-time preview, and submission handling. Deduct 5 points if category validation is missing, 3 points for lack of draft saving, and 5 points if publishing doesn't update the feed view.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Are the messaging and chat functionalities in the right section properly implemented?",
+      "description": "Evaluate the friends list display and chat functionality. Check if the friends list shows online status, if messages can be sent and received, and if there's message history. Verify that real-time communication is implemented (or simulated). Award 10 points for complete implementation with message threading, typing indicators, and message status. Deduct 5 points if there's no message persistence mechanism, 3 points if friend status updates are missing, and 5 points if the chat UI doesn't scroll or handle long conversations properly.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as API failures, invalid user inputs, authentication timeouts) and provide friendly error prompts or recovery mechanisms. Check for proper form validation, defensive programming, and error boundaries. Award 10 points if the code effectively handles edge cases with meaningful user feedback. Give 5 points for average robustness (basic error handling), and 0 points if exceptions are unhandled or cause the application to crash.",
+      "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. Dark/light mode toggle 2. Personalized content recommendations 3. Interactive post reactions beyond simple likes 4. Keyboard shortcuts for power users). Award 3 points for each practical innovative feature implemented that improves usability or engagement (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 notification systems) 2. Function modules unrelated to the social/content platform (e.g., a built-in calculator) 3. Fancy effects that affect performance (e.g., excessive animations on scroll). 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 the Vue component design (Options API vs. Composition API usage), state management approach (Vuex/Pinia), code splitting, and build optimization. Check for proper separation of concerns, reusable components, and maintainability practices. Deduct 5 points if global state is overused, 5 points if components exceed 300 lines, and 5 points if there's no consideration for lazy loading large views/components. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the design follows modern web standards: 1) Consistent color scheme across the three sections 2) Appropriate whitespace and component padding 3) Typography hierarchy for different content types 4) Responsive design considerations. Deduct 3 points for inconsistent spacing, 5 points for poor visual hierarchy, and 5 points for inaccessible color contrast ratios. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the interactions feel natural and responsive: 1) Smooth transitions between views 2) Immediate feedback on user actions 3) Appropriate loading states during data fetching 4) Intuitive UI for post creation and messaging. Deduct 5 points for unresponsive UI elements, 3 points for jarring transitions, and 5 points for confusing interaction patterns. Check if Vue transitions are properly used for state changes. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Communication",
+  "difficulty": "medium"
+}

package/library/web_applications-communication/vue-wechat-chat-effect-implementation.json

@@ -0,0 +1,68 @@
+{
+  "index": 1128,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate, professional responses. Be sure to ensure that the code you generate is executable and can be demonstrated. Implement a WeChat chat effect using Vue.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the core WeChat chat interface structure fully implemented?",
+      "description": "Review whether the Vue components accurately reproduce WeChat's chat interface layout, including message list, input area, header navigation, and contact list. Check if the message bubble design matches WeChat's visual style (left/right alignment, different colors for sent/received messages, timestamps, read status indicators). Score 0 if basic chat interface is missing, 5 if only simple message display is implemented, and 10 if all WeChat-style interface elements are fully included.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are the Vue-based message interaction features properly implemented?",
+      "description": "Evaluate whether Vue's reactive data binding correctly handles real-time message updates, message sending/receiving animations, scroll-to-bottom behavior, and message status changes. Check if Vue lifecycle hooks are properly used for component mounting and data initialization. Deduct 5 points if message list doesn't auto-scroll, and 3 points if Vue reactivity issues cause UI lag. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the message data management and persistence mechanism designed correctly?",
+      "description": "Check whether Vuex or Vue 3 Composition API is used for state management, and if message history is properly stored (localStorage/sessionStorage). Evaluate if the data structure supports different message types (text, images, emojis, voice messages). Deduct 5 points if no state management pattern is used, and 3 points if message persistence is not implemented. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Are WeChat-specific interactive features implemented comprehensively?",
+      "description": "Verify if the code includes WeChat-characteristic features such as emoji picker, voice message recording simulation, image preview, message forwarding, and long-press context menus. Check if typing indicators, message read receipts, and contact online status are implemented. Deduct 5 points if emoji support is missing, and 3 points if no multimedia message handling exists. Give 10 points if fully implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as empty message input, network simulation errors, large message volumes, component unmounting, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should effectively handle edge cases like message sending failures and component lifecycle issues, giving 10 points. If robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprise features that enhance the WeChat-like experience (e.g., 1. Message search functionality 2. Chat theme switching 3. Message encryption simulation 4. Group chat avatars 5. Voice-to-text conversion mock). 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 methods coexisting) 2. Function modules unrelated to WeChat chat (e.g., built-in games or shopping features) 3. Overly complex animations that affect performance (e.g., excessive particle effects on message sending). Deduct 3 points for each redundancy found, and directly deduct 10 points if core chat functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review Vue component modularization (separating chat components, message components, input components), proper use of Vue best practices (props validation, event handling, computed properties), and code organization. Deduct 5 points if global state pollution is found or Vue patterns are misused; deduct 5 points if component coupling is too high; deduct 5 points if no proper component hierarchy exists. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface design accurately replicate WeChat's visual standards?",
+      "description": "Evaluate whether the design faithfully reproduces WeChat's visual identity: 1) Correct color scheme (WeChat green #07C160, proper gray tones) 2) Accurate spacing and typography matching WeChat's design 3) Proper message bubble styling and avatar placement 4) Consistent iconography and visual hierarchy. Deduct 3 points for each visual inconsistency with WeChat's design, 5 points for incorrect color usage, and 5 points for poor layout resemblance. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Are the chat interactions smooth and WeChat-authentic?",
+      "description": "Judge whether the interaction patterns match WeChat's behavior: 1) Message sending animation and feedback ≤ 100ms 2) Smooth scrolling and message transitions 3) Proper keyboard handling and input focus 4) Authentic touch interactions and gesture responses. Deduct 5 points for each sluggish interaction, 3 points for unnatural animation timing, and 5 points for poor input responsiveness. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Communication",
+  "difficulty": "medium"
+}

package/library/web_applications-communication/vue2-elementui-flask-file-download-interface.json

@@ -0,0 +1,68 @@
+{
+  "index": 1590,
+  "question": "You are a code expert. Please utilize your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable for demonstration purposes. Create a file download interface using Vue2 with ElementUI and Flask.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the Vue2 front-end file download interface fully implemented?",
+      "description": "Review whether the code includes proper Vue2 components with ElementUI integration for file selection, download progress tracking, and file handling. Check for proper event handling, data binding, and computed properties. Score 0 if the core Vue2 structure is missing, 5 if basic components are implemented but missing key features, and 10 if the implementation includes file list display, filtering, and robust download functionality.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the Flask backend API properly implemented?",
+      "description": "Evaluate whether the Flask API includes routes for file listing, downloading, and proper HTTP responses with appropriate status codes and headers (especially Content-Disposition, Content-Type). Check for proper file path handling, security measures against path traversal attacks, and streaming for large files. Deduct 5 points if security measures are missing, and 3 points if streaming for large files is not implemented. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the communication between Vue2 and Flask properly implemented?",
+      "description": "Check whether the code uses Axios or Fetch API correctly with proper error handling, request/response interceptors, and download progress tracking. Assess whether appropriate HTTP methods are used (GET for listing, GET with proper parameters or POST for downloading). Deduct 5 points if error handling is inadequate, 3 points if download progress tracking is missing. Give 10 points for complete implementation with proper CORS handling.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the file download functionality feature-complete?",
+      "description": "Verify whether the implementation includes essential file download features: file size display, mime-type identification, download progress indication, pause/resume capability (if applicable), and batch download functionality. Check for proper handling of various file types. Deduct 5 points if key features are missing, 3 points if the user experience during download is poor. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid file paths, file access permissions, network interruption, large file downloads, 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. Preview for common file types 2. MD5/SHA verification for downloads 3. Download speed limiting options 4. Drag-and-drop interface for file organization). 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 download methods coexisting) 2. Function modules unrelated to file downloading (e.g., a built-in media player) 3. Fancy effects that affect performance (e.g., excessive animations during downloads). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating UI components, API services, and utility functions), unit test coverage, and build process automation. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the build process is not automated. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching (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 for download buttons and progress indicators. Deduct 5 points for each operation without feedback, 3 points for visual after-images during fast scrolling of file lists, and 5 points for hard-to-find download buttons. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Communication",
+  "difficulty": "easy"
+}

package/library/web_applications-communication/vue2-uniapp-membership-card.json

@@ -0,0 +1,68 @@
+{
+  "index": 243,
+  "question": "You are a code expert. Please utilize your professional knowledge to generate accurate and professional responses. Be sure to ensure that the code you generate is executable for demonstration. Use Vue2 and uniApp to create a membership card.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the membership card core functionality fully implemented?",
+      "description": "Review whether the Vue2 components properly implement the membership card with appropriate data structures (user information, card status, points/balance) and necessary interactions (view details, use card). Score 0 if the core card functionality is missing, 5 if basic display is implemented, and 10 if full functionality including conditional rendering based on membership levels is implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the uniApp cross-platform adaptation correctly implemented?",
+      "description": "Evaluate whether the code properly uses uniApp's conditional compilation (@ifdef), responsive layouts, and platform-specific API calls. Check if styles adapt to different screen sizes and device capabilities. Deduct 3 points if only one platform works well, 5 points if platform-specific features aren't utilized appropriately. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the membership card state management properly designed?",
+      "description": "Examine whether the solution properly manages membership data (using Vuex or similar state management), implements appropriate caching strategies for offline usage, and handles state transitions (card activation, expiration, level upgrades). Deduct 5 points if there's no persistent storage solution, 3 points if state updates aren't reactive. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Are authentication and security measures appropriately implemented?",
+      "description": "Check if the membership card includes necessary security features such as token-based authentication, secure storage of sensitive information, and protection against unauthorized access. Assess if the solution includes verification methods (QR codes, barcodes) for in-store usage. Deduct 5 points if authentication is missing, 3 points if there's no expiration/refresh mechanism. 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, invalid card data, expired memberships, 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. Dynamic card visual effects based on usage 2. Location-based promotions integration 3. Interactive point redemption animations). 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 card display components with overlapping functionality) 2. Function modules unrelated to membership cards (e.g., a built-in game unrelated to the loyalty program) 3. Fancy effects that affect performance (e.g., excessive animations that slow rendering). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating UI components/API services/state management), component reusability, and build configuration for uniApp. Deduct 5 points if global properties are overused or Vue best practices are ignored; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if conditional compilation isn't properly handled. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the membership card design follows modern design principles: 1) Harmonious color matching suitable for brand identity (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) Card flip/reveal animations feel natural with proper easing 2) Transition animation duration controlled between 300-500ms 3) Clear visual feedback when scanning or using the card. Deduct 5 points for each operation without feedback, 3 points for jerky animations during transitions, 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/vue3-announcement-viewer-count-real-time-updates.json

@@ -0,0 +1,68 @@
+{
+  "index": 936,
+  "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 is executable for display. Vue3 announcement viewer count with real-time updates.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the Vue3 component structure correctly implemented?",
+      "description": "Evaluate if the code follows Vue3 best practices with Composition API usage (setup(), ref(), reactive()), proper component organization (single file components), and correct lifecycle hooks (onMounted(), onUnmounted()). Deduct 5 points if Options API is used instead of Composition API; deduct 3 points if lifecycle hooks are improperly utilized; deduct 5 points if reactive state management is not implemented. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is real-time functionality properly implemented?",
+      "description": "Check if the code includes an effective real-time update mechanism (WebSockets, Server-Sent Events, or polling with appropriate intervals). Verify if connection management handles reconnection attempts, error states, and displays loading/error indicators. Deduct 5 points if only manual refresh is implemented, 3 points if the update mechanism has no error handling, and 5 points if there's no visual indicator during data loading. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the viewer count data storage and manipulation well-designed?",
+      "description": "Examine if the data structure for storing viewer counts is appropriate (time-series format for historical tracking, optimized for frequent updates). Check if state mutations follow Vue3 reactivity principles and if the code handles edge cases (null values, server errors, data type conversions). Deduct 5 points for improper reactivity implementation, 3 points for missing data validation, and 3 points for inefficient data structure choices. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is data visualization of viewer count implemented effectively?",
+      "description": "Evaluate the implementation of data visualization (charts/graphs using libraries like Chart.js, D3.js, or Vue-specific visualization libraries). Check if the visualization is responsive, handles different data ranges gracefully, includes proper axes labels, and shows trends clearly. Deduct 5 points if visualization is static (non-reactive to data changes), 3 points if it lacks visual clarity, and 5 points if it's not responsive to different screen sizes. 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, API failures, data inconsistencies) and provide friendly error prompts or recovery mechanisms. Code should gracefully handle edge cases like empty data sets, unexpected data formats, and connection timeouts. Give 10 points if robust error handling is implemented throughout, 5 points if only basic error handling exists, and 0 points if exceptions are unhandled.",
+      "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. Viewer engagement metrics besides raw count 2. Notification system for significant viewer changes 3. Predictive analytics for viewer trends). 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 methods updating the same state) 2. Function modules unrelated to viewer count tracking 3. Fancy effects that affect performance (e.g., excessive animations that impact data refresh rates). 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 (separation of data fetching, state management, and UI rendering), component reusability, and proper use of Vue3 features. Deduct 5 points if global state is used where component state would suffice; deduct 5 points if the codebase shows significant repetition; deduct 5 points if Vue3 reactivity system is misused. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the design follows modern UI principles: 1) Harmonious color scheme appropriate for data visualization (distinguishable data series, proper contrast) 2) Clean layout with appropriate spacing between elements 3) Typography that enhances readability of metrics and labels (proper sizing hierarchy, readable fonts). Deduct 3 points for cluttered interfaces, 5 points for poor color choices affecting data readability, and 5 points for inconsistent styling. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the real-time updates and transitions follow good UX principles: 1) Smooth transitions when counts update (no jarring changes) 2) Clear visual indication of new data arrival 3) Appropriate animation speed for count changes (not too fast to read, not too slow to feel outdated). Deduct 5 points for abrupt visual changes during updates, 3 points for missing loading states, and 5 points for animations that distract from data comprehension. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Communication",
+  "difficulty": "easy"
+}

package/library/web_applications-communication/vue3-element-plus-wechat-chat-interface.json

@@ -0,0 +1,68 @@
+{
+  "index": 1200,
+  "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. I need to design a WeChat-like chat interface. Please help me write a page component using element-plus and Vue 3.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the basic UI structure of a WeChat-like chat interface implemented?",
+      "description": "Review whether the code properly implements the essential UI components of a chat interface using Element Plus and Vue 3: contact list sidebar, chat area with message bubbles, input area with send button, and header with user information. Score 0 if basic structure is missing, 5 if only partial components are implemented, and 10 if all core components with proper layout are fully implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the message display functionality properly implemented?",
+      "description": "Check if the code correctly handles different message types (text, image, voice, etc.), renders them appropriately with sender/recipient distinction, displays timestamps, and supports message status indicators (sent, delivered, read). Deduct 3 points if message styling lacks sender distinction, 4 points if timestamps are missing, and 5 points if different message types aren't properly supported. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the input functionality with sending mechanism implemented?",
+      "description": "Verify that the chat input area includes text input with proper validation, send button functionality, emoji picker integration, and file attachment options. Check for event handling (Enter key to send, Shift+Enter for new line). Deduct 3 points for missing emoji support, 4 points for lack of input validation, and 5 points if file attachment isn't implemented. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the contact management and conversation switching implemented?",
+      "description": "Evaluate if the code properly implements contact list display, conversation switching logic, unread message counters, contact search functionality, and persistence of chat history when switching conversations. Deduct 3 points if search functionality is missing, 4 points if unread counters aren't implemented, and 5 points if chat history doesn't persist between conversation switches. 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, failed message delivery, 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. Message reactions 2. Voice messages with waveform visualization 3. Read receipts with timestamps 4. Typing indicators). 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 methods coexisting) 2. Function modules unrelated to chat (e.g., a built-in game) 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 components, state management, and service layers), proper use of Vue 3 Composition API, reusable components, and proper integration with Element Plus. 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 Vue 3 features aren't properly leveraged. 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 WeChat-like design principles: 1) Consistent color scheme with WeChat's green accent 2) Proper layout spacing (chat bubbles aligned appropriately, proper padding) 3) Professional typography system (readable font sizes, appropriate line heights). Deduct 3 points for each misaligned visual element, 5 points for inconsistent styling with WeChat, and 5 points for poor readability. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the dynamic effects conform to chat application expectations: 1) Message sending feedback delay ≤ 100ms 2) Smooth scrolling in message history 3) Proper transitions when switching conversations. Deduct 5 points for each operation without feedback, 3 points for jerky scrolling, and 5 points for abrupt conversation transitions. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Web Applications-Communication",
+  "difficulty": "easy"
+}